diff --git a/.tx/config b/.tx/config index 44cf99d51..ba5a28481 100644 --- a/.tx/config +++ b/.tx/config @@ -57,11 +57,6 @@ file_filter = locale//LC_MESSAGES/inventory.po source_file = locale/sources/inventory.pot source_lang = en -[odoo-10-doc.legal] -file_filter = locale//LC_MESSAGES/legal.po -source_file = locale/sources/legal.pot -source_lang = en - [odoo-10-doc.manufacturing] file_filter = locale//LC_MESSAGES/manufacturing.po source_file = locale/sources/manufacturing.pot diff --git a/accounting/others/taxes.rst b/accounting/others/taxes.rst index 95e2ca40d..684803d91 100644 --- a/accounting/others/taxes.rst +++ b/accounting/others/taxes.rst @@ -12,3 +12,4 @@ Taxes taxes/tax_included taxes/retention taxes/B2B_B2C + taxes/cash_basis_taxes \ No newline at end of file diff --git a/accounting/others/taxes/cash_basis_taxes.rst b/accounting/others/taxes/cash_basis_taxes.rst new file mode 100644 index 000000000..a6a7e2b30 --- /dev/null +++ b/accounting/others/taxes/cash_basis_taxes.rst @@ -0,0 +1,87 @@ +============================== +How to manage cash basis taxes +============================== + +The cash basis taxes are due when the payment has been done and not at +the validation of the invoice (as it is the case with standard taxes). +Reporting your income and expenses to the administration based on the +cash basis method is legal in some countries and under some conditions. + +Example : You sell a product in the 1st quarter of your fiscal year and +receive the payment the 2nd quarter of your fiscal year. Based on the +cash basis method, the tax you have to pay to the administration is due +for the 2nd quarter. + +How to configure cash basis taxes ? +------------------------------------ + +You first have to activate the setting in +:menuselection:`Accounting --> Configuration --> Settings --> Allow Tax Cash Basis`. +You will be asked to define the Tax Cash Basis Journal. + +.. image:: media/cash_basis_taxes01.png + :width: 5.04688in + :height: 0.79688in + :align: center + +Once this is done, you can configure your taxes in +:menuselection:`Accounting --> Configuration --> Taxes`. +You can open a tax and in the *Advanced Options* +tab you will see the checkbox *Use Cash Basis*. You will then have to +define the *Tax Received Account*. + +.. image:: media/cash_basis_taxes02.png + :width: 6.50000in + :height: 1.81944in + :align: center + +What is the impact of cash basis taxes in my accounting ? +---------------------------------------------------------- + +Let’s take an example. You make a sale of $100 with a 15% cash basis +tax. When you validate the customer invoice, the following entry is +created in your accounting: + ++-----------------------------+-----------------------+ +| Customer Invoices Journal | | ++=============================+=======================+ +| **Debit** | **Credit** | ++-----------------------------+-----------------------+ +| Receivables $115 | | ++-----------------------------+-----------------------+ +| | Tax Account $15 | ++-----------------------------+-----------------------+ +| | Income Account $100 | ++-----------------------------+-----------------------+ + +A few days later, you receive the payment: + ++----------------+--------------------+ +| Bank Journal | | ++================+====================+ +| **Debit** | **Credit** | ++----------------+--------------------+ +| Bank $115 | | ++----------------+--------------------+ +| | Receivables $115 | ++----------------+--------------------+ + +When you reconcile the invoice and the payment, this entry is generated: + ++--------------------------+----------------------------+ +| Tax Cash Basis Journal | ++==========================+============================+ +| **Debit** | **Credit** | ++--------------------------+----------------------------+ +| Tax Account $15 | | ++--------------------------+----------------------------+ +| | Tax Received Account $15 | ++--------------------------+----------------------------+ +| Income Account $100 | | ++--------------------------+----------------------------+ +| | Income Account $100 | ++--------------------------+----------------------------+ + +.. tip:: + The two journal items created in the Income Account are neutral but + they are needed to insure correct tax reports in Odoo. diff --git a/accounting/others/taxes/media/cash_basis_taxes01.png b/accounting/others/taxes/media/cash_basis_taxes01.png new file mode 100644 index 000000000..81a143538 Binary files /dev/null and b/accounting/others/taxes/media/cash_basis_taxes01.png differ diff --git a/accounting/others/taxes/media/cash_basis_taxes02.png b/accounting/others/taxes/media/cash_basis_taxes02.png new file mode 100644 index 000000000..9effae496 Binary files /dev/null and b/accounting/others/taxes/media/cash_basis_taxes02.png differ diff --git a/accounting/receivables/customer_payments/credit_cards.rst b/accounting/receivables/customer_payments/credit_cards.rst index 8831b2459..108e5de1b 100644 --- a/accounting/receivables/customer_payments/credit_cards.rst +++ b/accounting/receivables/customer_payments/credit_cards.rst @@ -47,7 +47,7 @@ Create a Journal called 'Credit card payments' with the following data: - **Default debit account**: Credit cards - **Default credit account**: Credit cards -Once it's done, don't forget to set the "Credit cards" account as "Allow +The account type should be "Credit Card". Once it's done, don't forget to set the "Credit cards" account as "Allow Reconciliation". .. image:: ./media/credit01.png @@ -164,6 +164,6 @@ account). .. seealso:: * :doc:`recording` - * :doc:`paypal` + * :doc:`../../bank/feeds/paypal` * :doc:`check` * :doc:`followup` diff --git a/accounting/receivables/customer_payments/recording.rst b/accounting/receivables/customer_payments/recording.rst index 15b30fd8b..9baf6d12b 100644 --- a/accounting/receivables/customer_payments/recording.rst +++ b/accounting/receivables/customer_payments/recording.rst @@ -125,6 +125,6 @@ payments. .. seealso:: * :doc:`credit_cards` - * :doc:`paypal` + * :doc:`../../bank/feeds/paypal` * :doc:`check` * :doc:`followup` diff --git a/crm/calendar/google_calendar_credentials.rst b/crm/calendar/google_calendar_credentials.rst index ec7202307..c5b486320 100644 --- a/crm/calendar/google_calendar_credentials.rst +++ b/crm/calendar/google_calendar_credentials.rst @@ -1,51 +1,84 @@ -===================================================== -How to synchronize your calendar with Google Calendar -===================================================== +========================================================== +How to synchronize your Odoo Calendar with Google Calendar +========================================================== -- Connect on your google account and go to `https://console.developers.google.com/ `_. +Odoo is perfectly integrated with Google Calendar so that you +can see & manage your meetings from both platforms +(updates go through both directions). -- Click on **Create a project...** and enter a project name and change your id if you want. - Don't forget to accept the Terms of Services +Setup in Google +=============== +- Go to `Google APIs platform `__ + to generate Google Calendar API credentials. Log in with your Google account. + +- Choose *Calendar API*. .. image:: media/google_calendar_credentials01.png :align: center -- In the menu on left side, select the sub menu APIs (from menu APIs and auth) and click on 'Calendar API'. - Activate the Calendar API by clicking on the blue button 'Enable API'. - When it's done, the Calendar API overview will be available +- Create a new project and give it a name (e.g. Odoo). This project is needed + to store your API credentials. .. image:: media/google_calendar_credentials02.png :align: center +- Enable the API. + .. image:: media/google_calendar_credentials03.png :align: center +- Create credentials to use in Odoo. + .. image:: media/google_calendar_credentials04.png :align: center -- In the menu on left side, select the sub menu 'Credentials' (from menu APIs and auth) and click on - button 'Create new Client ID' +- Select *Web browser (Javascript)* + as calling source and *User data* as kind of data. .. image:: media/google_calendar_credentials05.png :align: center -- Check that the Application type is set on 'Web Application', then click on 'Configure consent screen'. - Specify an email address and a product name, then save. +- Then you can create a Client ID. + Enter the name of the application (e.g. Odoo) and the allowed pages on + which you will be redirected. The *Authorized JavaScript origin* is your + Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance + URL followed by '/google_account/authentication'. .. image:: media/google_calendar_credentials06.png :align: center +- Go through the Consent Screen step by entering a product name + (e.g. Odoo). Feel free to check the customizations options + but this is not mandatory. The Consent Screen will only show up when you + enter the Client ID in Odoo for the first time. + +- Finally you are provided with your **Client ID**. Go to *Credentials* to + get the **Client secret** as well. You will need both of them in Odoo. + .. image:: media/google_calendar_credentials07.png :align: center -You should now configure the allowed pages on which you will be redirected. To do it, you need to complete the field "Authorized redirect URI" and set as value (your own domain followed by '/google_account/authentication'): -==> http://mydomain.odoo.com/google_account/authentication -You can now click on 'Create Client ID' +Setup in Odoo +============= + +- Install **Google Calendar** app. .. image:: media/google_calendar_credentials08.png :align: center -- Once done, you will have the both informations (Client ID and Client Secret) that you need to insert in the 2 fields below! +- Go to :menuselection:`Settings --> General Settings` and enter your + credentials in Google Calendar option. .. image:: media/google_calendar_credentials09.png :align: center + +- The setup is now ready. Open your Odoo Calendar and sync with Google. + The first time you do it you are redirected to Google to authorize + the connection. Once back in Odoo, click the sync button again. + You can click it whenever you want to synchronize your calendar. + +.. image:: media/google_calendar_credentials10.png + :align: center + +As of now you no longer have excuses to miss a meeting! + diff --git a/crm/calendar/media/google_calendar_credentials01.png b/crm/calendar/media/google_calendar_credentials01.png index ea3fe2639..534961a15 100644 Binary files a/crm/calendar/media/google_calendar_credentials01.png and b/crm/calendar/media/google_calendar_credentials01.png differ diff --git a/crm/calendar/media/google_calendar_credentials02.png b/crm/calendar/media/google_calendar_credentials02.png index c8aa3f2dc..4a45286ab 100644 Binary files a/crm/calendar/media/google_calendar_credentials02.png and b/crm/calendar/media/google_calendar_credentials02.png differ diff --git a/crm/calendar/media/google_calendar_credentials03.png b/crm/calendar/media/google_calendar_credentials03.png index 842a2794c..a3978af38 100644 Binary files a/crm/calendar/media/google_calendar_credentials03.png and b/crm/calendar/media/google_calendar_credentials03.png differ diff --git a/crm/calendar/media/google_calendar_credentials04.png b/crm/calendar/media/google_calendar_credentials04.png index f4d24254a..567b626e8 100644 Binary files a/crm/calendar/media/google_calendar_credentials04.png and b/crm/calendar/media/google_calendar_credentials04.png differ diff --git a/crm/calendar/media/google_calendar_credentials05.png b/crm/calendar/media/google_calendar_credentials05.png index 10c460c85..52a8548ce 100644 Binary files a/crm/calendar/media/google_calendar_credentials05.png and b/crm/calendar/media/google_calendar_credentials05.png differ diff --git a/crm/calendar/media/google_calendar_credentials06.png b/crm/calendar/media/google_calendar_credentials06.png index 6da28abe7..1a7223b9a 100644 Binary files a/crm/calendar/media/google_calendar_credentials06.png and b/crm/calendar/media/google_calendar_credentials06.png differ diff --git a/crm/calendar/media/google_calendar_credentials07.png b/crm/calendar/media/google_calendar_credentials07.png index 37bd91787..140b97624 100644 Binary files a/crm/calendar/media/google_calendar_credentials07.png and b/crm/calendar/media/google_calendar_credentials07.png differ diff --git a/crm/calendar/media/google_calendar_credentials08.png b/crm/calendar/media/google_calendar_credentials08.png index db3c955e4..8a55f7ae3 100644 Binary files a/crm/calendar/media/google_calendar_credentials08.png and b/crm/calendar/media/google_calendar_credentials08.png differ diff --git a/crm/calendar/media/google_calendar_credentials09.png b/crm/calendar/media/google_calendar_credentials09.png index a2216d893..ba4d03604 100644 Binary files a/crm/calendar/media/google_calendar_credentials09.png and b/crm/calendar/media/google_calendar_credentials09.png differ diff --git a/crm/calendar/media/google_calendar_credentials10.png b/crm/calendar/media/google_calendar_credentials10.png new file mode 100644 index 000000000..3bc3d5be3 Binary files /dev/null and b/crm/calendar/media/google_calendar_credentials10.png differ diff --git a/crm/leads/generate/manual.rst b/crm/leads/generate/manual.rst index a9536d872..f31db7a91 100644 --- a/crm/leads/generate/manual.rst +++ b/crm/leads/generate/manual.rst @@ -32,9 +32,7 @@ Go to :menuselection:`Sales --> Leads` and click the **Create** button. From the contact form, provide all the details in your possession (contact name, email, phone, address, etc.) as well as some additional -information in the **Internal notes** field. You can also link the -lead to an existing company by editing the**Customer** field. Click -on save and the contact will be visible as a lead in your pipeline . +information in the **Internal notes** field. .. note:: diff --git a/crm/leads/generate/media/manual03.jpg b/crm/leads/generate/media/manual03.jpg index 5276b3661..afb50075d 100644 Binary files a/crm/leads/generate/media/manual03.jpg and b/crm/leads/generate/media/manual03.jpg differ diff --git a/db_management/documentation.rst b/db_management/documentation.rst index 4ada742f7..44bfa3204 100644 --- a/db_management/documentation.rst +++ b/db_management/documentation.rst @@ -71,7 +71,7 @@ Uninstalling Apps ================= .. warning:: Make sure you first test what you are about to do on a - :ref:`duplicate ` of your database before making any + :ref:`duplicate ` of your database before making any changes (*especially* installing/uninstalling apps). In your Odoo instance click on **Settings**; in this app, you will be diff --git a/discuss/email_servers.rst b/discuss/email_servers.rst index 91f428d8e..61eacc753 100644 --- a/discuss/email_servers.rst +++ b/discuss/email_servers.rst @@ -18,9 +18,9 @@ and check *External Email Servers* Then, go through the following steps. .. note:: - Office 365 doesn't allow external hosts like Odoo. - Consequently you can't use Office 365 email servers to send - or receive messages in Odoo. + Office 365 email servers don't allow to send external emails + from hosts like Odoo. + Consequently you can only use such email servers for incoming messages. Set an outgoing email server for outbound messages -------------------------------------------------- @@ -81,31 +81,28 @@ If you want to use another alias, you have extra steps in Odoo: How to use my own email servers with Odoo Online ================================================ Odoo Online comes up with an embedded and ready-to-use email -server (*@yourcompany.odoo.com*). -We recommend to keep this default setting as it is really convenient. -Indeed, while it is Odoo-labelled, the visible source of any message -sent from Odoo will be your personal email address (your Odoo login). -Your contacts will therefore trust your messages. +solution with *@yourcompany.odoo.com* as domain. +We recommend to keep this default setup as it is really convenient. -You can still use your own email servers if you want your contacts to see -your historic email address when they reply to your messages or if you want -to manage the reputation of your email servers yourself. +Nevertheless you can still use your own email servers if you want +to manage your email server's reputation (blacklisting, etc). +The configuration for both incoming and outgoing mail servers is +given here above. -There are 2 methods: +However when it comes to incoming messages, we don't recommend +to exclusively use your own email server. Indeed, Odoo Online is fetching +incoming messages from the email server once every hour only. +To receive emails in real time, you should rather use +a **catchall redirection** (your server -> Odoo server). To do so: -* [Recommended] **Use a catchall redirection** (your server -> Odoo server) - to receive emails in Odoo in real time thanks to the Odoo email server. - Create a catchall address in your email server settings. - Then apply following redirection: +* Create a catchall address in your email server settings (e.g. catchall). +* Still from such settings, set a redirection + from this catchall address to Odoo's one: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. - That's it you're ready to go! -* **Use a catchall mailbox** to exclusively use your own email server. - That way you can also manage your email server reputation (blacklisting, etc). - However, incoming messages are fetched from the email server - thanks to a cron running every hour. This is the shortest time lap - for crons in Online instances. - If you opt for this solution, simply follow the procedure - of above section. +* In Odoo check *External Email Servers* in :menuselection:`Settings --> General Settings` + and enter your email domain name (i.e. yourdomain.ext). +* No need to set up an incoming email server in such a case. + How to be SPF-compliant when using external email servers in Odoo ================================================================= diff --git a/ecommerce/managing_products/variants.rst b/ecommerce/managing_products/variants.rst index 2e8b30977..a464e6cd0 100644 --- a/ecommerce/managing_products/variants.rst +++ b/ecommerce/managing_products/variants.rst @@ -4,7 +4,9 @@ How to manage product variants Product variants are used to offer variations of the same product to your customers on the products page. For example, the customer chooses a T-shirt -and then selects its size and color. +and then selects its size and color. In the example below, the customer +chooses a phone, and then selects the memory; color and Wi-Fi band from the +available options. .. image:: ./media/variants.png :align: center diff --git a/ecommerce/shopper_experience.rst b/ecommerce/shopper_experience.rst index bdba04924..c20d12956 100644 --- a/ecommerce/shopper_experience.rst +++ b/ecommerce/shopper_experience.rst @@ -7,6 +7,7 @@ Get paid shopper_experience/payment shopper_experience/paypal + shopper_experience/authorize shopper_experience/wire_transfer shopper_experience/payment_acquirer shopper_experience/portal diff --git a/ecommerce/shopper_experience/authorize.rst b/ecommerce/shopper_experience/authorize.rst new file mode 100644 index 000000000..3e3796586 --- /dev/null +++ b/ecommerce/shopper_experience/authorize.rst @@ -0,0 +1,77 @@ +================================== +How to get paid with Authorize.Net +================================== + +Authorize.Net is one of the most popular eCommerce payment platforms in North America. +Unlike most of the other payment acquirers compatible with Odoo, +Authorize.Net can be used as `payment gateway `__ only. +That way you can use the `payment processor or merchant `__ that you like. + + +Create an Authorize.Net account +=============================== + +* Create an `Authorize.Net account `__ + by clicking 'Get Started'. +* In the pricing page, press *Sign up now* if you want to use Authorize.net as + both payment gateway and merchant. If you want to use your own merchant, press + the related option. + + .. image:: media/authorize01.png + :align: center + +* Go through the registration steps. +* The account is set as a test account by default. You can use this test + account to process a test transaction from Odoo. +* Once ready, switch to **Production** mode. + + +Set up Odoo +=========== +* Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or Accounting + --> Settings --> Payment Acquirers`. +* Enter both your **Login ID** + and your **API Transaction Key**. + + .. image:: media/authorize02.png + :align: center + + To get those credentials in Authorize.Net, you can rely on + *API Login ID and Transaction Key* video of + `Authorize.Net Video Tutorials `__. + Such videos give meaningful insights about how to set up your + Authorize.Net account according to your needs. + + +Go live +======= +Your configuration is now ready! +You can make Authorize.Net visible on your merchant interface +and activate the **Production** mode. + +.. image:: media/paypal_live.png + :align: center + +.. note:: Credentials provided by Authorize.net are different for both + test and production mode. Don't forget to update them in Odoo when you + turn on the production mode. + + +Assess Authorize.Net as payment solution +======================================== +You can test and assess Authorize.Net for free by creating a `developer account `__. + +Once the account created you receive sandbox credentials. +Enter them in Odoo as explained here above and make sure +you are still in *Test* mode. + +You can also log in to `Authorize.Net sandbox platform `__ +to configure your sandbox account. + +To perform ficticious transactions you can use fake card numbers +provided in the `Authorize.Net Testing Guide `__. + +.. seealso:: + + * :doc:`payment` + * :doc:`payment_acquirer` diff --git a/ecommerce/shopper_experience/media/authorize01.png b/ecommerce/shopper_experience/media/authorize01.png new file mode 100644 index 000000000..13bd3eb50 Binary files /dev/null and b/ecommerce/shopper_experience/media/authorize01.png differ diff --git a/ecommerce/shopper_experience/media/authorize02.png b/ecommerce/shopper_experience/media/authorize02.png new file mode 100644 index 000000000..e89403879 Binary files /dev/null and b/ecommerce/shopper_experience/media/authorize02.png differ diff --git a/ecommerce/shopper_experience/media/paypal_ipn_setup.png b/ecommerce/shopper_experience/media/paypal_ipn_setup.png index 117afd237..8435bc793 100644 Binary files a/ecommerce/shopper_experience/media/paypal_ipn_setup.png and b/ecommerce/shopper_experience/media/paypal_ipn_setup.png differ diff --git a/ecommerce/shopper_experience/media/paypal_live.png b/ecommerce/shopper_experience/media/paypal_live.png index 0e9fc3428..862725188 100644 Binary files a/ecommerce/shopper_experience/media/paypal_live.png and b/ecommerce/shopper_experience/media/paypal_live.png differ diff --git a/ecommerce/shopper_experience/paypal.rst b/ecommerce/shopper_experience/paypal.rst index f614c28f3..7a43a9ace 100644 --- a/ecommerce/shopper_experience/paypal.rst +++ b/ecommerce/shopper_experience/paypal.rst @@ -2,8 +2,8 @@ How to get paid with Paypal =========================== -Paypal is the easiest online payment method to configure. -It is also the only one without any subscription free. +Paypal is the easiest online payment acquirer to configure. +It is also the only one without any subscription fee. We definitely advise it to any starter. @@ -70,8 +70,8 @@ Set up your Paypal account :align: center -Set up Paypal's payment method in Odoo -====================================== +Set up Odoo +=========== * Open Paypal setup form in :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers+`. Enter both your **Email ID** and your **Merchant ID** and check **Use IPN**. @@ -152,4 +152,4 @@ You can test the entire payment flow thanks to Paypal Sandbox accounts. .. seealso:: * :doc:`payment` - * :doc:`payment_acquirer` \ No newline at end of file + * :doc:`payment_acquirer` diff --git a/general/base_import/import_faq.rst b/general/base_import/import_faq.rst index 7729534c0..d13626b9d 100644 --- a/general/base_import/import_faq.rst +++ b/general/base_import/import_faq.rst @@ -10,7 +10,7 @@ contacts, products, bank statements, journal entries and even orders! Open the view of the object you want to populate and click *Import*. -.. image:: media/import_button.gif +.. image:: media/import_button.png :align: center There you are provided with templates you can easily populate diff --git a/inventory/management/delivery/scheduled_dates.rst b/inventory/management/delivery/scheduled_dates.rst index a7dc17883..f56fefbb5 100644 --- a/inventory/management/delivery/scheduled_dates.rst +++ b/inventory/management/delivery/scheduled_dates.rst @@ -12,7 +12,7 @@ are dependent on the different leads times configured in Odoo. Configuring lead times ====================== -Configuring **lead times** is a first essentiel move in order to compute +Configuring **lead times** is a first essential move in order to compute scheduled dates. Lead times are the delays (in term of delivery, manufacturing, ...) promised to your different partners and/or clients. diff --git a/legal/terms/i18n/enterprise_fr.rst b/legal/terms/i18n/enterprise_fr.rst index 2e8cd120d..937239525 100644 --- a/legal/terms/i18n/enterprise_fr.rst +++ b/legal/terms/i18n/enterprise_fr.rst @@ -161,7 +161,7 @@ Ce service est fourni par le biais d'une plateforme automatisée, afin de permet d'effectuer des migration sans intervention humain, dès lors qu’une version précédente de la base de données du Client a été migrée avec succès pour une Version Couverte donnée. Le client peut soumettre des demandes de migration successives pour une base de données, -et accepte de soumettre au moins 1 demande de mifration de test avant de soumettre la demande de +et accepte de soumettre au moins 1 demande de migration de test avant de soumettre la demande de migration finale. Le service de migration est limité à la conversion et à l'adaptation techniques de la base @@ -527,4 +527,4 @@ DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION RELATIVE AU LOGICIEL. .. raw:: html - \ No newline at end of file + diff --git a/legal/terms/partnership.rst b/legal/terms/partnership.rst index 0efefec7c..021c1d5a2 100644 --- a/legal/terms/partnership.rst +++ b/legal/terms/partnership.rst @@ -214,7 +214,7 @@ For _____________, -.. _appendix_a: +.. _appendix_p_a: 10 Appendix A: Odoo Enterprise Edition License ============================================== diff --git a/locale/es/LC_MESSAGES/accounting.po b/locale/es/LC_MESSAGES/accounting.po index bfbe7f250..119089f51 100644 --- a/locale/es/LC_MESSAGES/accounting.po +++ b/locale/es/LC_MESSAGES/accounting.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Christopher Ormaza , 2017\n" +"Last-Translator: Cristóbal Martí Oliver , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -99,7 +99,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:23 #: ../../accounting/receivables/getting_paid/automated_followups.rst:31 msgid "Configuration" msgstr "Configuración" @@ -1032,7 +1031,6 @@ msgstr "" #: ../../accounting/bank/misc/batch.rst:124 #: ../../accounting/payables/pay/sepa.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:134 msgid "Troubleshooting" msgstr "Solución de problemas" @@ -1977,6 +1975,11 @@ msgstr "" "En la pestaña Asientos de Diarios, la cuenta Débito y Crédito preestablecida" " puede ser configurada también como la moneda del diario" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "Tipo" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1995,14 +1998,26 @@ msgstr "" msgid "Select 'General' for miscellaneous operations journals." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "Compañía" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Company related to this journal" msgstr "Compañía relacionada con este diario" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "Código corto" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The journal entries of this journal will be named using this prefix." msgstr "Los asientos de este diario será nombrados usando este prefijo." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "Secuencia de factura rectificativa dedicada" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if you don't want to share the same sequence for invoices and" @@ -2011,6 +2026,10 @@ msgstr "" "Marque esta casilla si no quiere compartir la misma secuencia para facturas " "y facturas rectificativas hechas desde este diario" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "Secuencia del asiento" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the journal " @@ -2019,6 +2038,10 @@ msgstr "" "Este campo contiene información relacionada con la numeración de los " "asientos de este diario." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "Secuencia de asiento rectificativo" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the refund " @@ -2027,18 +2050,34 @@ msgstr "" "Este campo contiene la información relativa a la numeración de los asientos " "rectificativos de este diario." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "Cuenta deudora por defecto" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for debit amount" msgstr "Actúa como una cuenta por defecto para importes en el debe." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "Cuenta acreedora por defecto" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for credit amount" msgstr "Actúa como una cuenta por defecto para los importes en el haber." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "Moneda" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The currency used to enter statement" msgstr "La divisa utilizada para introducir asientos." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "Métodos de débito" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for collecting money. Odoo modules offer various payments " @@ -2049,6 +2088,10 @@ msgstr "" "facilidades de pago, pero usted siempre puede usar el método de pago " "'Manual' para gestionar pagos por fuera del software." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "Métodos de pago" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for sending money. Odoo modules offer various payments " @@ -2059,6 +2102,10 @@ msgstr "" "facilidades de pago, pero usted siempre puede usar el método de pago " "'Manual' para gestionar pagos por fuera del software." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "Agrupar líneas de factura" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "If this box is checked, the system will try to group the accounting lines " @@ -2067,6 +2114,10 @@ msgstr "" "Si esta opción está marcada, el sistema tratará de agrupar las líneas del " "asiento cuando se generen desde facturas." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "Cuenta de beneficios" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a profit when the ending balance of a cash register differs" @@ -2075,6 +2126,10 @@ msgstr "" "Usado para registrar una ganancia cuando el saldo final de un registro de " "caja difiere de lo que el sistema calcula" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "Cuenta de pérdidas" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a loss when the ending balance of a cash register differs " @@ -2083,10 +2138,18 @@ msgstr "" "Usado para registrar una pérdida cuando el saldo final de un registro de " "caja difiere de lo que el sistema calcula" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "Mostrar diario en el tablero" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Whether this journal should be displayed on the dashboard or not" msgstr "Si este diario debe mostrarse en el tablero o no" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Technical feature used to know whether check printing was enabled as payment" @@ -2095,19 +2158,36 @@ msgstr "" "Campo técnico usado para saber si la impresión de cheques se habilitó como " "método de pago." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "Secuencia de los cheques" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Checks numbering sequence." msgstr "Secuencia de numeración de los cheques." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "Numeración manual" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 #: ../../accounting/payables/pay/check.rst:0 msgid "Check this option if your pre-printed checks are not numbered." msgstr "Marque esta opción si sus cheques pre-impresos no están numerados." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "Nº del próximo cheque" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Sequence number of the next printed check." msgstr "Número de secuencia del próximo cheque impreso." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "Activo en Punto de Venta" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if this journal define a payment method that can be used in a" @@ -2116,6 +2196,10 @@ msgstr "" "Marca esta casilla de selección si este diario define un método de pago que " "puede ser utilizado en el punto de venta." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "Importe de la diferencia permitida" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field depicts the maximum difference allowed between the ending balance" @@ -2367,6 +2451,10 @@ msgstr "" msgid "Explanation of the fields:" msgstr "Explicación de los campos:" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "Estado" + #: ../../accounting/others/adviser/assets.rst:0 msgid "When an asset is created, the status is 'Draft'." msgstr "Cuando un activo es creado, el estado es 'Borrador'." @@ -2388,22 +2476,42 @@ msgstr "" "última línea de depreciación es publicada, el activo automáticamente va a " "ese estado." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "Categoría" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Category of asset" msgstr "Categoría del activo" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "Fecha" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Date of asset" msgstr "Fecha del activo" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "Valor bruto" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Gross value of asset" msgstr "Valor bruto del activo" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "Valor de rescate" + #: ../../accounting/others/adviser/assets.rst:0 msgid "It is the amount you plan to have that you cannot depreciate." msgstr "Es el importe que prevee tener que no puede depreciar" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "Método de cálculo" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the amount of depreciation lines." msgstr "" @@ -2420,6 +2528,10 @@ msgid "" msgstr "" "Decreciente: Calculado en base de: Valor Residual * Factor Decreciente" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "Método de tiempo basado en" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Choose the method to use to compute the dates and number of depreciation " @@ -2444,6 +2556,10 @@ msgstr "" "Fecha de Cierre: Elija el tiempo entre 2 depreciaciones y la fecha en que " "las depreciaciones no irán por encima de." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "Tiempo prorrateado" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Indicates that the first depreciation entry for this asset have to be done " @@ -2453,10 +2569,18 @@ msgstr "" "Indica que el primer asiento de amortización tiene que ser realizado desde " "la compra en vez desde el 1 de Enero / Empieza en la fecha del año fiscal." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "Número de depreciaciones" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The number of depreciations needed to depreciate your asset" msgstr "El número de amortizaciones para amortizar el activo" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "Número de meses en un periodo" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The amount of time between two depreciations, in months" msgstr "La cantidad de tiempo entre dos amortizaciones, en meses" @@ -4374,15 +4498,27 @@ msgstr "" "legales específicos de cada país, y establecer las reglas para cerrar un " "ejercicio fiscal y generar los apuntes de apertura." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "Etiquetas" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Optional tags you may want to assign for custom reporting" msgstr "Etiquetas opcionales a asignar en informes de ventas" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "Cuenta de la moneda" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Forces all moves for this account to have this account currency." msgstr "" "Fuerza a todos los movimientos de esta cuenta a tener la moneda de la misma." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "Tipo interno" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "The 'Internal Type' is used for features available on different types of " @@ -4393,6 +4529,10 @@ msgstr "" "tipos de cuentas: el tipo liquidez es para efectivo o cuentas bancarias, " "pagable/pendiente de pago es para cuentas de proveedores/clientes." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "Permitir conciliación" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "Check this box if this account allows invoices & payments matching of " @@ -9418,10 +9558,18 @@ msgstr "" msgid "Explanation of the fields of the payment screen:" msgstr "Explicación de los campos en la pantalla de pago: " +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used for usability purposes" msgstr "Campo técnico utilizado por usabilidad" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to hide the payment method if the selected journal has " @@ -9430,6 +9578,10 @@ msgstr "" "Campo técnico utilizado para ocultar el método de pago si el diario " "seleccionado tiene únicamente como disponible el 'manual'" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "Código" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to adapt the interface to the payment type selected." @@ -9437,6 +9589,10 @@ msgstr "" "Campo técnico utilizado para adaptar la interfaz al tipo de pago " "seleccionado." +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "Número de cheque" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "The selected journal is configured to print check numbers. If your pre-" @@ -12343,8 +12499,8 @@ msgstr ":doc:`recording`" #: ../../accounting/receivables/customer_payments/credit_cards.rst:167 #: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`paypal`" -msgstr ":doc:`paypal`" +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:169 #: ../../accounting/receivables/customer_payments/recording.rst:130 @@ -12653,260 +12809,6 @@ msgstr "" "Puede obtener el DDV de su compañía desde el reporte Resumen Ejecutivo bajo " "Reportes (revisar el KPI días promedio de deudores)." -#: ../../accounting/receivables/customer_payments/paypal.rst:3 -msgid "How to accept paypal payments on invoices?" -msgstr "¿Cómo aceptar pagos paypal en facturas?" - -#: ../../accounting/receivables/customer_payments/paypal.rst:5 -msgid "" -"The \"Paypal Payment Acquirer\" module allows you to accept payments via " -"paypal, for your sales orders, invoices, or online orders. As paypal accepts" -" payments through credit cards (VISA, Mastercard, …), you will be able to " -"process most payment methods." -msgstr "" -"El módulo \"Comprador de Pagos Paypal\" le permite aceptar pagos vía paypal," -" para sus órdenes de venta, facturas, u órdenes en línea. Como paypal acepta" -" pagos a través de tarjetas de crédito (VISA, Mastercard, ...), Ud. podrá " -"procesar la mayoría de métodos de pago." - -#: ../../accounting/receivables/customer_payments/paypal.rst:10 -msgid "Paypal support two modes:" -msgstr "Paypal soporta dos modos:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:12 -msgid "" -"Paypal Merchant Account: the user is redirected to paypal to do the payment " -"(either with a credit card or a paypal account)" -msgstr "" -"Cuenta Comerciante Paypal: el usuario es redirigido a paypal para hacer el " -"pago (ya sea con una tarjeta de crédito o una cuenta paypal)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:15 -msgid "" -"PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to " -"paypal and the payment can be done in the background. This method is mostly " -"used for subscription businesses where you need to charge your customers " -"periodically." -msgstr "" -"PayPal PayFlow Pro (S2S, Server 2 Server): el usuario no es redirigido a " -"paypal y el pago puede ser hecho en segundo plano. Este método es usado más " -"que todo para suscripciones de negocio donde necesita cargar a sus clientes " -"periódicamente." - -#: ../../accounting/receivables/customer_payments/paypal.rst:20 -msgid "As of today, Odoo only support the normal Paypal Merchant Account." -msgstr "Hasta hoy, Odoo solo soporta la Cuenta Comerciante Paypal normal." - -#: ../../accounting/receivables/customer_payments/paypal.rst:26 -msgid "Install the \"PayPal Payment Acquirer\" module" -msgstr "Instalar el módulo \"Comprador de Pagos Paypal\"" - -#: ../../accounting/receivables/customer_payments/paypal.rst:28 -msgid "Start by installing the **PayPal Payment Acquirer** module." -msgstr "Empezar instalando el módulo **Comprador de Pagos Paypal**." - -#: ../../accounting/receivables/customer_payments/paypal.rst:30 -msgid "" -"Once the module is installed, you should see a new payment acquirer in the " -"Setting application, menu \"Payment Acquirers\"." -msgstr "" -"Una vez el módulo esta instalado, deberá ver un nuevo comprador de pago en " -"la aplicación Ajustes, menú \"Comprador de Pagos\"." - -#: ../../accounting/receivables/customer_payments/paypal.rst:36 -msgid "" -"By default, Paypal is configured to work in a test environment, out-of-the-" -"box. It means you can already test the full order to payment flow with the " -"paypal sandbox, without having to configure the next steps." -msgstr "" -"Por defecto, Paypal es configurado para trabajar en un ambiente de prueba, " -"fuera de la caja. Lo que significa que ya puede probar la órden completa " -"para el flujo de pago con la caja de arena de paypal, sin tener que " -"configuar los siguientes pasos." - -#: ../../accounting/receivables/customer_payments/paypal.rst:42 -msgid "Creating and configuring a PayPal merchant account" -msgstr "Crear y configurar una cuenta de comerciante Paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:45 -msgid "Create a basic Paypal account" -msgstr "Crear una cuenta Paypal básica" - -#: ../../accounting/receivables/customer_payments/paypal.rst:47 -msgid "Existing or newly created Personal Paypal account can be used." -msgstr "" -"Las cuentas Paypal Personales existentes o recientemente creadas pueden ser " -"usadas." - -#: ../../accounting/receivables/customer_payments/paypal.rst:49 -msgid "Or upgrade your account to Business account (merchant) if needed" -msgstr "" -"O actualice su cuenta a cuenta de Negocios (Comerciante) si es necesario" - -#: ../../accounting/receivables/customer_payments/paypal.rst:55 -msgid "Paypal Account Summary page" -msgstr "Página de resumen de la Cuenta Paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:58 -msgid "Paypal Configuration" -msgstr "Configuración Paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:60 -msgid "" -"Access \"Seller preferences\" menu from `PayPal website " -"`__" -msgstr "" -"Acceso al menú \"Preferencias del vendedor\" desde `sitio web PayPal " -"`__" - -#: ../../accounting/receivables/customer_payments/paypal.rst:66 -msgid "" -"Access \"Website preferences\" and configure Auto Return (Payment Data " -"Transfer must be left to Off)" -msgstr "" -"Ingrese a las \"Preferencias del sitio Web\" y configure Auto Devolución (la" -" Transferencia de Datos de Pagos debe ser dejada en Apagado)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:69 -msgid "**Database name**: yourcompany" -msgstr "**Nombre base de datos**: sucompañía" - -#: ../../accounting/receivables/customer_payments/paypal.rst:70 -#: ../../accounting/receivables/customer_payments/paypal.rst:88 -msgid "**Website URL**: https://yourcompany.odoo.com/" -msgstr "**Website URL**: https://yourcompany.odoo.com/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:71 -msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" -msgstr "**Devolución URL**: https://yourcompany.odoo.com/shop/confirmation" - -#: ../../accounting/receivables/customer_payments/paypal.rst:76 -msgid "These settings will redirect your buyer to your web confirmation page." -msgstr "" -"Estos ajustes redirigirán a su comprador a su página web de confirmación." - -#: ../../accounting/receivables/customer_payments/paypal.rst:80 -msgid "Access and edit Instant payment notifications settings - IPN" -msgstr "" -"Ingresar y editar los ajustes para Notificaciones de Pago Instantáneas - IPN" - -#: ../../accounting/receivables/customer_payments/paypal.rst:85 -msgid "Example" -msgstr "Ejemplo" - -#: ../../accounting/receivables/customer_payments/paypal.rst:87 -msgid "**Database name**: \"yourcompany\"" -msgstr "**Nombre base de datos**: \"sucompañía\"" - -#: ../../accounting/receivables/customer_payments/paypal.rst:89 -msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" -msgstr "" -"**Notificación URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:91 -msgid "" -"Verify that your Notify URL uses the correct protocol (HTTP / HTTPS). If you" -" use the odoo.com domain, we advise you to use HTTPS." -msgstr "" -"Verifique que su URL de Notificación use el protocolo correcto (HTTP / " -"HTTPS). Si usa el dominio odoo.com, le recomendamos usar HTTPS." - -#: ../../accounting/receivables/customer_payments/paypal.rst:94 -msgid "" -"Set the encoding to UTF-8 from the menu :menuselection:`Settings --> " -"Language Encoding --> More Options --> More selling tools`" -msgstr "" -"Configurar la codificación a UTF-8 desde el menú :menuselection:`Ajustes -->" -" Lenguaje de Codificación --> Más Opciones --> Más herramientas de ventas`" - -#: ../../accounting/receivables/customer_payments/paypal.rst:103 -msgid "" -"Record your Merchant Paypal ID (personal or business account both will have " -"it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> " -"Account Options`." -msgstr "" -"Registrar su ID de Comerciante Paypal (cuenta personal o de negocios ambas " -"lo tienen) será ingresado en el backend de Odoo :menuselection:`Paypal " -"Ajustes --> Opciones de Cuenta`." - -#: ../../accounting/receivables/customer_payments/paypal.rst:111 -msgid "" -"If you want your customers to be able to pay through Paypal while not having" -" a Paypal account- following setting \"Paypal Account Optional\" needs to be" -" set to **ON**. All users will be able to choose Credit/debit card payment " -"option - Paypal account not required." -msgstr "" -"Si quiere que sus clientes puedan pagar a través de Paypal mientras no tiene" -" una cuenta Paypal- los siguientes ajustes \"Cuenta Paypal Opcional\" " -"necesita ser configurada a **Encendido**. Todos los usuarios podrán elegir " -"la opción de pago con tarjeta Crédito/débito - Cuenta Paypal no es " -"requerido." - -#: ../../accounting/receivables/customer_payments/paypal.rst:120 -msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" -msgstr "Instalar sus credenciales de cuenta Comprador de Pagos Paypal en Odoo" - -#: ../../accounting/receivables/customer_payments/paypal.rst:122 -msgid "" -":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" -msgstr "" -":menuselection:`Ajustes --> Pagos --> Compradores de Pagos --> Paypal`" - -#: ../../accounting/receivables/customer_payments/paypal.rst:124 -msgid "**Paypal Email ID**: your paypal account email address" -msgstr "**Paypal Email ID**: su dirección de email en su cuenta paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:126 -msgid "**Paypal Merchant ID**: ID retrieved at previous step" -msgstr "**Paypal Comerciante ID**: ID traído del paso anterior" - -#: ../../accounting/receivables/customer_payments/paypal.rst:136 -msgid "" -"If your eCommerce customer gets this Error Message after completing Paypal " -"payment instead of being redirected to your database:" -msgstr "" -"Si su cliente de comercio electrónico obtiene este Mensaje de Error después " -"de haber completado el pago Paypal en lugar de ser redireccionado a su base " -"de datos:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:142 -msgid "" -"Verify the settings you have `configured in Paypal `_:" -msgstr "" -"Verifique los ajustes que ha `configurado en Paypal `_:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:144 -msgid "" -"Auto Return should be on (the value can be quite generic, like " -"/shop/confirmation; the correct URL will be set for each " -"transaction)" -msgstr "" -"La Auto Devolución debe estar encendida (el valor puede ser algo genérico, " -"como /shop/confirmation; la URL correcta debe ser configurada" -" para cada transacción)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:148 -msgid "Payment Data Transfer should be off" -msgstr "La Transferencia de Datos de Pago debe estar apagada" - -#: ../../accounting/receivables/customer_payments/paypal.rst:150 -msgid "" -"On-premise databases must be accessible through classic HTTP/HTTPS ports " -"(80/443) for Paypal to work correctly, usually through a reverse proxy. " -"Contact your integrating partner if you are unsure this is the case. " -"Databases hosted on odoo.com are already configured correctly." -msgstr "" -"Las bases de datos En-sitio debe ser accesibles a través de los clásicos " -"puertos HTTP/HTTPS (80/443) para que Paypal funcione correctamente, " -"usualmente a través de un proxy inverso. Contacte a su asociado integrador " -"si esta poco seguro de que este sea el caso. Las bases de datos alojadas en " -"odoo.com ya estan configuradas correctamente." - -#: ../../accounting/receivables/customer_payments/paypal.rst:157 -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" -msgstr ":doc:`credit_cards`" - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "¿Cuáles son las diferentes formas de registrar un pago?" @@ -13120,6 +13022,10 @@ msgstr "" "a cuenta. No haga este proceso de nuevo en la otra cuenta bancaria o " "terminará con dos entradas de diario para la misma transacción." +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr ":doc:`credit_cards`" + #: ../../accounting/receivables/getting_paid.rst:3 msgid "How to get paid?" msgstr "¿Cómo obtener pagos?" diff --git a/locale/es/LC_MESSAGES/discuss.po b/locale/es/LC_MESSAGES/discuss.po index 09425e072..227ae411d 100644 --- a/locale/es/LC_MESSAGES/discuss.po +++ b/locale/es/LC_MESSAGES/discuss.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Antonio Trueba , 2017\n" +"Last-Translator: Ruben Dario Machado , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -23,146 +23,238 @@ msgid "Discuss" msgstr "Debates" #: ../../discuss/email_servers.rst:3 -msgid "How to use my own email servers to send and receive messages in Odoo" +msgid "How to use my own email servers to send and receive email in Odoo" msgstr "" #: ../../discuss/email_servers.rst:6 msgid "When is it needed" -msgstr "" +msgstr "Cuando sea necesario" #: ../../discuss/email_servers.rst:7 -msgid "You need it if you use Odoo Community or Enterprise." -msgstr "" - -#: ../../discuss/email_servers.rst:10 -msgid "What if I use Odoo Online" -msgstr "" - -#: ../../discuss/email_servers.rst:11 msgid "" -"You are done! Odoo Online comes up with an embedded and ready-to-use email " -"server (*@yourcompany.odoo.com*). We recommend to keep this default setting " -"as is as it is really convenient." +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." +msgstr "" + +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" msgstr "" #: ../../discuss/email_servers.rst:15 msgid "" -"Indeed, while it is branded by Odoo, the visible source of any message sent " -"from Odoo will be your personal email address (your Odoo login). Your " -"contacts will therefore trust your messages." -msgstr "" - -#: ../../discuss/email_servers.rst:20 -msgid "How does it work when a contact replies to an email sent from Odoo" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." msgstr "" #: ../../discuss/email_servers.rst:21 msgid "" -"Default reply-to is a generic address used to automatically route any " -"incoming email to the discussion thread of the origin business object " -"(opportunity, order, task, etc.) and to the inbox of all its followers. By " -"default this address is \"catchall@\" but it can be changed. Thanks to it, " -"you get a perfect message thread in Odoo and you don't pollute your external" -" email box with Odoo-related topics." +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:29 -msgid "How to use my own email servers" -msgstr "" - -#: ../../discuss/email_servers.rst:30 -msgid "" -"You need to be a system admin to set this up. Go to :menuselection:`Settings" -" --> General Settings` and check *External Email Servers* (watch out: this " -"checkbox only shows up after Odoo 10). Then, go through the following steps." -msgstr "" - -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/email_servers.rst:26 msgid "Set an outgoing email server for outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:37 +#: ../../discuss/email_servers.rst:27 msgid "" "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " "etc.) as well as your admin credentials. Once all the information has been " "filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:45 +#: ../../discuss/email_servers.rst:35 msgid "Set an incoming email server for inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:46 +#: ../../discuss/email_servers.rst:36 msgid "" "Fill out the form according to your email provider’s settings. Leave the " "*Actions to Perform on Incoming Mails* blank. Once all the information has " "been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:53 +#: ../../discuss/email_servers.rst:43 msgid "" "By default inbound messages are fetched every 5 minutes. You can change this" " value in developer mode. Go to :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/email_servers.rst:59 +#: ../../discuss/email_servers.rst:49 msgid "Set the domain name" msgstr "" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/email_servers.rst:50 msgid "" "Enter the domain name of your email servers (e.g. mycompany.com) in General " "Settings." msgstr "" -#: ../../discuss/email_servers.rst:67 +#: ../../discuss/email_servers.rst:57 msgid "Create a catchall address" msgstr "" -#: ../../discuss/email_servers.rst:68 +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 msgid "" "Create a catchall address in your email server settings. We advise you to " "use \"catchall@\" so that everything works out straight away. If you want to" " use another alias, you have extra steps in Odoo:" msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/email_servers.rst:67 msgid "Activate the developer mode from your Settings Dashboard." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/email_servers.rst:72 msgid "" "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " "Parameters --> System Parameters` and enter your custom catchall alias in " "*mail.catchall.alias*." msgstr "" -#: ../../discuss/email_servers.rst:84 +#: ../../discuss/email_servers.rst:79 msgid "You can edit the email alias used for bounced messages the same way." msgstr "" -#: ../../discuss/email_servers.rst:87 -msgid "How to perfectly combine Odoo Discuss and my traditional email tool" +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" msgstr "" -#: ../../discuss/email_servers.rst:88 +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here `__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 msgid "" "Odoo Discuss is a perfect tool to send and read messages related to business" -" objects. But it doesn't aim to replace a full-featured email software " -"(Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " "both systems without mingling them: What is related to Odoo business objects" -" or applications goes into Odoo; What is not stays into your external email " -"boxes." +" or applications goes into Odoo; What is not can be managed into your " +"external email box." msgstr "" -#: ../../discuss/email_servers.rst:95 +#: ../../discuss/email_servers.rst:150 msgid "" "To do so, create specific email aliases to use in Odoo (to generate leads or" " opportunities, helpdesk tickets, etc.). If you take an email alias already " "used for messaging outside of Odoo, incoming messages will land into both " -"systems. This will negatively impact your productivity when it comes to " -"process them." +"systems. This will negatively impact your productivity." msgstr "" #: ../../discuss/mail_twitter.rst:3 diff --git a/locale/es/LC_MESSAGES/ecommerce.po b/locale/es/LC_MESSAGES/ecommerce.po index f45242ce2..3800421d9 100644 --- a/locale/es/LC_MESSAGES/ecommerce.po +++ b/locale/es/LC_MESSAGES/ecommerce.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Mateo Tibaquirá Palacios , 2017\n" +"Last-Translator: Antonio Trueba , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -655,23 +655,21 @@ msgid "Launch my website" msgstr "" #: ../../ecommerce/shopper_experience.rst:3 -msgid "Improve shopper experience" +msgid "Get paid" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to set up payment methods" +msgid "How to get paid with payment acquirers" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:5 msgid "" -"To collect payments, you can either request your customers to process it " -"manually (e.g. wire transfer) or redirect them to payment acquirers. The " -"payment process described hereunder is common to both eCommerce and online " -"quotations." +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "Payment methods" +msgid "What are the payment methods available" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:13 @@ -681,451 +679,561 @@ msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:15 msgid "" "Wire Transfer is the default payment method available. The aim is providing " -"your customers with your bank details so that they can pay via their bank. " -"This is very easy to start with but slow and inefficient process-wise. Opt " -"for online acquirers as soon as you can!" +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "" -"For B2B users: you can create new manually-processed payment methods (check," -" purchase order, etc.) by renaming 'Wire Transfer' or duplicating it." +msgid "Payment acquirers" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:25 -msgid "Online payment acquirers" +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "" -"Redirect your customers to payment acquirer platforms to collect money " -"effortless. Odoo supports more and more platforms over time: Paypal, " -"Ingenico, Authorize.net, etc. Once the payment accepted, orders are " -"confirmed in Odoo so that the delivery & invoicing processes are triggered " -"automatically." +msgid "`Paypal `__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "Adyen" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "Buckaroo" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Custom (advanced)" -msgstr "" +msgid "Sips" +msgstr "Sips" -#: ../../ecommerce/shopper_experience/payment.rst:35 -msgid "" -"Can be used to request payments to any payment acquirer not listed in Odoo." +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "Edit a payment method" +msgid "How to go live" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:40 msgid "" -"To make payment methods intuitive for your customers feel free to customize " -"them by editing:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:42 -msgid "the name," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:44 -msgid "the picture," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:46 -msgid "" -"the notification messages (thank you & next step, error, cancellation)." +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 msgid "" -"Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers`" -" to do so." +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:51 -msgid "Generic setup" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:53 -msgid "Review the elements here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:55 -msgid "Enter your credentials (online acquirers only)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:57 -msgid "Choose your order confirmation preference (see below)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:59 -msgid "Publish the payment method." +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "Test the payment flow in *Test* mode (default mode)." +msgid "How to debit credit cards to pay subscriptions" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:63 -msgid "Switch to *Production* mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:65 +#: ../../ecommerce/shopper_experience/payment.rst:62 msgid "" -"Se your default payment acquirer in :menuselection:`Accounting --> " -"Configuration --> Settings`. It will be auto-selected for your customers " -"when they enter the payment screen." +"`Odoo Subscription `__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:69 +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 msgid "" -"Rely on the documentation related to your payment acquirer to go through " -"step 2, 5 and 6. Some acquirers provides you with specific credentials for " -"test and production modes (Paypal). Others let you switch mode in their " -"setup interface (Authorize.net)." +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:74 +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 msgid "" -"With Ingenico and Authorize.net, you can let your customers save and reuse a" -" payment card to accelerate the process on next checkouts. See *Store Card " -"Data* in Configuration tab." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:78 -msgid "Payment flow" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:80 -msgid "" -"When choosing the payment method, the customer is taken to the payment " -"acquirer interface to process the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:83 -msgid "" -"Once done he is taken back to Odoo's confirmation page. The transaction " -"status shows up:" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "" -"*Pending*: the order will be confirmed as soon as you authorize the " -"transaction in the acquirer interface." +msgid "How to:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "*Confirmed*: the payment has been authorized automatically." +msgid "Switch to developer mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "" -"A confirmation email is sent to the customer with a copy of the order in " -"pdf. It shows the payment status." +msgid "Take the **Custom** payment method." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Launch the delivery and invoicing from:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:93 msgid "" -"eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:95 -msgid "" -"online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales " -"Orders`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:97 -msgid "" -"For internal tracking purposes, a link to the transaction status is provided" -" in the sales order." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:100 -msgid "" -"If the customer cancels the payment while on the payment acquirer form, it " -"is taken back to the store page (or online quotation) in order to reprocess " -"the order. The payment is marked as *Cancelled* in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:105 -msgid "" -"You can edit the confirmation email template from :menuselection:`Website " -"Admin --> Configuration --> Settings`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:109 -msgid "Order confirmation preferences" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid "There are 4 different behaviors available for any payment acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:114 -msgid "No automatic confirmation" -msgstr "Sin confirmación automática" - -#: ../../ecommerce/shopper_experience/payment.rst:116 -msgid "" -"This is the default mode for *Wire Transfer*. It means Odoo does not confirm" -" orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid " -"Order*). Once you get the payment, you are expected to confirm the order " -"manually to pursue the process (delivery, invoicing)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:121 -msgid "" -"Authorize the amount and confirm the SO on acquirer confirmation (capture " -"manually)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:123 -msgid "" -"Odoo confirms the order as soon as the payment success notification comes " -"in. To get the money however, you need to capture it from your payment " -"transaction. In lots of countries you are indeed requested to deliver your " -"goods before capturing the amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:128 -msgid "" -"Authorize & capture the amount and confirm the SO on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:130 -msgid "" -"This is the default mode for payment acquirers. The amount is captured " -"automatically." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:133 -msgid "" -"For B2B: if you use a manual payment method like *Wire Transfer* and don't " -"expect any upfront payment to launch the delivery, switch to this mode as " -"well." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:137 -msgid "" -"Authorize & capture the amount, confirm the SO and auto-validate the invoice" -" on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:139 -msgid "" -"If you invoice upfront and not at the delivery, switch to this last mode to " -"automate everything. You are requested to select a Payment Journal to record" -" such payments (see " -":doc:`../../accounting/receivables/customer_payments/credit_cards`)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:144 -msgid "Custom payment acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:146 -msgid "" -"Odoo can submit payment requests and redirect to any payment acquirer. In " -"such a case, you need to confirm the sale manually in Odoo once you get paid" -" because Odoo cannot read any payment status sent by the acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:150 -msgid "To configure this:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:152 -msgid "switch to developer mode," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:154 -msgid "edit the *Custom* payment method," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:156 -msgid "" -"set up the payment form (S2S Form Template) as instructed by your payment " +"Set up the payment form (S2S Form Template) as instructed by your payment " "acquirer. You can start from *default_acquirer_button* that you can " "duplicate." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:160 -msgid "Recurring payments & Installment plans" +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:162 +#: ../../ecommerce/shopper_experience/payment.rst:98 msgid "" -"The Ingenico integration allows you to process and manage recurring payments" -" from Odoo Subscriptions app out-of-the-box (more information coming soon)." +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"`__)." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:165 +#: ../../ecommerce/shopper_experience/payment.rst:102 msgid "" -"With some customization, Odoo can also trigger installment plans if this is " -"permitted by your payment acquirer’s API:" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. `__" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:168 -msgid "" -"e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic" -"/paypal-payments-standard/integration-guide/installment_buttons)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:170 -msgid "" -"Such a service is made on-demand by our technical experts based on your own " -"requirements. Ask our business advisors at info@odoo.com." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:175 +#: ../../ecommerce/shopper_experience/payment.rst:109 msgid ":doc:`paypal`" msgstr ":doc:`paypal`" +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + #: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "How to collect payments with Paypal" +msgid "How to get paid with Paypal" msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:5 msgid "" -"Paypal is the easiest payment method to configure. It is also the only one " -"without any subscription free." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:9 -msgid "Setup your Paypal account" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:11 -msgid "" -"1. Create a business account at Paypal.com (see: https://www.paypal.com/in" -"/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-" -"outside) or upgrade your account to Business account (merchant) if you have " -"a basic account." +msgid "Set up your Paypal account" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:15 +#: ../../ecommerce/shopper_experience/paypal.rst:13 msgid "" -"2. Log in to your account at Paypal.com and go to :menuselection:`My Account" -" --> Profile --> My Selling Tools`. There click *PayPal button language " -"encoding* under *More Selling Tools* section. Then, click *More Options* and" -" replace the two default encoding formats by *UTF-8*." +"Create a `Paypal Business Account `__ or upgrade " +"your account to *Business account* if you have a basic account." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:20 -msgid "Open Paypal setup form in Odoo and enter your *Email ID*." +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "" +"Log in to `Paypal `__ and open the settings of your " +"**Profile**." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:22 -msgid "" -"4. The Paypal Merchant ID is not mandatory (extra verification level). It is" -" provided in Paypal under :menuselection:`My Account --> Overview`." +msgid "Now enter the menu **My selling tools**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:25 -msgid "" -"5. Configure the IPN feedback (Paypal contacting your Odoo instance without " -"needing the redirection). The setting can be found in " -":menuselection:`Profile --> My Selling Tools --> Instant payment " -"notification`. Activate it and set it to " -"/payment/paypal/ipn." +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:30 +#: ../../ecommerce/shopper_experience/paypal.rst:29 msgid "" -"6. To test the workflow, you can create sandbox accounts by logging in at " -"https://developer.paypal.com/webapps/developer/applications/myapps with the " -"same Paypal credentials. Two default sandbox accounts are automatically " -"generated when you register to Paypal: one is a buyer, the other is a " -"shopper." +"Turn on **Auto Return** and enter the **Return URL**: " +"/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:35 +#: ../../ecommerce/shopper_experience/paypal.rst:36 msgid "" -"7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com " -"(same password than real account) and apply the same format change." +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:39 +#: ../../ecommerce/shopper_experience/paypal.rst:43 msgid "" -"To automatically redirect your customers when the payment is completed, go " -"to your Website Preferences and turn *Auto Return* on. Set *Return URL* to " -"/shop/confirmation. Verify that your *Notify URL* uses " -"the correct protocol (HTTP/HTTPS)." +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "" -"If you want your customers to pay without creating a Paypal account, *Paypal" -" Account Optional* needs to be turned on." +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: /payment/paypal/ipn" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:48 +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 msgid "Transaction fees" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:50 +#: ../../ecommerce/shopper_experience/paypal.rst:114 msgid "" "You can charge an extra to the customer to cover the transaction fees Paypal" " charges you. Once redirected to Paypal, your customer sees an extra applied" " to the order amount." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:53 +#: ../../ecommerce/shopper_experience/paypal.rst:117 msgid "" -"To activate this, go to the *Configuration* tab and check *Add Extra Fees*. " -"Default fees are the ones charged by Paypal." +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site `__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox `__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:3 -msgid "How customers can access their portal" +msgid "How customers can access their customer account" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:5 msgid "" -"It has never been so easy for your customers to access their documents " -"through a portal. Forget endless signup forms, Odoo makes it as easy as ABC." -" With eCommerce and Online Quotation apps, your customers are requested to " -"create a portal account (name, email, password only) from the very first " -"order confirmation or online quotation email they get from you." +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:12 +#: ../../ecommerce/shopper_experience/portal.rst:14 msgid "Sign up" msgstr "Registrarse" -#: ../../ecommerce/shopper_experience/portal.rst:14 +#: ../../ecommerce/shopper_experience/portal.rst:16 msgid "" -"When clicking the link in the email or when clicking *Sign up* in the " -"checkout process, your customer is directed to the *Sign up* page." -msgstr "" - -#: ../../ecommerce/shopper_experience/portal.rst:21 -msgid "Customer account" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 msgid "" -"Once logged in the customer will access his account by clicking *My Account*" +"Once logged in the customer will access the account by clicking *My Account*" " in the login dropdown menu." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:29 +#: ../../ecommerce/shopper_experience/portal.rst:31 msgid "" -"From the portal menu all the customer history can be reviewed. The main " -"address (billing) can also be modified." +"THere they find all their history. The main address (billing) can also be " +"modified." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:36 +#: ../../ecommerce/shopper_experience/portal.rst:37 msgid "" -"If a portal user is a contact of a company (*Company* field set in customer " -"detail form), this last will see all the documents of the company and all " -"its other contacts through the portal." +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." msgstr "" #: ../../ecommerce/taxes.rst:3 diff --git a/locale/es/LC_MESSAGES/general.po b/locale/es/LC_MESSAGES/general.po index 5aba72237..2572b1167 100644 --- a/locale/es/LC_MESSAGES/general.po +++ b/locale/es/LC_MESSAGES/general.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Sergio Flores , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" @@ -23,8 +23,8 @@ msgid "General" msgstr "General" #: ../../general/auth.rst:3 -msgid "Authentification" -msgstr "" +msgid "Authentication" +msgstr "Autentificación" #: ../../general/auth/google.rst:3 msgid "How to allow users to sign in with their Google account" @@ -84,64 +84,196 @@ msgid "" msgstr "" #: ../../general/base_import.rst:3 -msgid "BASE IMPORT" +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" #: ../../general/base_import/import_faq.rst:3 -msgid "Import CSV file to Odoo" +msgid "How to import data into Odoo" msgstr "" -#: ../../general/base_import/import_faq.rst:8 -msgid "Frequently Asked Questions" -msgstr "Preguntas más frecuentes" +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "" -#: ../../general/base_import/import_faq.rst:12 -msgid "Need to import data from an other application?" -msgstr "¿Se necesita importar datos desde otra aplicación?" - -#: ../../general/base_import/import_faq.rst:14 +#: ../../general/base_import/import_faq.rst:7 msgid "" -"In order to re-create relationships between different records, you should " -"use the unique identifier from the original application and map it to the " -"**ID** (External ID) column in Odoo. When you import an other record that " -"links to the first one, use **XXX/ID** (XXX/External ID) to the original " -"unique identifier." +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." msgstr "" #: ../../general/base_import/import_faq.rst:16 msgid "" -"The **ID** (External ID) will also be used to update the original import if " -"you need to re-import modified data later, it's thus good practice to " -"specify it whenever possible." +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." msgstr "" -#: ../../general/base_import/import_faq.rst:21 -msgid "I cannot find the field I want to map my column to?" +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" msgstr "" -#: ../../general/base_import/import_faq.rst:23 -msgid "" -"Odoo try to find with some heuristic, based on the first ten lines of the " -"files, the type of field for each columns inside your file. For example if " -"you have a column only containing numbers, only the fields that are of type " -"integer will be displayed for you to choose from. While this behaviour might" -" be good and easy for most cases scenarios, it is also possible that it goes" -" wrong sometimes or that you want to map your column to a field that is not " -"proposed by default." +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" #: ../../general/base_import/import_faq.rst:25 -msgid "" -"If that happens, you just have to check the **Show all fields for completion" -" (advanced)** option, you will then be able to choose from the complete list" -" of fields for each columns." +msgid "We advise to not remove the **ID** one (see why in the next section)." msgstr "" -#: ../../general/base_import/import_faq.rst:30 +#: ../../general/base_import/import_faq.rst:31 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 msgid "Where can I change the date import format?" msgstr "" -#: ../../general/base_import/import_faq.rst:32 +#: ../../general/base_import/import_faq.rst:81 msgid "" "Odoo can automatically detect if a column is a date and it will try to guess" " the date format from a set of most used date format. While this process can" @@ -151,7 +283,7 @@ msgid "" " day and which one is the month in a date like '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:34 +#: ../../general/base_import/import_faq.rst:83 msgid "" "To view which date format Odoo has found from your file you can check the " "**Date Format** that is shown when clicking on **Options** under the file " @@ -159,7 +291,7 @@ msgid "" " the *ISO 8601* to define the format." msgstr "" -#: ../../general/base_import/import_faq.rst:37 +#: ../../general/base_import/import_faq.rst:86 msgid "" "If you are importing an excel (.xls, .xlsx) file, you can use date cells to " "store dates as the display of dates in excel is different from the way it is" @@ -167,11 +299,11 @@ msgid "" "whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:42 +#: ../../general/base_import/import_faq.rst:91 msgid "Can I import numbers with currency sign (e.g.: $32.00)?" msgstr "" -#: ../../general/base_import/import_faq.rst:44 +#: ../../general/base_import/import_faq.rst:93 msgid "" "Yes, we fully support numbers with parenthesis to represent negative sign as" " well as numbers with currency sign attached to them. Odoo also " @@ -181,56 +313,56 @@ msgid "" "crash." msgstr "" -#: ../../general/base_import/import_faq.rst:46 +#: ../../general/base_import/import_faq.rst:95 msgid "" "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:48 +#: ../../general/base_import/import_faq.rst:97 msgid "32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:49 +#: ../../general/base_import/import_faq.rst:98 msgid "32000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:50 +#: ../../general/base_import/import_faq.rst:99 msgid "32,000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:51 +#: ../../general/base_import/import_faq.rst:100 msgid "-32000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:52 +#: ../../general/base_import/import_faq.rst:101 msgid "(32000.00)" msgstr "" -#: ../../general/base_import/import_faq.rst:53 +#: ../../general/base_import/import_faq.rst:102 msgid "$ 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:54 +#: ../../general/base_import/import_faq.rst:103 msgid "(32000.00 €)" msgstr "" -#: ../../general/base_import/import_faq.rst:56 +#: ../../general/base_import/import_faq.rst:105 msgid "Example that will not work:" msgstr "" -#: ../../general/base_import/import_faq.rst:58 +#: ../../general/base_import/import_faq.rst:107 msgid "ABC 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:59 +#: ../../general/base_import/import_faq.rst:108 msgid "$ (32.000,00)" msgstr "" -#: ../../general/base_import/import_faq.rst:64 +#: ../../general/base_import/import_faq.rst:113 msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" -#: ../../general/base_import/import_faq.rst:66 +#: ../../general/base_import/import_faq.rst:115 msgid "" "By default the Import preview is set on commas as field separators and " "quotation marks as text delimiters. If your csv file does not have these " @@ -238,20 +370,20 @@ msgid "" " CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:68 +#: ../../general/base_import/import_faq.rst:117 msgid "" "Note that if your CSV file has a tabulation as separator, Odoo will not " "detect the separations. You will need to change the file format options in " "your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:73 +#: ../../general/base_import/import_faq.rst:122 msgid "" "How can I change the CSV file format options when saving in my spreadsheet " "application?" msgstr "" -#: ../../general/base_import/import_faq.rst:75 +#: ../../general/base_import/import_faq.rst:124 msgid "" "If you edit and save CSV files in speadsheet applications, your computer's " "regional settings will be applied for the separator and delimiter. We " @@ -260,17 +392,17 @@ msgid "" "filter settings' > Save)." msgstr "" -#: ../../general/base_import/import_faq.rst:77 +#: ../../general/base_import/import_faq.rst:126 msgid "" "Microsoft Excel will allow you to modify only the encoding when saving (in " "'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." msgstr "" -#: ../../general/base_import/import_faq.rst:82 +#: ../../general/base_import/import_faq.rst:131 msgid "What's the difference between Database ID and External ID?" msgstr "" -#: ../../general/base_import/import_faq.rst:84 +#: ../../general/base_import/import_faq.rst:133 msgid "" "Some fields define a relationship with another object. For example, the " "country of a contact is a link to a record of the 'Country' object. When you" @@ -280,58 +412,58 @@ msgid "" "import." msgstr "" -#: ../../general/base_import/import_faq.rst:86 +#: ../../general/base_import/import_faq.rst:135 msgid "" "For example, to reference the country of a contact, Odoo proposes you 3 " "different fields to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:88 +#: ../../general/base_import/import_faq.rst:137 msgid "Country: the name or code of the country" msgstr "País: el nombre o código del país" -#: ../../general/base_import/import_faq.rst:89 +#: ../../general/base_import/import_faq.rst:138 msgid "" "Country/Database ID: the unique Odoo ID for a record, defined by the ID " "postgresql column" msgstr "" -#: ../../general/base_import/import_faq.rst:90 +#: ../../general/base_import/import_faq.rst:139 msgid "" "Country/External ID: the ID of this record referenced in another application" " (or the .XML file that imported it)" msgstr "" -#: ../../general/base_import/import_faq.rst:92 +#: ../../general/base_import/import_faq.rst:141 msgid "For the country Belgium, you can use one of these 3 ways to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:94 +#: ../../general/base_import/import_faq.rst:143 msgid "Country: Belgium" msgstr "País: Bélgica" -#: ../../general/base_import/import_faq.rst:95 +#: ../../general/base_import/import_faq.rst:144 msgid "Country/Database ID: 21" msgstr "" -#: ../../general/base_import/import_faq.rst:96 +#: ../../general/base_import/import_faq.rst:145 msgid "Country/External ID: base.be" msgstr "País/Id. externo: base.be" -#: ../../general/base_import/import_faq.rst:98 +#: ../../general/base_import/import_faq.rst:147 msgid "" "According to your need, you should use one of these 3 ways to reference " "records in relations. Here is when you should use one or the other, " "according to your need:" msgstr "" -#: ../../general/base_import/import_faq.rst:100 +#: ../../general/base_import/import_faq.rst:149 msgid "" "Use Country: This is the easiest way when your data come from CSV files that" " have been created manually." msgstr "" -#: ../../general/base_import/import_faq.rst:101 +#: ../../general/base_import/import_faq.rst:150 msgid "" "Use Country/Database ID: You should rarely use this notation. It's mostly " "used by developers as it's main advantage is to never have conflicts (you " @@ -339,13 +471,13 @@ msgid "" "Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:102 +#: ../../general/base_import/import_faq.rst:151 msgid "" "Use Country/External ID: Use External ID when you import data from a third " "party application." msgstr "" -#: ../../general/base_import/import_faq.rst:104 +#: ../../general/base_import/import_faq.rst:153 msgid "" "When you use External IDs, you can import CSV files with the \"External ID\"" " column to define the External ID of each record you import. Then, you will " @@ -354,23 +486,23 @@ msgid "" "Products and their Categories." msgstr "" -#: ../../general/base_import/import_faq.rst:106 +#: ../../general/base_import/import_faq.rst:155 msgid "" "`CSV file for categories " "<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:108 +#: ../../general/base_import/import_faq.rst:157 msgid "" "`CSV file for Products " "<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:112 +#: ../../general/base_import/import_faq.rst:161 msgid "What can I do if I have multiple matches for a field?" msgstr "¿Qué puedo hacer si tengo múltiples coincidencias para un campo?" -#: ../../general/base_import/import_faq.rst:114 +#: ../../general/base_import/import_faq.rst:163 msgid "" "If for example you have two product categories with the child name " "\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " @@ -381,20 +513,20 @@ msgid "" "the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:116 +#: ../../general/base_import/import_faq.rst:165 msgid "" "However if you do not wish to change your configuration of product " "categories, we recommend you use make use of the external ID for this field " "'Category'." msgstr "" -#: ../../general/base_import/import_faq.rst:121 +#: ../../general/base_import/import_faq.rst:170 msgid "" "How can I import a many2many relationship field (e.g. a customer that has " "multiple tags)?" msgstr "" -#: ../../general/base_import/import_faq.rst:123 +#: ../../general/base_import/import_faq.rst:172 msgid "" "The tags should be separated by a comma without any spacing. For example, if" " you want your customer to be linked to both tags 'Manufacturer' and " @@ -402,19 +534,19 @@ msgid "" " of your CSV file." msgstr "" -#: ../../general/base_import/import_faq.rst:125 +#: ../../general/base_import/import_faq.rst:174 msgid "" "`CSV file for Manufacturer, Retailer " "<../../_static/example_files/m2m_customers_tags.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:130 +#: ../../general/base_import/import_faq.rst:179 msgid "" "How can I import a one2many relationship (e.g. several Order Lines of a " "Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:132 +#: ../../general/base_import/import_faq.rst:181 msgid "" "If you want to import sales order having several order lines; for each order" " line, you need to reserve a specific row in the CSV file. The first order " @@ -425,41 +557,41 @@ msgid "" "you can import, based on demo data." msgstr "" -#: ../../general/base_import/import_faq.rst:135 +#: ../../general/base_import/import_faq.rst:184 msgid "" "`File for some Quotations " "<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:137 +#: ../../general/base_import/import_faq.rst:186 msgid "" "The following CSV file shows how to import purchase orders with their " "respective purchase order lines:" msgstr "" -#: ../../general/base_import/import_faq.rst:139 +#: ../../general/base_import/import_faq.rst:188 msgid "" "`Purchase orders with their respective purchase order lines " "<../../_static/example_files/o2m_purchase_order_lines.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:141 +#: ../../general/base_import/import_faq.rst:190 msgid "" "The following CSV file shows how to import customers and their respective " "contacts:" msgstr "" -#: ../../general/base_import/import_faq.rst:143 +#: ../../general/base_import/import_faq.rst:192 msgid "" "`Customers and their respective contacts " "<../../_static/example_files/o2m_customers_contacts.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:148 +#: ../../general/base_import/import_faq.rst:197 msgid "Can I import several times the same record?" msgstr "¿Se puede importar varias veces el mismo registro?" -#: ../../general/base_import/import_faq.rst:150 +#: ../../general/base_import/import_faq.rst:199 msgid "" "If you import a file that contains one of the column \"External ID\" or " "\"Database ID\", records that have already been imported will be modified " @@ -469,17 +601,17 @@ msgid "" "depending if it's new or not." msgstr "" -#: ../../general/base_import/import_faq.rst:152 +#: ../../general/base_import/import_faq.rst:201 msgid "" "This feature allows you to use the Import/Export tool of Odoo to modify a " "batch of records in your favorite spreadsheet application." msgstr "" -#: ../../general/base_import/import_faq.rst:157 +#: ../../general/base_import/import_faq.rst:206 msgid "What happens if I do not provide a value for a specific field?" msgstr "" -#: ../../general/base_import/import_faq.rst:159 +#: ../../general/base_import/import_faq.rst:208 msgid "" "If you do not set all fields in your CSV file, Odoo will assign the default " "value for every non defined fields. But if you set fields with empty values " @@ -487,11 +619,11 @@ msgid "" "assigning the default value." msgstr "" -#: ../../general/base_import/import_faq.rst:164 +#: ../../general/base_import/import_faq.rst:213 msgid "How to export/import different tables from an SQL application to Odoo?" msgstr "" -#: ../../general/base_import/import_faq.rst:166 +#: ../../general/base_import/import_faq.rst:215 msgid "" "If you need to import data from different tables, you will have to recreate " "relations between records belonging to different tables. (e.g. if you import" @@ -499,7 +631,7 @@ msgid "" "person and the company they work for)." msgstr "" -#: ../../general/base_import/import_faq.rst:168 +#: ../../general/base_import/import_faq.rst:217 msgid "" "To manage relations between tables, you can use the \"External ID\" " "facilities of Odoo. The \"External ID\" of a record is the unique identifier" @@ -509,7 +641,7 @@ msgid "" "'company_1', 'person_1' instead of '1')" msgstr "" -#: ../../general/base_import/import_faq.rst:170 +#: ../../general/base_import/import_faq.rst:219 msgid "" "As an example, suppose you have a SQL database with two tables you want to " "import: companies and persons. Each person belong to one company, so you " @@ -519,27 +651,27 @@ msgid "" "PostgreSQL database)" msgstr "" -#: ../../general/base_import/import_faq.rst:172 +#: ../../general/base_import/import_faq.rst:221 msgid "" "We will first export all companies and their \"External ID\". In PSQL, write" " the following command:" msgstr "" -#: ../../general/base_import/import_faq.rst:178 +#: ../../general/base_import/import_faq.rst:227 msgid "This SQL command will create the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:185 +#: ../../general/base_import/import_faq.rst:234 msgid "" "To create the CSV file for persons, linked to companies, we will use the " "following SQL command in PSQL:" msgstr "" -#: ../../general/base_import/import_faq.rst:191 +#: ../../general/base_import/import_faq.rst:240 msgid "It will produce the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:199 +#: ../../general/base_import/import_faq.rst:248 msgid "" "As you can see in this file, Fabien and Laurence are working for the Bigees " "company (company_1) and Eric is working for the Organi company. The relation" @@ -549,7 +681,7 @@ msgid "" " who shared the same ID 1 in the orignial database)." msgstr "" -#: ../../general/base_import/import_faq.rst:201 +#: ../../general/base_import/import_faq.rst:250 msgid "" "The two files produced are ready to be imported in Odoo without any " "modifications. After having imported these two CSV files, you will have 4 " diff --git a/locale/es/LC_MESSAGES/inventory.po b/locale/es/LC_MESSAGES/inventory.po index d669fc034..64ababf63 100644 --- a/locale/es/LC_MESSAGES/inventory.po +++ b/locale/es/LC_MESSAGES/inventory.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Julián Andrés Osorio López , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" @@ -920,6 +920,10 @@ msgstr "" "Crear ** para establecer los valores de las existencias mínimas y máximas " "para un producto determinado." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "Activo" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "If the active field is set to False, it will allow you to hide the " @@ -928,11 +932,19 @@ msgstr "" "Si el campo activo se desmarca, permite ocultar la regla de stock mínimo sin" " eliminarla." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "Unidad de medida del producto" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Default Unit of Measure used for all stock operation." msgstr "" "Unidad de medida por defecto utilizada para todas las operaciones de stock." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "Grupo de abastecimiento" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Moves created through this orderpoint will be put in this procurement group." @@ -944,6 +956,10 @@ msgstr "" "movimientos generados por las reglas de abastecimiento serán agrupados en un" " gran albarán." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "Cantidad mínima" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity specified for this field," @@ -954,6 +970,10 @@ msgstr "" "especificada en este campo, Odoo generará un abastecimiento para llevar la " "cantidad prevista a la cantidad máxima." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "Cantidad máxima" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity, Odoo generates a " @@ -964,6 +984,10 @@ msgstr "" "generará un abastecimiento para llevar la cantidad prevista a la cantidad " "especificada como aquí como máxima." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "Múltiplo de la cantidad" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "The procurement quantity will be rounded up to this multiple. If it is 0, " @@ -972,6 +996,10 @@ msgstr "" "La cantidad a abastecer se redondeará a este múltiplo. Si es 0, se utilizará" " la cantidad exacta." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "Plazo de entrega" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Number of days after the orderpoint is triggered to receive the products or " diff --git a/locale/es/LC_MESSAGES/legal.po b/locale/es/LC_MESSAGES/legal.po deleted file mode 100644 index d5423a435..000000000 --- a/locale/es/LC_MESSAGES/legal.po +++ /dev/null @@ -1,2021 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Inigo Zuluaga , 2017\n" -"Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: es\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../legal.rst:5 -msgid "Legal" -msgstr "" - -#: ../../legal.rst:15 ../../legal/licenses.rst:5 -#: ../../legal/licenses/licenses.rst:6 -msgid "Licenses" -msgstr "" - -#: ../../legal.rst:17 -msgid ":ref:`licenses`" -msgstr "" - -#: ../../legal.rst:20 ../../legal/terms.rst:5 -msgid "Terms and Conditions" -msgstr "Términos y condiciones" - -#: ../../legal.rst:38 -msgid ":ref:`enterprise_agreement` |nbsp| |nbsp| |download_enterprise|" -msgstr "" - -#: ../../legal.rst:40 -msgid ":ref:`enterprise_agreement_fr` |nbsp| |nbsp| |download_enterprise_fr|" -msgstr "" - -#: ../../legal.rst:47 ../../legal/others.rst:5 -msgid "Other legal references" -msgstr "" - -#: ../../legal.rst:49 -msgid "" -"`Odoo Online Service Level Agreement `_" -msgstr "" - -#: ../../legal.rst:50 -msgid "" -"`Odoo Online Acceptable Use Policy `_" -msgstr "" - -#: ../../legal.rst:51 -msgid ":ref:`cla`" -msgstr "" - -#: ../../legal/licenses/licenses.rst:11 -msgid "Odoo 10 Community Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:13 -msgid "" -"Odoo 10 Community Edition is licensed under `LGPL version 3 " -"`_ (also known as LGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/licenses/licenses.rst:22 -msgid "Odoo 10 Enterprise Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:24 -msgid "" -"Odoo 10 Enterprise Edition is licensed under the Odoo Enterprise Edition " -"License v1.0, defined as follows:" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:1 -#: ../../legal/terms/i18n/enterprise_fr.rst:487 -msgid "Odoo Enterprise Edition License v1.0" -msgstr "Licencia edición empresarial Odoo v1.0" - -#: ../../legal/licenses/enterprise_license.txt:3 -msgid "" -"This software and associated files (the \"Software\") can only be used " -"(executed, modified, executed after modifications) with a valid Odoo " -"Enterprise Subscription for the correct number of users." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:7 -msgid "" -"With a valid Partnership Agreement with Odoo S.A., the above permissions are" -" also granted, as long as the usage is limited to a testing or development " -"environment." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:11 -msgid "" -"You may develop Odoo modules based on the Software and distribute them under" -" the license of your choice, provided that it is compatible with the terms " -"of the Odoo Enterprise Edition License (For example: LGPL, MIT, or " -"proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:16 -msgid "" -"You may use Odoo modules published under any license along with the " -"Software, provided that their license is compatible with the terms of the " -"Odoo Enterprise License (Including, but not limited to, any module published" -" on the Odoo Apps Store on odoo.com/apps)" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:21 -#: ../../legal/licenses/licenses.rst:69 -msgid "" -"It is forbidden to publish, distribute, sublicense, or sell copies of the " -"Software or modified copies of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:24 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:27 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE" -" AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM," -" OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN " -"THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:43 -msgid "Odoo Apps" -msgstr "" - -#: ../../legal/licenses/licenses.rst:45 -msgid "" -"Unless otherwise stated, Odoo Apps by Odoo SA (including the website themes)" -" are published under the Odoo Proprietary License v1.0, defined as follows" -msgstr "" - -#: ../../legal/licenses/licenses.rst:54 -msgid "Odoo Proprietary License v1.0" -msgstr "Licencia Propietario Odoo v1.0" - -#: ../../legal/licenses/licenses.rst:56 -msgid "" -"This software and associated files (the \"Software\") may only be used " -"(executed, modified, executed after modifications) if you have purchased a " -"valid license from the authors, typically via Odoo Apps, or if you have " -"received a written agreement from the authors of the Software (see the " -"COPYRIGHT file)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:62 -msgid "" -"You may develop Odoo modules that use the Software as a library (typically " -"by depending on it, importing it and using its resources), but without " -"copying any source code or material from the Software. You may distribute " -"those modules under the license of your choice, provided that this license " -"is compatible with the terms of the Odoo Proprietary License (For example: " -"LGPL, MIT, or proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:72 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/licenses.rst:75 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " -"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " -"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS" -" IN THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:91 -msgid "Odoo 9" -msgstr "" - -#: ../../legal/licenses/licenses.rst:93 -msgid "" -"The licenses for both editions of Odoo 9 were respectively the same as for " -":ref:`odoo_community_license` and :ref:`odoo_enterprise_license`." -msgstr "" - -#: ../../legal/licenses/licenses.rst:100 -msgid "Odoo 8" -msgstr "" - -#: ../../legal/licenses/licenses.rst:102 -msgid "" -"Odoo 8 is licensed under `AGPL version 3 " -"`_ (also known as AGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/others/cla.rst:5 -msgid "Contributor License Agreement" -msgstr "" - -#: ../../legal/others/cla.rst:7 -msgid "" -"In order to contribute to any of the Odoo projects, companies and " -"individuals have to sign the Odoo Contributor License Agreement (CLA)." -msgstr "" - -#: ../../legal/others/cla.rst:10 -msgid "" -"More information about this requirement, the procedure to sign the " -"agreement, and a FAQ can be found on our `GitHub project page " -"`_." -msgstr "" - -#: ../../legal/others/privacy.rst:5 -msgid "Privacy Policy" -msgstr "" - -#: ../../legal/others/privacy.rst:7 -msgid "" -"Temporary version at ``__ " -"(needs cleanup)" -msgstr "" - -#: ../../legal/terms/enterprise.rst:6 -msgid "Odoo Enterprise Subscription Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:8 -msgid "Version 5b - Last revision: June 30, 2016." -msgstr "" - -#: ../../legal/terms/enterprise.rst:10 -msgid "" -"By subscribing to the Odoo Enterprise services (the \"Services\") provided " -"by Odoo SA and its affiliates (collectively, \"Odoo SA\") in relation with " -"Odoo Enterprise Edition or Odoo Community Edition (the \"Software\"), you " -"(the \"Customer\") are agreeing to be bound by the following terms and " -"conditions (the \"Agreement\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:18 -msgid "1 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:20 -msgid "" -"The duration of this Agreement (the “Term”) shall be minimally one year and " -"as specified in writing at the signature of this Agreement, beginning on the" -" date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term by registered mail to the other party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:28 -msgid "2 Definitions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:34 -msgid "User" -msgstr "Usuario" - -#: ../../legal/terms/enterprise.rst:31 -msgid "" -"Any active user account with access to the Software in creation and/or " -"edition mode. Deactivated user accounts and accounts used by external people" -" (or systems) who only have limited access to the Software through the " -"portal facilities (known as \"portal Users\") are not counted as Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:42 -#: ../../legal/terms/i18n/enterprise_fr.rst:55 -msgid "Bug" -msgstr "" - -#: ../../legal/terms/enterprise.rst:37 -msgid "" -"Is considered a Bug any failure of the Software that results in a complete " -"stop, error traceback or security breach, and is not directly caused by a " -"defective installation or configuration. Non-compliance with specifications " -"or requirements will be considered as Bugs at the discretion of Odoo SA " -"(typically, when the Software does not produce the results or performance it" -" was designed to produce, or when a country-specific feature does not meet " -"legal accounting requirements anymore)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:51 -msgid "Covered Versions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:45 -msgid "" -"All Services provided under this Agreement are applicable only to the " -"Covered Versions of the Software, which include the 3 (three) most recently " -"released major versions." -msgstr "" - -#: ../../legal/terms/enterprise.rst:48 -msgid "" -"To be covered by the current Agreement, Customer’s installations have to run" -" the most recent Covered Version at the time of this Agreement’s signature. " -"When this is not the case, additional costs are applicable, as described in " -":ref:`charges`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:56 ../../legal/terms/partnership.rst:42 -msgid "3 Access to Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/enterprise.rst:58 -msgid "" -"For the duration of this Agreement, Odoo SA gives the Customer a non-" -"exclusive, non-transferable license to use (execute, modify, execute after " -"modification) the Odoo Enterprise Edition software, under the terms set " -"forth in :ref:`appendix_a`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:62 -msgid "" -"The Customer agrees to take all necessary measures to guarantee the " -"unmodified execution of the part of the Software that verifies the validity " -"of the Odoo Enterprise Edition usage and collects statistics for that " -"purpose, including but not limited to the running of an instance and the " -"number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:67 -msgid "" -"Odoo SA commits not to disclose individual or named figures to third parties" -" without the consent of the Customer, and to deal with all collected data in" -" compliance with its official Privacy Policy, as published on `Odoo SA's " -"website `_." -msgstr "" - -#: ../../legal/terms/enterprise.rst:71 -msgid "" -"Upon expiration or termination of this Agreement, this license is revoked " -"immediately and the Customer agrees to stop using the Odoo Enterprise " -"Edition software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:74 -msgid "" -"Should the Customer breach the terms of this section, the Customer agrees to" -" pay Odoo SA an extra fee equal to 300% of the applicable list price for the" -" actual number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:81 -msgid "4 Included Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:84 -msgid "4.1 Bug Fixing Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:86 -msgid "" -"For the duration of this Agreement, Odoo SA commits to making all reasonable" -" efforts to remedy any Bug of the Software submitted by the Customer through" -" the appropriate channel (typically, Odoo SA's service desk email address or" -" website form), and to start handling such Customer submissions within 2 " -"business days." -msgstr "" - -#: ../../legal/terms/enterprise.rst:91 -msgid "" -"The Customer understands that Bugs caused by a modification or extension " -"that is not part of the official Software will not be covered by this " -"service." -msgstr "" - -#: ../../legal/terms/enterprise.rst:94 -msgid "" -"As soon as the Bug is fixed an appropriate remedy will be communicated to " -"the Customer. If the bug has been addressed in a more recent revision of the" -" Covered Version of the Software used by the Customer, the Customer agrees " -"to update its systems to that revision in order to obtain the correction. " -"The Customer will not be asked to upgrade to a more recent Covered Version " -"of the Software as a remedy to a Bug." -msgstr "" - -#: ../../legal/terms/enterprise.rst:100 -msgid "" -"When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the " -"Bug in all more recent Covered Versions of the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:103 -msgid "" -"Both parties acknowledge that as specified in the license of the Software " -"and in the :ref:`liability` section of this Agreement, Odoo SA cannot be " -"held liable for Bugs in the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:108 -msgid "4.2 Security Advisories Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:110 -msgid "" -"For the duration of this Agreement, Odoo SA commits to sending a \"Security " -"Advisory\" to the Customer for any security Bug that are discovered in the " -"Covered Versions of the Software, at least 2 weeks before making the " -"Security Advisory public, unless the Bug has already been disclosed publicly" -" by a third party. Security Advisories include a complete description of the" -" Bug, its cause, its possible impacts on the Customer's systems, and the " -"corresponding remedy for each Covered Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:117 -msgid "" -"The Customer understands that the Bug and the information in the Security " -"Advisory must be treated are Confidential Information as described in " -":ref:`confidentiality` during the embargo period prior to the public " -"disclosure." -msgstr "" - -#: ../../legal/terms/enterprise.rst:124 -msgid "4.3 Upgrade Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:129 -msgid "Upgrade Service for the Software" -msgstr "" - -#: ../../legal/terms/enterprise.rst:131 -msgid "" -"For the duration of this Agreement, the Customer can submit upgrade requests" -" through the appropriate channel (typically Odoo SA's upgrade service " -"website), in order to convert a database of the Software from one Covered " -"Version of the Software to a more recent Covered Version (the \"Target " -"Version\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:135 -msgid "" -"Upgrade requests must include a complete backup copy of the Customer's " -"database and the associated data (typically obtained from the Backup menu of" -" the Software). Where necessary for data security or regulation reasons, the" -" Upgrade Service includes an optional tool to anonymize identifiable data " -"inside a database before submitting the upgrade request, and a tool to " -"restore the anonymized data after the upgrade." -msgstr "" - -#: ../../legal/terms/enterprise.rst:141 -msgid "" -"This service provided through an automated platform in order to allow the " -"Customer to perform unattended upgrades once a previous version of the " -"Customer's database has been successfully upgraded for a Covered Version. " -"The Customer may submit successive upgrade requests for a database, and " -"agrees to submit at least 1 upgrade request for testing purposes before " -"submitting the final upgrade request." -msgstr "" - -#: ../../legal/terms/enterprise.rst:147 -msgid "" -"The Upgrade Service is limited to the technical conversion and adaptation of" -" the Customer's database to make it compatible with the Target Version, and " -"the correction of any Bug directly caused by the upgrade operation and not " -"normally occurring in the Target Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:151 -msgid "" -"It is the sole responsibility of the Customer to verify and validate the " -"upgraded database in order to detect Bugs, to analyze the impact of changes " -"and new features implemented in the Target Version, and to convert and adapt" -" for the Target Version any third-party extensions of the Software that were" -" installed in the database before the upgrade (except where applicable as " -"foreseen in section :ref:`upgrade_extra`). The Customer may submit multiple " -"upgrade requests for a database, until an acceptable result is achieved." -msgstr "" - -#: ../../legal/terms/enterprise.rst:162 -msgid "Upgrade Service for third-party extensions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:164 -msgid "" -"For the duration of this Agreement, the Customer may request optional " -"upgrade services for third-party extension modules of the Software, in " -"addition to the regular Upgrade Services. This optional service is subject " -"to additional fees (as described in charges_) and includes the technical " -"adaptation of third-party modules installed in the Customer's database and " -"their corresponding data in order to be compatible with the Target Version. " -"The Customer will receive an upgraded version of all installed third-party " -"modules along with the upgraded database." -msgstr "" - -#: ../../legal/terms/enterprise.rst:174 -msgid "5 Charges and Fees" -msgstr "" - -#: ../../legal/terms/enterprise.rst:179 -msgid "5.1 Standard charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:181 -msgid "" -"The standard charges for the Odoo Enterprise subscription, the Bug Fixing " -"Service, Security Advisories Service and the Upgrade Service are based on " -"the number of Users and the Software version used by the Customer, and " -"specified in writing at the signature of the Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:185 -msgid "" -"When during the Term, the Customer has more Users than specified at the time" -" of signature of this Agreement, the Customer agrees to pay an extra fee " -"equivalent to the applicable list price (at the beginning of the Term) for " -"the additional Users, for the remainder of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:189 -msgid "" -"If at the time of the signature of this Agreement, the Customer uses a " -"Covered Version that is not the most recent one, the standard charges will " -"be increased by 50% for the duration of the first Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:196 -msgid "5.2 Renewal charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:198 -msgid "" -"Upon renewal as covered in section :ref:`term`, if the per-User charges " -"applied during the previous Term are lower than the most current applicable " -"per-User list price, the per-User charges will increase by up to 7%, unless " -"Odoo SA provides written notice of a new price to the Customer at least 60 " -"days prior to the end of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:207 -msgid "5.3 Charges for Upgrade Services of third-party modules" -msgstr "" - -#: ../../legal/terms/enterprise.rst:211 -msgid "" -"The additional charge for the Upgrade Service for third-party modules is EUR" -" (€) 1000.00 (one thousand euros) per 1000 Lines of Code in the third-party " -"modules, rounded up to the next thousand lines. Lines of Code include all " -"text lines in the source code of those modules, regardless of the " -"programming language (Python, Javascript, etc.) or data format (XML, CSV, " -"etc.), excluding blank lines and comment lines." -msgstr "" - -#: ../../legal/terms/enterprise.rst:217 -msgid "" -"Odoo SA reserves the right to reject an upgrade request for third-party " -"modules under the above conditions if the quality of the source code of " -"those modules is too low, or if these modules constitute an interface with " -"third-party software or systems. The upgrade of such modules will subject to" -" a separate offer, outside of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:225 -msgid "5.4 Taxes" -msgstr "" - -#: ../../legal/terms/enterprise.rst:229 -msgid "" -"All fees and charges are exclusive of all applicable federal, provincial, " -"state, local or other governmental taxes, fees or charges (collectively, " -"\"Taxes\"). The Customer is responsible for paying all Taxes associated with" -" purchases made by the Customer under this Agreement, except when Odoo SA is" -" legally obliged to pay or collect Taxes for which the Customer is " -"responsible." -msgstr "" - -#: ../../legal/terms/enterprise.rst:238 -msgid "6 Conditions of Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:241 -msgid "6.1 Customer Obligations" -msgstr "" - -#: ../../legal/terms/enterprise.rst:245 -msgid "The Customer agrees to:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:247 -msgid "" -"pay Odoo SA any applicable charges for the Services of the present " -"Agreement, in accordance with the payment conditions specified in the " -"corresponding invoice ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:249 -msgid "" -"immediately notify Odoo SA when the actual number of Users exceeds the " -"number of Users specified at the signature of the Agreement, and in this " -"event, pay the applicable additional fee as described in section " -":ref:`charges_standard`;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:252 -msgid "" -"take all measures necessary to guarantee the unmodified execution of the " -"part of the Software that verifies the validity of the Odoo Enterprise " -"Edition usage, as described in :ref:`enterprise_access` ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:255 -msgid "" -"grant Odoo SA the necessary access to verify the validity of the Odoo " -"Enterprise Edition usage upon request (e.g. if the automatic validation is " -"found to be inoperant for the Customer);" -msgstr "" - -#: ../../legal/terms/enterprise.rst:257 -msgid "" -"appoint 1 dedicated Customer contact person for the entire duration of the " -"Agreement;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:258 -msgid "" -"take all reasonable measures to protect Customer’s files and databases and " -"to ensure Customer’s data is safe and secure, acknowledging that Odoo SA " -"cannot be held liable for any data loss;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:265 -msgid "6.2 No Soliciting or Hiring" -msgstr "" - -#: ../../legal/terms/enterprise.rst:267 -msgid "" -"Except where the other party gives its consent in writing, each party, its " -"affiliates and representatives agree not to solicit or offer employment to " -"any employee of the other party who is involved in performing or using the " -"Services under this Agreement, for the duration of the Agreement and for a " -"period of 12 months from the date of termination or expiration of this " -"Agreement. In case of any breach of the conditions of this section that " -"leads to the termination of said employee toward that end, the breaching " -"party agrees to pay to the other party an amount of EUR (€) 30 000.00 " -"(thirty thousand euros)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:279 -msgid "6.3 Publicity" -msgstr "" - -#: ../../legal/terms/enterprise.rst:281 -msgid "" -"Except where notified otherwise in writing, each party grants the other a " -"non-transferable, non-exclusive, royalty free, worldwide license to " -"reproduce and display the other party’s name, logos and trademarks, solely " -"for the purpose of referring to the other party as a customer or supplier, " -"on websites, press releases and other marketing materials." -msgstr "" - -#: ../../legal/terms/enterprise.rst:290 -msgid "6.4 Confidentiality" -msgstr "" - -#: ../../legal/terms/enterprise.rst:298 -msgid "Definition of \"Confidential Information\":" -msgstr "" - -#: ../../legal/terms/enterprise.rst:293 -msgid "" -"All information disclosed by a party (the \"Disclosing Party\") to the other" -" party (the \"Receiving Party\"), whether orally or in writing, that is " -"designated as confidential or that reasonably should be understood to be " -"confidential given the nature of the information and the circumstances of " -"disclosure. In particular any information related to the business, affairs, " -"products, developments, trade secrets, know-how, personnel, customers and " -"suppliers of either party should be regarded as confidential." -msgstr "" - -#: ../../legal/terms/enterprise.rst:300 -msgid "" -"For all Confidential Information received during the Term of this Agreement," -" the Receiving Party will use the same degree of care that it uses to " -"protect the confidentiality of its own similar Confidential Information, but" -" not less than reasonable care." -msgstr "" - -#: ../../legal/terms/enterprise.rst:304 -msgid "" -"The Receiving Party may disclose Confidential Information of the Disclosing " -"Party to the extent compelled by law to do so, provided the Receiving Party " -"gives the Disclosing Party prior notice of the compelled disclosure, to the " -"extent permitted by law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:311 -msgid "6.5 Termination" -msgstr "" - -#: ../../legal/terms/enterprise.rst:313 -msgid "" -"In the event that either Party fails to fulfill any of its obligations " -"arising herein, and if such breach has not been remedied within 30 calendar " -"days from the written notice of such breach, this Agreement may be " -"terminated immediately by the non-breaching Party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:317 -msgid "" -"Further, Odoo SA may terminate the Agreement immediately in the event the " -"Customer fails to pay the applicable fees for the Services within the due " -"date specified on the corresponding invoice." -msgstr "" - -#: ../../legal/terms/enterprise.rst:324 -msgid "Surviving Provisions:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:321 -msgid "" -"The sections \":ref:`confidentiality`”, “:ref:`disclaimers`”, " -"“:ref:`liability`”, and “:ref:`general_provisions`” will survive any " -"termination or expiration of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:329 -msgid "7 Warranties, Disclaimers, Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:334 -msgid "7.1 Warranties" -msgstr "" - -#: ../../legal/terms/enterprise.rst:338 -msgid "" -"For the duration of this Agreement, Odoo SA commits to using commercially " -"reasonable efforts to execute the Services in accordance with the generally " -"accepted industry standards provided that:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:341 -msgid "" -"the Customer’s computing systems are in good operational order and the " -"Software is installed in a suitable operating environment;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:343 -msgid "" -"the Customer provides adequate troubleshooting information and access so " -"that Odoo SA can identify, reproduce and address problems;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:345 -msgid "all amounts due to Odoo SA have been paid." -msgstr "" - -#: ../../legal/terms/enterprise.rst:347 -msgid "" -"The Customer's sole and exclusive remedy and Odoo SA's only obligation for " -"any breach of this warranty is for Odoo SA to resume the execution of the " -"Services at no additional charge." -msgstr "" - -#: ../../legal/terms/enterprise.rst:353 -msgid "7.2 Disclaimers" -msgstr "" - -#: ../../legal/terms/enterprise.rst:357 -msgid "" -"Except as expressly provided herein, neither party makes any warranty of any" -" kind, whether express, implied, statutory or otherwise, and each party " -"specifically disclaims all implied warranties, including any implied " -"warranty of merchantability, fitness for a particular purpose or non-" -"infringement, to the maximum extent permitted by applicable law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:362 -msgid "" -"Odoo SA does not warrant that the Software complies with any local or " -"international law or regulations." -msgstr "" - -#: ../../legal/terms/enterprise.rst:367 -msgid "7.3 Limitation of Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:369 -msgid "" -"To the maximum extent permitted by law, the aggregate liability of each " -"party together with its affiliates arising out of or related to this " -"Agreement will not exceed 50% of the total amount paid by the Customer under" -" this Agreement during the 12 months immediately preceding the date of the " -"event giving rise to such claim. Multiple claims shall not enlarge this " -"limitation." -msgstr "" - -#: ../../legal/terms/enterprise.rst:374 -msgid "" -"In no event will either party or its affiliates be liable for any indirect, " -"special, exemplary, incidental or consequential damages of any kind, " -"including but not limited to loss of revenue, profits, savings, loss of " -"business or other financial loss, costs of standstill or delay, lost or " -"corrupted data, arising out of or in connection with this Agreement " -"regardless of the form of action, whether in contract, tort (including " -"strict negligence) or any other legal or equitable theory, even if a party " -"or its affiliates have been advised of the possibility of such damages, or " -"if a party or its affiliates' remedy otherwise fails of its essential " -"purpose." -msgstr "" - -#: ../../legal/terms/enterprise.rst:385 -#: ../../legal/terms/i18n/enterprise_fr.rst:418 -msgid "7.4 Force Majeure" -msgstr "" - -#: ../../legal/terms/enterprise.rst:387 -msgid "" -"Neither party shall be liable to the other party for the delay in any " -"performance or failure to render any performance under this Agreement when " -"such failure or delay is caused by governmental regulations, fire, strike, " -"war, flood, accident, epidemic, embargo, appropriation of plant or product " -"in whole or in part by any government or public authority, or any other " -"cause or causes, whether of like or different nature, beyond the reasonable " -"control of such party as long as such cause or causes exist." -msgstr "" - -#: ../../legal/terms/enterprise.rst:398 -msgid "8 General Provisions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:403 -msgid "8.1 Governing Law" -msgstr "" - -#: ../../legal/terms/enterprise.rst:405 -msgid "" -"Both parties agree that the laws of Belgium will apply, should any dispute " -"arise out of or in connection with this Agreement, without regard to choice " -"or conflict of law principles. To the extent that any lawsuit or court " -"proceeding is permitted hereinabove, both parties agree to submit to the " -"sole jurisdiction of the Nivelles (Belgium) court for the purpose of " -"litigating all disputes." -msgstr "" - -#: ../../legal/terms/enterprise.rst:414 -msgid "8.2 Severability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:416 -msgid "" -"In case any one or more of the provisions of this Agreement or any " -"application thereof shall be invalid, illegal or unenforceable in any " -"respect, the validity, legality and enforceability of the remaining " -"provisions of this Agreement and any application thereof shall be in no way " -"thereby affected or impaired. Both parties undertake to replace any invalid," -" illegal or unenforceable provision of this Agreement by a valid provision " -"having the same effects and objectives." -msgstr "" - -#: ../../legal/terms/enterprise.rst:427 -msgid "9 Appendix A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:6 -msgid "Odoo Enterprise Subscription Agreement (FR)" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:9 -msgid "" -"Ceci est une traduction en français du contrat “Odoo Enterprise Subscription" -" Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera " -"sa compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes du contrat “Odoo Enterprise Subscription Agreement” " -"est la :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:15 -msgid "" -"This is a french translation of the \"Odoo Enterprise Subscription " -"Agreement”. This translation is provided in the hope that it will facilitate" -" understanding, but it has no legal value. The only official reference of " -"the terms and conditions of the “Odoo Enterprise Subscription Agreement” is " -"the :ref:`original english version `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:21 -msgid "Version 5b - Dernière modification: 30 juin 2016." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:23 -msgid "" -"En vous abonnant aux services de Odoo Enterprise (les \"Services\") fournis " -"par Odoo SA et ses filiales (collectivement, \"Odoo SA\") en relation avec " -"Odoo Enterprise Edition ou Odoo Community Edition (le \"Logiciel\"), vous " -"(le \"Client\") acceptez d'être lié par les conditions générales suivantes " -"(le \"Contrat\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:31 -msgid "1 Durée du Contrat" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:33 -msgid "" -"La durée du présent contrat (la \"Durée\") doit être au minimum d'un an et " -"telle que spécifiée par écrit à la signature du Contrat, à compter de la " -"date de la signature. Celui-ci est automatiquement reconduit pour une même " -"durée, à moins que l'une des parties n’envoie à l'autre partie un préavis " -"écrit de résiliation, par lettre recommandée, et au moins 30 jours avant la " -"date d'échéance du contrat ." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:41 -msgid "2 Définitions" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:47 -msgid "Utilisateur" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:44 -msgid "" -"Tout compte utilisateur actif donnant accès au Logiciel en mode création " -"et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des " -"personnes ou systèmes extérieur(e)s n'ayant qu'un accès limité au Logiciel " -"via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme " -"Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:50 -msgid "" -"Désigne toute défaillance du Logiciel qui se traduit par un arrêt complet, " -"un message d'erreur avec trace d'exécution, ou une brèche de sécurité, et " -"n'est pas directement causé par un problème d'installation ou une " -"configuration défectueuse. Un non-respect des spécifications ou des besoins " -"sera considéré comme un Bug à la discrétion d'Odoo SA (en général, lorsque " -"le Logiciel ne produit pas les résultats ou la performance pour lesquels il " -"a été conçu, ou lorsqu'une fonctionnalité spécifique à un pays ne répond " -"plus aux exigences comptables légales de ce pays)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:65 -msgid "Versions Couvertes" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:58 -msgid "" -"Tous les Services dans le cadre du présent contrat s'appliquent uniquement " -"aux Versions Couvertes du Logiciel, qui comprennent les trois (3) plus " -"récentes versions majeures." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:61 -msgid "" -"Afin d'être considérées comme couvertes par le Contrat, les installations du" -" client doivent utiliser la Version couverte la plus récente au moment de " -"la signature du Contrat. Dans le cas contraire, des frais supplémentaires " -"sont d'application, tels que décrit dans la section :ref:`charges_fr`" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:70 -msgid "3 Accès à Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:72 -msgid "" -"Pour toute la durée du présent Contrat, Odoo SA octroie au Client une " -"licence non exclusive, non transférable d'utilisation (exécution, " -"modification, exécution après modification) du logiciel Odoo Enterprise " -"Edition, conformément aux conditions énoncées à la section " -":ref:`appendix_a_fr`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:76 -msgid "" -"Le Client accepte de prendre toutes les mesures nécessaires pour garantir " -"l'exécution sans aucune modification de la partie du Logiciel qui vérifie la" -" validité de l'utilisation d'Odoo Enterprise Edition et recueille des " -"statistiques à cet effet, y compris mais sans s'y limiter, l'exécution du " -"Logiciel et le nombre d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:81 -msgid "" -"Odoo SA s'engage à ne pas divulguer à une tierce partie d'informations " -"chiffrées personnelles ou spécifiques sans le consentement du Client, et à " -"traiter toutes les données recueillies en respectant sa politique officielle" -" de confidentialité, telle que publiée sur `le site web d'Odoo SA " -"`_." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:86 -msgid "" -"À l'expiration ou la résiliation de ce Contrat, cette licence est " -"immédiatement révoquée et le Client accepte de cesser toute utilisation du " -"logiciel Odoo Enterprise Edition." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:89 -msgid "" -"Si le Client devait enfreindre les dispositions de la présente section, il " -"accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du " -"tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:97 -msgid "4 Services inclus" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:100 -msgid "4.1 Service de correction de Bugs" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:102 -msgid "" -"Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts " -"raisonnables pour corriger tout Bug du Logiciel qui pourrait être signalé " -"par le Client en suivant la procédure appropriée (généralement par le biais " -"d'un e-mail adressé au service d'assistance d'Odoo SA ou via le formulaire " -"correspondant sur le site web), et de commencer à traiter ces signalements " -"du Client dans un délai de 2 jours ouvrables." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:108 -msgid "" -"Le Client accepte que les Bugs causés par toute modification ou extension " -"qui ne fait pas partie de la version officielle du Logiciel ne seront pas " -"couverts par ce service." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:111 -msgid "" -"Dès que le Bug est remédié, un correctif approprié sera communiqué au " -"Client. Si le Bug a été résolu dans une nouvelle mise à jour de la Version " -"Couverte du Logiciel utilisée par le Client, ce dernier s'engage à " -"actualiser ses systèmes vers la nouvelle mise à jour, afin d'obtenir le " -"correctif. Il ne sera jamais demandé au Client de passer à une Version " -"Couverte plus récente pour obtenir un correctif." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:117 -msgid "" -"Lorsqu'un Bug est corrigé dans une Version Couverte, Odoo SA s'engage à le " -"corriger dans toutes les Versions Couvertes plus récentes du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:120 -msgid "" -"Les deux parties reconnaissent que comme spécifié dans la licence du " -"Logiciel et à la section :ref:`liability_fr` de ce Contrat, Odoo SA ne peut " -"être tenue responsable des Bugs du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:125 -msgid "4.2 Service d'alertes de sécurité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:127 -msgid "" -"Pour la durée du Contrat, Odoo SA s'engage à envoyer une \"alerte de " -"sécurité\"\" au Client pour tout Bug présentant un risque de sécurité qui " -"serait découvert dans les Versions Couvertes du Logiciel, au moins 2 " -"semaines avant de rendre ladite alerte de sécurité publique, et ce à moins " -"que le Bug ait déjà été rendu public par un tiers. Les alertes de sécurité " -"comprennent une description complète du Bug, de sa cause, ses conséquences " -"possibles sur les systèmes du Client, et le correctif correspondant pour " -"chaque Version Couverte." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:134 -msgid "" -"Le Client s'engage à traiter le Bug de sécurité et les informations figurant" -" dans l'alerte de sécurité comme des Informations Confidentielles telles que" -" décrites à la section :ref:`confidentiality_fr` pendant toute la période " -"d'embargo avant la divulgation publique." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:141 -msgid "4.3 Service de migration" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:146 -msgid "Service de migration du Logiciel" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:148 -msgid "" -"Pour la durée du présent Contrat, le Client peut soumettre des demandes de " -"migration en suivant les procédures appropriées (généralement, via le site " -"du service de migration d'Odoo SA), afin de convertir une base de données du" -" Logiciel d'une Version Couverte du Logiciel à une Version Couverte plus " -"récente (la \"Version Cible\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:153 -msgid "" -"Les demandes de migration doivent inclure une copie de sauvegarde complète " -"de la base de données du Client et les données associées (généralement " -"obtenues à partir du menu Backup du Logiciel). Lorsque cela est nécessaire " -"pour des raisons de sécurité des données ou de réglementation, le Service de" -" migration inclut un outil facultatif pour rendre anonymes les données " -"identifiables figurant dans la base de données, avant de soumettre la " -"demande de migration, et un outil pour restaurer les données rendues " -"anonymes après la migration." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:160 -msgid "" -"Ce service est fourni par le biais d'une plateforme automatisée, afin de " -"permettre au Client d'effectuer des migration sans intervention humain, dès " -"lors qu’une version précédente de la base de données du Client a été migrée " -"avec succès pour une Version Couverte donnée. Le client peut soumettre des " -"demandes de migration successives pour une base de données, et accepte de " -"soumettre au moins 1 demande de mifration de test avant de soumettre la " -"demande de migration finale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:167 -msgid "" -"Le service de migration est limité à la conversion et à l'adaptation " -"techniques de la base de données du Client pour la rendre compatible avec la" -" Version Cible, et à la correction de tout Bug directement causé par " -"l'opération de migration, et ne se produisant normalement pas dans la " -"Version Cible." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:172 -msgid "" -"Il incombe au Client de vérifier et valider la base de données migrée afin " -"de détecter tout Bug, d'analyser l'impact des changements et des nouvelles " -"fonctionnalités ajoutées dans la Version Cible, de convertir et d'adapter " -"pour la Version Cible les modules tiers du Logiciel qui auraient été " -"installées dans la base de données avant la migration (sauf le cas échéant, " -"comme prévu à la section :ref:`upgrade_extra_fr`). Le client peut soumettre " -"plusieurs demandes de migration pour une base de données, jusqu'à ce qu'un " -"résultat satisfaisant soit obtenu." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:183 -msgid "Service de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:185 -msgid "" -"Pour la durée du Contrat, le Client a la possibilité de faire une demande de" -" migration pour des modules d'extension tiers, en plus de la migration " -"normale du Logiciel. Ce service en option implique des frais supplémentaires" -" (décrits dans la section charges_fr_) et comprend l'adaptation technique " -"des modules tiers installés dans la base de données du Client et de leurs " -"données correspondantes afin qu'elles soient compatibles avec la Version " -"Cible. Le Client recevra une version migrée de tous les modules tiers " -"installés accompagnée de la base de données migrée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:196 -msgid "5 Tarifs et Frais" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:201 -msgid "5.1 Tarifs standards" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:203 -msgid "" -"Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise, le " -"service de correction de Bugs, le service d'alertes de sécurité et le " -"service de migration sont basés sur le nombre d'Utilisateurs et la version " -"du Logiciel utilisée par le Client, et précisés par écrit à la signature du " -"contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:208 -msgid "" -"Pendant la durée du contrat, si le Client a plus d'Utilisateurs que spécifié" -" au moment de la signature du présent Contrat, le Client accepte de payer un" -" supplément équivalent au tarif en vigueur applicable (au début du Contrat) " -"pour les utilisateurs supplémentaires, pour le reste de la durée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:213 -msgid "" -"Si, au moment de la signature du présent Contrat, le Client utilise une " -"Version Couverte qui n'est pas l'une des plus récentes, les tarifs standards" -" seront augmentés de 50% pour la première Durée du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:221 -msgid "5.2 Tarifs de reconduction" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:223 -msgid "" -"Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si " -"les tarifs par Utilisateur qui ont été appliqués pendant la Durée précédente" -" sont inférieurs aux tarifs par Utilisateur en vigueur les plus récents, les" -" tarifs par Utilisateur augmenteront automatiquement de maximum 7%, à moins " -"qu'Odoo SA ne notifie par écrit un nouveau tarif au client, au moins 60 " -"jours avant l’échéance du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:232 -msgid "5.3 Tarifs de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:234 -msgid "" -"Les frais supplémentaires pour le service de migration des modules tiers " -"sont de 1000,00- euros (€) (mille euros) pour 1000 lignes de code de modules" -" tiers, le nombre de lignes étant arrondi au millier de lignes supérieur. " -"Les lignes de code comprennent toutes les lignes de texte dans le code " -"source de ces modules, quel que soit le langage de programmation (Python, " -"Javascript, etc.) ou format de données (XML, CSV, etc.), à l'exclusion des " -"lignes vides et des lignes de commentaires." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:240 -msgid "" -"Odoo SA se réserve le droit de refuser une demande de migration pour des " -"modules tiers conformément aux conditions décrites ci-dessus, si la qualité " -"du code source de ces modules est trop faible, ou si ces modules font partie" -" d'une interface d'intégration avec des logiciels ou systèmes tiers. La " -"migration de ces modules sera soumise à une proposition distincte, non " -"couverte par le présent Contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:250 -msgid "5.4 Taxes et impôts" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:252 -msgid "" -"Tous les frais et tarifs sont indiqués hors taxes et hors impôts, frais et " -"charges fédérales, provinciales, locales ou autres taxes gouvernementales " -"applicables (collectivement, les \"Taxes\"). Le Client est responsable du " -"paiement de toutes les Taxes liées aux achats effectués par le Client en " -"vertu du présent Contrat, sauf lorsque Odoo SA est légalement tenue de payer" -" ou de percevoir les Taxes dont le client est responsable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:261 -msgid "6 Conditions des Services" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:264 -msgid "6.1 Obligations du Client" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:266 -msgid "Le Client accepte de / d':" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:268 -msgid "" -"Payer à Odoo SA les frais applicables pour les Services en vertu du présent " -"Contrat, conformément aux conditions de paiement spécifiées dans la facture " -"correspondante ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:270 -msgid "" -"Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs dépasse le " -"nombre d'Utilisateurs spécifiés à la signature du Contrat, et dans ce cas, " -"de régler les frais supplémentaires applicables telles que décrits à la " -"section :ref:`charges_standard_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:273 -msgid "" -"Prendre toutes les mesures nécessaires pour garantir l'exécution non " -"modifiée de la partie du Logiciel qui vérifie la validité de l'utilisation " -"de Odoo Enterprise Edition, comme décrit à la section " -":ref:`enterprise_access_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:276 -msgid "" -"Fournir tout accès nécessaire à Odoo SA pour vérifier la validité de " -"l'utilisation d'Odoo Enterprise Edition sur demande (par exemple, si la " -"validation automatique ne fonctionne pas pour le Client) ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:279 -msgid "" -"Désigner 1 personne de contact représentant le Client pour toute la durée du" -" contrat ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:280 -msgid "" -"Prendre toutes les mesures raisonnables pour protéger les fichiers et les " -"bases de données du Client et s'assurer que les données du Client sont en " -"sûreté et sécurisées, en reconnaissant qu'Odoo SA ne peut être tenue " -"responsable de toute perte de données ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:288 -msgid "6.2 Non solicitation ou embauche" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:290 -msgid "" -"Sauf si l'autre partie donne son consentement par écrit, chaque partie, ses " -"sociétés affiliées et ses représentants conviennent de ne pas solliciter ou " -"offrir un emploi à tout employé de l'autre partie qui est impliqué dans " -"l'exécution ou l'utilisation des Services en vertu du présent Contrat, " -"pendant la Durée du Contrat et pendant une période de 12 mois à compter de " -"la date de résiliation ou de l'expiration du présent Contrat. En cas de " -"violation des conditions de la présente section qui conduirait à la " -"démission dudit employé à cette fin, la partie ayant enfreint ces " -"dispositions accepte de payer à l'autre partie un montant forfaitaire de 30 " -"000,00 euros (€) (trente mille euros)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:303 -msgid "6.3 Publicité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:305 -msgid "" -"Sauf demande contraire par écrit, chaque partie accorde à l'autre partie une" -" licence mondiale libre de droits, non transférable, non exclusive pour " -"reproduire et afficher le nom, les logos et les marques de l'autre partie, " -"dans le seul but de citer l'autre partie en tant que client ou fournisseur, " -"sur les sites Web, dans des communiqués de presse et autres documents de " -"marketing." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:313 -msgid "6.4 Confidentialité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:324 -msgid "Définition des \"Informations Confidentielles\" :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:316 -msgid "" -"Désigne toutes les informations divulguées par une partie (la \"Partie " -"Communicante\") à l'autre partie (la \"Partie Bénéficiaire\"), que ce soit " -"oralement ou par écrit, qui sont désignées comme confidentielles ou qui " -"devraient raisonnablement être comprises comme étant confidentielles étant " -"donné la nature des informations et les circonstances de la divulgation. En " -"particulier, toute information liée aux activités, aux affaires, aux " -"produits, aux développements, aux secrets commerciaux, au savoir-faire, au " -"personnel, aux clients et aux fournisseurs de l'une des parties doit être " -"considérée comme confidentielle." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:326 -msgid "" -"Pour toute Information Confidentielle reçue pendant la durée du présent " -"contrat, la Partie Bénéficiaire utilisera le même degré de précaution " -"qu'elle utilise pour protéger la confidentialité de ses propres Informations" -" Confidentielles de même importance. Ce degré de précaution devra " -"correspondre au minimum à une précaution raisonnable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:331 -msgid "" -"La Partie Bénéficiaire peut divulguer les Informations Confidentielles de la" -" Partie Communicante dans la mesure où la loi l'y oblige, à condition que la" -" Partie Bénéficiaire avise au préalable par écrit la Partie Communicante de " -"son obligation de divulgation, dans la mesure permise par la loi." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:339 -msgid "6.5 Résiliation" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:341 -msgid "" -"Dans le cas où l'une des parties ne remplit pas ses obligations découlant du" -" présent contrat, et si une telle violation n’est pas résolue dans les 30 " -"jours civils à compter de la notification écrite de cette violation, le " -"présent contrat peut être résilié immédiatement par la partie qui n'a pas " -"commis la violation." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:347 -msgid "" -"En outre, Odoo SA peut résilier le contrat immédiatement dans le cas où le " -"Client ne paie pas les frais applicables pour les services à la date " -"d'échéance indiquée sur la facture correspondante." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:354 -msgid "Durée de l'applicabilité des dispositions:" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:352 -msgid "" -"Les sections \":ref:`confidentiality_fr`\", “:ref:`disclaimers_fr`\", " -"“:ref:`liability_fr`\", et “:ref:`general_provisions_fr`\" survivront la " -"résiliation ou l'expiration du présent contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:359 -msgid "7 Limitations de garantie et de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:364 -msgid "7.1 Garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:366 -msgid "" -"Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts" -" raisonnables sur le plan commercial pour exécuter les Services conformément" -" aux normes du secteur généralement acceptées à condition que :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:370 -msgid "" -"Les systèmes informatiques du Client soient en bon état de fonctionnement et" -" que le Logiciel soit installé dans un système d'exploitation approprié ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:372 -msgid "" -"Le Client fournisse les informations adéquates nécessaires au dépannage et à" -" l'accès, de telle sorte qu'Odoo SA puisse identifier, reproduire et gérer " -"les problèmes ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:374 -msgid "Tous les montants dus à Odoo SA aient été réglés." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:376 -msgid "" -"La reprise de l'exécution des Services par Odoo SA sans frais " -"supplémentaires constitue la seule et unique réparation pour le Client et la" -" seule obligation d'Odoo SA pour toute violation de cette garantie." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:383 -msgid "7.2 Limitation de garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:385 -msgid "" -"Mis à part les dispositions expresses du présent Contrat, aucune des parties" -" ne donne de garantie d'aucune sorte, expresse, implicite, légale ou autre, " -"et chaque partie décline expressément toutes garanties implicites, y compris" -" toute garantie implicite de qualité marchande, d'adéquation à un usage " -"particulier ou de non- contrefaçon, dans les limites autorisées par la loi " -"en vigueur." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:391 -msgid "" -"Odoo SA ne garantit pas que le Logiciel soit conforme à toute loi ou " -"réglementation locale ou internationale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:398 -msgid "7.3 Limitation de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:400 -msgid "" -"Dans la limite autorisée par la loi, la responsabilité globale de chaque " -"partie, ainsi que de ses filiales, découlant ou liée au présent Contrat ne " -"dépassera pas 50% du montant total réglé par le Client en vertu du présent " -"Contrat au cours des 12 mois précédant la date de l'événement donnant lieu à" -" une telle réclamation. Des réclamations multiples n'augmenteront pas cette " -"limite." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:405 -msgid "" -"Les parties et leurs filiales ne pourront en aucun cas être tenues " -"responsables des dommages indirects, spéciaux, accessoires ou consécutifs de" -" quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de " -"revenus, perte de profits, perte d’économies, perte commerciale ou toute " -"autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte " -"ou altération des données, découlant ou en relation avec le présent Contrat," -" quelle que soit la forme de l'action, qu'elle soit fondée sur une " -"obligation contractuelle, délictuelle (y compris la stricte négligence) ou " -"fondée sur toute autre règle de droit ou d'équité, même si la partie ou ses " -"filiales ont été informées du risque de tels dommages, ou si le recours " -"proposé par la partie ou ses filiales n'atteint pas son but essentiel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:420 -msgid "" -"Aucune des parties ne sera tenue pour responsable envers l'autre partie de " -"tout retard ou manquement d'exécution en vertu du présent Contrat, si ce " -"manquement ou retard est causé par une règlementation gouvernementale, un " -"incendie, une grève, une guerre, une inondation, un accident, une épidémie, " -"un embargo, la saisie d'une usine ou d'un produit dans son intégralité ou en" -" partie par un gouvernement ou une autorité publique, ou toute (s) autre (s)" -" cause (s), qu’elle (s) soit (soient) de nature similaire ou différente, " -"pour autant que cette cause soit hors du contrôle raisonnable de la partie " -"concernée, et tant qu'une telle cause existe." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:431 -msgid "8 Dispositions générales" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:436 -msgid "8.1 Droit applicable" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:438 -msgid "" -"Les parties conviennent que les lois de Belgique seront applicables en cas " -"de litige découlant ou en relation avec le présent Contrat, sans tenir " -"compte des règles ou dispositions en matière de compétence législative ou de" -" conflit de lois. Dans la mesure où une poursuite ou procédure judiciaire ou" -" administrative serait autorisée ci-avant, les parties conviennent de se " -"soumettre à la compétence exclusive du tribunal de Nivelles (Belgique) aux " -"fins de la procédure de tout litige." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:448 -msgid "8.2 Divisibilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:450 -msgid "" -"Dans le cas où une ou plusieurs des dispositions du présent contrat ou toute" -" autre application de celles-ci se trouvent non valables, illégales ou non " -"exécutoires, la validité, la légalité et le caractère exécutoire des autres " -"dispositions du présent contrat et toute application de celles-ci ne doivent" -" en aucun cas en être affectés ou compromis. Les parties s'engagent à " -"remplacer toute disposition non valable, illégale ou non exécutoire du " -"présent contrat par une disposition valable ayant les mêmes effets et " -"objectifs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:460 -msgid "9 Appendice A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:462 -msgid "" -"Odoo 9 Enterprise Edition est publié sous la licence Odoo Enterprise Edition" -" License v1.0, définie ci-dessous." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:466 -msgid "" -"Ceci est une traduction en français de la licence “Odoo Enterprise Edition " -"License”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa " -"compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes de la licence “Odoo Enterprise Edition License” est la" -" :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:472 -msgid "" -"This is a french translation of the \"Odoo Enterprise Edition License”. This" -" translation is provided in the hope that it will facilitate understanding, " -"but it has no legal value. The only official reference of the terms of the " -"“Odoo Enterprise Edition License” is the :ref:`original english version " -"`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:489 -msgid "" -"Ce logiciel et les fichiers associés (le \"Logiciel\") ne peuvent être " -"utilisés (c'est-à-dire exécutés, modifiés, ou exécutés avec des " -"modifications) qu'avec un contrat Odoo Enterprise Subscription en ordre de " -"validité, et pour le nombre d'utilisateurs prévus dans ce contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:494 -msgid "" -"Un contrat de Partnariat avec Odoo S.A. en ordre de validité donne les mêmes" -" permissions que ci-dessus, mais uniquement pour un usage restreint à un " -"environnement de test ou de développement." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:498 -msgid "" -"Vous êtes autorisé à développer des modules Odoo basés sur le Logiciel et à " -"les distribuer sous la license de votre choix, pour autant que cette licence" -" soit compatible avec les conditions de la licence Odoo Enterprise Edition " -"Licence (Par exemple: LGPL, MIT ou d'autres licenses propriétaires " -"similaires à celle-ci)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:503 -msgid "" -"Vous êtes autorisé à utiliser des modules Odoo publiés sous n'importe quelle" -" licence, pour autant que leur licence soit compatible avec les conditions " -"de la licence Odoo Enterprise Edition License (Notamment tous les modules " -"publiés sur l'Odoo Apps Store sur odoo.com/apps)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:508 -msgid "" -"Il est interdit de publier, distribuer, accorder des sous-licences, ou " -"vendre tout copie du Logiciel ou toute copie modifiée du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:511 -msgid "" -"Toute copie du Logiciel ou d'une partie substantielle de celui-ci doit " -"inclure l'avis de droit d'auteur original ainsi que le texte de la présente " -"licence." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:514 -msgid "" -"LE LOGICIEL EST FOURNI \"EN L'ETAT\", SANS AUCUNE GARANTIE DE QUELQUE NATURE" -" QUE CE SOIT, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS Y ETRE LIMITE, LES" -" GARANTIES IMPLICITES DE COMMERCIABILITE, DE CONFORMITE A UNE UTILISATION " -"PARTICULIERE, OU DE NON INFRACTION AUX DROITS D'UN TIERS." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:519 -msgid "" -"EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE " -"TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES " -"RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU " -"LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION " -"RELATIVE AU LOGICIEL." -msgstr "" - -#: ../../legal/terms/online.rst:3 -msgid "Odoo Online Terms & Conditions" -msgstr "" - -#: ../../legal/terms/partnership.rst:6 -msgid "Odoo Partnership Agreement - Under Revision!" -msgstr "" - -#: ../../legal/terms/partnership.rst:8 -msgid "Version 5_work-in-progress - Last revision: March 02, 2016." -msgstr "" - -#: ../../legal/terms/partnership.rst:11 -msgid "BETWEEN:" -msgstr "" - -#: ../../legal/terms/partnership.rst:13 -msgid "" -"ODOO SA registered at the Trade and Companies Register of Nivelles under " -"number RCN 95656, having its registered office at Chaussée de Namur, 40 - " -"1367 Grand-Rosière, Belgium." -msgstr "" - -#: ../../legal/terms/partnership.rst:16 -msgid "" -"AND ________________________________, a company having its registered office" -" at _____________________ (Hereinafter referred to as “PARTNER”)" -msgstr "" - -#: ../../legal/terms/partnership.rst:22 -msgid "1 Purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:23 -msgid "" -"The purpose of this agreement is to set forth the conditions under which " -"ODOO provides services to PARTNER, and access to Odoo Enterprise Edition " -"software, and PARTNER complies with the obligations set out hereafter." -msgstr "" - -#: ../../legal/terms/partnership.rst:27 -msgid "" -"ODOO hereby appoints PARTNER, and PARTNER hereby accepts appointment, to be " -"a non-exclusive partner promoting and selling the Odoo Enterprise " -"Subscriptions to clients. PARTNER commits to do its best effort to sell Odoo" -" Enterprise Subscriptions to its clients. To support that, PARTNER will " -"market in priority the ‘Odoo Enterprise Edition’ version to prospects and " -"clients. PARTNER still has the option to sell services on other versions of " -"the software, like \"Odoo Community Edition\", should it be needed." -msgstr "" - -#: ../../legal/terms/partnership.rst:35 -msgid "2 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/partnership.rst:36 -msgid "" -"The duration of this Agreement (the “Term”) shall be one year beginning on " -"the date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term to the other party." -msgstr "" - -#: ../../legal/terms/partnership.rst:45 -msgid "3.1 Project platform access" -msgstr "" - -#: ../../legal/terms/partnership.rst:46 -msgid "" -"To help PARTNER promoting Odoo Enterprise, ODOO grants access to its Github " -"code repository to PARTNER for all ‘Enterprise Edition’ modules, under the " -"terms set forth in Exhibit A and the conditions restricted under this " -"agreement. This access will be granted as of the signature of this agreement" -" and be revoked should the partnership contract be revoked." -msgstr "" - -#: ../../legal/terms/partnership.rst:50 -msgid "3.2 Restrictions" -msgstr "" - -#: ../../legal/terms/partnership.rst:51 -msgid "" -"PARTNER commits to keep confidentiality of the source code of Odoo " -"Enterprise edition modules licensed under restricted rights (labelled as " -"‘Enterprise Edition’) within its staff. The access to clients is governed by" -" the Odoo Enterprise Contract (version 4.0 and above). PARTNER agrees to NOT" -" redistribute this code to 3rd parties without the explicit agreement of " -"ODOO. Notwithstanding the above, PARTNER commits to wholly preserve the " -"integrity of the Odoo Enterprise edition code that is required to verify the" -" validity of usage of Odoo Enterprise edition, collects statistics that are " -"needed for that purpose and enforce the payment of the subscription." -msgstr "" - -#: ../../legal/terms/partnership.rst:56 -msgid "4 Partnership Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:59 -msgid "4.1 Partnership levels" -msgstr "" - -#: ../../legal/terms/partnership.rst:60 -msgid "" -"The ODOO partner program consists of three partnership levels; Ready, Silver" -" and Gold with specific requirements and benefits for each level. " -"Partnership level granted to PARTNER depends on the annual new Odoo " -"Enterprise revenues generated for ODOO. Renewals of existing contracts does " -"not account for the partnership level, but the partner still get his " -"commission on these contracts as stated in 5.2 The table below summarizes " -"the requirement for each partnership level." -msgstr "" - -#: ../../legal/terms/partnership.rst:64 -msgid "" -"Ready Silver Gold Annual New Net Odoo Enterprise Revenues 1.000 € 12.000 € " -"25.000 €" -msgstr "" - -#: ../../legal/terms/partnership.rst:72 -msgid "" -"The level of partnerships will be reviewed quarterly by ODOO based on Odoo " -"Enterprise contracts sold by partners, over the preceeding 12 months. " -"Partners may be upgraded automatically to a higher level once they reach the" -" requirements for a higher level. Silver and Gold partners which are not " -"complying with their partnerships requirements will be assigned to a lower " -"level of partnership if they have not met their requirement at the end of " -"the annual period. For new partners, the initial partner level is granted " -"for one year." -msgstr "" - -#: ../../legal/terms/partnership.rst:77 -msgid "4.2 Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:78 -msgid "" -"The details of the benefits for each level of partnership are described in " -"the table below:" -msgstr "" - -#: ../../legal/terms/partnership.rst:81 -msgid "" -"Ready Silver Gold Recognition Visibility on odoo.com Ready Partner Silver " -"Partner Gold Partner Rights to use the Odoo trademark Ready logo Silver logo" -" Gold logo Learning benefits Yearly upgrades seminars Yes Yes Yes Sales " -"Training Yes Yes Yes Weekly functional training webinars Yes Yes Yes " -"Software Benefits Access to Odoo Enterprise source code Yes Yes Yes Sales " -"benefits Discount on all ODOO services 10% 15% 20% Discount on ODOO " -"Enterprise (Minimum 10 users per contract, applied then for all users). 10% " -"15% 20% Access to an Account Manager Yes Yes Yes Marketing Benefits Access " -"to marketing materials Yes Yes Yes Partner EVENT – ODOO Support & Promotion " -"No Yes Yes" -msgstr "" - -#: ../../legal/terms/partnership.rst:135 -msgid "4.3 Partner Recognition" -msgstr "" - -#: ../../legal/terms/partnership.rst:136 -msgid "" -"ODOO will promote PARTNER as an official partner on its website (odoo.com) " -"for agreed countries. ODOO grants to PARTNER, on a non-exclusive basis, the " -"right to use and reproduce only the ODOO Partner’s logo, and the Odoo name " -"in connection with this Agreement. Each Party undertakes to respect all the " -"rights of the other Party in all the items referred to in the previous " -"paragraph and, more particularly, each Party shall refrain from causing any " -"analogy or creating any confusion between their respective company in the " -"mind of the general public, for any reason whatsoever and by any means " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:141 -msgid "4.4 Learning Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:142 -msgid "" -"In order to train PARTNER, ODOO will organize online training sessions once " -"a week. Sessions are organized into discovery and advanced topics. A session" -" is usually 2 hours and cover an application of the Odoo Enterprise " -"software: sales and CRM, inventory management, project management, " -"eCommerce, human resources, manufacturing, advanced customizations, etc. " -"PARTNER can attend these training sessions at no additional cost and commit " -"to attend at least 20 sessions per year. ODOO will organize at least four " -"sales training session per year of a duration of one week. Each sales " -"training session is organized in one of the ODOO office. PARTNER can send " -"any employee to these training session. Once a new version of Odoo " -"Enterprise is released, ODOO must organize upgrade training session for " -"partners." -msgstr "" - -#: ../../legal/terms/partnership.rst:148 -msgid "4.5 Commission on Odoo Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:149 -msgid "" -"For every ODOO services directly purchased by a customer through PARTNER, " -"PARTNER shall receive retribution as follows For “ODOO Enterprise” contracts" -" sold to CUSTOMER: ODOO will invoice directly the CUSTOMER based on final " -"pricing agreed between ODOO, the PARTNER & the CUSTOMER. Then, PARTNER will " -"invoice his commission to ODOO based on Odoo Enteprise price, net of " -"possible rebates, and based on his current partnership level at the time of " -"signature. For Other Services; Partner invoice directly the CLIENT and ODOO " -"will invoice the PARTNER directly commission included. (as a discount) For " -"“ODOO Enterprise” contracts; PARTNER get a commission as long as the PARTNER" -" maintains a contractual relationship with the CUSTOMER." -msgstr "" - -#: ../../legal/terms/partnership.rst:156 -msgid "5 Miscellaneous" -msgstr "" - -#: ../../legal/terms/partnership.rst:159 -msgid "5.1 Communications" -msgstr "" - -#: ../../legal/terms/partnership.rst:160 -msgid "" -"No communications from either party to the other shall have any validity " -"under this Agreement unless made in writing by or on behalf of PARTNER or " -"ODOO, as the case may be, in accordance with the provisions of this " -"Agreement. Any notice whatsoever which either party hereto is required or " -"authorised by this Agreement to give or make to the other shall be given or " -"made either by post in a prepaid letter, or by hand delivery or facsimile " -"transmission or E-mail." -msgstr "" - -#: ../../legal/terms/partnership.rst:164 -msgid "5.2 BRAND IMAGE" -msgstr "" - -#: ../../legal/terms/partnership.rst:165 -msgid "" -"Both Parties shall refrain from harming the brand image and reputation of " -"the other Party, in any way whatsoever, in the performance of this " -"Agreement. Non-compliance to this provision shall be a cause for termination" -" of this Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:168 -msgid "5.3 Publicity" -msgstr "" - -#: ../../legal/terms/partnership.rst:169 -msgid "" -"ODOO shall publish any press release, advertisement or other public " -"announcement using the PARTNER’s name or trademarks without its prior " -"written consent. In particular, PARTNER accepts to be mentioned, and that " -"its logo and trademark is used for this purpose only, in the list of the " -"partners of ODOO." -msgstr "" - -#: ../../legal/terms/partnership.rst:172 -msgid "5.4 No SOLICITING" -msgstr "" - -#: ../../legal/terms/partnership.rst:173 -msgid "" -"Each party, its subsidiaries and any entity controlled indirectly agrees not" -" to solicit, offer employment to, or use the services of any employee of the" -" other party who is involved in performing the Services for the duration of " -"the Agreement and for a period of twenty four (24) Months from the date of " -"termination of this Agreement, except as expressly provided for in the " -"Agreement or where the other party gives its consent in writing to this. In " -"case of any breach of the terms of this article, the defaulting Party shall " -"pay an indemnity equivalent to 12 months of the gross salary of the employee" -" sought or dismissed, or to at least a minimum of € 30,000." -msgstr "" - -#: ../../legal/terms/partnership.rst:177 -msgid "5.5 Independent Contractor" -msgstr "" - -#: ../../legal/terms/partnership.rst:178 -msgid "" -"The Parties are independent contractors, and this Agreement shall not be " -"construed as constituting either Party as partner, joint venture or " -"fiduciary of the other, as creating any other form of legal association that" -" would impose liability on one Party for the act or failure to act of the " -"other or as providing either Party with the right, power or authority " -"(express or implied) to create any duty or obligation of the other." -msgstr "" - -#: ../../legal/terms/partnership.rst:181 -msgid "6 FEES AND CHARGES" -msgstr "" - -#: ../../legal/terms/partnership.rst:182 -msgid "" -"PARTNER shall pay the charges and the annual fee immediately upon receipt of" -" the invoice sent by ODOO.The annual partnership fees is 2950€. PARTNER " -"shall automatically pay a late payment interest at the rate equivalent to " -"the applicable interest rate of the principal instrument of re-financing of " -"the European Central Bank increased by 7% per year, which shall accrue on a " -"daily basis from the due date of payment; it not being necessary for such " -"accrual that ODOO request or claims the unpaid amount in any manner " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:186 -msgid "7 Termination" -msgstr "" - -#: ../../legal/terms/partnership.rst:187 -msgid "" -"In the event that either Party fails to fulfil one or more of its " -"obligations arising hereunder, and if such breach has not been remedied " -"within thirty (30) calendar days from the first presentation of a letter, " -"sent by the injured Party by registered letter with advice of receipt, " -"giving notice of the breaches, this Agreement may be terminated immediately " -"as of right at the request of the injured Party, without prejudice to any " -"damages that may be claimed from the defaulting Party." -msgstr "" - -#: ../../legal/terms/partnership.rst:189 -msgid "" -"On expiry or termination of this Agreement, PARTNER: shall not use anymore " -"the materials and/or the Odoo brand name or claim the existence of any " -"partnership or link with ODOO, shall during any notice period prior to such " -"termination comply with its obligations. shall not use Odoo Enterprise " -"anymore, for development, test or production purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:195 -msgid "8 Liability AND Indemnities" -msgstr "" - -#: ../../legal/terms/partnership.rst:196 -msgid "" -"Both Parties are bound by a best endeavours obligation hereunder. To the " -"maximum extent permitted by law, ODOO’s liability for any and all claims, " -"losses, damages or expenses from any cause whatsoever and howsoever arising " -"under this Agreement will be limited to the direct damages proven, but will " -"in no event exceed for all damage causing event or series of connected " -"events causing damages the total amount for the charges paid by PARTNER in " -"the course of the six (6) months immediately preceding the date of the event" -" giving rise to such claim. In no event will ODOO be liable for any indirect" -" or consequential damages, including but not limited third parties or " -"Customer claims, loss of revenue, profits, savings, loss of business or " -"other financial loss, costs of standstill or delay, lost or corrupted data " -"arising out of or in connection with the performance of its obligations. " -"PARTNER acknowledges that he has no expectation and has received no " -"assurances that any investment made in execution of this Agreement and the " -"ODOO Partners Program will be recovered or recouped or that he shall obtain " -"any anticipated amount of profits by virtue of this Agreement. Partner " -"waives any commitment whatsoever on behalf of ODOO regarding the evolution " -"of Software." -msgstr "" - -#: ../../legal/terms/partnership.rst:202 -msgid "" -"According to the terms of the Software license, ODOO will not be liable for " -"any bug or for the quality and the performance of the Software, ODOO’s " -"commitment being limited to the correction of bugs as defined in this " -"Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:205 -msgid "9 Governing Law and Jurisdiction" -msgstr "" - -#: ../../legal/terms/partnership.rst:206 -msgid "" -"This Agreement will be governed by and construed in accordance with the laws" -" of Belgium. All disputes arising in connection with the Agreement for which" -" no amicable settlement can be found shall be finally settled by the Courts " -"of Belgium in Nivelles." -msgstr "" - -#: ../../legal/terms/partnership.rst:208 -msgid "For Odoo SA," -msgstr "" - -#: ../../legal/terms/partnership.rst:213 -msgid "For _____________," -msgstr "" - -#: ../../legal/terms/partnership.rst:220 -msgid "10 Appendix A: Odoo Enterprise Edition License" -msgstr "" diff --git a/locale/es/LC_MESSAGES/point_of_sale.po b/locale/es/LC_MESSAGES/point_of_sale.po index 46d442e6f..244f3072d 100644 --- a/locale/es/LC_MESSAGES/point_of_sale.po +++ b/locale/es/LC_MESSAGES/point_of_sale.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Mateo Tibaquirá Palacios , 2017\n" +"Last-Translator: Carles Antoli , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2413,18 +2413,34 @@ msgstr "" "Puede configurar cada punto de venta de acuerdo a su sistema operativo, " "ubicación,..." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "Nombre del TPV" + #: ../../point_of_sale/overview/start.rst:0 msgid "An internal identification of the point of sale" msgstr "Identificación interna del TPV" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "Diario de ventas" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to post sales entries." msgstr "Diario contable usado para contabilizar los asientos." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "Diario de factura" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to create invoices." msgstr "Diario contable utilizado para crear facturas." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "Agrupar apuntes" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Check this if you want to group the Journal Items by Product while closing a" @@ -2433,6 +2449,10 @@ msgstr "" "Marque esta casilla si quiere agrupar los apuntes contable por producto en " "el cierre de sesión." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "Códigos de barras" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Defines what kind of barcodes are available and how they are assigned to " @@ -2441,6 +2461,10 @@ msgstr "" "Define que tipo de códigos de barra están disponibles y como se asignan a " "productos, clientes y cajeros" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "Secuencia de identificadores del pedido" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "This sequence is automatically created by Odoo but you can change it to " @@ -2449,18 +2473,34 @@ msgstr "" "La secuencia es creada automáticamente por Odoo, pero puede cambiarla para " "personalizar los números de referencia de sus pedidos." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "Canal de Ventas" + #: ../../point_of_sale/overview/start.rst:0 msgid "This Point of sale's sales will be related to this Sales Channel." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "Teclado virtual" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables an integrated Virtual Keyboard" msgstr "Habilitar un teclado virtual integrado" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "Facturación" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables invoice generation from the Point of Sale" msgstr "Habilitar generación de facturas desde el TPV" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "Llenado previo pago en efectivo" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The payment input will behave similarily to bank payment input, and will be " @@ -2469,6 +2509,10 @@ msgstr "" "La entrada de pago se comportará similarmente a la entrada de pago bancario " ", y se auto rellenará con la cantidad exacta debido" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "Categoría inicial" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The point of sale will display this product category by default. If no " @@ -2477,6 +2521,10 @@ msgstr "" "El punto de venta mostrará esta categoría de productos por defecto. Si no se" " especifica una categoría, todos los productos disponibles se mostrarán" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "Producto Propina" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The product used to encode the customer tip. Leave empty if you do not " @@ -2485,6 +2533,10 @@ msgstr "" "El producto utilizado para codificar la propina del cliente. Dejar en blanco" " si usted no acepta propina ." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "Incluir Impuestos en los precios" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The displayed prices will always include all taxes, even if the taxes have " @@ -2493,16 +2545,28 @@ msgstr "" "Los precios mostrados no siempre incluyen todos los impuestos , incluso si " "los impuestos se han configurado de forma diferente" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "Barras de desplazamiento grandes" + #: ../../point_of_sale/overview/start.rst:0 msgid "For imprecise industrial touchscreens" msgstr "Para pantallas táctiles industriales imprecisas" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "Mostrar Imágenes de Categoría" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product categories will be displayed with pictures." msgstr "" "El punto de venta mostrará esta categoría de Productos por Defecto . Si no " "se ESPECIFICA Una categoría , Todos los Productos Disponibles se mostrarán" +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "Dirección IP" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The hostname or ip address of the hardware proxy, Will be autodetected if " @@ -2511,27 +2575,51 @@ msgstr "" "El nombre de equipo o la dirección IP del proxy hardware. Será autodetectado" " si se deja vacío" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "Lector de códigos de barras" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enable barcode scanning with a remotely connected barcode scanner" msgstr "" "Habilitar escaneado de código de barras con un escáner remoto conectado" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "Balanza electrónica" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Electronic Scale integration" msgstr "Habilitar integración de una balanza electrónica" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "Cajón de monedas" + #: ../../point_of_sale/overview/start.rst:0 msgid "Automatically open the cashdrawer" msgstr "Abrir automáticamente el cajón de monedas" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "Impresora de recibos" + #: ../../point_of_sale/overview/start.rst:0 msgid "Bypass browser printing and prints via the hardware proxy" msgstr "Saltar impresión del navegador e imprimir vía el proxy hardware" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "Impresión automática del recibo" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt will automatically be printed at the end of each order" msgstr "El recibo se imprimirá automáticamente al final de cada orden" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "Saltar Pantalla de Recibo" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The receipt screen will be skipped if the receipt can be printed " @@ -2540,30 +2628,58 @@ msgstr "" "Se omitirá la pantalla de recibo si el recibo se puede imprimir de forma " "automática." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "Encabezado" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a header in the printed receipt" msgstr "Un texto corto que se insertará como cabecera en el recibo impreso" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "Pie de página" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a footer in the printed receipt" msgstr "Un texto corto que se insertará como pie en el recibo impreso" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "Control de efectivo" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check the amount of the cashbox at opening and closing." msgstr "Revisar la cantidad en caja al inicio y al cierre." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "Separación de la cuenta" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Bill Splitting in the Point of Sale" msgstr "Habilita la separación de cuentas en el TPV" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "Impresión de la cuenta" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allows to print the Bill before payment" msgstr "Permitir imprimir la cuenta antes del pago" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "Notas de la Línea de Pedido" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allow custom notes on Orderlines" msgstr "Permite notas en las líneas de pedido" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "Pisos del Restaurante" + #: ../../point_of_sale/overview/start.rst:0 msgid "The restaurant floors served by this point of sale" msgstr "Los pisos del restaurante atendidos en este punto de venta" @@ -3476,11 +3592,19 @@ msgstr "" "Puede estar hecho para todos los productos o para cada uno en específico. " "Haga clic en **Agregar elemento**." +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "Activo" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "" "If unchecked, it will allow you to hide the pricelist without removing it." msgstr "Si no está marcado, la tarifa podrá ocultarse sin eliminarla." +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "Seleccionable" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "Allow the end user to choose this price list" msgstr "Permitirle al usuario escoger esta lista de precios" diff --git a/locale/es/LC_MESSAGES/purchase.po b/locale/es/LC_MESSAGES/purchase.po index 5fcab8438..564e51623 100644 --- a/locale/es/LC_MESSAGES/purchase.po +++ b/locale/es/LC_MESSAGES/purchase.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Miguel Orueta , 2017\n" +"Last-Translator: Alejandro Die Sanchis , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2111,10 +2111,18 @@ msgstr "" " marcha, haga clic en **Crear y Editar**. En el campo **Fecha de pedido**, " "seleccione la fecha en la que desea continuar con el orden real." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "Envío" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Incoming Shipments" msgstr "Envíos a recibir" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "Referencia de proveedor" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the sales order or bid sent by the vendor. It's used to do the " @@ -2126,6 +2134,10 @@ msgstr "" "esta referencia se suele escribir en la orden de entrega enviado por el " "proveedor." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "Fecha de pedido" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Depicts the date where the Quotation should be validated and converted into " @@ -2134,16 +2146,28 @@ msgstr "" "Representa la fecha en que el presupuesto debe ser validado y se convierte " "en una orden de compra." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "Documento origen" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the document that generated this purchase order request (e.g. a" " sales order or an internal procurement request)" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "Entregar a" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "This will determine picking type of incoming shipment" msgstr "Esto determinará el tipo de albarán de la recepción" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "Dirección Drop Ship" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Put an address if you want to deliver directly from the vendor to the " @@ -2152,10 +2176,18 @@ msgstr "" "Ponga una dirección si desea entregar directamente desde el proveedor al " "cliente. De lo contrario, mantenga vacía para entregar a su propia compañía." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "Tipo de ubicación de destino" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Technical field used to display the Drop Ship Address" msgstr "Campo técnico utilizado para mostrar la dirección de envió directo" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "Incoterm" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "International Commercial Terms are a series of predefined commercial terms " diff --git a/locale/es/LC_MESSAGES/sales.po b/locale/es/LC_MESSAGES/sales.po index bf335030a..d278a9cef 100644 --- a/locale/es/LC_MESSAGES/sales.po +++ b/locale/es/LC_MESSAGES/sales.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: José Vicente , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" @@ -937,16 +937,11 @@ msgstr "" #: ../../sales/invoicing/services/support.rst:66 msgid "" -"There are different ways to track the service related to a sale order or " +"There are different ways to track the service related to a sales order or " "product sold. With the above configuration, you can only sell one support " "contract per order. If your customer orders several service contracts on " "timesheet, you will have to split the quotation into several orders." msgstr "" -"Hay diferentes maneras de seguir el servicio relacionado con una orden de " -"venta o producto vendido. Con la configuración anterior, sólo se puede " -"vender un contrato de soporte por pedido. Si sus pedidos de clientes de " -"varios contratos de servicios en parte de horas, que tendrá que dividir el " -"presupuesto en varios órdenes." #: ../../sales/invoicing/services/support.rst:72 msgid "" @@ -966,21 +961,16 @@ msgid "Managing support contract" msgstr "La gestión de contrato de soporte" #: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sale Orders" -msgstr "Órdenes de Citas y Ventas" +msgid "Quotations and Sales Orders" +msgstr "Presupuestos y pedidos de venta" #: ../../sales/invoicing/services/support.rst:83 msgid "" -"Once the product is created, you can create a quotation or a sale order with" -" the related product. Once the quotation is confirmed and transformed into a" -" sale order, your users will be able to record services related to this " -"support contract using the timesheet application." +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." msgstr "" -"Una vez que el productos es creado, usted puede crear una cotización o una " -"orden de venta con el producto relacionado. Una vez que la cotización está " -"confirmada y se transformó en una orden de venta, los usuarios podrán grabar" -" los servicios relacionados con el contrato de soporte utilizando la " -"aplicación de la hoja de horas." #: ../../sales/invoicing/services/support.rst:93 msgid "Timesheets" @@ -1001,8 +991,8 @@ msgstr "" "vendido." #: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sale order" -msgstr "Control de entrega de apoyo en la orden de venta" +msgid "Control delivered support on the sales order" +msgstr "" #: ../../sales/invoicing/services/support.rst:106 msgid "" @@ -1025,30 +1015,14 @@ msgstr "Sobreventa y renovación" #: ../../sales/invoicing/services/support.rst:118 msgid "" "If the number of hours you performed on the support contract is bigger or " -"equal to the number of hours the customer purchased, the sale order " -"**Invoicing Status** is automatically set to **Upselling**. This means you " -"have an opportunity to sell an extra contract to the customer since he used " -"all his quota of service." +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." msgstr "" -"Si el número de horas que trabajó sobre el contrato de soporte es mayor o " -"igual que el número de horas que el cliente compró, la orden de venta de " -"**Estado de Facturación** se ajusta automáticamente a **Vendiendo**. Esto " -"significa que usted tiene la oportunidad de vender un contrato adicional " -"para el cliente ya que él usó toda su cuota de servicio." -#: ../../sales/invoicing/services/support.rst:124 -msgid "" -"Periodically (ideally once every two weeks), you should check the sales " -"order that are in an upselling status. To do this, go to the " -":menuselection:`Sales --> Sales Order` menu and use the **Upselling** filter" -" to get all orders that are in upselling." -msgstr "" -"Periódicamente (idealmente una vez cada dos semanas), usted debe comprobar " -"la orden de venta que se encuentran en un estado de vendiendo. Para ello, " -"vaya a :menuselection:`Ventas --> Orden de Venta` y usar el filtro de " -"**Vendiendo** para obtener todos los pedidos que están en vendidos." - -#: ../../sales/invoicing/services/support.rst:130 +#: ../../sales/invoicing/services/support.rst:127 msgid "" "If you use Odoo CRM, a good practice is to create an opportunity for every " "sale order in upselling invoice status so that you easily track your " @@ -1058,26 +1032,20 @@ msgstr "" "que cada orden de venta en estado vendiendo de la factura, seguirá " "fácilmente su esfuerzo de mejorarar una venta." -#: ../../sales/invoicing/services/support.rst:134 +#: ../../sales/invoicing/services/support.rst:131 msgid "" "If you sell an extra support contract, you can either add a new line on the " -"existing sale order (thus, you continue to timesheet on the same order) or " +"existing sales order (thus, you continue to timesheet on the same order) or " "create a new order (thus, people will timesheet their hours on the new " -"contract). To unmark the sale order as **Upselling**, you can set the sale " -"order as done and it will disappear from your upselling list." +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." msgstr "" -"Si usted vende un contrato de soporte adicional, puede añadir una nueva " -"línea en la orden de venta existente (por lo tanto, continúa de parte de " -"horas en el mismo orden) o crea una nueva orden (por lo tanto, la gente verá" -" su hoja de horas en el nuevo contrato). Para desmarcar la orden de venta " -"como **Vendiendo**, puede establecer la orden de la venta como hecho y va a " -"desaparecer de su lista de vendiendo." -#: ../../sales/invoicing/services/support.rst:141 +#: ../../sales/invoicing/services/support.rst:138 msgid "Special Configuration" msgstr "Configuración Especial" -#: ../../sales/invoicing/services/support.rst:143 +#: ../../sales/invoicing/services/support.rst:140 msgid "" "When creating the product form, you may set a different approach to track " "the service:" @@ -1085,33 +1053,23 @@ msgstr "" "Al crear la forma del producto, es posible establecer un enfoque diferente " "para realizar el seguimiento del servicio:" -#: ../../sales/invoicing/services/support.rst:146 +#: ../../sales/invoicing/services/support.rst:143 msgid "" "**Create task and track hours**: in this mode, a task is created for every " -"sale order line. Then when you do the timesheet, you don't record hours on a" -" sale order/contract, but you record hours on a task (that represents the " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " "contract). The advantage of this solution is that it allows to sell several " -"service contracts within the same sale order." +"service contracts within the same sales order." msgstr "" -"**Crear tareas y seguimiento de horas**: en este modo, se crea una tarea " -"para cada línea de la orden de venta. Entonces, cuando usted hace la hoja de" -" tiempos, no grabar las horas en una orden de venta/contrato, pero ustedes " -"registrarán las horas en una tarea (que representa el contrato). La ventaja " -"de esta solución es que permite vender varios contratos de servicio dentro " -"de la misma orden de venta." -#: ../../sales/invoicing/services/support.rst:153 +#: ../../sales/invoicing/services/support.rst:150 msgid "" "**Manually**: you can use this mode if you don't record timesheets in Odoo. " "The number of hours you worked on a specific contract can be recorded " -"manually on the sale order line directly, in the delivered quantity field." +"manually on the sales order line directly, in the delivered quantity field." msgstr "" -"**Manualmente**: usted puede utilizar este modo si no desea registrar las " -"hojas de horas en Odoo. El número de horas de Odoo trabajado está " -"especificado en el contrato y puede ser registrado manualmente en la orden " -"de venta en una línea directamente, en el campo de la cantidad entregada." -#: ../../sales/invoicing/services/support.rst:159 +#: ../../sales/invoicing/services/support.rst:156 msgid ":doc:`../../../inventory/settings/products/uom`" msgstr ":doc:`../../../inventory/settings/products/uom`" @@ -1382,15 +1340,11 @@ msgstr ":menuselection:`Orden de Comercio electrónico --> Factura`" #: ../../sales/overview/main_concepts/invoicing.rst:69 msgid "" -"An eCommerce order will also trigger the creation of the order when it is " +"An eCommerce order will also trigger the creation of the invoice when it is " "fully paid. If you allow paying orders by check or wire transfer, Odoo only " "creates an order and the invoice will be triggered once the payment is " "received." msgstr "" -"Una orden de comercio electrónico también se activará la creación de la " -"orden cuando está totalmente pagada. Si usted permite que el pago de pedidos" -" por cheque o transferencia bancaria, Odoo sólo creará un pedido y la " -"factura se activará una vez que se recibe el pago." #: ../../sales/overview/main_concepts/invoicing.rst:75 msgid "Creating an invoice manually" @@ -1709,140 +1663,76 @@ msgid "Manage your products" msgstr "" #: ../../sales/products_prices/products/import.rst:3 -msgid "How to import my products" +msgid "How to import products with categories and variants" msgstr "" -#: ../../sales/products_prices/products/import.rst:6 -msgid "How to start" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:8 -msgid "Download the following import templates:" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:10 +#: ../../sales/products_prices/products/import.rst:5 msgid "" -"Partners: customers, vendors (no relation field, can be imported as is)" +"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 "Products (no relation field, can be imported as is)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:12 -msgid "Product Website Categories" +msgid "How to customize the file" msgstr "" #: ../../sales/products_prices/products/import.rst:13 -msgid "Product Attributes & Values" +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:14 -msgid "Products with Categories & Attributes (3 & 4 must be imported first)" +#: ../../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 "" -"Download link: " -"https://drive.google.com/drive/folders/0B1uIL9E_zXrrTEp5eGI2dXJSUjg?usp=sharing" +"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 "" -"You can open them with any spreadsheets software (Microsoft Office, " -"OpenOffice, Google Drive, etc.)." +"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:21 -msgid "How to customize the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:23 -msgid "" -"Remove columns you don't need. Don't remove the first one (called *ID*, see " -"why here below)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:25 -msgid "" -"Don't change labels of columns you want to import. Otherwse Odoo won't match" -" the columns automatically." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:27 -msgid "" -"Feel free to add new columns but the fields need to exist in Odoo. If Odoo " -"fails in matching the column name with a field, you can make it manually " -"when importing by browsing a list of available fields." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:30 -msgid "Once modified, keep your file in .csv format." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:33 -msgid "How to import the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:35 -msgid "Go to the Products menu in Sales, Purchase, Website Admin, etc." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:36 -msgid "Switch to list view (top-right corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:37 -msgid "Click the *Import* button (top-left corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:38 -msgid "" -"Make sure all the columns match an existing field. If not select it manually" -" from the drop-down list." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:40 -msgid "Press * Validate* to test the import." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:41 -msgid "" -"If you get \"Everything seems valid.\" as result message, press *Import* to " -"process the real import. Otherwise correct the issues spotted during the " -"test." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:45 +#: ../../sales/products_prices/products/import.rst:24 msgid "Why an “ID” column" msgstr "" -#: ../../sales/products_prices/products/import.rst:47 +#: ../../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:50 +#: ../../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:52 +#: ../../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:53 +#: ../../sales/products_prices/products/import.rst:32 msgid "Import relation fields (see here below)." msgstr "" -#: ../../sales/products_prices/products/import.rst:56 +#: ../../sales/products_prices/products/import.rst:35 msgid "How to import relation fields" msgstr "" -#: ../../sales/products_prices/products/import.rst:58 +#: ../../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 " @@ -1850,7 +1740,7 @@ msgid "" "their own list menu." msgstr "" -#: ../../sales/products_prices/products/import.rst:62 +#: ../../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 \" / " diff --git a/locale/es/LC_MESSAGES/website.po b/locale/es/LC_MESSAGES/website.po index eab98b91d..6d711b443 100644 --- a/locale/es/LC_MESSAGES/website.po +++ b/locale/es/LC_MESSAGES/website.po @@ -10,7 +10,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-04-20 15:45+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: RGB Consulting , 2017\n" +"Last-Translator: Luis M. Ontalba , 2017\n" "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1499,7 +1499,7 @@ msgstr "" #: ../../website/publish/domain_name.rst:15 msgid "Simple and obvious" -msgstr "" +msgstr "Simple y obvio" #: ../../website/publish/domain_name.rst:16 msgid "Easy to remember and spell" @@ -1507,7 +1507,7 @@ msgstr "Fácilmente de recordar y pronunciar" #: ../../website/publish/domain_name.rst:17 msgid "The shorter the better" -msgstr "" +msgstr "Cuanto más corto mejor" #: ../../website/publish/domain_name.rst:18 msgid "Avoid special characters" diff --git a/locale/fr/LC_MESSAGES/accounting.po b/locale/fr/LC_MESSAGES/accounting.po index 58b805433..4b9b3dc78 100644 --- a/locale/fr/LC_MESSAGES/accounting.po +++ b/locale/fr/LC_MESSAGES/accounting.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Cyrille de Lambert , 2017\n" +"Last-Translator: leemannd , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -99,7 +99,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:23 #: ../../accounting/receivables/getting_paid/automated_followups.rst:31 msgid "Configuration" msgstr "Configuration" @@ -1049,7 +1048,6 @@ msgstr "" #: ../../accounting/bank/misc/batch.rst:124 #: ../../accounting/payables/pay/sepa.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:134 msgid "Troubleshooting" msgstr "Dépannage" @@ -1963,6 +1961,11 @@ msgstr "" "Dans l'onglet Pièces Comptables, les comptes de débit et de crédit par " "défaut peuvent être configurés, de même que la devise du journal" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "Type" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1981,14 +1984,26 @@ msgstr "" msgid "Select 'General' for miscellaneous operations journals." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "Société" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Company related to this journal" msgstr "Société associée à ce journal" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "Code" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The journal entries of this journal will be named using this prefix." msgstr "Les pièces comptables de ce journal seront nommées avec ce préfixe." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "Séquence dédiée aux avoirs" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if you don't want to share the same sequence for invoices and" @@ -1997,6 +2012,10 @@ msgstr "" "Cochez cette case si vous ne souhaitez pas partager une même numérotation " "pour les factures et avoirs de ce journal" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "Séquence d'écriture" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the journal " @@ -2005,6 +2024,10 @@ msgstr "" "Cet champ contient les informations relatives à la numérotation des " "écritures de ce journal." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "Séquence d'écriture d'avoir" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the refund " @@ -2013,18 +2036,34 @@ msgstr "" "Ce champ contient les informations relatives à la numérotation des entrées " "d'avoir de ce journal." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "Compte de débit par défaut" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for debit amount" msgstr "Ça sert de compte par défaut pour les montants en débit" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "Compte de crédit par défaut" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for credit amount" msgstr "Sert de compte par défaut pour le crédit" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "Devise" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The currency used to enter statement" msgstr "La devise utilisée pour entrer les relevés" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "Méthodes de débit" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for collecting money. Odoo modules offer various payments " @@ -2036,6 +2075,10 @@ msgstr "" "la méthode de paiement \"Manuelle\" afin de pouvoir gérer les paiements en " "dehors du logiciel. " +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "Moyens de paiement" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for sending money. Odoo modules offer various payments " @@ -2047,6 +2090,10 @@ msgstr "" "la méthode de paiement \"Manuelle\" afin de pouvoir gérer les paiements en " "dehors du logiciel. " +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "Grouper les lignes de facture" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "If this box is checked, the system will try to group the accounting lines " @@ -2055,6 +2102,10 @@ msgstr "" "Si cette case est cochée, le système essaiera de grouper les lignes " "comptables lorsqu'il les créera à partir des factures." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "Compte de profit" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a profit when the ending balance of a cash register differs" @@ -2063,6 +2114,10 @@ msgstr "" "Utilisé pour enregistrer un profit lorsque le solde final de la caisse est " "différent de ce qui a été calculé par le système" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "Compte de perte" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a loss when the ending balance of a cash register differs " @@ -2071,10 +2126,18 @@ msgstr "" "Utilisé pour enregistrer une perte lorsque le solde final de la caisse est " "différent de ce qui a été calculé par le système" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "Montrer le journal dans le tableau de bord" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Whether this journal should be displayed on the dashboard or not" msgstr "Si ce journal doit être affiché sur le tableau de bord ou non." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Technical feature used to know whether check printing was enabled as payment" @@ -2083,20 +2146,37 @@ msgstr "" "Fonction technique utilisée afin de savoir si l'impression du chèque a été " "activée comme méthode de paiement." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "Séquence chèque" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Checks numbering sequence." msgstr "Séquence de numérotation des chèques." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "Numérotation manuelle" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 #: ../../accounting/payables/pay/check.rst:0 msgid "Check this option if your pre-printed checks are not numbered." msgstr "" "Cochez cette option si vos chèques pré-imprimés ne sont pas numérotés." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "Numéro de chèque suivant" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Sequence number of the next printed check." msgstr "Numéro de séquence du prochain chèque imprimé." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "Activé dans le point de vente" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if this journal define a payment method that can be used in a" @@ -2105,6 +2185,10 @@ msgstr "" "Cochez cette case si ce journal défini une méthode de paiement qui peut être" " utilisée dans le point de vente." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "Montant d'écart autorisé" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field depicts the maximum difference allowed between the ending balance" @@ -2358,6 +2442,10 @@ msgstr "" msgid "Explanation of the fields:" msgstr "Explication des champs :" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "État" + #: ../../accounting/others/adviser/assets.rst:0 msgid "When an asset is created, the status is 'Draft'." msgstr "Lorsqu'une immobilisation est créée, le statut est « Brouillon »." @@ -2379,22 +2467,42 @@ msgstr "" "est terminé. Si la dernière ligne de l'amortissement est comptabilisée, " "l'immobilisation passe automatiquement dans ce statut." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "Catégorie" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Category of asset" msgstr "Catégorie d'immobilisation" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "Date " + #: ../../accounting/others/adviser/assets.rst:0 msgid "Date of asset" msgstr "Date de l'immobilisation" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "Valeur brute" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Gross value of asset" msgstr "Valeur brute des immobilisations" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "Valeur résiduelle" + #: ../../accounting/others/adviser/assets.rst:0 msgid "It is the amount you plan to have that you cannot depreciate." msgstr "Il s'agit de la part non dépréciable de l'immobilisation." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "Méthode de calcul" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the amount of depreciation lines." msgstr "" @@ -2414,6 +2522,10 @@ msgstr "" "* Dégressif : Calculé sur la base de: Valeur résiduelle * Taux " "d'amortissement Dégressif" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "Méthode temporelle basée sur" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Choose the method to use to compute the dates and number of depreciation " @@ -2438,6 +2550,10 @@ msgstr "" "* Date de fin : Choisissez le temps entre 2 amortissements et la date au " "delà de laquelle les amortissements cesseront." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "Prorata temporis" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Indicates that the first depreciation entry for this asset have to be done " @@ -2447,11 +2563,19 @@ msgstr "" "Indiquez si le premier amortissement doit être calculé à partir de la date " "d'achat ou à partir du 1er janvier / premier jour de l'exercice comptable." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "Nombre d'amortissements" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The number of depreciations needed to depreciate your asset" msgstr "" "Le nombre d'amortissements nécessaire pour amortir votre immobilisation" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "Nombre de mois dans une période" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The amount of time between two depreciations, in months" msgstr "La durée entre deux amortissements, en mois" @@ -4388,17 +4512,29 @@ msgstr "" "pour gérer les clôtures d'exercices (et établir les écritures " "correspondantes)" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "Étiquettes" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Optional tags you may want to assign for custom reporting" msgstr "" "Étiquettes optionnelles que vous pourriez assigner pour des rapports " "personnalisés" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "Devise du compte" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Forces all moves for this account to have this account currency." msgstr "" "Oblige toutes les écritures de ce compte à avoir cette devise secondaire." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "Type interne" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "The 'Internal Type' is used for features available on different types of " @@ -4410,6 +4546,10 @@ msgstr "" "les comptes banquaires, payabls/recevables par les comptes des " "vendeurs/clients" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "Autoriser le lettrage" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "Check this box if this account allows invoices & payments matching of " @@ -9439,10 +9579,18 @@ msgstr "" msgid "Explanation of the fields of the payment screen:" msgstr "Explication des champs de l'écran de paiement :" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used for usability purposes" msgstr "Champ technique utilisé à des fins ergonomiques" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to hide the payment method if the selected journal has " @@ -9451,6 +9599,10 @@ msgstr "" "Champ technique utilisé pour cacher la méthode de paiement si le journal " "sélectionné a seulement une méthode possible qui est \"manuelle\"" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "Code" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to adapt the interface to the payment type selected." @@ -9458,6 +9610,10 @@ msgstr "" "Champ technique utilisé pour adapter l'interface au type de paiement " "sélectionné ." +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "Numéro de chèque" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "The selected journal is configured to print check numbers. If your pre-" @@ -12421,8 +12577,8 @@ msgstr ":doc:`recording`" #: ../../accounting/receivables/customer_payments/credit_cards.rst:167 #: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`paypal`" -msgstr ":doc:`paypal`" +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:169 #: ../../accounting/receivables/customer_payments/recording.rst:130 @@ -12730,268 +12886,6 @@ msgstr "" "Vous pouvez obtenir le DMP de votre entreprise dans le rapport Note de " "Synthèse (vérifier les ICP jours moyens débiteurs)." -#: ../../accounting/receivables/customer_payments/paypal.rst:3 -msgid "How to accept paypal payments on invoices?" -msgstr "Comment accepter les paiements PayPal des factures?" - -#: ../../accounting/receivables/customer_payments/paypal.rst:5 -msgid "" -"The \"Paypal Payment Acquirer\" module allows you to accept payments via " -"paypal, for your sales orders, invoices, or online orders. As paypal accepts" -" payments through credit cards (VISA, Mastercard, …), you will be able to " -"process most payment methods." -msgstr "" -"Le module « Intermédiaire de paiement PayPal » vous permet d'accepter les " -"paiements par PayPal, pour vos commandes client, vos factures, ou vos " -"commandes en ligne. Comme PayPal accepte les paiements par cartes de crédit " -"(VISA, Mastercard, ...), vous serez en mesure de traiter la plupart des " -"méthodes de paiement." - -#: ../../accounting/receivables/customer_payments/paypal.rst:10 -msgid "Paypal support two modes:" -msgstr "Paypal prend en charge deux modes de fonctionnement :" - -#: ../../accounting/receivables/customer_payments/paypal.rst:12 -msgid "" -"Paypal Merchant Account: the user is redirected to paypal to do the payment " -"(either with a credit card or a paypal account)" -msgstr "" -"Compte marchand PayPal : l'utilisateur est redirigé vers PayPal pour faire " -"le paiement (avec une carte de crédit ou un compte PayPal)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:15 -msgid "" -"PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to " -"paypal and the payment can be done in the background. This method is mostly " -"used for subscription businesses where you need to charge your customers " -"periodically." -msgstr "" -"PayPal PayFlow Pro (S2S, Serveur 2 Serveur): l'utilisateur n'est pas " -"redirigé vers PayPal et le paiement peut être fait en arrière-plan. Cette " -"méthode est surtout utilisée par les entreprises vendant des abonnements qui" -" doivent facturer périodiquement leurs clients." - -#: ../../accounting/receivables/customer_payments/paypal.rst:20 -msgid "As of today, Odoo only support the normal Paypal Merchant Account." -msgstr "À ce jour, Odoo ne supporte que la méthode Compte Marchand PayPal." - -#: ../../accounting/receivables/customer_payments/paypal.rst:26 -msgid "Install the \"PayPal Payment Acquirer\" module" -msgstr "Installez le module « Intermédiaire de paiement PayPal »" - -#: ../../accounting/receivables/customer_payments/paypal.rst:28 -msgid "Start by installing the **PayPal Payment Acquirer** module." -msgstr "" -"Commencez par installer le module **Intermédiaire de paiement PayPal**" - -#: ../../accounting/receivables/customer_payments/paypal.rst:30 -msgid "" -"Once the module is installed, you should see a new payment acquirer in the " -"Setting application, menu \"Payment Acquirers\"." -msgstr "" -"Une fois le module installé, vous devriez trouver un nouvel intermédiaire de" -" paiement en allant dans :menuselection:`Configuration -->Intermédiaires de " -"paiement`." - -#: ../../accounting/receivables/customer_payments/paypal.rst:36 -msgid "" -"By default, Paypal is configured to work in a test environment, out-of-the-" -"box. It means you can already test the full order to payment flow with the " -"paypal sandbox, without having to configure the next steps." -msgstr "" -"Par défaut, PayPal est configuré pour fonctionner dans un environnement de " -"test, out-of-the-box. Cela signifie que vous pouvez déjà tester le " -"cheminement complet de la commande au paiement avec le bac à sable PayPal, " -"sans avoir à configurer les prochaines étapes." - -#: ../../accounting/receivables/customer_payments/paypal.rst:42 -msgid "Creating and configuring a PayPal merchant account" -msgstr "Création et configuration d'un compte marchand PayPal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:45 -msgid "Create a basic Paypal account" -msgstr "Créer un compte de base PayPal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:47 -msgid "Existing or newly created Personal Paypal account can be used." -msgstr "" -"Un compte personnel PayPal existant ou nouvellement créé peut être utilisé." - -#: ../../accounting/receivables/customer_payments/paypal.rst:49 -msgid "Or upgrade your account to Business account (merchant) if needed" -msgstr "" -"Et transformez votre compte en un compte Business (marchand) si nécessaire" - -#: ../../accounting/receivables/customer_payments/paypal.rst:55 -msgid "Paypal Account Summary page" -msgstr "Extrait de la page de gestion de compte PayPal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:58 -msgid "Paypal Configuration" -msgstr "Configuration Paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:60 -msgid "" -"Access \"Seller preferences\" menu from `PayPal website " -"`__" -msgstr "" -"Accéder au menu \"Préférences de vendeur\" sur le `site PayPal " -"` __" - -#: ../../accounting/receivables/customer_payments/paypal.rst:66 -msgid "" -"Access \"Website preferences\" and configure Auto Return (Payment Data " -"Transfer must be left to Off)" -msgstr "" -"Allez à \"Website preferences\" and activez Auto Return (Payment Data " -"Transfer doit être laissé à Off)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:69 -msgid "**Database name**: yourcompany" -msgstr "**Nom de la base de données** : yourcompany" - -#: ../../accounting/receivables/customer_payments/paypal.rst:70 -#: ../../accounting/receivables/customer_payments/paypal.rst:88 -msgid "**Website URL**: https://yourcompany.odoo.com/" -msgstr "**URL du site web**: https://yourcompany.odoo.com/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:71 -msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" -msgstr "**URL de retour**: https://yourcompany.odoo.com/shop/confirmation" - -#: ../../accounting/receivables/customer_payments/paypal.rst:76 -msgid "These settings will redirect your buyer to your web confirmation page." -msgstr "" -"Ces paramètres redirigerons votre acheteur vers votre page web de " -"confirmation." - -#: ../../accounting/receivables/customer_payments/paypal.rst:80 -msgid "Access and edit Instant payment notifications settings - IPN" -msgstr "" -"Accédez et modifiez les réglages de notification instantanée de paiement - " -"IPN" - -#: ../../accounting/receivables/customer_payments/paypal.rst:85 -msgid "Example" -msgstr "Exemple" - -#: ../../accounting/receivables/customer_payments/paypal.rst:87 -msgid "**Database name**: \"yourcompany\"" -msgstr "**Nom de la base de données** : \"yourcompany\"" - -#: ../../accounting/receivables/customer_payments/paypal.rst:89 -msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" -msgstr "" -"**URL de notification**: https://yourcompany.odoo.com/payment/paypal/ipn/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:91 -msgid "" -"Verify that your Notify URL uses the correct protocol (HTTP / HTTPS). If you" -" use the odoo.com domain, we advise you to use HTTPS." -msgstr "" -"Vérifiez que votre Notification URL utilise the bon protocole (HTTP / " -"HTTPS). Si vous utilisez le domaine odoo.com, nous vous conseillons " -"d'utiliser HTTPS." - -#: ../../accounting/receivables/customer_payments/paypal.rst:94 -msgid "" -"Set the encoding to UTF-8 from the menu :menuselection:`Settings --> " -"Language Encoding --> More Options --> More selling tools`" -msgstr "" -"Définissez l'encodage à UTF-8 dans le menu :menuselection:`Paramètres --> " -"Jeu de caractères --> Plus d'Options --> Plus d'outils vente`" - -#: ../../accounting/receivables/customer_payments/paypal.rst:103 -msgid "" -"Record your Merchant Paypal ID (personal or business account both will have " -"it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> " -"Account Options`." -msgstr "" -"Notez votre ID de marchand PayPal (un compte personnel comme un compte " -"business en aura un), il devra être enregistré en retour dans Odoo " -":menuselection:`Réglages PayPal --> Options du Compte`." - -#: ../../accounting/receivables/customer_payments/paypal.rst:111 -msgid "" -"If you want your customers to be able to pay through Paypal while not having" -" a Paypal account- following setting \"Paypal Account Optional\" needs to be" -" set to **ON**. All users will be able to choose Credit/debit card payment " -"option - Paypal account not required." -msgstr "" -"Si vous voulez que vos clients puissent payer avec Paypal sans avoir de " -"compte Paypal, le paramètre \"Compte Paypal Facultatif\" doit être réglé sur" -" **ON**. Tous les utilisateurs pourrront alors choisir l'option de paiement " -"par carte de crédit. Un compte Paypal ne sera pas nécessaire." - -#: ../../accounting/receivables/customer_payments/paypal.rst:120 -msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" -msgstr "" -"Configurez les informations d'identification de votre compte « Intermédiaire" -" de paiement Paypal » dans Odoo" - -#: ../../accounting/receivables/customer_payments/paypal.rst:122 -msgid "" -":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" -msgstr "" -":menuselection:`Configuration --> Paiements --> Intermédiaires de paiement " -"--> Paypal`" - -#: ../../accounting/receivables/customer_payments/paypal.rst:124 -msgid "**Paypal Email ID**: your paypal account email address" -msgstr "" -"**Email du compte Paypal** : l'adresse de courriel de votre compte paypal" - -#: ../../accounting/receivables/customer_payments/paypal.rst:126 -msgid "**Paypal Merchant ID**: ID retrieved at previous step" -msgstr "**ID de marchand Paypal**: ID noté à une étape précédente" - -#: ../../accounting/receivables/customer_payments/paypal.rst:136 -msgid "" -"If your eCommerce customer gets this Error Message after completing Paypal " -"payment instead of being redirected to your database:" -msgstr "" -"Si votre client eCommerce reçoit ce message d'erreur après avoir terminé le " -"paiement PayPal au lieu d'être redirigé vers votre site :" - -#: ../../accounting/receivables/customer_payments/paypal.rst:142 -msgid "" -"Verify the settings you have `configured in Paypal `_:" -msgstr "" -"Vérifiez les réglages que vous avez `configurés dans Paypal " -"`_:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:144 -msgid "" -"Auto Return should be on (the value can be quite generic, like " -"/shop/confirmation; the correct URL will be set for each " -"transaction)" -msgstr "" -"Auto Return doit être sur On (la valeur peut être assez générique, comme " -"/shop/confirmation, l'URL correcte sera définie pour chaque " -"transaction)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:148 -msgid "Payment Data Transfer should be off" -msgstr "Payment Data Transfer doit être sur off" - -#: ../../accounting/receivables/customer_payments/paypal.rst:150 -msgid "" -"On-premise databases must be accessible through classic HTTP/HTTPS ports " -"(80/443) for Paypal to work correctly, usually through a reverse proxy. " -"Contact your integrating partner if you are unsure this is the case. " -"Databases hosted on odoo.com are already configured correctly." -msgstr "" -"Les bases de données sur-site doivent être accessibles par le biais des " -"ports classiques HTTP/HTTPS (80/443) pour que Paypal fonctionne " -"correctement, généralement par le biais d'un proxy inverse. Contactez votre " -"partenaire intégrateur si vous n'êtes pas sûr que ce soit le cas. Les bases " -"de données hébergées sur odoo.com sont déjà correctement configurées." - -#: ../../accounting/receivables/customer_payments/paypal.rst:157 -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" -msgstr ":doc:`credit_cards`" - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "Quelles sont les différentes façons d'enregistrer un paiement ?" @@ -13206,6 +13100,10 @@ msgstr "" "Pour faire un transfert interne d'un compte bancaire à un autre, depuis le tableau de bord sélectionnez « Tranfert interne » sur la carte du compte bancaire à débiter. Puis dans l'écran d'enregistrement des paiements, sélectionnez le compte à créditer.\n" "Ne refaites pas la même opération à partir du compte bancaire à créditer, ou vous allez créer deux pièces comptables qui vont s'annuler pour la même transaction." +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr ":doc:`credit_cards`" + #: ../../accounting/receivables/getting_paid.rst:3 msgid "How to get paid?" msgstr "Comment se faire payer ?" diff --git a/locale/fr/LC_MESSAGES/applications.po b/locale/fr/LC_MESSAGES/applications.po index 742be1c6c..273cf4eaf 100644 --- a/locale/fr/LC_MESSAGES/applications.po +++ b/locale/fr/LC_MESSAGES/applications.po @@ -20,4 +20,4 @@ msgstr "" #: ../../applications.rst:3 msgid "Applications" -msgstr "Candidatures" +msgstr "Applications" diff --git a/locale/fr/LC_MESSAGES/discuss.po b/locale/fr/LC_MESSAGES/discuss.po index b813d0c1d..6cdbfb617 100644 --- a/locale/fr/LC_MESSAGES/discuss.po +++ b/locale/fr/LC_MESSAGES/discuss.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Martin Trigaux , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" @@ -23,7 +23,7 @@ msgid "Discuss" msgstr "Discussions" #: ../../discuss/email_servers.rst:3 -msgid "How to use my own email servers to send and receive messages in Odoo" +msgid "How to use my own email servers to send and receive email in Odoo" msgstr "" #: ../../discuss/email_servers.rst:6 @@ -31,138 +31,230 @@ msgid "When is it needed" msgstr "" #: ../../discuss/email_servers.rst:7 -msgid "You need it if you use Odoo Community or Enterprise." -msgstr "" - -#: ../../discuss/email_servers.rst:10 -msgid "What if I use Odoo Online" -msgstr "" - -#: ../../discuss/email_servers.rst:11 msgid "" -"You are done! Odoo Online comes up with an embedded and ready-to-use email " -"server (*@yourcompany.odoo.com*). We recommend to keep this default setting " -"as is as it is really convenient." +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." +msgstr "" + +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" msgstr "" #: ../../discuss/email_servers.rst:15 msgid "" -"Indeed, while it is branded by Odoo, the visible source of any message sent " -"from Odoo will be your personal email address (your Odoo login). Your " -"contacts will therefore trust your messages." -msgstr "" - -#: ../../discuss/email_servers.rst:20 -msgid "How does it work when a contact replies to an email sent from Odoo" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." msgstr "" #: ../../discuss/email_servers.rst:21 msgid "" -"Default reply-to is a generic address used to automatically route any " -"incoming email to the discussion thread of the origin business object " -"(opportunity, order, task, etc.) and to the inbox of all its followers. By " -"default this address is \"catchall@\" but it can be changed. Thanks to it, " -"you get a perfect message thread in Odoo and you don't pollute your external" -" email box with Odoo-related topics." +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:29 -msgid "How to use my own email servers" -msgstr "" - -#: ../../discuss/email_servers.rst:30 -msgid "" -"You need to be a system admin to set this up. Go to :menuselection:`Settings" -" --> General Settings` and check *External Email Servers* (watch out: this " -"checkbox only shows up after Odoo 10). Then, go through the following steps." -msgstr "" - -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/email_servers.rst:26 msgid "Set an outgoing email server for outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:37 +#: ../../discuss/email_servers.rst:27 msgid "" "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " "etc.) as well as your admin credentials. Once all the information has been " "filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:45 +#: ../../discuss/email_servers.rst:35 msgid "Set an incoming email server for inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:46 +#: ../../discuss/email_servers.rst:36 msgid "" "Fill out the form according to your email provider’s settings. Leave the " "*Actions to Perform on Incoming Mails* blank. Once all the information has " "been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:53 +#: ../../discuss/email_servers.rst:43 msgid "" "By default inbound messages are fetched every 5 minutes. You can change this" " value in developer mode. Go to :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/email_servers.rst:59 +#: ../../discuss/email_servers.rst:49 msgid "Set the domain name" msgstr "" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/email_servers.rst:50 msgid "" "Enter the domain name of your email servers (e.g. mycompany.com) in General " "Settings." msgstr "" -#: ../../discuss/email_servers.rst:67 +#: ../../discuss/email_servers.rst:57 msgid "Create a catchall address" msgstr "" -#: ../../discuss/email_servers.rst:68 +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 msgid "" "Create a catchall address in your email server settings. We advise you to " "use \"catchall@\" so that everything works out straight away. If you want to" " use another alias, you have extra steps in Odoo:" msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/email_servers.rst:67 msgid "Activate the developer mode from your Settings Dashboard." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/email_servers.rst:72 msgid "" "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " "Parameters --> System Parameters` and enter your custom catchall alias in " "*mail.catchall.alias*." msgstr "" -#: ../../discuss/email_servers.rst:84 +#: ../../discuss/email_servers.rst:79 msgid "You can edit the email alias used for bounced messages the same way." msgstr "" -#: ../../discuss/email_servers.rst:87 -msgid "How to perfectly combine Odoo Discuss and my traditional email tool" +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" msgstr "" -#: ../../discuss/email_servers.rst:88 +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here `__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 msgid "" "Odoo Discuss is a perfect tool to send and read messages related to business" -" objects. But it doesn't aim to replace a full-featured email software " -"(Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " "both systems without mingling them: What is related to Odoo business objects" -" or applications goes into Odoo; What is not stays into your external email " -"boxes." +" or applications goes into Odoo; What is not can be managed into your " +"external email box." msgstr "" -#: ../../discuss/email_servers.rst:95 +#: ../../discuss/email_servers.rst:150 msgid "" "To do so, create specific email aliases to use in Odoo (to generate leads or" " opportunities, helpdesk tickets, etc.). If you take an email alias already " "used for messaging outside of Odoo, incoming messages will land into both " -"systems. This will negatively impact your productivity when it comes to " -"process them." +"systems. This will negatively impact your productivity." msgstr "" #: ../../discuss/mail_twitter.rst:3 diff --git a/locale/fr/LC_MESSAGES/ecommerce.po b/locale/fr/LC_MESSAGES/ecommerce.po index 5af805091..d7455d0b0 100644 --- a/locale/fr/LC_MESSAGES/ecommerce.po +++ b/locale/fr/LC_MESSAGES/ecommerce.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Clo , 2017\n" +"Last-Translator: Melanie Bernard , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -655,23 +655,21 @@ msgid "Launch my website" msgstr "" #: ../../ecommerce/shopper_experience.rst:3 -msgid "Improve shopper experience" +msgid "Get paid" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to set up payment methods" +msgid "How to get paid with payment acquirers" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:5 msgid "" -"To collect payments, you can either request your customers to process it " -"manually (e.g. wire transfer) or redirect them to payment acquirers. The " -"payment process described hereunder is common to both eCommerce and online " -"quotations." +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "Payment methods" +msgid "What are the payment methods available" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:13 @@ -681,451 +679,561 @@ msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:15 msgid "" "Wire Transfer is the default payment method available. The aim is providing " -"your customers with your bank details so that they can pay via their bank. " -"This is very easy to start with but slow and inefficient process-wise. Opt " -"for online acquirers as soon as you can!" +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "" -"For B2B users: you can create new manually-processed payment methods (check," -" purchase order, etc.) by renaming 'Wire Transfer' or duplicating it." +msgid "Payment acquirers" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:25 -msgid "Online payment acquirers" +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "" -"Redirect your customers to payment acquirer platforms to collect money " -"effortless. Odoo supports more and more platforms over time: Paypal, " -"Ingenico, Authorize.net, etc. Once the payment accepted, orders are " -"confirmed in Odoo so that the delivery & invoicing processes are triggered " -"automatically." +msgid "`Paypal `__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "Adyen" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "Buckaroo" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Custom (advanced)" -msgstr "" +msgid "Sips" +msgstr "Sips" -#: ../../ecommerce/shopper_experience/payment.rst:35 -msgid "" -"Can be used to request payments to any payment acquirer not listed in Odoo." +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "Edit a payment method" +msgid "How to go live" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:40 msgid "" -"To make payment methods intuitive for your customers feel free to customize " -"them by editing:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:42 -msgid "the name," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:44 -msgid "the picture," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:46 -msgid "" -"the notification messages (thank you & next step, error, cancellation)." +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 msgid "" -"Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers`" -" to do so." +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:51 -msgid "Generic setup" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:53 -msgid "Review the elements here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:55 -msgid "Enter your credentials (online acquirers only)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:57 -msgid "Choose your order confirmation preference (see below)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:59 -msgid "Publish the payment method." +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "Test the payment flow in *Test* mode (default mode)." +msgid "How to debit credit cards to pay subscriptions" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:63 -msgid "Switch to *Production* mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:65 +#: ../../ecommerce/shopper_experience/payment.rst:62 msgid "" -"Se your default payment acquirer in :menuselection:`Accounting --> " -"Configuration --> Settings`. It will be auto-selected for your customers " -"when they enter the payment screen." +"`Odoo Subscription `__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:69 +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 msgid "" -"Rely on the documentation related to your payment acquirer to go through " -"step 2, 5 and 6. Some acquirers provides you with specific credentials for " -"test and production modes (Paypal). Others let you switch mode in their " -"setup interface (Authorize.net)." +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:74 +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 msgid "" -"With Ingenico and Authorize.net, you can let your customers save and reuse a" -" payment card to accelerate the process on next checkouts. See *Store Card " -"Data* in Configuration tab." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:78 -msgid "Payment flow" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:80 -msgid "" -"When choosing the payment method, the customer is taken to the payment " -"acquirer interface to process the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:83 -msgid "" -"Once done he is taken back to Odoo's confirmation page. The transaction " -"status shows up:" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "" -"*Pending*: the order will be confirmed as soon as you authorize the " -"transaction in the acquirer interface." +msgid "How to:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "*Confirmed*: the payment has been authorized automatically." +msgid "Switch to developer mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "" -"A confirmation email is sent to the customer with a copy of the order in " -"pdf. It shows the payment status." +msgid "Take the **Custom** payment method." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Launch the delivery and invoicing from:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:93 msgid "" -"eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:95 -msgid "" -"online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales " -"Orders`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:97 -msgid "" -"For internal tracking purposes, a link to the transaction status is provided" -" in the sales order." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:100 -msgid "" -"If the customer cancels the payment while on the payment acquirer form, it " -"is taken back to the store page (or online quotation) in order to reprocess " -"the order. The payment is marked as *Cancelled* in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:105 -msgid "" -"You can edit the confirmation email template from :menuselection:`Website " -"Admin --> Configuration --> Settings`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:109 -msgid "Order confirmation preferences" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid "There are 4 different behaviors available for any payment acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:114 -msgid "No automatic confirmation" -msgstr "Pas de confirmation automatique" - -#: ../../ecommerce/shopper_experience/payment.rst:116 -msgid "" -"This is the default mode for *Wire Transfer*. It means Odoo does not confirm" -" orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid " -"Order*). Once you get the payment, you are expected to confirm the order " -"manually to pursue the process (delivery, invoicing)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:121 -msgid "" -"Authorize the amount and confirm the SO on acquirer confirmation (capture " -"manually)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:123 -msgid "" -"Odoo confirms the order as soon as the payment success notification comes " -"in. To get the money however, you need to capture it from your payment " -"transaction. In lots of countries you are indeed requested to deliver your " -"goods before capturing the amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:128 -msgid "" -"Authorize & capture the amount and confirm the SO on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:130 -msgid "" -"This is the default mode for payment acquirers. The amount is captured " -"automatically." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:133 -msgid "" -"For B2B: if you use a manual payment method like *Wire Transfer* and don't " -"expect any upfront payment to launch the delivery, switch to this mode as " -"well." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:137 -msgid "" -"Authorize & capture the amount, confirm the SO and auto-validate the invoice" -" on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:139 -msgid "" -"If you invoice upfront and not at the delivery, switch to this last mode to " -"automate everything. You are requested to select a Payment Journal to record" -" such payments (see " -":doc:`../../accounting/receivables/customer_payments/credit_cards`)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:144 -msgid "Custom payment acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:146 -msgid "" -"Odoo can submit payment requests and redirect to any payment acquirer. In " -"such a case, you need to confirm the sale manually in Odoo once you get paid" -" because Odoo cannot read any payment status sent by the acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:150 -msgid "To configure this:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:152 -msgid "switch to developer mode," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:154 -msgid "edit the *Custom* payment method," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:156 -msgid "" -"set up the payment form (S2S Form Template) as instructed by your payment " +"Set up the payment form (S2S Form Template) as instructed by your payment " "acquirer. You can start from *default_acquirer_button* that you can " "duplicate." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:160 -msgid "Recurring payments & Installment plans" +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:162 +#: ../../ecommerce/shopper_experience/payment.rst:98 msgid "" -"The Ingenico integration allows you to process and manage recurring payments" -" from Odoo Subscriptions app out-of-the-box (more information coming soon)." +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"`__)." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:165 +#: ../../ecommerce/shopper_experience/payment.rst:102 msgid "" -"With some customization, Odoo can also trigger installment plans if this is " -"permitted by your payment acquirer’s API:" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. `__" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:168 -msgid "" -"e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic" -"/paypal-payments-standard/integration-guide/installment_buttons)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:170 -msgid "" -"Such a service is made on-demand by our technical experts based on your own " -"requirements. Ask our business advisors at info@odoo.com." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:175 +#: ../../ecommerce/shopper_experience/payment.rst:109 msgid ":doc:`paypal`" msgstr ":doc:`paypal`" +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + #: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "How to collect payments with Paypal" +msgid "How to get paid with Paypal" msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:5 msgid "" -"Paypal is the easiest payment method to configure. It is also the only one " -"without any subscription free." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:9 -msgid "Setup your Paypal account" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:11 -msgid "" -"1. Create a business account at Paypal.com (see: https://www.paypal.com/in" -"/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-" -"outside) or upgrade your account to Business account (merchant) if you have " -"a basic account." +msgid "Set up your Paypal account" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:15 +#: ../../ecommerce/shopper_experience/paypal.rst:13 msgid "" -"2. Log in to your account at Paypal.com and go to :menuselection:`My Account" -" --> Profile --> My Selling Tools`. There click *PayPal button language " -"encoding* under *More Selling Tools* section. Then, click *More Options* and" -" replace the two default encoding formats by *UTF-8*." +"Create a `Paypal Business Account `__ or upgrade " +"your account to *Business account* if you have a basic account." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:20 -msgid "Open Paypal setup form in Odoo and enter your *Email ID*." +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "" +"Log in to `Paypal `__ and open the settings of your " +"**Profile**." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:22 -msgid "" -"4. The Paypal Merchant ID is not mandatory (extra verification level). It is" -" provided in Paypal under :menuselection:`My Account --> Overview`." +msgid "Now enter the menu **My selling tools**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:25 -msgid "" -"5. Configure the IPN feedback (Paypal contacting your Odoo instance without " -"needing the redirection). The setting can be found in " -":menuselection:`Profile --> My Selling Tools --> Instant payment " -"notification`. Activate it and set it to " -"/payment/paypal/ipn." +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:30 +#: ../../ecommerce/shopper_experience/paypal.rst:29 msgid "" -"6. To test the workflow, you can create sandbox accounts by logging in at " -"https://developer.paypal.com/webapps/developer/applications/myapps with the " -"same Paypal credentials. Two default sandbox accounts are automatically " -"generated when you register to Paypal: one is a buyer, the other is a " -"shopper." +"Turn on **Auto Return** and enter the **Return URL**: " +"/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:35 +#: ../../ecommerce/shopper_experience/paypal.rst:36 msgid "" -"7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com " -"(same password than real account) and apply the same format change." +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:39 +#: ../../ecommerce/shopper_experience/paypal.rst:43 msgid "" -"To automatically redirect your customers when the payment is completed, go " -"to your Website Preferences and turn *Auto Return* on. Set *Return URL* to " -"/shop/confirmation. Verify that your *Notify URL* uses " -"the correct protocol (HTTP/HTTPS)." +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "" -"If you want your customers to pay without creating a Paypal account, *Paypal" -" Account Optional* needs to be turned on." +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: /payment/paypal/ipn" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:48 +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 msgid "Transaction fees" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:50 +#: ../../ecommerce/shopper_experience/paypal.rst:114 msgid "" "You can charge an extra to the customer to cover the transaction fees Paypal" " charges you. Once redirected to Paypal, your customer sees an extra applied" " to the order amount." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:53 +#: ../../ecommerce/shopper_experience/paypal.rst:117 msgid "" -"To activate this, go to the *Configuration* tab and check *Add Extra Fees*. " -"Default fees are the ones charged by Paypal." +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site `__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox `__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:3 -msgid "How customers can access their portal" +msgid "How customers can access their customer account" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:5 msgid "" -"It has never been so easy for your customers to access their documents " -"through a portal. Forget endless signup forms, Odoo makes it as easy as ABC." -" With eCommerce and Online Quotation apps, your customers are requested to " -"create a portal account (name, email, password only) from the very first " -"order confirmation or online quotation email they get from you." +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:12 +#: ../../ecommerce/shopper_experience/portal.rst:14 msgid "Sign up" msgstr "S'enregistrer" -#: ../../ecommerce/shopper_experience/portal.rst:14 +#: ../../ecommerce/shopper_experience/portal.rst:16 msgid "" -"When clicking the link in the email or when clicking *Sign up* in the " -"checkout process, your customer is directed to the *Sign up* page." -msgstr "" - -#: ../../ecommerce/shopper_experience/portal.rst:21 -msgid "Customer account" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 msgid "" -"Once logged in the customer will access his account by clicking *My Account*" +"Once logged in the customer will access the account by clicking *My Account*" " in the login dropdown menu." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:29 +#: ../../ecommerce/shopper_experience/portal.rst:31 msgid "" -"From the portal menu all the customer history can be reviewed. The main " -"address (billing) can also be modified." +"THere they find all their history. The main address (billing) can also be " +"modified." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:36 +#: ../../ecommerce/shopper_experience/portal.rst:37 msgid "" -"If a portal user is a contact of a company (*Company* field set in customer " -"detail form), this last will see all the documents of the company and all " -"its other contacts through the portal." +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." msgstr "" #: ../../ecommerce/taxes.rst:3 diff --git a/locale/fr/LC_MESSAGES/general.po b/locale/fr/LC_MESSAGES/general.po index de74fad24..a52e32cf0 100644 --- a/locale/fr/LC_MESSAGES/general.po +++ b/locale/fr/LC_MESSAGES/general.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Olivier Lenoir , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" @@ -23,8 +23,8 @@ msgid "General" msgstr "Général" #: ../../general/auth.rst:3 -msgid "Authentification" -msgstr "" +msgid "Authentication" +msgstr "Authentification" #: ../../general/auth/google.rst:3 msgid "How to allow users to sign in with their Google account" @@ -84,64 +84,196 @@ msgid "" msgstr "" #: ../../general/base_import.rst:3 -msgid "BASE IMPORT" +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" #: ../../general/base_import/import_faq.rst:3 -msgid "Import CSV file to Odoo" +msgid "How to import data into Odoo" msgstr "" -#: ../../general/base_import/import_faq.rst:8 -msgid "Frequently Asked Questions" -msgstr "Foire aux questions" +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "" -#: ../../general/base_import/import_faq.rst:12 -msgid "Need to import data from an other application?" -msgstr "Besoin d'importer des données d'une autre application ?" - -#: ../../general/base_import/import_faq.rst:14 +#: ../../general/base_import/import_faq.rst:7 msgid "" -"In order to re-create relationships between different records, you should " -"use the unique identifier from the original application and map it to the " -"**ID** (External ID) column in Odoo. When you import an other record that " -"links to the first one, use **XXX/ID** (XXX/External ID) to the original " -"unique identifier." +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." msgstr "" #: ../../general/base_import/import_faq.rst:16 msgid "" -"The **ID** (External ID) will also be used to update the original import if " -"you need to re-import modified data later, it's thus good practice to " -"specify it whenever possible." +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." msgstr "" -#: ../../general/base_import/import_faq.rst:21 -msgid "I cannot find the field I want to map my column to?" +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" msgstr "" -#: ../../general/base_import/import_faq.rst:23 -msgid "" -"Odoo try to find with some heuristic, based on the first ten lines of the " -"files, the type of field for each columns inside your file. For example if " -"you have a column only containing numbers, only the fields that are of type " -"integer will be displayed for you to choose from. While this behaviour might" -" be good and easy for most cases scenarios, it is also possible that it goes" -" wrong sometimes or that you want to map your column to a field that is not " -"proposed by default." +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" #: ../../general/base_import/import_faq.rst:25 -msgid "" -"If that happens, you just have to check the **Show all fields for completion" -" (advanced)** option, you will then be able to choose from the complete list" -" of fields for each columns." +msgid "We advise to not remove the **ID** one (see why in the next section)." msgstr "" -#: ../../general/base_import/import_faq.rst:30 +#: ../../general/base_import/import_faq.rst:31 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 msgid "Where can I change the date import format?" msgstr "" -#: ../../general/base_import/import_faq.rst:32 +#: ../../general/base_import/import_faq.rst:81 msgid "" "Odoo can automatically detect if a column is a date and it will try to guess" " the date format from a set of most used date format. While this process can" @@ -151,7 +283,7 @@ msgid "" " day and which one is the month in a date like '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:34 +#: ../../general/base_import/import_faq.rst:83 msgid "" "To view which date format Odoo has found from your file you can check the " "**Date Format** that is shown when clicking on **Options** under the file " @@ -159,7 +291,7 @@ msgid "" " the *ISO 8601* to define the format." msgstr "" -#: ../../general/base_import/import_faq.rst:37 +#: ../../general/base_import/import_faq.rst:86 msgid "" "If you are importing an excel (.xls, .xlsx) file, you can use date cells to " "store dates as the display of dates in excel is different from the way it is" @@ -167,11 +299,11 @@ msgid "" "whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:42 +#: ../../general/base_import/import_faq.rst:91 msgid "Can I import numbers with currency sign (e.g.: $32.00)?" msgstr "" -#: ../../general/base_import/import_faq.rst:44 +#: ../../general/base_import/import_faq.rst:93 msgid "" "Yes, we fully support numbers with parenthesis to represent negative sign as" " well as numbers with currency sign attached to them. Odoo also " @@ -181,56 +313,56 @@ msgid "" "crash." msgstr "" -#: ../../general/base_import/import_faq.rst:46 +#: ../../general/base_import/import_faq.rst:95 msgid "" "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:48 +#: ../../general/base_import/import_faq.rst:97 msgid "32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:49 +#: ../../general/base_import/import_faq.rst:98 msgid "32000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:50 +#: ../../general/base_import/import_faq.rst:99 msgid "32,000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:51 +#: ../../general/base_import/import_faq.rst:100 msgid "-32000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:52 +#: ../../general/base_import/import_faq.rst:101 msgid "(32000.00)" msgstr "" -#: ../../general/base_import/import_faq.rst:53 +#: ../../general/base_import/import_faq.rst:102 msgid "$ 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:54 +#: ../../general/base_import/import_faq.rst:103 msgid "(32000.00 €)" msgstr "" -#: ../../general/base_import/import_faq.rst:56 +#: ../../general/base_import/import_faq.rst:105 msgid "Example that will not work:" msgstr "" -#: ../../general/base_import/import_faq.rst:58 +#: ../../general/base_import/import_faq.rst:107 msgid "ABC 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:59 +#: ../../general/base_import/import_faq.rst:108 msgid "$ (32.000,00)" msgstr "" -#: ../../general/base_import/import_faq.rst:64 +#: ../../general/base_import/import_faq.rst:113 msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" -#: ../../general/base_import/import_faq.rst:66 +#: ../../general/base_import/import_faq.rst:115 msgid "" "By default the Import preview is set on commas as field separators and " "quotation marks as text delimiters. If your csv file does not have these " @@ -238,20 +370,20 @@ msgid "" " CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:68 +#: ../../general/base_import/import_faq.rst:117 msgid "" "Note that if your CSV file has a tabulation as separator, Odoo will not " "detect the separations. You will need to change the file format options in " "your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:73 +#: ../../general/base_import/import_faq.rst:122 msgid "" "How can I change the CSV file format options when saving in my spreadsheet " "application?" msgstr "" -#: ../../general/base_import/import_faq.rst:75 +#: ../../general/base_import/import_faq.rst:124 msgid "" "If you edit and save CSV files in speadsheet applications, your computer's " "regional settings will be applied for the separator and delimiter. We " @@ -260,17 +392,17 @@ msgid "" "filter settings' > Save)." msgstr "" -#: ../../general/base_import/import_faq.rst:77 +#: ../../general/base_import/import_faq.rst:126 msgid "" "Microsoft Excel will allow you to modify only the encoding when saving (in " "'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." msgstr "" -#: ../../general/base_import/import_faq.rst:82 +#: ../../general/base_import/import_faq.rst:131 msgid "What's the difference between Database ID and External ID?" msgstr "" -#: ../../general/base_import/import_faq.rst:84 +#: ../../general/base_import/import_faq.rst:133 msgid "" "Some fields define a relationship with another object. For example, the " "country of a contact is a link to a record of the 'Country' object. When you" @@ -280,58 +412,58 @@ msgid "" "import." msgstr "" -#: ../../general/base_import/import_faq.rst:86 +#: ../../general/base_import/import_faq.rst:135 msgid "" "For example, to reference the country of a contact, Odoo proposes you 3 " "different fields to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:88 +#: ../../general/base_import/import_faq.rst:137 msgid "Country: the name or code of the country" msgstr "Pays : le nom ou code du pays" -#: ../../general/base_import/import_faq.rst:89 +#: ../../general/base_import/import_faq.rst:138 msgid "" "Country/Database ID: the unique Odoo ID for a record, defined by the ID " "postgresql column" msgstr "" -#: ../../general/base_import/import_faq.rst:90 +#: ../../general/base_import/import_faq.rst:139 msgid "" "Country/External ID: the ID of this record referenced in another application" " (or the .XML file that imported it)" msgstr "" -#: ../../general/base_import/import_faq.rst:92 +#: ../../general/base_import/import_faq.rst:141 msgid "For the country Belgium, you can use one of these 3 ways to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:94 +#: ../../general/base_import/import_faq.rst:143 msgid "Country: Belgium" msgstr "Pays : Belgique" -#: ../../general/base_import/import_faq.rst:95 +#: ../../general/base_import/import_faq.rst:144 msgid "Country/Database ID: 21" msgstr "" -#: ../../general/base_import/import_faq.rst:96 +#: ../../general/base_import/import_faq.rst:145 msgid "Country/External ID: base.be" msgstr "Pays/Id. externe: base.be" -#: ../../general/base_import/import_faq.rst:98 +#: ../../general/base_import/import_faq.rst:147 msgid "" "According to your need, you should use one of these 3 ways to reference " "records in relations. Here is when you should use one or the other, " "according to your need:" msgstr "" -#: ../../general/base_import/import_faq.rst:100 +#: ../../general/base_import/import_faq.rst:149 msgid "" "Use Country: This is the easiest way when your data come from CSV files that" " have been created manually." msgstr "" -#: ../../general/base_import/import_faq.rst:101 +#: ../../general/base_import/import_faq.rst:150 msgid "" "Use Country/Database ID: You should rarely use this notation. It's mostly " "used by developers as it's main advantage is to never have conflicts (you " @@ -339,13 +471,13 @@ msgid "" "Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:102 +#: ../../general/base_import/import_faq.rst:151 msgid "" "Use Country/External ID: Use External ID when you import data from a third " "party application." msgstr "" -#: ../../general/base_import/import_faq.rst:104 +#: ../../general/base_import/import_faq.rst:153 msgid "" "When you use External IDs, you can import CSV files with the \"External ID\"" " column to define the External ID of each record you import. Then, you will " @@ -354,23 +486,23 @@ msgid "" "Products and their Categories." msgstr "" -#: ../../general/base_import/import_faq.rst:106 +#: ../../general/base_import/import_faq.rst:155 msgid "" "`CSV file for categories " "<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:108 +#: ../../general/base_import/import_faq.rst:157 msgid "" "`CSV file for Products " "<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:112 +#: ../../general/base_import/import_faq.rst:161 msgid "What can I do if I have multiple matches for a field?" msgstr "Que puis-je faire si j'ai plusieurs correspondances pour un champ ?" -#: ../../general/base_import/import_faq.rst:114 +#: ../../general/base_import/import_faq.rst:163 msgid "" "If for example you have two product categories with the child name " "\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " @@ -381,20 +513,20 @@ msgid "" "the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:116 +#: ../../general/base_import/import_faq.rst:165 msgid "" "However if you do not wish to change your configuration of product " "categories, we recommend you use make use of the external ID for this field " "'Category'." msgstr "" -#: ../../general/base_import/import_faq.rst:121 +#: ../../general/base_import/import_faq.rst:170 msgid "" "How can I import a many2many relationship field (e.g. a customer that has " "multiple tags)?" msgstr "" -#: ../../general/base_import/import_faq.rst:123 +#: ../../general/base_import/import_faq.rst:172 msgid "" "The tags should be separated by a comma without any spacing. For example, if" " you want your customer to be linked to both tags 'Manufacturer' and " @@ -402,19 +534,19 @@ msgid "" " of your CSV file." msgstr "" -#: ../../general/base_import/import_faq.rst:125 +#: ../../general/base_import/import_faq.rst:174 msgid "" "`CSV file for Manufacturer, Retailer " "<../../_static/example_files/m2m_customers_tags.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:130 +#: ../../general/base_import/import_faq.rst:179 msgid "" "How can I import a one2many relationship (e.g. several Order Lines of a " "Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:132 +#: ../../general/base_import/import_faq.rst:181 msgid "" "If you want to import sales order having several order lines; for each order" " line, you need to reserve a specific row in the CSV file. The first order " @@ -425,41 +557,41 @@ msgid "" "you can import, based on demo data." msgstr "" -#: ../../general/base_import/import_faq.rst:135 +#: ../../general/base_import/import_faq.rst:184 msgid "" "`File for some Quotations " "<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:137 +#: ../../general/base_import/import_faq.rst:186 msgid "" "The following CSV file shows how to import purchase orders with their " "respective purchase order lines:" msgstr "" -#: ../../general/base_import/import_faq.rst:139 +#: ../../general/base_import/import_faq.rst:188 msgid "" "`Purchase orders with their respective purchase order lines " "<../../_static/example_files/o2m_purchase_order_lines.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:141 +#: ../../general/base_import/import_faq.rst:190 msgid "" "The following CSV file shows how to import customers and their respective " "contacts:" msgstr "" -#: ../../general/base_import/import_faq.rst:143 +#: ../../general/base_import/import_faq.rst:192 msgid "" "`Customers and their respective contacts " "<../../_static/example_files/o2m_customers_contacts.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:148 +#: ../../general/base_import/import_faq.rst:197 msgid "Can I import several times the same record?" msgstr "Puis-je importer plusieurs fois le même enregistrement ?" -#: ../../general/base_import/import_faq.rst:150 +#: ../../general/base_import/import_faq.rst:199 msgid "" "If you import a file that contains one of the column \"External ID\" or " "\"Database ID\", records that have already been imported will be modified " @@ -469,17 +601,17 @@ msgid "" "depending if it's new or not." msgstr "" -#: ../../general/base_import/import_faq.rst:152 +#: ../../general/base_import/import_faq.rst:201 msgid "" "This feature allows you to use the Import/Export tool of Odoo to modify a " "batch of records in your favorite spreadsheet application." msgstr "" -#: ../../general/base_import/import_faq.rst:157 +#: ../../general/base_import/import_faq.rst:206 msgid "What happens if I do not provide a value for a specific field?" msgstr "" -#: ../../general/base_import/import_faq.rst:159 +#: ../../general/base_import/import_faq.rst:208 msgid "" "If you do not set all fields in your CSV file, Odoo will assign the default " "value for every non defined fields. But if you set fields with empty values " @@ -487,11 +619,11 @@ msgid "" "assigning the default value." msgstr "" -#: ../../general/base_import/import_faq.rst:164 +#: ../../general/base_import/import_faq.rst:213 msgid "How to export/import different tables from an SQL application to Odoo?" msgstr "" -#: ../../general/base_import/import_faq.rst:166 +#: ../../general/base_import/import_faq.rst:215 msgid "" "If you need to import data from different tables, you will have to recreate " "relations between records belonging to different tables. (e.g. if you import" @@ -499,7 +631,7 @@ msgid "" "person and the company they work for)." msgstr "" -#: ../../general/base_import/import_faq.rst:168 +#: ../../general/base_import/import_faq.rst:217 msgid "" "To manage relations between tables, you can use the \"External ID\" " "facilities of Odoo. The \"External ID\" of a record is the unique identifier" @@ -509,7 +641,7 @@ msgid "" "'company_1', 'person_1' instead of '1')" msgstr "" -#: ../../general/base_import/import_faq.rst:170 +#: ../../general/base_import/import_faq.rst:219 msgid "" "As an example, suppose you have a SQL database with two tables you want to " "import: companies and persons. Each person belong to one company, so you " @@ -519,27 +651,27 @@ msgid "" "PostgreSQL database)" msgstr "" -#: ../../general/base_import/import_faq.rst:172 +#: ../../general/base_import/import_faq.rst:221 msgid "" "We will first export all companies and their \"External ID\". In PSQL, write" " the following command:" msgstr "" -#: ../../general/base_import/import_faq.rst:178 +#: ../../general/base_import/import_faq.rst:227 msgid "This SQL command will create the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:185 +#: ../../general/base_import/import_faq.rst:234 msgid "" "To create the CSV file for persons, linked to companies, we will use the " "following SQL command in PSQL:" msgstr "" -#: ../../general/base_import/import_faq.rst:191 +#: ../../general/base_import/import_faq.rst:240 msgid "It will produce the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:199 +#: ../../general/base_import/import_faq.rst:248 msgid "" "As you can see in this file, Fabien and Laurence are working for the Bigees " "company (company_1) and Eric is working for the Organi company. The relation" @@ -549,7 +681,7 @@ msgid "" " who shared the same ID 1 in the orignial database)." msgstr "" -#: ../../general/base_import/import_faq.rst:201 +#: ../../general/base_import/import_faq.rst:250 msgid "" "The two files produced are ready to be imported in Odoo without any " "modifications. After having imported these two CSV files, you will have 4 " diff --git a/locale/fr/LC_MESSAGES/inventory.po b/locale/fr/LC_MESSAGES/inventory.po index 568fdeccb..f5f47b3ee 100644 --- a/locale/fr/LC_MESSAGES/inventory.po +++ b/locale/fr/LC_MESSAGES/inventory.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Xavier Belmere , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" @@ -789,6 +789,10 @@ msgstr "" "réapprovisionnement`. Là, cliquez sur **Créer** pour définir les valeurs de " "stock minimum et maximum pour un article donné." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "Actif" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "If the active field is set to False, it will allow you to hide the " @@ -797,11 +801,19 @@ msgstr "" "Si le champ \"Actif\" n'est pas coché, cela vous permettra de cacher les " "points de commande sans les supprimer." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "Unité de mesure d'article" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Default Unit of Measure used for all stock operation." msgstr "" "Unité de mesure par défaut utilisée pour toutes les opérations de stock" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "Groupe d'approvisionnement" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Moves created through this orderpoint will be put in this procurement group." @@ -813,6 +825,10 @@ msgstr "" " les règles d'approvisionnement seront regroupés en une seule grande " "préparation." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "Quantité minimum" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity specified for this field," @@ -823,6 +839,10 @@ msgstr "" " champ, Odoo génère un approvisionnement pour ramener la quantité prévue à " "la quantité maxi." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "Quantité maximale" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity, Odoo generates a " @@ -833,6 +853,10 @@ msgstr "" "approvisionnement pour ramener la quantité prévue à la quantité indiquée " "ici." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "Quantité multiple de" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "The procurement quantity will be rounded up to this multiple. If it is 0, " @@ -841,6 +865,10 @@ msgstr "" "La quantité à approvisionner sera arrondie à ce multiple. S'il est à 0, la " "quantité exacte sera utilisée." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "Délai" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Number of days after the orderpoint is triggered to receive the products or " diff --git a/locale/fr/LC_MESSAGES/legal.po b/locale/fr/LC_MESSAGES/legal.po deleted file mode 100644 index dd926dcda..000000000 --- a/locale/fr/LC_MESSAGES/legal.po +++ /dev/null @@ -1,2021 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Olivier Lenoir , 2017\n" -"Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: fr\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" - -#: ../../legal.rst:5 -msgid "Legal" -msgstr "" - -#: ../../legal.rst:15 ../../legal/licenses.rst:5 -#: ../../legal/licenses/licenses.rst:6 -msgid "Licenses" -msgstr "" - -#: ../../legal.rst:17 -msgid ":ref:`licenses`" -msgstr "" - -#: ../../legal.rst:20 ../../legal/terms.rst:5 -msgid "Terms and Conditions" -msgstr "Conditions générales" - -#: ../../legal.rst:38 -msgid ":ref:`enterprise_agreement` |nbsp| |nbsp| |download_enterprise|" -msgstr "" - -#: ../../legal.rst:40 -msgid ":ref:`enterprise_agreement_fr` |nbsp| |nbsp| |download_enterprise_fr|" -msgstr "" - -#: ../../legal.rst:47 ../../legal/others.rst:5 -msgid "Other legal references" -msgstr "" - -#: ../../legal.rst:49 -msgid "" -"`Odoo Online Service Level Agreement `_" -msgstr "" - -#: ../../legal.rst:50 -msgid "" -"`Odoo Online Acceptable Use Policy `_" -msgstr "" - -#: ../../legal.rst:51 -msgid ":ref:`cla`" -msgstr "" - -#: ../../legal/licenses/licenses.rst:11 -msgid "Odoo 10 Community Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:13 -msgid "" -"Odoo 10 Community Edition is licensed under `LGPL version 3 " -"`_ (also known as LGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/licenses/licenses.rst:22 -msgid "Odoo 10 Enterprise Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:24 -msgid "" -"Odoo 10 Enterprise Edition is licensed under the Odoo Enterprise Edition " -"License v1.0, defined as follows:" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:1 -#: ../../legal/terms/i18n/enterprise_fr.rst:487 -msgid "Odoo Enterprise Edition License v1.0" -msgstr "Odoo Enterprise Edition License v1.0" - -#: ../../legal/licenses/enterprise_license.txt:3 -msgid "" -"This software and associated files (the \"Software\") can only be used " -"(executed, modified, executed after modifications) with a valid Odoo " -"Enterprise Subscription for the correct number of users." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:7 -msgid "" -"With a valid Partnership Agreement with Odoo S.A., the above permissions are" -" also granted, as long as the usage is limited to a testing or development " -"environment." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:11 -msgid "" -"You may develop Odoo modules based on the Software and distribute them under" -" the license of your choice, provided that it is compatible with the terms " -"of the Odoo Enterprise Edition License (For example: LGPL, MIT, or " -"proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:16 -msgid "" -"You may use Odoo modules published under any license along with the " -"Software, provided that their license is compatible with the terms of the " -"Odoo Enterprise License (Including, but not limited to, any module published" -" on the Odoo Apps Store on odoo.com/apps)" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:21 -#: ../../legal/licenses/licenses.rst:69 -msgid "" -"It is forbidden to publish, distribute, sublicense, or sell copies of the " -"Software or modified copies of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:24 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:27 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE" -" AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM," -" OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN " -"THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:43 -msgid "Odoo Apps" -msgstr "" - -#: ../../legal/licenses/licenses.rst:45 -msgid "" -"Unless otherwise stated, Odoo Apps by Odoo SA (including the website themes)" -" are published under the Odoo Proprietary License v1.0, defined as follows" -msgstr "" - -#: ../../legal/licenses/licenses.rst:54 -msgid "Odoo Proprietary License v1.0" -msgstr "License propriétaire Odoo v1.0" - -#: ../../legal/licenses/licenses.rst:56 -msgid "" -"This software and associated files (the \"Software\") may only be used " -"(executed, modified, executed after modifications) if you have purchased a " -"valid license from the authors, typically via Odoo Apps, or if you have " -"received a written agreement from the authors of the Software (see the " -"COPYRIGHT file)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:62 -msgid "" -"You may develop Odoo modules that use the Software as a library (typically " -"by depending on it, importing it and using its resources), but without " -"copying any source code or material from the Software. You may distribute " -"those modules under the license of your choice, provided that this license " -"is compatible with the terms of the Odoo Proprietary License (For example: " -"LGPL, MIT, or proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:72 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/licenses.rst:75 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " -"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " -"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS" -" IN THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:91 -msgid "Odoo 9" -msgstr "" - -#: ../../legal/licenses/licenses.rst:93 -msgid "" -"The licenses for both editions of Odoo 9 were respectively the same as for " -":ref:`odoo_community_license` and :ref:`odoo_enterprise_license`." -msgstr "" - -#: ../../legal/licenses/licenses.rst:100 -msgid "Odoo 8" -msgstr "" - -#: ../../legal/licenses/licenses.rst:102 -msgid "" -"Odoo 8 is licensed under `AGPL version 3 " -"`_ (also known as AGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/others/cla.rst:5 -msgid "Contributor License Agreement" -msgstr "" - -#: ../../legal/others/cla.rst:7 -msgid "" -"In order to contribute to any of the Odoo projects, companies and " -"individuals have to sign the Odoo Contributor License Agreement (CLA)." -msgstr "" - -#: ../../legal/others/cla.rst:10 -msgid "" -"More information about this requirement, the procedure to sign the " -"agreement, and a FAQ can be found on our `GitHub project page " -"`_." -msgstr "" - -#: ../../legal/others/privacy.rst:5 -msgid "Privacy Policy" -msgstr "" - -#: ../../legal/others/privacy.rst:7 -msgid "" -"Temporary version at ``__ " -"(needs cleanup)" -msgstr "" - -#: ../../legal/terms/enterprise.rst:6 -msgid "Odoo Enterprise Subscription Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:8 -msgid "Version 5b - Last revision: June 30, 2016." -msgstr "" - -#: ../../legal/terms/enterprise.rst:10 -msgid "" -"By subscribing to the Odoo Enterprise services (the \"Services\") provided " -"by Odoo SA and its affiliates (collectively, \"Odoo SA\") in relation with " -"Odoo Enterprise Edition or Odoo Community Edition (the \"Software\"), you " -"(the \"Customer\") are agreeing to be bound by the following terms and " -"conditions (the \"Agreement\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:18 -msgid "1 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:20 -msgid "" -"The duration of this Agreement (the “Term”) shall be minimally one year and " -"as specified in writing at the signature of this Agreement, beginning on the" -" date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term by registered mail to the other party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:28 -msgid "2 Definitions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:34 -msgid "User" -msgstr "Utilisateur" - -#: ../../legal/terms/enterprise.rst:31 -msgid "" -"Any active user account with access to the Software in creation and/or " -"edition mode. Deactivated user accounts and accounts used by external people" -" (or systems) who only have limited access to the Software through the " -"portal facilities (known as \"portal Users\") are not counted as Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:42 -#: ../../legal/terms/i18n/enterprise_fr.rst:55 -msgid "Bug" -msgstr "" - -#: ../../legal/terms/enterprise.rst:37 -msgid "" -"Is considered a Bug any failure of the Software that results in a complete " -"stop, error traceback or security breach, and is not directly caused by a " -"defective installation or configuration. Non-compliance with specifications " -"or requirements will be considered as Bugs at the discretion of Odoo SA " -"(typically, when the Software does not produce the results or performance it" -" was designed to produce, or when a country-specific feature does not meet " -"legal accounting requirements anymore)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:51 -msgid "Covered Versions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:45 -msgid "" -"All Services provided under this Agreement are applicable only to the " -"Covered Versions of the Software, which include the 3 (three) most recently " -"released major versions." -msgstr "" - -#: ../../legal/terms/enterprise.rst:48 -msgid "" -"To be covered by the current Agreement, Customer’s installations have to run" -" the most recent Covered Version at the time of this Agreement’s signature. " -"When this is not the case, additional costs are applicable, as described in " -":ref:`charges`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:56 ../../legal/terms/partnership.rst:42 -msgid "3 Access to Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/enterprise.rst:58 -msgid "" -"For the duration of this Agreement, Odoo SA gives the Customer a non-" -"exclusive, non-transferable license to use (execute, modify, execute after " -"modification) the Odoo Enterprise Edition software, under the terms set " -"forth in :ref:`appendix_a`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:62 -msgid "" -"The Customer agrees to take all necessary measures to guarantee the " -"unmodified execution of the part of the Software that verifies the validity " -"of the Odoo Enterprise Edition usage and collects statistics for that " -"purpose, including but not limited to the running of an instance and the " -"number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:67 -msgid "" -"Odoo SA commits not to disclose individual or named figures to third parties" -" without the consent of the Customer, and to deal with all collected data in" -" compliance with its official Privacy Policy, as published on `Odoo SA's " -"website `_." -msgstr "" - -#: ../../legal/terms/enterprise.rst:71 -msgid "" -"Upon expiration or termination of this Agreement, this license is revoked " -"immediately and the Customer agrees to stop using the Odoo Enterprise " -"Edition software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:74 -msgid "" -"Should the Customer breach the terms of this section, the Customer agrees to" -" pay Odoo SA an extra fee equal to 300% of the applicable list price for the" -" actual number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:81 -msgid "4 Included Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:84 -msgid "4.1 Bug Fixing Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:86 -msgid "" -"For the duration of this Agreement, Odoo SA commits to making all reasonable" -" efforts to remedy any Bug of the Software submitted by the Customer through" -" the appropriate channel (typically, Odoo SA's service desk email address or" -" website form), and to start handling such Customer submissions within 2 " -"business days." -msgstr "" - -#: ../../legal/terms/enterprise.rst:91 -msgid "" -"The Customer understands that Bugs caused by a modification or extension " -"that is not part of the official Software will not be covered by this " -"service." -msgstr "" - -#: ../../legal/terms/enterprise.rst:94 -msgid "" -"As soon as the Bug is fixed an appropriate remedy will be communicated to " -"the Customer. If the bug has been addressed in a more recent revision of the" -" Covered Version of the Software used by the Customer, the Customer agrees " -"to update its systems to that revision in order to obtain the correction. " -"The Customer will not be asked to upgrade to a more recent Covered Version " -"of the Software as a remedy to a Bug." -msgstr "" - -#: ../../legal/terms/enterprise.rst:100 -msgid "" -"When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the " -"Bug in all more recent Covered Versions of the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:103 -msgid "" -"Both parties acknowledge that as specified in the license of the Software " -"and in the :ref:`liability` section of this Agreement, Odoo SA cannot be " -"held liable for Bugs in the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:108 -msgid "4.2 Security Advisories Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:110 -msgid "" -"For the duration of this Agreement, Odoo SA commits to sending a \"Security " -"Advisory\" to the Customer for any security Bug that are discovered in the " -"Covered Versions of the Software, at least 2 weeks before making the " -"Security Advisory public, unless the Bug has already been disclosed publicly" -" by a third party. Security Advisories include a complete description of the" -" Bug, its cause, its possible impacts on the Customer's systems, and the " -"corresponding remedy for each Covered Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:117 -msgid "" -"The Customer understands that the Bug and the information in the Security " -"Advisory must be treated are Confidential Information as described in " -":ref:`confidentiality` during the embargo period prior to the public " -"disclosure." -msgstr "" - -#: ../../legal/terms/enterprise.rst:124 -msgid "4.3 Upgrade Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:129 -msgid "Upgrade Service for the Software" -msgstr "" - -#: ../../legal/terms/enterprise.rst:131 -msgid "" -"For the duration of this Agreement, the Customer can submit upgrade requests" -" through the appropriate channel (typically Odoo SA's upgrade service " -"website), in order to convert a database of the Software from one Covered " -"Version of the Software to a more recent Covered Version (the \"Target " -"Version\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:135 -msgid "" -"Upgrade requests must include a complete backup copy of the Customer's " -"database and the associated data (typically obtained from the Backup menu of" -" the Software). Where necessary for data security or regulation reasons, the" -" Upgrade Service includes an optional tool to anonymize identifiable data " -"inside a database before submitting the upgrade request, and a tool to " -"restore the anonymized data after the upgrade." -msgstr "" - -#: ../../legal/terms/enterprise.rst:141 -msgid "" -"This service provided through an automated platform in order to allow the " -"Customer to perform unattended upgrades once a previous version of the " -"Customer's database has been successfully upgraded for a Covered Version. " -"The Customer may submit successive upgrade requests for a database, and " -"agrees to submit at least 1 upgrade request for testing purposes before " -"submitting the final upgrade request." -msgstr "" - -#: ../../legal/terms/enterprise.rst:147 -msgid "" -"The Upgrade Service is limited to the technical conversion and adaptation of" -" the Customer's database to make it compatible with the Target Version, and " -"the correction of any Bug directly caused by the upgrade operation and not " -"normally occurring in the Target Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:151 -msgid "" -"It is the sole responsibility of the Customer to verify and validate the " -"upgraded database in order to detect Bugs, to analyze the impact of changes " -"and new features implemented in the Target Version, and to convert and adapt" -" for the Target Version any third-party extensions of the Software that were" -" installed in the database before the upgrade (except where applicable as " -"foreseen in section :ref:`upgrade_extra`). The Customer may submit multiple " -"upgrade requests for a database, until an acceptable result is achieved." -msgstr "" - -#: ../../legal/terms/enterprise.rst:162 -msgid "Upgrade Service for third-party extensions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:164 -msgid "" -"For the duration of this Agreement, the Customer may request optional " -"upgrade services for third-party extension modules of the Software, in " -"addition to the regular Upgrade Services. This optional service is subject " -"to additional fees (as described in charges_) and includes the technical " -"adaptation of third-party modules installed in the Customer's database and " -"their corresponding data in order to be compatible with the Target Version. " -"The Customer will receive an upgraded version of all installed third-party " -"modules along with the upgraded database." -msgstr "" - -#: ../../legal/terms/enterprise.rst:174 -msgid "5 Charges and Fees" -msgstr "" - -#: ../../legal/terms/enterprise.rst:179 -msgid "5.1 Standard charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:181 -msgid "" -"The standard charges for the Odoo Enterprise subscription, the Bug Fixing " -"Service, Security Advisories Service and the Upgrade Service are based on " -"the number of Users and the Software version used by the Customer, and " -"specified in writing at the signature of the Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:185 -msgid "" -"When during the Term, the Customer has more Users than specified at the time" -" of signature of this Agreement, the Customer agrees to pay an extra fee " -"equivalent to the applicable list price (at the beginning of the Term) for " -"the additional Users, for the remainder of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:189 -msgid "" -"If at the time of the signature of this Agreement, the Customer uses a " -"Covered Version that is not the most recent one, the standard charges will " -"be increased by 50% for the duration of the first Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:196 -msgid "5.2 Renewal charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:198 -msgid "" -"Upon renewal as covered in section :ref:`term`, if the per-User charges " -"applied during the previous Term are lower than the most current applicable " -"per-User list price, the per-User charges will increase by up to 7%, unless " -"Odoo SA provides written notice of a new price to the Customer at least 60 " -"days prior to the end of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:207 -msgid "5.3 Charges for Upgrade Services of third-party modules" -msgstr "" - -#: ../../legal/terms/enterprise.rst:211 -msgid "" -"The additional charge for the Upgrade Service for third-party modules is EUR" -" (€) 1000.00 (one thousand euros) per 1000 Lines of Code in the third-party " -"modules, rounded up to the next thousand lines. Lines of Code include all " -"text lines in the source code of those modules, regardless of the " -"programming language (Python, Javascript, etc.) or data format (XML, CSV, " -"etc.), excluding blank lines and comment lines." -msgstr "" - -#: ../../legal/terms/enterprise.rst:217 -msgid "" -"Odoo SA reserves the right to reject an upgrade request for third-party " -"modules under the above conditions if the quality of the source code of " -"those modules is too low, or if these modules constitute an interface with " -"third-party software or systems. The upgrade of such modules will subject to" -" a separate offer, outside of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:225 -msgid "5.4 Taxes" -msgstr "" - -#: ../../legal/terms/enterprise.rst:229 -msgid "" -"All fees and charges are exclusive of all applicable federal, provincial, " -"state, local or other governmental taxes, fees or charges (collectively, " -"\"Taxes\"). The Customer is responsible for paying all Taxes associated with" -" purchases made by the Customer under this Agreement, except when Odoo SA is" -" legally obliged to pay or collect Taxes for which the Customer is " -"responsible." -msgstr "" - -#: ../../legal/terms/enterprise.rst:238 -msgid "6 Conditions of Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:241 -msgid "6.1 Customer Obligations" -msgstr "" - -#: ../../legal/terms/enterprise.rst:245 -msgid "The Customer agrees to:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:247 -msgid "" -"pay Odoo SA any applicable charges for the Services of the present " -"Agreement, in accordance with the payment conditions specified in the " -"corresponding invoice ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:249 -msgid "" -"immediately notify Odoo SA when the actual number of Users exceeds the " -"number of Users specified at the signature of the Agreement, and in this " -"event, pay the applicable additional fee as described in section " -":ref:`charges_standard`;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:252 -msgid "" -"take all measures necessary to guarantee the unmodified execution of the " -"part of the Software that verifies the validity of the Odoo Enterprise " -"Edition usage, as described in :ref:`enterprise_access` ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:255 -msgid "" -"grant Odoo SA the necessary access to verify the validity of the Odoo " -"Enterprise Edition usage upon request (e.g. if the automatic validation is " -"found to be inoperant for the Customer);" -msgstr "" - -#: ../../legal/terms/enterprise.rst:257 -msgid "" -"appoint 1 dedicated Customer contact person for the entire duration of the " -"Agreement;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:258 -msgid "" -"take all reasonable measures to protect Customer’s files and databases and " -"to ensure Customer’s data is safe and secure, acknowledging that Odoo SA " -"cannot be held liable for any data loss;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:265 -msgid "6.2 No Soliciting or Hiring" -msgstr "" - -#: ../../legal/terms/enterprise.rst:267 -msgid "" -"Except where the other party gives its consent in writing, each party, its " -"affiliates and representatives agree not to solicit or offer employment to " -"any employee of the other party who is involved in performing or using the " -"Services under this Agreement, for the duration of the Agreement and for a " -"period of 12 months from the date of termination or expiration of this " -"Agreement. In case of any breach of the conditions of this section that " -"leads to the termination of said employee toward that end, the breaching " -"party agrees to pay to the other party an amount of EUR (€) 30 000.00 " -"(thirty thousand euros)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:279 -msgid "6.3 Publicity" -msgstr "" - -#: ../../legal/terms/enterprise.rst:281 -msgid "" -"Except where notified otherwise in writing, each party grants the other a " -"non-transferable, non-exclusive, royalty free, worldwide license to " -"reproduce and display the other party’s name, logos and trademarks, solely " -"for the purpose of referring to the other party as a customer or supplier, " -"on websites, press releases and other marketing materials." -msgstr "" - -#: ../../legal/terms/enterprise.rst:290 -msgid "6.4 Confidentiality" -msgstr "" - -#: ../../legal/terms/enterprise.rst:298 -msgid "Definition of \"Confidential Information\":" -msgstr "" - -#: ../../legal/terms/enterprise.rst:293 -msgid "" -"All information disclosed by a party (the \"Disclosing Party\") to the other" -" party (the \"Receiving Party\"), whether orally or in writing, that is " -"designated as confidential or that reasonably should be understood to be " -"confidential given the nature of the information and the circumstances of " -"disclosure. In particular any information related to the business, affairs, " -"products, developments, trade secrets, know-how, personnel, customers and " -"suppliers of either party should be regarded as confidential." -msgstr "" - -#: ../../legal/terms/enterprise.rst:300 -msgid "" -"For all Confidential Information received during the Term of this Agreement," -" the Receiving Party will use the same degree of care that it uses to " -"protect the confidentiality of its own similar Confidential Information, but" -" not less than reasonable care." -msgstr "" - -#: ../../legal/terms/enterprise.rst:304 -msgid "" -"The Receiving Party may disclose Confidential Information of the Disclosing " -"Party to the extent compelled by law to do so, provided the Receiving Party " -"gives the Disclosing Party prior notice of the compelled disclosure, to the " -"extent permitted by law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:311 -msgid "6.5 Termination" -msgstr "" - -#: ../../legal/terms/enterprise.rst:313 -msgid "" -"In the event that either Party fails to fulfill any of its obligations " -"arising herein, and if such breach has not been remedied within 30 calendar " -"days from the written notice of such breach, this Agreement may be " -"terminated immediately by the non-breaching Party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:317 -msgid "" -"Further, Odoo SA may terminate the Agreement immediately in the event the " -"Customer fails to pay the applicable fees for the Services within the due " -"date specified on the corresponding invoice." -msgstr "" - -#: ../../legal/terms/enterprise.rst:324 -msgid "Surviving Provisions:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:321 -msgid "" -"The sections \":ref:`confidentiality`”, “:ref:`disclaimers`”, " -"“:ref:`liability`”, and “:ref:`general_provisions`” will survive any " -"termination or expiration of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:329 -msgid "7 Warranties, Disclaimers, Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:334 -msgid "7.1 Warranties" -msgstr "" - -#: ../../legal/terms/enterprise.rst:338 -msgid "" -"For the duration of this Agreement, Odoo SA commits to using commercially " -"reasonable efforts to execute the Services in accordance with the generally " -"accepted industry standards provided that:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:341 -msgid "" -"the Customer’s computing systems are in good operational order and the " -"Software is installed in a suitable operating environment;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:343 -msgid "" -"the Customer provides adequate troubleshooting information and access so " -"that Odoo SA can identify, reproduce and address problems;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:345 -msgid "all amounts due to Odoo SA have been paid." -msgstr "" - -#: ../../legal/terms/enterprise.rst:347 -msgid "" -"The Customer's sole and exclusive remedy and Odoo SA's only obligation for " -"any breach of this warranty is for Odoo SA to resume the execution of the " -"Services at no additional charge." -msgstr "" - -#: ../../legal/terms/enterprise.rst:353 -msgid "7.2 Disclaimers" -msgstr "" - -#: ../../legal/terms/enterprise.rst:357 -msgid "" -"Except as expressly provided herein, neither party makes any warranty of any" -" kind, whether express, implied, statutory or otherwise, and each party " -"specifically disclaims all implied warranties, including any implied " -"warranty of merchantability, fitness for a particular purpose or non-" -"infringement, to the maximum extent permitted by applicable law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:362 -msgid "" -"Odoo SA does not warrant that the Software complies with any local or " -"international law or regulations." -msgstr "" - -#: ../../legal/terms/enterprise.rst:367 -msgid "7.3 Limitation of Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:369 -msgid "" -"To the maximum extent permitted by law, the aggregate liability of each " -"party together with its affiliates arising out of or related to this " -"Agreement will not exceed 50% of the total amount paid by the Customer under" -" this Agreement during the 12 months immediately preceding the date of the " -"event giving rise to such claim. Multiple claims shall not enlarge this " -"limitation." -msgstr "" - -#: ../../legal/terms/enterprise.rst:374 -msgid "" -"In no event will either party or its affiliates be liable for any indirect, " -"special, exemplary, incidental or consequential damages of any kind, " -"including but not limited to loss of revenue, profits, savings, loss of " -"business or other financial loss, costs of standstill or delay, lost or " -"corrupted data, arising out of or in connection with this Agreement " -"regardless of the form of action, whether in contract, tort (including " -"strict negligence) or any other legal or equitable theory, even if a party " -"or its affiliates have been advised of the possibility of such damages, or " -"if a party or its affiliates' remedy otherwise fails of its essential " -"purpose." -msgstr "" - -#: ../../legal/terms/enterprise.rst:385 -#: ../../legal/terms/i18n/enterprise_fr.rst:418 -msgid "7.4 Force Majeure" -msgstr "" - -#: ../../legal/terms/enterprise.rst:387 -msgid "" -"Neither party shall be liable to the other party for the delay in any " -"performance or failure to render any performance under this Agreement when " -"such failure or delay is caused by governmental regulations, fire, strike, " -"war, flood, accident, epidemic, embargo, appropriation of plant or product " -"in whole or in part by any government or public authority, or any other " -"cause or causes, whether of like or different nature, beyond the reasonable " -"control of such party as long as such cause or causes exist." -msgstr "" - -#: ../../legal/terms/enterprise.rst:398 -msgid "8 General Provisions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:403 -msgid "8.1 Governing Law" -msgstr "" - -#: ../../legal/terms/enterprise.rst:405 -msgid "" -"Both parties agree that the laws of Belgium will apply, should any dispute " -"arise out of or in connection with this Agreement, without regard to choice " -"or conflict of law principles. To the extent that any lawsuit or court " -"proceeding is permitted hereinabove, both parties agree to submit to the " -"sole jurisdiction of the Nivelles (Belgium) court for the purpose of " -"litigating all disputes." -msgstr "" - -#: ../../legal/terms/enterprise.rst:414 -msgid "8.2 Severability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:416 -msgid "" -"In case any one or more of the provisions of this Agreement or any " -"application thereof shall be invalid, illegal or unenforceable in any " -"respect, the validity, legality and enforceability of the remaining " -"provisions of this Agreement and any application thereof shall be in no way " -"thereby affected or impaired. Both parties undertake to replace any invalid," -" illegal or unenforceable provision of this Agreement by a valid provision " -"having the same effects and objectives." -msgstr "" - -#: ../../legal/terms/enterprise.rst:427 -msgid "9 Appendix A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:6 -msgid "Odoo Enterprise Subscription Agreement (FR)" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:9 -msgid "" -"Ceci est une traduction en français du contrat “Odoo Enterprise Subscription" -" Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera " -"sa compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes du contrat “Odoo Enterprise Subscription Agreement” " -"est la :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:15 -msgid "" -"This is a french translation of the \"Odoo Enterprise Subscription " -"Agreement”. This translation is provided in the hope that it will facilitate" -" understanding, but it has no legal value. The only official reference of " -"the terms and conditions of the “Odoo Enterprise Subscription Agreement” is " -"the :ref:`original english version `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:21 -msgid "Version 5b - Dernière modification: 30 juin 2016." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:23 -msgid "" -"En vous abonnant aux services de Odoo Enterprise (les \"Services\") fournis " -"par Odoo SA et ses filiales (collectivement, \"Odoo SA\") en relation avec " -"Odoo Enterprise Edition ou Odoo Community Edition (le \"Logiciel\"), vous " -"(le \"Client\") acceptez d'être lié par les conditions générales suivantes " -"(le \"Contrat\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:31 -msgid "1 Durée du Contrat" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:33 -msgid "" -"La durée du présent contrat (la \"Durée\") doit être au minimum d'un an et " -"telle que spécifiée par écrit à la signature du Contrat, à compter de la " -"date de la signature. Celui-ci est automatiquement reconduit pour une même " -"durée, à moins que l'une des parties n’envoie à l'autre partie un préavis " -"écrit de résiliation, par lettre recommandée, et au moins 30 jours avant la " -"date d'échéance du contrat ." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:41 -msgid "2 Définitions" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:47 -msgid "Utilisateur" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:44 -msgid "" -"Tout compte utilisateur actif donnant accès au Logiciel en mode création " -"et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des " -"personnes ou systèmes extérieur(e)s n'ayant qu'un accès limité au Logiciel " -"via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme " -"Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:50 -msgid "" -"Désigne toute défaillance du Logiciel qui se traduit par un arrêt complet, " -"un message d'erreur avec trace d'exécution, ou une brèche de sécurité, et " -"n'est pas directement causé par un problème d'installation ou une " -"configuration défectueuse. Un non-respect des spécifications ou des besoins " -"sera considéré comme un Bug à la discrétion d'Odoo SA (en général, lorsque " -"le Logiciel ne produit pas les résultats ou la performance pour lesquels il " -"a été conçu, ou lorsqu'une fonctionnalité spécifique à un pays ne répond " -"plus aux exigences comptables légales de ce pays)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:65 -msgid "Versions Couvertes" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:58 -msgid "" -"Tous les Services dans le cadre du présent contrat s'appliquent uniquement " -"aux Versions Couvertes du Logiciel, qui comprennent les trois (3) plus " -"récentes versions majeures." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:61 -msgid "" -"Afin d'être considérées comme couvertes par le Contrat, les installations du" -" client doivent utiliser la Version couverte la plus récente au moment de " -"la signature du Contrat. Dans le cas contraire, des frais supplémentaires " -"sont d'application, tels que décrit dans la section :ref:`charges_fr`" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:70 -msgid "3 Accès à Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:72 -msgid "" -"Pour toute la durée du présent Contrat, Odoo SA octroie au Client une " -"licence non exclusive, non transférable d'utilisation (exécution, " -"modification, exécution après modification) du logiciel Odoo Enterprise " -"Edition, conformément aux conditions énoncées à la section " -":ref:`appendix_a_fr`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:76 -msgid "" -"Le Client accepte de prendre toutes les mesures nécessaires pour garantir " -"l'exécution sans aucune modification de la partie du Logiciel qui vérifie la" -" validité de l'utilisation d'Odoo Enterprise Edition et recueille des " -"statistiques à cet effet, y compris mais sans s'y limiter, l'exécution du " -"Logiciel et le nombre d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:81 -msgid "" -"Odoo SA s'engage à ne pas divulguer à une tierce partie d'informations " -"chiffrées personnelles ou spécifiques sans le consentement du Client, et à " -"traiter toutes les données recueillies en respectant sa politique officielle" -" de confidentialité, telle que publiée sur `le site web d'Odoo SA " -"`_." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:86 -msgid "" -"À l'expiration ou la résiliation de ce Contrat, cette licence est " -"immédiatement révoquée et le Client accepte de cesser toute utilisation du " -"logiciel Odoo Enterprise Edition." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:89 -msgid "" -"Si le Client devait enfreindre les dispositions de la présente section, il " -"accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du " -"tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:97 -msgid "4 Services inclus" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:100 -msgid "4.1 Service de correction de Bugs" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:102 -msgid "" -"Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts " -"raisonnables pour corriger tout Bug du Logiciel qui pourrait être signalé " -"par le Client en suivant la procédure appropriée (généralement par le biais " -"d'un e-mail adressé au service d'assistance d'Odoo SA ou via le formulaire " -"correspondant sur le site web), et de commencer à traiter ces signalements " -"du Client dans un délai de 2 jours ouvrables." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:108 -msgid "" -"Le Client accepte que les Bugs causés par toute modification ou extension " -"qui ne fait pas partie de la version officielle du Logiciel ne seront pas " -"couverts par ce service." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:111 -msgid "" -"Dès que le Bug est remédié, un correctif approprié sera communiqué au " -"Client. Si le Bug a été résolu dans une nouvelle mise à jour de la Version " -"Couverte du Logiciel utilisée par le Client, ce dernier s'engage à " -"actualiser ses systèmes vers la nouvelle mise à jour, afin d'obtenir le " -"correctif. Il ne sera jamais demandé au Client de passer à une Version " -"Couverte plus récente pour obtenir un correctif." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:117 -msgid "" -"Lorsqu'un Bug est corrigé dans une Version Couverte, Odoo SA s'engage à le " -"corriger dans toutes les Versions Couvertes plus récentes du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:120 -msgid "" -"Les deux parties reconnaissent que comme spécifié dans la licence du " -"Logiciel et à la section :ref:`liability_fr` de ce Contrat, Odoo SA ne peut " -"être tenue responsable des Bugs du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:125 -msgid "4.2 Service d'alertes de sécurité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:127 -msgid "" -"Pour la durée du Contrat, Odoo SA s'engage à envoyer une \"alerte de " -"sécurité\"\" au Client pour tout Bug présentant un risque de sécurité qui " -"serait découvert dans les Versions Couvertes du Logiciel, au moins 2 " -"semaines avant de rendre ladite alerte de sécurité publique, et ce à moins " -"que le Bug ait déjà été rendu public par un tiers. Les alertes de sécurité " -"comprennent une description complète du Bug, de sa cause, ses conséquences " -"possibles sur les systèmes du Client, et le correctif correspondant pour " -"chaque Version Couverte." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:134 -msgid "" -"Le Client s'engage à traiter le Bug de sécurité et les informations figurant" -" dans l'alerte de sécurité comme des Informations Confidentielles telles que" -" décrites à la section :ref:`confidentiality_fr` pendant toute la période " -"d'embargo avant la divulgation publique." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:141 -msgid "4.3 Service de migration" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:146 -msgid "Service de migration du Logiciel" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:148 -msgid "" -"Pour la durée du présent Contrat, le Client peut soumettre des demandes de " -"migration en suivant les procédures appropriées (généralement, via le site " -"du service de migration d'Odoo SA), afin de convertir une base de données du" -" Logiciel d'une Version Couverte du Logiciel à une Version Couverte plus " -"récente (la \"Version Cible\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:153 -msgid "" -"Les demandes de migration doivent inclure une copie de sauvegarde complète " -"de la base de données du Client et les données associées (généralement " -"obtenues à partir du menu Backup du Logiciel). Lorsque cela est nécessaire " -"pour des raisons de sécurité des données ou de réglementation, le Service de" -" migration inclut un outil facultatif pour rendre anonymes les données " -"identifiables figurant dans la base de données, avant de soumettre la " -"demande de migration, et un outil pour restaurer les données rendues " -"anonymes après la migration." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:160 -msgid "" -"Ce service est fourni par le biais d'une plateforme automatisée, afin de " -"permettre au Client d'effectuer des migration sans intervention humain, dès " -"lors qu’une version précédente de la base de données du Client a été migrée " -"avec succès pour une Version Couverte donnée. Le client peut soumettre des " -"demandes de migration successives pour une base de données, et accepte de " -"soumettre au moins 1 demande de mifration de test avant de soumettre la " -"demande de migration finale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:167 -msgid "" -"Le service de migration est limité à la conversion et à l'adaptation " -"techniques de la base de données du Client pour la rendre compatible avec la" -" Version Cible, et à la correction de tout Bug directement causé par " -"l'opération de migration, et ne se produisant normalement pas dans la " -"Version Cible." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:172 -msgid "" -"Il incombe au Client de vérifier et valider la base de données migrée afin " -"de détecter tout Bug, d'analyser l'impact des changements et des nouvelles " -"fonctionnalités ajoutées dans la Version Cible, de convertir et d'adapter " -"pour la Version Cible les modules tiers du Logiciel qui auraient été " -"installées dans la base de données avant la migration (sauf le cas échéant, " -"comme prévu à la section :ref:`upgrade_extra_fr`). Le client peut soumettre " -"plusieurs demandes de migration pour une base de données, jusqu'à ce qu'un " -"résultat satisfaisant soit obtenu." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:183 -msgid "Service de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:185 -msgid "" -"Pour la durée du Contrat, le Client a la possibilité de faire une demande de" -" migration pour des modules d'extension tiers, en plus de la migration " -"normale du Logiciel. Ce service en option implique des frais supplémentaires" -" (décrits dans la section charges_fr_) et comprend l'adaptation technique " -"des modules tiers installés dans la base de données du Client et de leurs " -"données correspondantes afin qu'elles soient compatibles avec la Version " -"Cible. Le Client recevra une version migrée de tous les modules tiers " -"installés accompagnée de la base de données migrée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:196 -msgid "5 Tarifs et Frais" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:201 -msgid "5.1 Tarifs standards" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:203 -msgid "" -"Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise, le " -"service de correction de Bugs, le service d'alertes de sécurité et le " -"service de migration sont basés sur le nombre d'Utilisateurs et la version " -"du Logiciel utilisée par le Client, et précisés par écrit à la signature du " -"contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:208 -msgid "" -"Pendant la durée du contrat, si le Client a plus d'Utilisateurs que spécifié" -" au moment de la signature du présent Contrat, le Client accepte de payer un" -" supplément équivalent au tarif en vigueur applicable (au début du Contrat) " -"pour les utilisateurs supplémentaires, pour le reste de la durée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:213 -msgid "" -"Si, au moment de la signature du présent Contrat, le Client utilise une " -"Version Couverte qui n'est pas l'une des plus récentes, les tarifs standards" -" seront augmentés de 50% pour la première Durée du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:221 -msgid "5.2 Tarifs de reconduction" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:223 -msgid "" -"Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si " -"les tarifs par Utilisateur qui ont été appliqués pendant la Durée précédente" -" sont inférieurs aux tarifs par Utilisateur en vigueur les plus récents, les" -" tarifs par Utilisateur augmenteront automatiquement de maximum 7%, à moins " -"qu'Odoo SA ne notifie par écrit un nouveau tarif au client, au moins 60 " -"jours avant l’échéance du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:232 -msgid "5.3 Tarifs de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:234 -msgid "" -"Les frais supplémentaires pour le service de migration des modules tiers " -"sont de 1000,00- euros (€) (mille euros) pour 1000 lignes de code de modules" -" tiers, le nombre de lignes étant arrondi au millier de lignes supérieur. " -"Les lignes de code comprennent toutes les lignes de texte dans le code " -"source de ces modules, quel que soit le langage de programmation (Python, " -"Javascript, etc.) ou format de données (XML, CSV, etc.), à l'exclusion des " -"lignes vides et des lignes de commentaires." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:240 -msgid "" -"Odoo SA se réserve le droit de refuser une demande de migration pour des " -"modules tiers conformément aux conditions décrites ci-dessus, si la qualité " -"du code source de ces modules est trop faible, ou si ces modules font partie" -" d'une interface d'intégration avec des logiciels ou systèmes tiers. La " -"migration de ces modules sera soumise à une proposition distincte, non " -"couverte par le présent Contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:250 -msgid "5.4 Taxes et impôts" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:252 -msgid "" -"Tous les frais et tarifs sont indiqués hors taxes et hors impôts, frais et " -"charges fédérales, provinciales, locales ou autres taxes gouvernementales " -"applicables (collectivement, les \"Taxes\"). Le Client est responsable du " -"paiement de toutes les Taxes liées aux achats effectués par le Client en " -"vertu du présent Contrat, sauf lorsque Odoo SA est légalement tenue de payer" -" ou de percevoir les Taxes dont le client est responsable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:261 -msgid "6 Conditions des Services" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:264 -msgid "6.1 Obligations du Client" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:266 -msgid "Le Client accepte de / d':" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:268 -msgid "" -"Payer à Odoo SA les frais applicables pour les Services en vertu du présent " -"Contrat, conformément aux conditions de paiement spécifiées dans la facture " -"correspondante ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:270 -msgid "" -"Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs dépasse le " -"nombre d'Utilisateurs spécifiés à la signature du Contrat, et dans ce cas, " -"de régler les frais supplémentaires applicables telles que décrits à la " -"section :ref:`charges_standard_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:273 -msgid "" -"Prendre toutes les mesures nécessaires pour garantir l'exécution non " -"modifiée de la partie du Logiciel qui vérifie la validité de l'utilisation " -"de Odoo Enterprise Edition, comme décrit à la section " -":ref:`enterprise_access_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:276 -msgid "" -"Fournir tout accès nécessaire à Odoo SA pour vérifier la validité de " -"l'utilisation d'Odoo Enterprise Edition sur demande (par exemple, si la " -"validation automatique ne fonctionne pas pour le Client) ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:279 -msgid "" -"Désigner 1 personne de contact représentant le Client pour toute la durée du" -" contrat ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:280 -msgid "" -"Prendre toutes les mesures raisonnables pour protéger les fichiers et les " -"bases de données du Client et s'assurer que les données du Client sont en " -"sûreté et sécurisées, en reconnaissant qu'Odoo SA ne peut être tenue " -"responsable de toute perte de données ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:288 -msgid "6.2 Non solicitation ou embauche" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:290 -msgid "" -"Sauf si l'autre partie donne son consentement par écrit, chaque partie, ses " -"sociétés affiliées et ses représentants conviennent de ne pas solliciter ou " -"offrir un emploi à tout employé de l'autre partie qui est impliqué dans " -"l'exécution ou l'utilisation des Services en vertu du présent Contrat, " -"pendant la Durée du Contrat et pendant une période de 12 mois à compter de " -"la date de résiliation ou de l'expiration du présent Contrat. En cas de " -"violation des conditions de la présente section qui conduirait à la " -"démission dudit employé à cette fin, la partie ayant enfreint ces " -"dispositions accepte de payer à l'autre partie un montant forfaitaire de 30 " -"000,00 euros (€) (trente mille euros)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:303 -msgid "6.3 Publicité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:305 -msgid "" -"Sauf demande contraire par écrit, chaque partie accorde à l'autre partie une" -" licence mondiale libre de droits, non transférable, non exclusive pour " -"reproduire et afficher le nom, les logos et les marques de l'autre partie, " -"dans le seul but de citer l'autre partie en tant que client ou fournisseur, " -"sur les sites Web, dans des communiqués de presse et autres documents de " -"marketing." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:313 -msgid "6.4 Confidentialité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:324 -msgid "Définition des \"Informations Confidentielles\" :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:316 -msgid "" -"Désigne toutes les informations divulguées par une partie (la \"Partie " -"Communicante\") à l'autre partie (la \"Partie Bénéficiaire\"), que ce soit " -"oralement ou par écrit, qui sont désignées comme confidentielles ou qui " -"devraient raisonnablement être comprises comme étant confidentielles étant " -"donné la nature des informations et les circonstances de la divulgation. En " -"particulier, toute information liée aux activités, aux affaires, aux " -"produits, aux développements, aux secrets commerciaux, au savoir-faire, au " -"personnel, aux clients et aux fournisseurs de l'une des parties doit être " -"considérée comme confidentielle." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:326 -msgid "" -"Pour toute Information Confidentielle reçue pendant la durée du présent " -"contrat, la Partie Bénéficiaire utilisera le même degré de précaution " -"qu'elle utilise pour protéger la confidentialité de ses propres Informations" -" Confidentielles de même importance. Ce degré de précaution devra " -"correspondre au minimum à une précaution raisonnable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:331 -msgid "" -"La Partie Bénéficiaire peut divulguer les Informations Confidentielles de la" -" Partie Communicante dans la mesure où la loi l'y oblige, à condition que la" -" Partie Bénéficiaire avise au préalable par écrit la Partie Communicante de " -"son obligation de divulgation, dans la mesure permise par la loi." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:339 -msgid "6.5 Résiliation" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:341 -msgid "" -"Dans le cas où l'une des parties ne remplit pas ses obligations découlant du" -" présent contrat, et si une telle violation n’est pas résolue dans les 30 " -"jours civils à compter de la notification écrite de cette violation, le " -"présent contrat peut être résilié immédiatement par la partie qui n'a pas " -"commis la violation." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:347 -msgid "" -"En outre, Odoo SA peut résilier le contrat immédiatement dans le cas où le " -"Client ne paie pas les frais applicables pour les services à la date " -"d'échéance indiquée sur la facture correspondante." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:354 -msgid "Durée de l'applicabilité des dispositions:" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:352 -msgid "" -"Les sections \":ref:`confidentiality_fr`\", “:ref:`disclaimers_fr`\", " -"“:ref:`liability_fr`\", et “:ref:`general_provisions_fr`\" survivront la " -"résiliation ou l'expiration du présent contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:359 -msgid "7 Limitations de garantie et de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:364 -msgid "7.1 Garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:366 -msgid "" -"Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts" -" raisonnables sur le plan commercial pour exécuter les Services conformément" -" aux normes du secteur généralement acceptées à condition que :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:370 -msgid "" -"Les systèmes informatiques du Client soient en bon état de fonctionnement et" -" que le Logiciel soit installé dans un système d'exploitation approprié ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:372 -msgid "" -"Le Client fournisse les informations adéquates nécessaires au dépannage et à" -" l'accès, de telle sorte qu'Odoo SA puisse identifier, reproduire et gérer " -"les problèmes ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:374 -msgid "Tous les montants dus à Odoo SA aient été réglés." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:376 -msgid "" -"La reprise de l'exécution des Services par Odoo SA sans frais " -"supplémentaires constitue la seule et unique réparation pour le Client et la" -" seule obligation d'Odoo SA pour toute violation de cette garantie." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:383 -msgid "7.2 Limitation de garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:385 -msgid "" -"Mis à part les dispositions expresses du présent Contrat, aucune des parties" -" ne donne de garantie d'aucune sorte, expresse, implicite, légale ou autre, " -"et chaque partie décline expressément toutes garanties implicites, y compris" -" toute garantie implicite de qualité marchande, d'adéquation à un usage " -"particulier ou de non- contrefaçon, dans les limites autorisées par la loi " -"en vigueur." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:391 -msgid "" -"Odoo SA ne garantit pas que le Logiciel soit conforme à toute loi ou " -"réglementation locale ou internationale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:398 -msgid "7.3 Limitation de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:400 -msgid "" -"Dans la limite autorisée par la loi, la responsabilité globale de chaque " -"partie, ainsi que de ses filiales, découlant ou liée au présent Contrat ne " -"dépassera pas 50% du montant total réglé par le Client en vertu du présent " -"Contrat au cours des 12 mois précédant la date de l'événement donnant lieu à" -" une telle réclamation. Des réclamations multiples n'augmenteront pas cette " -"limite." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:405 -msgid "" -"Les parties et leurs filiales ne pourront en aucun cas être tenues " -"responsables des dommages indirects, spéciaux, accessoires ou consécutifs de" -" quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de " -"revenus, perte de profits, perte d’économies, perte commerciale ou toute " -"autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte " -"ou altération des données, découlant ou en relation avec le présent Contrat," -" quelle que soit la forme de l'action, qu'elle soit fondée sur une " -"obligation contractuelle, délictuelle (y compris la stricte négligence) ou " -"fondée sur toute autre règle de droit ou d'équité, même si la partie ou ses " -"filiales ont été informées du risque de tels dommages, ou si le recours " -"proposé par la partie ou ses filiales n'atteint pas son but essentiel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:420 -msgid "" -"Aucune des parties ne sera tenue pour responsable envers l'autre partie de " -"tout retard ou manquement d'exécution en vertu du présent Contrat, si ce " -"manquement ou retard est causé par une règlementation gouvernementale, un " -"incendie, une grève, une guerre, une inondation, un accident, une épidémie, " -"un embargo, la saisie d'une usine ou d'un produit dans son intégralité ou en" -" partie par un gouvernement ou une autorité publique, ou toute (s) autre (s)" -" cause (s), qu’elle (s) soit (soient) de nature similaire ou différente, " -"pour autant que cette cause soit hors du contrôle raisonnable de la partie " -"concernée, et tant qu'une telle cause existe." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:431 -msgid "8 Dispositions générales" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:436 -msgid "8.1 Droit applicable" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:438 -msgid "" -"Les parties conviennent que les lois de Belgique seront applicables en cas " -"de litige découlant ou en relation avec le présent Contrat, sans tenir " -"compte des règles ou dispositions en matière de compétence législative ou de" -" conflit de lois. Dans la mesure où une poursuite ou procédure judiciaire ou" -" administrative serait autorisée ci-avant, les parties conviennent de se " -"soumettre à la compétence exclusive du tribunal de Nivelles (Belgique) aux " -"fins de la procédure de tout litige." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:448 -msgid "8.2 Divisibilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:450 -msgid "" -"Dans le cas où une ou plusieurs des dispositions du présent contrat ou toute" -" autre application de celles-ci se trouvent non valables, illégales ou non " -"exécutoires, la validité, la légalité et le caractère exécutoire des autres " -"dispositions du présent contrat et toute application de celles-ci ne doivent" -" en aucun cas en être affectés ou compromis. Les parties s'engagent à " -"remplacer toute disposition non valable, illégale ou non exécutoire du " -"présent contrat par une disposition valable ayant les mêmes effets et " -"objectifs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:460 -msgid "9 Appendice A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:462 -msgid "" -"Odoo 9 Enterprise Edition est publié sous la licence Odoo Enterprise Edition" -" License v1.0, définie ci-dessous." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:466 -msgid "" -"Ceci est une traduction en français de la licence “Odoo Enterprise Edition " -"License”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa " -"compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes de la licence “Odoo Enterprise Edition License” est la" -" :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:472 -msgid "" -"This is a french translation of the \"Odoo Enterprise Edition License”. This" -" translation is provided in the hope that it will facilitate understanding, " -"but it has no legal value. The only official reference of the terms of the " -"“Odoo Enterprise Edition License” is the :ref:`original english version " -"`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:489 -msgid "" -"Ce logiciel et les fichiers associés (le \"Logiciel\") ne peuvent être " -"utilisés (c'est-à-dire exécutés, modifiés, ou exécutés avec des " -"modifications) qu'avec un contrat Odoo Enterprise Subscription en ordre de " -"validité, et pour le nombre d'utilisateurs prévus dans ce contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:494 -msgid "" -"Un contrat de Partnariat avec Odoo S.A. en ordre de validité donne les mêmes" -" permissions que ci-dessus, mais uniquement pour un usage restreint à un " -"environnement de test ou de développement." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:498 -msgid "" -"Vous êtes autorisé à développer des modules Odoo basés sur le Logiciel et à " -"les distribuer sous la license de votre choix, pour autant que cette licence" -" soit compatible avec les conditions de la licence Odoo Enterprise Edition " -"Licence (Par exemple: LGPL, MIT ou d'autres licenses propriétaires " -"similaires à celle-ci)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:503 -msgid "" -"Vous êtes autorisé à utiliser des modules Odoo publiés sous n'importe quelle" -" licence, pour autant que leur licence soit compatible avec les conditions " -"de la licence Odoo Enterprise Edition License (Notamment tous les modules " -"publiés sur l'Odoo Apps Store sur odoo.com/apps)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:508 -msgid "" -"Il est interdit de publier, distribuer, accorder des sous-licences, ou " -"vendre tout copie du Logiciel ou toute copie modifiée du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:511 -msgid "" -"Toute copie du Logiciel ou d'une partie substantielle de celui-ci doit " -"inclure l'avis de droit d'auteur original ainsi que le texte de la présente " -"licence." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:514 -msgid "" -"LE LOGICIEL EST FOURNI \"EN L'ETAT\", SANS AUCUNE GARANTIE DE QUELQUE NATURE" -" QUE CE SOIT, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS Y ETRE LIMITE, LES" -" GARANTIES IMPLICITES DE COMMERCIABILITE, DE CONFORMITE A UNE UTILISATION " -"PARTICULIERE, OU DE NON INFRACTION AUX DROITS D'UN TIERS." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:519 -msgid "" -"EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE " -"TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES " -"RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU " -"LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION " -"RELATIVE AU LOGICIEL." -msgstr "" - -#: ../../legal/terms/online.rst:3 -msgid "Odoo Online Terms & Conditions" -msgstr "" - -#: ../../legal/terms/partnership.rst:6 -msgid "Odoo Partnership Agreement - Under Revision!" -msgstr "" - -#: ../../legal/terms/partnership.rst:8 -msgid "Version 5_work-in-progress - Last revision: March 02, 2016." -msgstr "" - -#: ../../legal/terms/partnership.rst:11 -msgid "BETWEEN:" -msgstr "" - -#: ../../legal/terms/partnership.rst:13 -msgid "" -"ODOO SA registered at the Trade and Companies Register of Nivelles under " -"number RCN 95656, having its registered office at Chaussée de Namur, 40 - " -"1367 Grand-Rosière, Belgium." -msgstr "" - -#: ../../legal/terms/partnership.rst:16 -msgid "" -"AND ________________________________, a company having its registered office" -" at _____________________ (Hereinafter referred to as “PARTNER”)" -msgstr "" - -#: ../../legal/terms/partnership.rst:22 -msgid "1 Purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:23 -msgid "" -"The purpose of this agreement is to set forth the conditions under which " -"ODOO provides services to PARTNER, and access to Odoo Enterprise Edition " -"software, and PARTNER complies with the obligations set out hereafter." -msgstr "" - -#: ../../legal/terms/partnership.rst:27 -msgid "" -"ODOO hereby appoints PARTNER, and PARTNER hereby accepts appointment, to be " -"a non-exclusive partner promoting and selling the Odoo Enterprise " -"Subscriptions to clients. PARTNER commits to do its best effort to sell Odoo" -" Enterprise Subscriptions to its clients. To support that, PARTNER will " -"market in priority the ‘Odoo Enterprise Edition’ version to prospects and " -"clients. PARTNER still has the option to sell services on other versions of " -"the software, like \"Odoo Community Edition\", should it be needed." -msgstr "" - -#: ../../legal/terms/partnership.rst:35 -msgid "2 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/partnership.rst:36 -msgid "" -"The duration of this Agreement (the “Term”) shall be one year beginning on " -"the date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term to the other party." -msgstr "" - -#: ../../legal/terms/partnership.rst:45 -msgid "3.1 Project platform access" -msgstr "" - -#: ../../legal/terms/partnership.rst:46 -msgid "" -"To help PARTNER promoting Odoo Enterprise, ODOO grants access to its Github " -"code repository to PARTNER for all ‘Enterprise Edition’ modules, under the " -"terms set forth in Exhibit A and the conditions restricted under this " -"agreement. This access will be granted as of the signature of this agreement" -" and be revoked should the partnership contract be revoked." -msgstr "" - -#: ../../legal/terms/partnership.rst:50 -msgid "3.2 Restrictions" -msgstr "" - -#: ../../legal/terms/partnership.rst:51 -msgid "" -"PARTNER commits to keep confidentiality of the source code of Odoo " -"Enterprise edition modules licensed under restricted rights (labelled as " -"‘Enterprise Edition’) within its staff. The access to clients is governed by" -" the Odoo Enterprise Contract (version 4.0 and above). PARTNER agrees to NOT" -" redistribute this code to 3rd parties without the explicit agreement of " -"ODOO. Notwithstanding the above, PARTNER commits to wholly preserve the " -"integrity of the Odoo Enterprise edition code that is required to verify the" -" validity of usage of Odoo Enterprise edition, collects statistics that are " -"needed for that purpose and enforce the payment of the subscription." -msgstr "" - -#: ../../legal/terms/partnership.rst:56 -msgid "4 Partnership Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:59 -msgid "4.1 Partnership levels" -msgstr "" - -#: ../../legal/terms/partnership.rst:60 -msgid "" -"The ODOO partner program consists of three partnership levels; Ready, Silver" -" and Gold with specific requirements and benefits for each level. " -"Partnership level granted to PARTNER depends on the annual new Odoo " -"Enterprise revenues generated for ODOO. Renewals of existing contracts does " -"not account for the partnership level, but the partner still get his " -"commission on these contracts as stated in 5.2 The table below summarizes " -"the requirement for each partnership level." -msgstr "" - -#: ../../legal/terms/partnership.rst:64 -msgid "" -"Ready Silver Gold Annual New Net Odoo Enterprise Revenues 1.000 € 12.000 € " -"25.000 €" -msgstr "" - -#: ../../legal/terms/partnership.rst:72 -msgid "" -"The level of partnerships will be reviewed quarterly by ODOO based on Odoo " -"Enterprise contracts sold by partners, over the preceeding 12 months. " -"Partners may be upgraded automatically to a higher level once they reach the" -" requirements for a higher level. Silver and Gold partners which are not " -"complying with their partnerships requirements will be assigned to a lower " -"level of partnership if they have not met their requirement at the end of " -"the annual period. For new partners, the initial partner level is granted " -"for one year." -msgstr "" - -#: ../../legal/terms/partnership.rst:77 -msgid "4.2 Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:78 -msgid "" -"The details of the benefits for each level of partnership are described in " -"the table below:" -msgstr "" - -#: ../../legal/terms/partnership.rst:81 -msgid "" -"Ready Silver Gold Recognition Visibility on odoo.com Ready Partner Silver " -"Partner Gold Partner Rights to use the Odoo trademark Ready logo Silver logo" -" Gold logo Learning benefits Yearly upgrades seminars Yes Yes Yes Sales " -"Training Yes Yes Yes Weekly functional training webinars Yes Yes Yes " -"Software Benefits Access to Odoo Enterprise source code Yes Yes Yes Sales " -"benefits Discount on all ODOO services 10% 15% 20% Discount on ODOO " -"Enterprise (Minimum 10 users per contract, applied then for all users). 10% " -"15% 20% Access to an Account Manager Yes Yes Yes Marketing Benefits Access " -"to marketing materials Yes Yes Yes Partner EVENT – ODOO Support & Promotion " -"No Yes Yes" -msgstr "" - -#: ../../legal/terms/partnership.rst:135 -msgid "4.3 Partner Recognition" -msgstr "" - -#: ../../legal/terms/partnership.rst:136 -msgid "" -"ODOO will promote PARTNER as an official partner on its website (odoo.com) " -"for agreed countries. ODOO grants to PARTNER, on a non-exclusive basis, the " -"right to use and reproduce only the ODOO Partner’s logo, and the Odoo name " -"in connection with this Agreement. Each Party undertakes to respect all the " -"rights of the other Party in all the items referred to in the previous " -"paragraph and, more particularly, each Party shall refrain from causing any " -"analogy or creating any confusion between their respective company in the " -"mind of the general public, for any reason whatsoever and by any means " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:141 -msgid "4.4 Learning Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:142 -msgid "" -"In order to train PARTNER, ODOO will organize online training sessions once " -"a week. Sessions are organized into discovery and advanced topics. A session" -" is usually 2 hours and cover an application of the Odoo Enterprise " -"software: sales and CRM, inventory management, project management, " -"eCommerce, human resources, manufacturing, advanced customizations, etc. " -"PARTNER can attend these training sessions at no additional cost and commit " -"to attend at least 20 sessions per year. ODOO will organize at least four " -"sales training session per year of a duration of one week. Each sales " -"training session is organized in one of the ODOO office. PARTNER can send " -"any employee to these training session. Once a new version of Odoo " -"Enterprise is released, ODOO must organize upgrade training session for " -"partners." -msgstr "" - -#: ../../legal/terms/partnership.rst:148 -msgid "4.5 Commission on Odoo Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:149 -msgid "" -"For every ODOO services directly purchased by a customer through PARTNER, " -"PARTNER shall receive retribution as follows For “ODOO Enterprise” contracts" -" sold to CUSTOMER: ODOO will invoice directly the CUSTOMER based on final " -"pricing agreed between ODOO, the PARTNER & the CUSTOMER. Then, PARTNER will " -"invoice his commission to ODOO based on Odoo Enteprise price, net of " -"possible rebates, and based on his current partnership level at the time of " -"signature. For Other Services; Partner invoice directly the CLIENT and ODOO " -"will invoice the PARTNER directly commission included. (as a discount) For " -"“ODOO Enterprise” contracts; PARTNER get a commission as long as the PARTNER" -" maintains a contractual relationship with the CUSTOMER." -msgstr "" - -#: ../../legal/terms/partnership.rst:156 -msgid "5 Miscellaneous" -msgstr "" - -#: ../../legal/terms/partnership.rst:159 -msgid "5.1 Communications" -msgstr "" - -#: ../../legal/terms/partnership.rst:160 -msgid "" -"No communications from either party to the other shall have any validity " -"under this Agreement unless made in writing by or on behalf of PARTNER or " -"ODOO, as the case may be, in accordance with the provisions of this " -"Agreement. Any notice whatsoever which either party hereto is required or " -"authorised by this Agreement to give or make to the other shall be given or " -"made either by post in a prepaid letter, or by hand delivery or facsimile " -"transmission or E-mail." -msgstr "" - -#: ../../legal/terms/partnership.rst:164 -msgid "5.2 BRAND IMAGE" -msgstr "" - -#: ../../legal/terms/partnership.rst:165 -msgid "" -"Both Parties shall refrain from harming the brand image and reputation of " -"the other Party, in any way whatsoever, in the performance of this " -"Agreement. Non-compliance to this provision shall be a cause for termination" -" of this Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:168 -msgid "5.3 Publicity" -msgstr "" - -#: ../../legal/terms/partnership.rst:169 -msgid "" -"ODOO shall publish any press release, advertisement or other public " -"announcement using the PARTNER’s name or trademarks without its prior " -"written consent. In particular, PARTNER accepts to be mentioned, and that " -"its logo and trademark is used for this purpose only, in the list of the " -"partners of ODOO." -msgstr "" - -#: ../../legal/terms/partnership.rst:172 -msgid "5.4 No SOLICITING" -msgstr "" - -#: ../../legal/terms/partnership.rst:173 -msgid "" -"Each party, its subsidiaries and any entity controlled indirectly agrees not" -" to solicit, offer employment to, or use the services of any employee of the" -" other party who is involved in performing the Services for the duration of " -"the Agreement and for a period of twenty four (24) Months from the date of " -"termination of this Agreement, except as expressly provided for in the " -"Agreement or where the other party gives its consent in writing to this. In " -"case of any breach of the terms of this article, the defaulting Party shall " -"pay an indemnity equivalent to 12 months of the gross salary of the employee" -" sought or dismissed, or to at least a minimum of € 30,000." -msgstr "" - -#: ../../legal/terms/partnership.rst:177 -msgid "5.5 Independent Contractor" -msgstr "" - -#: ../../legal/terms/partnership.rst:178 -msgid "" -"The Parties are independent contractors, and this Agreement shall not be " -"construed as constituting either Party as partner, joint venture or " -"fiduciary of the other, as creating any other form of legal association that" -" would impose liability on one Party for the act or failure to act of the " -"other or as providing either Party with the right, power or authority " -"(express or implied) to create any duty or obligation of the other." -msgstr "" - -#: ../../legal/terms/partnership.rst:181 -msgid "6 FEES AND CHARGES" -msgstr "" - -#: ../../legal/terms/partnership.rst:182 -msgid "" -"PARTNER shall pay the charges and the annual fee immediately upon receipt of" -" the invoice sent by ODOO.The annual partnership fees is 2950€. PARTNER " -"shall automatically pay a late payment interest at the rate equivalent to " -"the applicable interest rate of the principal instrument of re-financing of " -"the European Central Bank increased by 7% per year, which shall accrue on a " -"daily basis from the due date of payment; it not being necessary for such " -"accrual that ODOO request or claims the unpaid amount in any manner " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:186 -msgid "7 Termination" -msgstr "" - -#: ../../legal/terms/partnership.rst:187 -msgid "" -"In the event that either Party fails to fulfil one or more of its " -"obligations arising hereunder, and if such breach has not been remedied " -"within thirty (30) calendar days from the first presentation of a letter, " -"sent by the injured Party by registered letter with advice of receipt, " -"giving notice of the breaches, this Agreement may be terminated immediately " -"as of right at the request of the injured Party, without prejudice to any " -"damages that may be claimed from the defaulting Party." -msgstr "" - -#: ../../legal/terms/partnership.rst:189 -msgid "" -"On expiry or termination of this Agreement, PARTNER: shall not use anymore " -"the materials and/or the Odoo brand name or claim the existence of any " -"partnership or link with ODOO, shall during any notice period prior to such " -"termination comply with its obligations. shall not use Odoo Enterprise " -"anymore, for development, test or production purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:195 -msgid "8 Liability AND Indemnities" -msgstr "" - -#: ../../legal/terms/partnership.rst:196 -msgid "" -"Both Parties are bound by a best endeavours obligation hereunder. To the " -"maximum extent permitted by law, ODOO’s liability for any and all claims, " -"losses, damages or expenses from any cause whatsoever and howsoever arising " -"under this Agreement will be limited to the direct damages proven, but will " -"in no event exceed for all damage causing event or series of connected " -"events causing damages the total amount for the charges paid by PARTNER in " -"the course of the six (6) months immediately preceding the date of the event" -" giving rise to such claim. In no event will ODOO be liable for any indirect" -" or consequential damages, including but not limited third parties or " -"Customer claims, loss of revenue, profits, savings, loss of business or " -"other financial loss, costs of standstill or delay, lost or corrupted data " -"arising out of or in connection with the performance of its obligations. " -"PARTNER acknowledges that he has no expectation and has received no " -"assurances that any investment made in execution of this Agreement and the " -"ODOO Partners Program will be recovered or recouped or that he shall obtain " -"any anticipated amount of profits by virtue of this Agreement. Partner " -"waives any commitment whatsoever on behalf of ODOO regarding the evolution " -"of Software." -msgstr "" - -#: ../../legal/terms/partnership.rst:202 -msgid "" -"According to the terms of the Software license, ODOO will not be liable for " -"any bug or for the quality and the performance of the Software, ODOO’s " -"commitment being limited to the correction of bugs as defined in this " -"Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:205 -msgid "9 Governing Law and Jurisdiction" -msgstr "" - -#: ../../legal/terms/partnership.rst:206 -msgid "" -"This Agreement will be governed by and construed in accordance with the laws" -" of Belgium. All disputes arising in connection with the Agreement for which" -" no amicable settlement can be found shall be finally settled by the Courts " -"of Belgium in Nivelles." -msgstr "" - -#: ../../legal/terms/partnership.rst:208 -msgid "For Odoo SA," -msgstr "" - -#: ../../legal/terms/partnership.rst:213 -msgid "For _____________," -msgstr "" - -#: ../../legal/terms/partnership.rst:220 -msgid "10 Appendix A: Odoo Enterprise Edition License" -msgstr "" diff --git a/locale/fr/LC_MESSAGES/point_of_sale.po b/locale/fr/LC_MESSAGES/point_of_sale.po index efd243fe4..99a85e1cc 100644 --- a/locale/fr/LC_MESSAGES/point_of_sale.po +++ b/locale/fr/LC_MESSAGES/point_of_sale.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: matthieu gaillet , 2017\n" +"Last-Translator: Adriana Ierfino , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1975,19 +1975,35 @@ msgid "" "location,..." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "Nom du point de vente" + #: ../../point_of_sale/overview/start.rst:0 msgid "An internal identification of the point of sale" msgstr "Une identification interne du point de vente" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "Journal de ventes" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to post sales entries." msgstr "" "Journal de comptabilité utilisé pour enregistrer des écritures de vente." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "Journal de facturation" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to create invoices." msgstr "Journal des comptes utilisé pour la création de factures." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "Regrouper les éléments du journal" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Check this if you want to group the Journal Items by Product while closing a" @@ -1996,6 +2012,10 @@ msgstr "" "Coché si vous voulez regrouper les éléments du journal par article lors de " "la fermeture d'une session." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "Codes-barres" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Defines what kind of barcodes are available and how they are assigned to " @@ -2004,6 +2024,10 @@ msgstr "" "Definis quel type de code-barres sont disponibles et comment ils sont " "attribués aux produits, clients, et caissiers" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "Séquence des id. commandes" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "This sequence is automatically created by Odoo but you can change it to " @@ -2012,19 +2036,35 @@ msgstr "" "Cette séquence est créée automatiquement par Odoo, mais vous pouvez la " "changer pour personnaliser les références de vos commandes." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "This Point of sale's sales will be related to this Sales Channel." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "Clavier virtuel" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables an integrated Virtual Keyboard" msgstr "Active le clavier virtuel intégré" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "Facturation" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables invoice generation from the Point of Sale" msgstr "" "Active la possibilité de générer des factures depuis le point de vente" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "Pré-remplir le paiement en espèce" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The payment input will behave similarily to bank payment input, and will be " @@ -2033,6 +2073,10 @@ msgstr "" "Ce paiement agira comme un paiement banquaire, et sera pré-rempli avec le " "montant exact " +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "Catégorie de départ" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The point of sale will display this product category by default. If no " @@ -2042,6 +2086,10 @@ msgstr "" " catégorie n'est pas spécifiée, tous les produits disponibles seront " "montrés. " +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "Produit pour pourboire" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The product used to encode the customer tip. Leave empty if you do not " @@ -2050,6 +2098,10 @@ msgstr "" "Le produit utilisé pour encore le pourboire du client. Laissez vide si vous " "n'acceptez pas les pourboires." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "Inclure les taxes dans les prix" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The displayed prices will always include all taxes, even if the taxes have " @@ -2058,14 +2110,26 @@ msgstr "" "Les prix affichés contiendrons toujours toutes les taxes, même si les taxes " "ont été mises en place différemment" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "Barres de défilement larges" + #: ../../point_of_sale/overview/start.rst:0 msgid "For imprecise industrial touchscreens" msgstr "Pour les écrans tactiles industriels non-précis" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "Afficher les photos des catégories" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product categories will be displayed with pictures." msgstr "Les catégories de produits seront affichées avec des photos. " +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "Adresse IP" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The hostname or ip address of the hardware proxy, Will be autodetected if " @@ -2074,28 +2138,52 @@ msgstr "" "Nom d'hôte ou adresse IP du proxy matériel. Laissez vide pour utiliser " "l'autodétection." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "Lecteur de code-barres" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enable barcode scanning with a remotely connected barcode scanner" msgstr "" "Permet de scanner un code-barre avec un scanner de code-barre connecté sans-" "fil." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "Balance électronique" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Electronic Scale integration" msgstr "Active l'interface avec une balance électronique" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "Tiroir-caisse" + #: ../../point_of_sale/overview/start.rst:0 msgid "Automatically open the cashdrawer" msgstr "Ouvre automatiquement le tiroir-caisse" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "Imprimante du reçu" + #: ../../point_of_sale/overview/start.rst:0 msgid "Bypass browser printing and prints via the hardware proxy" msgstr "Impression via le posbox" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "Impression automatique du reçu" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt will automatically be printed at the end of each order" msgstr "Le reçu sera automatiquement imprimé à la fin de chaque commande. " +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "Passer l'écran du reçu" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The receipt screen will be skipped if the receipt can be printed " @@ -2103,31 +2191,59 @@ msgid "" msgstr "" "L'écran de reçu sera passé si le reçu peut être imprimé automatiquement. " +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "Entête" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a header in the printed receipt" msgstr "Un texte court qui sera inséré comme en-tête dans le ticket de reçu" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "Bas de page" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a footer in the printed receipt" msgstr "" "Un texte court qui sera inséré comme pied de page dans le ticket de reçu" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "Contrôle de caisse" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check the amount of the cashbox at opening and closing." msgstr "Contrôle de caisse à l'ouverture et à la fermeture." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "Partage d'addition" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Bill Splitting in the Point of Sale" msgstr "Autoriser le partage d'addition en Point de Vente" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "Impression de la Facture" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allows to print the Bill before payment" msgstr "Autoriser l'impression de la facture avant le paiement" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "Notes de commandes" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allow custom notes on Orderlines" msgstr "Autoriser les notes personnalisées sur les lignes de commande" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "Plans du restaurant" + #: ../../point_of_sale/overview/start.rst:0 msgid "The restaurant floors served by this point of sale" msgstr "Les étages du restaurant servis par ce point de vente" @@ -2881,12 +2997,20 @@ msgid "" "all products or only on specific ones. Click on **Add an item**." msgstr "" +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "Actif" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "" "If unchecked, it will allow you to hide the pricelist without removing it." msgstr "" "Décocher cette case permet de masquer la liste de prix sans la supprimer." +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "Sélectionnable" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "Allow the end user to choose this price list" msgstr "Permettre à l'utilisateur final de choisir cette liste de prix" diff --git a/locale/fr/LC_MESSAGES/purchase.po b/locale/fr/LC_MESSAGES/purchase.po index 5d7f2ddd8..7016bf1d6 100644 --- a/locale/fr/LC_MESSAGES/purchase.po +++ b/locale/fr/LC_MESSAGES/purchase.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Nancy Bolognesi , 2017\n" +"Last-Translator: Fabrice Henrion , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2114,10 +2114,18 @@ msgstr "" "commande**, sélectionnez la date à laquelle vous souhaitez passer la " "commande." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "Expédition" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Incoming Shipments" msgstr "Réceptions" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "Référence fournisseur" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the sales order or bid sent by the vendor. It's used to do the " @@ -2129,6 +2137,10 @@ msgstr "" "articles, puisque cette référence est généralement écrite sur le bon de " "livraison envoyé par votre fournisseur." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "Date de la commande" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Depicts the date where the Quotation should be validated and converted into " @@ -2137,16 +2149,28 @@ msgstr "" "Représente la date où le devis devrait être validé et le converti en bon " "d'achat." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "Document d'origine" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the document that generated this purchase order request (e.g. a" " sales order or an internal procurement request)" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "Livrer à" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "This will determine picking type of incoming shipment" msgstr "Ceci déterminera le type de prélèvement de la réception" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "Adresse de livraison directe" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Put an address if you want to deliver directly from the vendor to the " @@ -2155,10 +2179,18 @@ msgstr "" "Ajoutez une adresse si vous voulez livrer directement du fournisseur au " "client. Sinon, laissez vide pour vous faire livrer à votre société." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "Type d'emplacement de destination" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Technical field used to display the Drop Ship Address" msgstr "Champ technique utilisé pour afficher l'adresse de livraison directe." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "Incoterm" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "International Commercial Terms are a series of predefined commercial terms " diff --git a/locale/fr/LC_MESSAGES/sales.po b/locale/fr/LC_MESSAGES/sales.po index 52122ce6a..2d26a7643 100644 --- a/locale/fr/LC_MESSAGES/sales.po +++ b/locale/fr/LC_MESSAGES/sales.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Lucas Deliege , 2017\n" "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n" @@ -944,16 +944,11 @@ msgstr "" #: ../../sales/invoicing/services/support.rst:66 msgid "" -"There are different ways to track the service related to a sale order or " +"There are different ways to track the service related to a sales order or " "product sold. With the above configuration, you can only sell one support " "contract per order. If your customer orders several service contracts on " "timesheet, you will have to split the quotation into several orders." msgstr "" -"Il existe différentes façons de suivre le service lié à un bon de commande " -"ou à un article vendu. Avec la configuration ci-dessus, vous ne pouvez " -"vendre qu'un contrat d'assistance par commande. Si votre client commande " -"plusieurs contrats d'assistance sur feuilles de temps, vous devrez diviser " -"le devis en plusieurs commandes." #: ../../sales/invoicing/services/support.rst:72 msgid "" @@ -973,21 +968,16 @@ msgid "Managing support contract" msgstr "Gestion d'un contrat d'assistance" #: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sale Orders" -msgstr "Devis et Bons de Commande" +msgid "Quotations and Sales Orders" +msgstr "Devis et bons de commande" #: ../../sales/invoicing/services/support.rst:83 msgid "" -"Once the product is created, you can create a quotation or a sale order with" -" the related product. Once the quotation is confirmed and transformed into a" -" sale order, your users will be able to record services related to this " -"support contract using the timesheet application." +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." msgstr "" -"Une fois que l'article est créé, vous pouvez créer un devis ou un bon de " -"commande avec l'article correspondant. Une fois que le devis est confirmé et" -" transformé en bon de commande, les utilisateurs seront en mesure " -"d'enregistrer les services liés à ce contrat d'assistance en utilisant " -"l'application de feuille de temps." #: ../../sales/invoicing/services/support.rst:93 msgid "Timesheets" @@ -1007,8 +997,8 @@ msgstr "" "services dès qu'il a été vendu." #: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sale order" -msgstr "Contrôler l'assistance fournie sur le bon de commande" +msgid "Control delivered support on the sales order" +msgstr "" #: ../../sales/invoicing/services/support.rst:106 msgid "" @@ -1031,32 +1021,14 @@ msgstr "Vente incitative et renouvellement" #: ../../sales/invoicing/services/support.rst:118 msgid "" "If the number of hours you performed on the support contract is bigger or " -"equal to the number of hours the customer purchased, the sale order " -"**Invoicing Status** is automatically set to **Upselling**. This means you " -"have an opportunity to sell an extra contract to the customer since he used " -"all his quota of service." +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." msgstr "" -"Si le nombre d'heures que vous avez effectuées sur le contrat d'assistance " -"est supérieur ou égal au nombre d'heures que le client a acheté, le ** " -"Status de facturation** du bon de commande est automatiquement réglé sur " -"**Vente incitative**. Cela signifie que vous avez la possibilité de vendre " -"un contrat supplémentaire pour le client depuis qu'il a utilisé tout son " -"quota d'assistance." -#: ../../sales/invoicing/services/support.rst:124 -msgid "" -"Periodically (ideally once every two weeks), you should check the sales " -"order that are in an upselling status. To do this, go to the " -":menuselection:`Sales --> Sales Order` menu and use the **Upselling** filter" -" to get all orders that are in upselling." -msgstr "" -"Périodiquement (idéalement une fois toutes les deux semaines), vous devriez " -"vérifier les bons de commande qui sont dans l'état upselling. Pour ce faire," -" allez au menu :menuselection:`Ventes --> Bons de commande` et utilisez le " -"filtre **Upselling** pour obtenir toutes les commandes qui sont en " -"upselling." - -#: ../../sales/invoicing/services/support.rst:130 +#: ../../sales/invoicing/services/support.rst:127 msgid "" "If you use Odoo CRM, a good practice is to create an opportunity for every " "sale order in upselling invoice status so that you easily track your " @@ -1066,26 +1038,20 @@ msgstr "" "opportunité pour chaque bon de commande en upselling afin que vous puissiez " "suivre facilement votre effort de vente incitative." -#: ../../sales/invoicing/services/support.rst:134 +#: ../../sales/invoicing/services/support.rst:131 msgid "" "If you sell an extra support contract, you can either add a new line on the " -"existing sale order (thus, you continue to timesheet on the same order) or " +"existing sales order (thus, you continue to timesheet on the same order) or " "create a new order (thus, people will timesheet their hours on the new " -"contract). To unmark the sale order as **Upselling**, you can set the sale " -"order as done and it will disappear from your upselling list." +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." msgstr "" -"Si vous vendez un contrat d'assistance supplémentaire, vous pouvez ajouter " -"une nouvelle ligne au bon de commande existant (ainsi, vous continuez à " -"pointer sur le même bon) ou créer une nouvelle commande (alors, les gens " -"vont pointer leurs heures sur le nouveau contrat) . Pour sortir le bon de " -"commande de l'état **Upselling**, vous pouvez définir le bon de commande " -"comme terminé et il disparaîtra de votre liste de upselling." -#: ../../sales/invoicing/services/support.rst:141 +#: ../../sales/invoicing/services/support.rst:138 msgid "Special Configuration" msgstr "Configuration Spéciale" -#: ../../sales/invoicing/services/support.rst:143 +#: ../../sales/invoicing/services/support.rst:140 msgid "" "When creating the product form, you may set a different approach to track " "the service:" @@ -1093,33 +1059,23 @@ msgstr "" "Lors de la création de la fiche article, vous pouvez définir une approche " "différente pour suivre l'assistance :" -#: ../../sales/invoicing/services/support.rst:146 +#: ../../sales/invoicing/services/support.rst:143 msgid "" "**Create task and track hours**: in this mode, a task is created for every " -"sale order line. Then when you do the timesheet, you don't record hours on a" -" sale order/contract, but you record hours on a task (that represents the " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " "contract). The advantage of this solution is that it allows to sell several " -"service contracts within the same sale order." +"service contracts within the same sales order." msgstr "" -"**Créer une tâche et suivre les heures** : dans ce mode, une tâche est créée" -" pour chaque ligne de commande. Puis, quand vous faites la feuille de temps," -" vous n'enregistrez pas les heures sur un contrat / bon de commande, mais " -"vous enregistrez les heures sur une tâche (qui représente le contrat). " -"L'avantage de cette solution est qu'elle permet de vendre plusieurs contrats" -" d'assistance dans le même bon de commande." -#: ../../sales/invoicing/services/support.rst:153 +#: ../../sales/invoicing/services/support.rst:150 msgid "" "**Manually**: you can use this mode if you don't record timesheets in Odoo. " "The number of hours you worked on a specific contract can be recorded " -"manually on the sale order line directly, in the delivered quantity field." +"manually on the sales order line directly, in the delivered quantity field." msgstr "" -"**Manuellement** : vous pouvez utiliser ce mode si vous n'enregistrez pas de" -" feuilles de temps dans Odoo. Le nombre d'heures travaillées sur un contrat " -"spécifique peut être enregistré manuellement directement sur la ligne de " -"commande, dans le champ quantité livrée." -#: ../../sales/invoicing/services/support.rst:159 +#: ../../sales/invoicing/services/support.rst:156 msgid ":doc:`../../../inventory/settings/products/uom`" msgstr ":doc:`../../../inventory/settings/products/uom`" @@ -1387,16 +1343,11 @@ msgstr ":menuselection:`Commande eCommerce --> Facture`" #: ../../sales/overview/main_concepts/invoicing.rst:69 msgid "" -"An eCommerce order will also trigger the creation of the order when it is " +"An eCommerce order will also trigger the creation of the invoice when it is " "fully paid. If you allow paying orders by check or wire transfer, Odoo only " "creates an order and the invoice will be triggered once the payment is " "received." msgstr "" -"Une commande d'eCommerce déclenchera également la création de la commande " -"lorqu'elle sera entièrement payée. Si vous autorisez le paiement des " -"commandes par chèque ou par virement bancaire, Odoo ne créera que la " -"commande, et la création de la facture ne sera déclenchée qu'une fois le " -"paiement reçu." #: ../../sales/overview/main_concepts/invoicing.rst:75 msgid "Creating an invoice manually" @@ -1711,140 +1662,76 @@ msgid "Manage your products" msgstr "" #: ../../sales/products_prices/products/import.rst:3 -msgid "How to import my products" +msgid "How to import products with categories and variants" msgstr "" -#: ../../sales/products_prices/products/import.rst:6 -msgid "How to start" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:8 -msgid "Download the following import templates:" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:10 +#: ../../sales/products_prices/products/import.rst:5 msgid "" -"Partners: customers, vendors (no relation field, can be imported as is)" +"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 "Products (no relation field, can be imported as is)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:12 -msgid "Product Website Categories" +msgid "How to customize the file" msgstr "" #: ../../sales/products_prices/products/import.rst:13 -msgid "Product Attributes & Values" +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:14 -msgid "Products with Categories & Attributes (3 & 4 must be imported first)" +#: ../../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 "" -"Download link: " -"https://drive.google.com/drive/folders/0B1uIL9E_zXrrTEp5eGI2dXJSUjg?usp=sharing" +"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 "" -"You can open them with any spreadsheets software (Microsoft Office, " -"OpenOffice, Google Drive, etc.)." +"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:21 -msgid "How to customize the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:23 -msgid "" -"Remove columns you don't need. Don't remove the first one (called *ID*, see " -"why here below)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:25 -msgid "" -"Don't change labels of columns you want to import. Otherwse Odoo won't match" -" the columns automatically." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:27 -msgid "" -"Feel free to add new columns but the fields need to exist in Odoo. If Odoo " -"fails in matching the column name with a field, you can make it manually " -"when importing by browsing a list of available fields." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:30 -msgid "Once modified, keep your file in .csv format." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:33 -msgid "How to import the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:35 -msgid "Go to the Products menu in Sales, Purchase, Website Admin, etc." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:36 -msgid "Switch to list view (top-right corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:37 -msgid "Click the *Import* button (top-left corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:38 -msgid "" -"Make sure all the columns match an existing field. If not select it manually" -" from the drop-down list." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:40 -msgid "Press * Validate* to test the import." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:41 -msgid "" -"If you get \"Everything seems valid.\" as result message, press *Import* to " -"process the real import. Otherwise correct the issues spotted during the " -"test." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:45 +#: ../../sales/products_prices/products/import.rst:24 msgid "Why an “ID” column" msgstr "" -#: ../../sales/products_prices/products/import.rst:47 +#: ../../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:50 +#: ../../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:52 +#: ../../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:53 +#: ../../sales/products_prices/products/import.rst:32 msgid "Import relation fields (see here below)." msgstr "" -#: ../../sales/products_prices/products/import.rst:56 +#: ../../sales/products_prices/products/import.rst:35 msgid "How to import relation fields" msgstr "" -#: ../../sales/products_prices/products/import.rst:58 +#: ../../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 " @@ -1852,7 +1739,7 @@ msgid "" "their own list menu." msgstr "" -#: ../../sales/products_prices/products/import.rst:62 +#: ../../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 \" / " diff --git a/locale/nl/LC_MESSAGES/accounting.po b/locale/nl/LC_MESSAGES/accounting.po index 666d46e2f..0490a95b1 100644 --- a/locale/nl/LC_MESSAGES/accounting.po +++ b/locale/nl/LC_MESSAGES/accounting.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Stephan Van Dyck , 2017\n" +"Last-Translator: Gunther Clauwaert , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -98,7 +98,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:23 #: ../../accounting/receivables/getting_paid/automated_followups.rst:31 msgid "Configuration" msgstr "Instellingen" @@ -874,7 +873,6 @@ msgstr "" #: ../../accounting/bank/misc/batch.rst:124 #: ../../accounting/payables/pay/sepa.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:134 msgid "Troubleshooting" msgstr "Problemen oplossen" @@ -1587,6 +1585,11 @@ msgid "" "configured as well as the currency of the journal" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "Soort" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1605,14 +1608,26 @@ msgstr "" msgid "Select 'General' for miscellaneous operations journals." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "Bedrijf" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Company related to this journal" msgstr "Bedrijf gerelateerd aan dit dagboek" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "Korte code" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The journal entries of this journal will be named using this prefix." msgstr "De boekingen van dit dagboek worden aangeduid met deze prefix." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "Specifieke reeks voor creditfacturen" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if you don't want to share the same sequence for invoices and" @@ -1621,6 +1636,10 @@ msgstr "" "Vink deze optie aan als u niet dezelfde reeks wil delen voor facturen en " "credit facturen vanuit dit dagboek" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "Dagboek reeks" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the journal " @@ -1629,6 +1648,10 @@ msgstr "" "Dit veld bevat de informatie gerelateerd aan de nummering van de boekingen " "in dit dagboek." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "Begin reeks voor creditfacturen" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the refund " @@ -1637,18 +1660,34 @@ msgstr "" "Dit veld bevat de informatie gerelateerd aan de nummering van de " "creditfacturen reeks van dit dagboek." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "Standaard debet grootboekrekening" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for debit amount" msgstr "Dit is de standaard rekening voor het debet bedrag" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "Standaard credit grootboekrekening" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for credit amount" msgstr "Dit is de standaard rekening voor het credit bedrag" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "Valuta" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The currency used to enter statement" msgstr "De gebruikte valuta" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "Debet methoden" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for collecting money. Odoo modules offer various payments " @@ -1660,6 +1699,10 @@ msgstr "" "betaling om betalingen af te handelen die niet standaard in de toepassing " "zijn opgenomen. " +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "Betaalwijzes" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for sending money. Odoo modules offer various payments " @@ -1671,6 +1714,10 @@ msgstr "" "betaling om betalingen af te handelen die niet standaard in de toepassing " "zijn opgenomen. " +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "Groepeer factuurregels" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "If this box is checked, the system will try to group the accounting lines " @@ -1679,6 +1726,10 @@ msgstr "" "Als dit is aangevinkt, dan zal het systeem proberen de boekingsregels te " "groeperen bij het genereren vanaf facturen." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "Winst & Verlies rekening" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a profit when the ending balance of a cash register differs" @@ -1687,6 +1738,10 @@ msgstr "" "Gebruikt om winst te registreren wanneer de eindsaldo van een kasregister " "verschilt van wat het systeem berekend" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "Verlies rekening" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a loss when the ending balance of a cash register differs " @@ -1695,11 +1750,19 @@ msgstr "" "Gebruikt om verlies te registreren wanneer de eindsaldo van een kasregister " "verschilt van wat het systeem berekend" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "Toon dagboek in dashboard" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Whether this journal should be displayed on the dashboard or not" msgstr "" "Bepaalt of dit dagboek al dan niet getoond moet worden in het dashboard" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Technical feature used to know whether check printing was enabled as payment" @@ -1708,20 +1771,37 @@ msgstr "" "Technische optie gebruikt om te weten of cheque afdrukken is opgezet als " "betaalmethode." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "Controleer reeks" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Checks numbering sequence." msgstr "Cheques nummering reeks." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "Handmatige nummering" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 #: ../../accounting/payables/pay/check.rst:0 msgid "Check this option if your pre-printed checks are not numbered." msgstr "" "Vink deze optie aan als uw her-afgedrukte cheques niet genummerd zijn." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "Volgende cheque numer" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Sequence number of the next printed check." msgstr "Reeksnummer van de volgende afgedrukte cheque." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "Actief in kassa" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if this journal define a payment method that can be used in a" @@ -1730,6 +1810,10 @@ msgstr "" "Vink deze optie aan indien dit dagboek een betaalmethode is voor gebruik " "binnen de kassa." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "Toegestaan bedrag afwijking" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field depicts the maximum difference allowed between the ending balance" @@ -1928,6 +2012,10 @@ msgstr "" msgid "Explanation of the fields:" msgstr "Verklaring van de velden:" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "Status" + #: ../../accounting/others/adviser/assets.rst:0 msgid "When an asset is created, the status is 'Draft'." msgstr "" @@ -1944,24 +2032,44 @@ msgid "" "line of depreciation is posted, the asset automatically goes in that status." msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "Categorie" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Category of asset" msgstr "Categorie van activa" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "Datum" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Date of asset" msgstr "Datum van activa" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "Bruto waarde" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Gross value of asset" msgstr "Bruto waarde van activa" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "Restwaarde" + #: ../../accounting/others/adviser/assets.rst:0 msgid "It is the amount you plan to have that you cannot depreciate." msgstr "" "Het is het bedrag dat u van plan bent te hebben, dat u niet kunt " "afschrijven." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "Berekeningsmethode" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the amount of depreciation lines." msgstr "" @@ -1976,6 +2084,10 @@ msgid "" "* Degressive: Calculated on basis of: Residual Value * Degressive Factor" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "Tijdmethode gebaseerd op" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Choose the method to use to compute the dates and number of depreciation " @@ -1994,6 +2106,10 @@ msgid "" "depreciations won't go beyond." msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "Prorata Temporis" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Indicates that the first depreciation entry for this asset have to be done " @@ -2004,10 +2120,18 @@ msgstr "" "zijn van de inkoopdatum in plaats van de eerste van januari / startdatum van" " het fiscale jaar" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "Aantal afschrijvingen" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The number of depreciations needed to depreciate your asset" msgstr "Het aantal afschrijvingen nodig om de activa af te schrijven." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "Aantal maanden in de periode" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The amount of time between two depreciations, in months" msgstr "De hoeveelheid tijd tussen twee afschrijvingen, in maanden" @@ -3516,14 +3640,26 @@ msgstr "" "rapportagedoeleinden en bepaalt de handelswijze bij het afsluiten van het " "boekjaar en het openen van de balans." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "Labels" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Optional tags you may want to assign for custom reporting" msgstr "Optionele labels die u wilt toewijzen voor aangepaste rapportages" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "Rekening valuta" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Forces all moves for this account to have this account currency." msgstr "Forceert alle boekingen voor deze rekening naar deze tweede valuta." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "Interne soort" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "The 'Internal Type' is used for features available on different types of " @@ -3534,6 +3670,10 @@ msgstr "" "verschillende rekeningen: liquiditeit is voor kas- en bankrekeningen, " "crediteuren/debiteuren is voor leverancier-/klantfacturen." +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "Afletteren toestaan" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "Check this box if this account allows invoices & payments matching of " @@ -7719,10 +7859,18 @@ msgstr "" msgid "Explanation of the fields of the payment screen:" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "Heeft facturen" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used for usability purposes" msgstr "Technisch veld gebruikt voor gebruiksvriendelijke doeleinden" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to hide the payment method if the selected journal has " @@ -7731,6 +7879,10 @@ msgstr "" "Technisch veld gebruikt om de betalingsmethode te verbergen als het " "geselecteerde dagboek maar één betaalmethode heeft die 'handmatig' is" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "Code" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to adapt the interface to the payment type selected." @@ -7738,6 +7890,10 @@ msgstr "" "Technisch veld dat gebruikt wordt om de interface te wijzigen naar de " "geselecteerde betalingsmethode." +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "Controleer nummer" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "The selected journal is configured to print check numbers. If your pre-" @@ -10017,8 +10173,8 @@ msgstr ":doc:`recording`" #: ../../accounting/receivables/customer_payments/credit_cards.rst:167 #: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`paypal`" -msgstr ":doc:`paypal`" +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:169 #: ../../accounting/receivables/customer_payments/recording.rst:130 @@ -10254,210 +10410,6 @@ msgid "" "Reporting (check the KPI average debtors days)." msgstr "" -#: ../../accounting/receivables/customer_payments/paypal.rst:3 -msgid "How to accept paypal payments on invoices?" -msgstr "Hoe Paypal betalingen aanvaarden op uw facturen?" - -#: ../../accounting/receivables/customer_payments/paypal.rst:5 -msgid "" -"The \"Paypal Payment Acquirer\" module allows you to accept payments via " -"paypal, for your sales orders, invoices, or online orders. As paypal accepts" -" payments through credit cards (VISA, Mastercard, …), you will be able to " -"process most payment methods." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:10 -msgid "Paypal support two modes:" -msgstr "Paypal ondersteund twee methodes:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:12 -msgid "" -"Paypal Merchant Account: the user is redirected to paypal to do the payment " -"(either with a credit card or a paypal account)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:15 -msgid "" -"PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to " -"paypal and the payment can be done in the background. This method is mostly " -"used for subscription businesses where you need to charge your customers " -"periodically." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:20 -msgid "As of today, Odoo only support the normal Paypal Merchant Account." -msgstr "" -"Vanaf vandaag ondersteunt Odoo enkel het normale PayPal handelaars account." - -#: ../../accounting/receivables/customer_payments/paypal.rst:26 -msgid "Install the \"PayPal Payment Acquirer\" module" -msgstr "Installeer de *PayPal betalingsverwerker* module" - -#: ../../accounting/receivables/customer_payments/paypal.rst:28 -msgid "Start by installing the **PayPal Payment Acquirer** module." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:30 -msgid "" -"Once the module is installed, you should see a new payment acquirer in the " -"Setting application, menu \"Payment Acquirers\"." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:36 -msgid "" -"By default, Paypal is configured to work in a test environment, out-of-the-" -"box. It means you can already test the full order to payment flow with the " -"paypal sandbox, without having to configure the next steps." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:42 -msgid "Creating and configuring a PayPal merchant account" -msgstr "Een PayPal handelaarsaccount aanmaken en configureren" - -#: ../../accounting/receivables/customer_payments/paypal.rst:45 -msgid "Create a basic Paypal account" -msgstr "Een basis Paypal account aanmaken" - -#: ../../accounting/receivables/customer_payments/paypal.rst:47 -msgid "Existing or newly created Personal Paypal account can be used." -msgstr "Een bestaand of nieuw persoonlijk PayPal account kan gebruikt worden." - -#: ../../accounting/receivables/customer_payments/paypal.rst:49 -msgid "Or upgrade your account to Business account (merchant) if needed" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:55 -msgid "Paypal Account Summary page" -msgstr "Paypal rekening samenvatting pagina" - -#: ../../accounting/receivables/customer_payments/paypal.rst:58 -msgid "Paypal Configuration" -msgstr "Paypal configuratie" - -#: ../../accounting/receivables/customer_payments/paypal.rst:60 -msgid "" -"Access \"Seller preferences\" menu from `PayPal website " -"`__" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:66 -msgid "" -"Access \"Website preferences\" and configure Auto Return (Payment Data " -"Transfer must be left to Off)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:69 -msgid "**Database name**: yourcompany" -msgstr "**Database naam**: yourcompany" - -#: ../../accounting/receivables/customer_payments/paypal.rst:70 -#: ../../accounting/receivables/customer_payments/paypal.rst:88 -msgid "**Website URL**: https://yourcompany.odoo.com/" -msgstr "**Website URL**: https://yourcompany.odoo.com/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:71 -msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" -msgstr "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" - -#: ../../accounting/receivables/customer_payments/paypal.rst:76 -msgid "These settings will redirect your buyer to your web confirmation page." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:80 -msgid "Access and edit Instant payment notifications settings - IPN" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:85 -msgid "Example" -msgstr "Voorbeeld" - -#: ../../accounting/receivables/customer_payments/paypal.rst:87 -msgid "**Database name**: \"yourcompany\"" -msgstr "**Database naam**: \"yourcompany\"" - -#: ../../accounting/receivables/customer_payments/paypal.rst:89 -msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" -msgstr "**Notificatie URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:91 -msgid "" -"Verify that your Notify URL uses the correct protocol (HTTP / HTTPS). If you" -" use the odoo.com domain, we advise you to use HTTPS." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:94 -msgid "" -"Set the encoding to UTF-8 from the menu :menuselection:`Settings --> " -"Language Encoding --> More Options --> More selling tools`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:103 -msgid "" -"Record your Merchant Paypal ID (personal or business account both will have " -"it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> " -"Account Options`." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:111 -msgid "" -"If you want your customers to be able to pay through Paypal while not having" -" a Paypal account- following setting \"Paypal Account Optional\" needs to be" -" set to **ON**. All users will be able to choose Credit/debit card payment " -"option - Paypal account not required." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:120 -msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:122 -msgid "" -":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:124 -msgid "**Paypal Email ID**: your paypal account email address" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:126 -msgid "**Paypal Merchant ID**: ID retrieved at previous step" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:136 -msgid "" -"If your eCommerce customer gets this Error Message after completing Paypal " -"payment instead of being redirected to your database:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:142 -msgid "" -"Verify the settings you have `configured in Paypal `_:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:144 -msgid "" -"Auto Return should be on (the value can be quite generic, like " -"/shop/confirmation; the correct URL will be set for each " -"transaction)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:148 -msgid "Payment Data Transfer should be off" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:150 -msgid "" -"On-premise databases must be accessible through classic HTTP/HTTPS ports " -"(80/443) for Paypal to work correctly, usually through a reverse proxy. " -"Contact your integrating partner if you are unsure this is the case. " -"Databases hosted on odoo.com are already configured correctly." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:157 -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" -msgstr ":doc:`credit_cards`" - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "" @@ -10591,7 +10543,7 @@ msgstr "" #: ../../accounting/receivables/customer_payments/recording.rst:101 msgid "Transferring money from one bank account to another" -msgstr "" +msgstr "Overboeking van geld van een bankrekening naar een andere" #: ../../accounting/receivables/customer_payments/recording.rst:103 msgid "" @@ -10603,7 +10555,7 @@ msgstr "" msgid "" "This will take you to the same screen you have for receiving and making " "payments." -msgstr "" +msgstr "Dit brengt u naar hetzelfde scherm als ontvangsten en betalingen." #: ../../accounting/receivables/customer_payments/recording.rst:118 msgid "" @@ -10614,13 +10566,17 @@ msgid "" " with two journal entries for the same transaction." msgstr "" +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr ":doc:`credit_cards`" + #: ../../accounting/receivables/getting_paid.rst:3 msgid "How to get paid?" msgstr "Hoe betaald worden?" #: ../../accounting/receivables/getting_paid/automated_followups.rst:3 msgid "How to automate customer follow-ups with plans?" -msgstr "" +msgstr "Hoe klantopvolgingen automatiseren via plannen?" #: ../../accounting/receivables/getting_paid/automated_followups.rst:5 msgid "" @@ -10705,11 +10661,11 @@ msgstr "Formele melding" #: ../../accounting/receivables/getting_paid/automated_followups.rst:27 msgid "Bailiff" -msgstr "" +msgstr "Deurwaarder" #: ../../accounting/receivables/getting_paid/automated_followups.rst:34 msgid "Install Reminder Module" -msgstr "" +msgstr "Installeer \"Herinnering\" module" #: ../../accounting/receivables/getting_paid/automated_followups.rst:36 msgid "" @@ -10855,7 +10811,7 @@ msgstr "" #: ../../accounting/receivables/getting_paid/automated_followups.rst:122 msgid "Drill down to an invoice" -msgstr "" +msgstr "Inzoomen op een factuur" #: ../../accounting/receivables/getting_paid/automated_followups.rst:124 msgid "" @@ -10874,11 +10830,13 @@ msgstr "" #: ../../accounting/receivables/getting_paid/automated_followups.rst:135 msgid "How to exclude an invoice from auto follow up?" -msgstr "" +msgstr "Hoe een factuur uitsluiten van automatische opvolging?" #: ../../accounting/receivables/getting_paid/automated_followups.rst:137 msgid "To see all **overdue invoices** or **on need of action**," msgstr "" +"Om alle ** achterstallige facturen ** of ** wanneer er actie nodig is ** te " +"zien," #: ../../accounting/receivables/getting_paid/automated_followups.rst:139 msgid "Go to :menuselection:`Accounting --> Sales --> Customers Statement`" @@ -10886,7 +10844,7 @@ msgstr "" #: ../../accounting/receivables/getting_paid/automated_followups.rst:145 msgid "Exclude a specific invoice for a specific date" -msgstr "" +msgstr "Sluit een bepaalde factuur uit voor een bepaalde datum" #: ../../accounting/receivables/getting_paid/automated_followups.rst:147 msgid "" @@ -10905,13 +10863,15 @@ msgstr "" #: ../../accounting/receivables/getting_paid/automated_followups.rst:162 msgid "Exclude a specific invoice forever" -msgstr "" +msgstr "Sluit een specifieke factuur permanent uit" #: ../../accounting/receivables/getting_paid/automated_followups.rst:164 msgid "" "Odoo can exclude an invoice for a specific customer by clicking on the " "checkbox **Excluded**" msgstr "" +"Odoo kan een factuur uitsluiten voor een specifieke klant door te klikken op" +" het selectievakje ** Uitgesloten **" #: ../../accounting/receivables/getting_paid/automated_followups.rst:168 msgid "If you click on **History**, you can see all follow ups actions." diff --git a/locale/nl/LC_MESSAGES/db_management.po b/locale/nl/LC_MESSAGES/db_management.po index 4646feeb6..f709254e5 100644 --- a/locale/nl/LC_MESSAGES/db_management.po +++ b/locale/nl/LC_MESSAGES/db_management.po @@ -20,11 +20,11 @@ msgstr "" #: ../../db_management/db_online.rst:8 msgid "Online Database management" -msgstr "" +msgstr "Online database beheer" #: ../../db_management/db_online.rst:13 msgid "Duplicating a database" -msgstr "" +msgstr "Een database dupliceren" #: ../../db_management/db_online.rst:15 msgid "" @@ -92,7 +92,7 @@ msgstr "" #: ../../db_management/db_premise.rst:10 msgid "Register a database" -msgstr "" +msgstr "Registreer een database" #: ../../db_management/db_premise.rst:12 msgid "" @@ -117,11 +117,11 @@ msgstr "" #: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97 #: ../../db_management/db_premise.rst:130 msgid "Solutions" -msgstr "" +msgstr "Oplossingen" #: ../../db_management/db_premise.rst:33 msgid "Do you have a valid Enterprise subscription?" -msgstr "" +msgstr "Heeft u een geldig Enterprise abonnement?" #: ../../db_management/db_premise.rst:35 msgid "" @@ -132,7 +132,7 @@ msgstr "" #: ../../db_management/db_premise.rst:39 msgid "Have you already linked a database with your subscription reference?" -msgstr "" +msgstr "Heeft u al een database gelinkt met uw abonnementsnummer?" #: ../../db_management/db_premise.rst:41 msgid "" @@ -231,7 +231,7 @@ msgstr "" #: ../../db_management/db_premise.rst:116 msgid "Database expired error message" -msgstr "" +msgstr "Database vervallen foutmelding" #: ../../db_management/db_premise.rst:118 msgid "" @@ -261,7 +261,7 @@ msgstr "" #: ../../db_management/db_premise.rst:136 msgid "Contact our `Support `__" -msgstr "" +msgstr "Contacteer onze `support `__" #: ../../db_management/db_premise.rst:138 msgid "" @@ -271,7 +271,7 @@ msgstr "" #: ../../db_management/db_premise.rst:145 msgid "Force an Update Notification" -msgstr "" +msgstr "Forceer een update notificatie" #: ../../db_management/db_premise.rst:147 msgid "" @@ -322,7 +322,7 @@ msgstr "" #: ../../db_management/db_premise.rst:174 msgid "Duplicate a database" -msgstr "" +msgstr "Dupliceer een database" #: ../../db_management/db_premise.rst:176 msgid "" diff --git a/locale/nl/LC_MESSAGES/discuss.po b/locale/nl/LC_MESSAGES/discuss.po index 15a8e2255..fb4612f4b 100644 --- a/locale/nl/LC_MESSAGES/discuss.po +++ b/locale/nl/LC_MESSAGES/discuss.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Yenthe Van Ginneken , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" @@ -23,146 +23,238 @@ msgid "Discuss" msgstr "Discussieer" #: ../../discuss/email_servers.rst:3 -msgid "How to use my own email servers to send and receive messages in Odoo" +msgid "How to use my own email servers to send and receive email in Odoo" msgstr "" #: ../../discuss/email_servers.rst:6 msgid "When is it needed" -msgstr "" +msgstr "Wanneer het nodig is" #: ../../discuss/email_servers.rst:7 -msgid "You need it if you use Odoo Community or Enterprise." -msgstr "" - -#: ../../discuss/email_servers.rst:10 -msgid "What if I use Odoo Online" -msgstr "" - -#: ../../discuss/email_servers.rst:11 msgid "" -"You are done! Odoo Online comes up with an embedded and ready-to-use email " -"server (*@yourcompany.odoo.com*). We recommend to keep this default setting " -"as is as it is really convenient." +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." msgstr "" +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" +msgstr "Hoe op te zetten" + #: ../../discuss/email_servers.rst:15 msgid "" -"Indeed, while it is branded by Odoo, the visible source of any message sent " -"from Odoo will be your personal email address (your Odoo login). Your " -"contacts will therefore trust your messages." -msgstr "" - -#: ../../discuss/email_servers.rst:20 -msgid "How does it work when a contact replies to an email sent from Odoo" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." msgstr "" #: ../../discuss/email_servers.rst:21 msgid "" -"Default reply-to is a generic address used to automatically route any " -"incoming email to the discussion thread of the origin business object " -"(opportunity, order, task, etc.) and to the inbox of all its followers. By " -"default this address is \"catchall@\" but it can be changed. Thanks to it, " -"you get a perfect message thread in Odoo and you don't pollute your external" -" email box with Odoo-related topics." +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:29 -msgid "How to use my own email servers" -msgstr "" - -#: ../../discuss/email_servers.rst:30 -msgid "" -"You need to be a system admin to set this up. Go to :menuselection:`Settings" -" --> General Settings` and check *External Email Servers* (watch out: this " -"checkbox only shows up after Odoo 10). Then, go through the following steps." -msgstr "" - -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/email_servers.rst:26 msgid "Set an outgoing email server for outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:37 +#: ../../discuss/email_servers.rst:27 msgid "" "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " "etc.) as well as your admin credentials. Once all the information has been " "filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:45 +#: ../../discuss/email_servers.rst:35 msgid "Set an incoming email server for inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:46 +#: ../../discuss/email_servers.rst:36 msgid "" "Fill out the form according to your email provider’s settings. Leave the " "*Actions to Perform on Incoming Mails* blank. Once all the information has " "been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:53 +#: ../../discuss/email_servers.rst:43 msgid "" "By default inbound messages are fetched every 5 minutes. You can change this" " value in developer mode. Go to :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/email_servers.rst:59 +#: ../../discuss/email_servers.rst:49 msgid "Set the domain name" -msgstr "" +msgstr "Stel de domeinnaam in" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/email_servers.rst:50 msgid "" "Enter the domain name of your email servers (e.g. mycompany.com) in General " "Settings." msgstr "" -#: ../../discuss/email_servers.rst:67 +#: ../../discuss/email_servers.rst:57 msgid "Create a catchall address" +msgstr "Maak een catchall adres" + +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." msgstr "" -#: ../../discuss/email_servers.rst:68 +#: ../../discuss/email_servers.rst:63 msgid "" "Create a catchall address in your email server settings. We advise you to " "use \"catchall@\" so that everything works out straight away. If you want to" " use another alias, you have extra steps in Odoo:" msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/email_servers.rst:67 msgid "Activate the developer mode from your Settings Dashboard." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/email_servers.rst:72 msgid "" "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " "Parameters --> System Parameters` and enter your custom catchall alias in " "*mail.catchall.alias*." msgstr "" -#: ../../discuss/email_servers.rst:84 +#: ../../discuss/email_servers.rst:79 msgid "You can edit the email alias used for bounced messages the same way." msgstr "" -#: ../../discuss/email_servers.rst:87 -msgid "How to perfectly combine Odoo Discuss and my traditional email tool" +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" msgstr "" -#: ../../discuss/email_servers.rst:88 +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here `__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 msgid "" "Odoo Discuss is a perfect tool to send and read messages related to business" -" objects. But it doesn't aim to replace a full-featured email software " -"(Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " "both systems without mingling them: What is related to Odoo business objects" -" or applications goes into Odoo; What is not stays into your external email " -"boxes." +" or applications goes into Odoo; What is not can be managed into your " +"external email box." msgstr "" -#: ../../discuss/email_servers.rst:95 +#: ../../discuss/email_servers.rst:150 msgid "" "To do so, create specific email aliases to use in Odoo (to generate leads or" " opportunities, helpdesk tickets, etc.). If you take an email alias already " "used for messaging outside of Odoo, incoming messages will land into both " -"systems. This will negatively impact your productivity when it comes to " -"process them." +"systems. This will negatively impact your productivity." msgstr "" #: ../../discuss/mail_twitter.rst:3 @@ -298,7 +390,7 @@ msgstr "" #: ../../discuss/overview.rst:3 msgid "Why to use Odoo Discuss" -msgstr "" +msgstr "Waarom Odoo discussies gebruiken" #: ../../discuss/overview.rst:5 msgid "" diff --git a/locale/nl/LC_MESSAGES/ecommerce.po b/locale/nl/LC_MESSAGES/ecommerce.po index b9a98ef0c..f41c2f39f 100644 --- a/locale/nl/LC_MESSAGES/ecommerce.po +++ b/locale/nl/LC_MESSAGES/ecommerce.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Erwin van der Ploeg , 2017\n" +"Last-Translator: Gunther Clauwaert , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -32,7 +32,7 @@ msgstr "" #: ../../ecommerce/getting_started/catalog.rst:6 msgid "Product Catalog" -msgstr "" +msgstr "Product catalogus" #: ../../ecommerce/getting_started/catalog.rst:8 msgid "" @@ -64,7 +64,7 @@ msgstr "" #: ../../ecommerce/getting_started/catalog.rst:29 msgid "Quick add to cart" -msgstr "" +msgstr "Snel toevoegen aan winkelmandje" #: ../../ecommerce/getting_started/catalog.rst:31 msgid "" @@ -77,7 +77,7 @@ msgstr "" #: ../../ecommerce/getting_started/product_page.rst:3 msgid "How to build a product page" -msgstr "" +msgstr "Hoe een productpagina bouwen" #: ../../ecommerce/getting_started/product_page.rst:5 msgid "On the website click *New Page* in the top-right corner." @@ -101,39 +101,39 @@ msgstr "" #: ../../ecommerce/getting_started/product_page.rst:26 msgid ":doc:`../managing_products/variants`" -msgstr "" +msgstr ":doc:`../managing_products/variants`" #: ../../ecommerce/getting_started/product_page.rst:27 msgid ":doc:`../../sales/products_prices/taxes`" -msgstr "" +msgstr ":doc:`../../sales/products_prices/taxes`" #: ../../ecommerce/getting_started/product_page.rst:28 msgid ":doc:`../managing_products/stock`" -msgstr "" +msgstr ":doc:`../managing_products/stock`" #: ../../ecommerce/getting_started/product_page.rst:29 msgid ":doc:`../maximizing_revenue/cross_selling`" -msgstr "" +msgstr ":doc:`../maximizing_revenue/cross_selling`" #: ../../ecommerce/getting_started/product_page.rst:30 msgid ":doc:`../maximizing_revenue/reviews`" -msgstr "" +msgstr ":doc:`../maximizing_revenue/reviews`" #: ../../ecommerce/getting_started/product_page.rst:31 msgid ":doc:`../maximizing_revenue/pricing`" -msgstr "" +msgstr ":doc:`../maximizing_revenue/pricing`" #: ../../ecommerce/getting_started/product_page.rst:32 msgid ":doc:`../../website/optimize/seo`" -msgstr "" +msgstr ":doc:`../../website/optimize/seo`" #: ../../ecommerce/managing_products.rst:3 msgid "Manage my products" -msgstr "" +msgstr "Beheer mijn producten" #: ../../ecommerce/managing_products/multi_images.rst:3 msgid "How to display several images per product" -msgstr "" +msgstr "Hoe meerdere afbeeldingen per product te tonen" #: ../../ecommerce/managing_products/multi_images.rst:5 msgid "" @@ -160,7 +160,7 @@ msgstr "" #: ../../ecommerce/managing_products/stock.rst:3 msgid "How to show product availability" -msgstr "" +msgstr "Hoe productbeschikbaarheid tonen" #: ../../ecommerce/managing_products/stock.rst:5 msgid "" @@ -193,7 +193,7 @@ msgstr "" #: ../../ecommerce/managing_products/variants.rst:3 msgid "How to manage product variants" -msgstr "" +msgstr "Hoe productvarianten beheren" #: ../../ecommerce/managing_products/variants.rst:5 msgid "" @@ -204,7 +204,7 @@ msgstr "" #: ../../ecommerce/managing_products/variants.rst:13 msgid "How to create attributes & variants" -msgstr "" +msgstr "Hoe attributen & varianten aanmaken" #: ../../ecommerce/managing_products/variants.rst:15 msgid "" @@ -241,19 +241,19 @@ msgstr "" #: ../../ecommerce/managing_products/variants.rst:41 msgid "Barcode," -msgstr "" +msgstr "Barcode," #: ../../ecommerce/managing_products/variants.rst:42 msgid "Internal Reference (SKU #)," -msgstr "" +msgstr "Interne referentie (SKU #)," #: ../../ecommerce/managing_products/variants.rst:43 msgid "Volume," -msgstr "" +msgstr "Volume," #: ../../ecommerce/managing_products/variants.rst:44 msgid "Weight," -msgstr "" +msgstr "Gewicht," #: ../../ecommerce/managing_products/variants.rst:45 msgid "Active (available in quotes & website)." @@ -499,7 +499,7 @@ msgstr "" #: ../../ecommerce/maximizing_revenue/promo_code.rst:43 msgid ":doc:`pricing`" -msgstr "" +msgstr ":doc:`prijzen`" #: ../../ecommerce/maximizing_revenue/reviews.rst:3 msgid "How to enable comments & rating" @@ -564,7 +564,7 @@ msgstr "" #: ../../ecommerce/maximizing_revenue/reviews.rst:56 msgid "..tip::" -msgstr "" +msgstr "..tip::" #: ../../ecommerce/maximizing_revenue/reviews.rst:55 msgid "" @@ -616,11 +616,11 @@ msgstr "" #: ../../ecommerce/overview/introduction.rst:13 msgid "Product Page" -msgstr "" +msgstr "Product pagina" #: ../../ecommerce/overview/introduction.rst:14 msgid "Shop Page" -msgstr "" +msgstr "Winkel pagina" #: ../../ecommerce/overview/introduction.rst:15 msgid "Pricing" @@ -648,30 +648,28 @@ msgstr "" #: ../../ecommerce/overview/introduction.rst:24 msgid ":doc:`../../website/publish/domain_name`" -msgstr "" +msgstr ":doc:`../../website/publish/domain_name`" #: ../../ecommerce/publish.rst:3 msgid "Launch my website" -msgstr "" +msgstr "Lanceer mijn website" #: ../../ecommerce/shopper_experience.rst:3 -msgid "Improve shopper experience" -msgstr "" +msgid "Get paid" +msgstr "Wordt betaald" #: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to set up payment methods" +msgid "How to get paid with payment acquirers" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:5 msgid "" -"To collect payments, you can either request your customers to process it " -"manually (e.g. wire transfer) or redirect them to payment acquirers. The " -"payment process described hereunder is common to both eCommerce and online " -"quotations." +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "Payment methods" +msgid "What are the payment methods available" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:13 @@ -681,457 +679,561 @@ msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:15 msgid "" "Wire Transfer is the default payment method available. The aim is providing " -"your customers with your bank details so that they can pay via their bank. " -"This is very easy to start with but slow and inefficient process-wise. Opt " -"for online acquirers as soon as you can!" +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "" -"For B2B users: you can create new manually-processed payment methods (check," -" purchase order, etc.) by renaming 'Wire Transfer' or duplicating it." +msgid "Payment acquirers" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:25 -msgid "Online payment acquirers" +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "" -"Redirect your customers to payment acquirer platforms to collect money " -"effortless. Odoo supports more and more platforms over time: Paypal, " -"Ingenico, Authorize.net, etc. Once the payment accepted, orders are " -"confirmed in Odoo so that the delivery & invoicing processes are triggered " -"automatically." -msgstr "" +msgid "`Paypal `__" +msgstr "`Paypal `__" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "Ingenico" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "Authorize.net" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "Adyen" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "Buckaroo" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" +msgstr "PayUmoney" #: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Custom (advanced)" -msgstr "" +msgid "Sips" +msgstr "Sips" -#: ../../ecommerce/shopper_experience/payment.rst:35 -msgid "" -"Can be used to request payments to any payment acquirer not listed in Odoo." -msgstr "" +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" +msgstr "Stripe" #: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "Edit a payment method" -msgstr "" +msgid "How to go live" +msgstr "Hoe live te gaan" #: ../../ecommerce/shopper_experience/payment.rst:40 msgid "" -"To make payment methods intuitive for your customers feel free to customize " -"them by editing:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:42 -msgid "the name," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:44 -msgid "the picture," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:46 -msgid "" -"the notification messages (thank you & next step, error, cancellation)." +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 msgid "" -"Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers`" -" to do so." +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:51 -msgid "Generic setup" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:53 -msgid "Review the elements here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:55 -msgid "Enter your credentials (online acquirers only)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:57 -msgid "Choose your order confirmation preference (see below)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:59 -msgid "Publish the payment method." +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "Test the payment flow in *Test* mode (default mode)." +msgid "How to debit credit cards to pay subscriptions" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:63 -msgid "Switch to *Production* mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:65 +#: ../../ecommerce/shopper_experience/payment.rst:62 msgid "" -"Se your default payment acquirer in :menuselection:`Accounting --> " -"Configuration --> Settings`. It will be auto-selected for your customers " -"when they enter the payment screen." +"`Odoo Subscription `__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:69 +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 msgid "" -"Rely on the documentation related to your payment acquirer to go through " -"step 2, 5 and 6. Some acquirers provides you with specific credentials for " -"test and production modes (Paypal). Others let you switch mode in their " -"setup interface (Authorize.net)." +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:74 +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 msgid "" -"With Ingenico and Authorize.net, you can let your customers save and reuse a" -" payment card to accelerate the process on next checkouts. See *Store Card " -"Data* in Configuration tab." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:78 -msgid "Payment flow" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:80 -msgid "" -"When choosing the payment method, the customer is taken to the payment " -"acquirer interface to process the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:83 -msgid "" -"Once done he is taken back to Odoo's confirmation page. The transaction " -"status shows up:" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "" -"*Pending*: the order will be confirmed as soon as you authorize the " -"transaction in the acquirer interface." +msgid "How to:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "*Confirmed*: the payment has been authorized automatically." -msgstr "" +msgid "Switch to developer mode." +msgstr "Wisselen naar ontwikkelaarsmodus." #: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "" -"A confirmation email is sent to the customer with a copy of the order in " -"pdf. It shows the payment status." +msgid "Take the **Custom** payment method." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Launch the delivery and invoicing from:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:93 msgid "" -"eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:95 -msgid "" -"online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales " -"Orders`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:97 -msgid "" -"For internal tracking purposes, a link to the transaction status is provided" -" in the sales order." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:100 -msgid "" -"If the customer cancels the payment while on the payment acquirer form, it " -"is taken back to the store page (or online quotation) in order to reprocess " -"the order. The payment is marked as *Cancelled* in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:105 -msgid "" -"You can edit the confirmation email template from :menuselection:`Website " -"Admin --> Configuration --> Settings`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:109 -msgid "Order confirmation preferences" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid "There are 4 different behaviors available for any payment acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:114 -msgid "No automatic confirmation" -msgstr "Geen automatische bevestiging" - -#: ../../ecommerce/shopper_experience/payment.rst:116 -msgid "" -"This is the default mode for *Wire Transfer*. It means Odoo does not confirm" -" orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid " -"Order*). Once you get the payment, you are expected to confirm the order " -"manually to pursue the process (delivery, invoicing)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:121 -msgid "" -"Authorize the amount and confirm the SO on acquirer confirmation (capture " -"manually)" -msgstr "" -"Autoriseer het bedrag en bevestig de verkooporder bij betalingsverwerker " -"bevestiging (handmatige vastlegging)" - -#: ../../ecommerce/shopper_experience/payment.rst:123 -msgid "" -"Odoo confirms the order as soon as the payment success notification comes " -"in. To get the money however, you need to capture it from your payment " -"transaction. In lots of countries you are indeed requested to deliver your " -"goods before capturing the amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:128 -msgid "" -"Authorize & capture the amount and confirm the SO on acquirer confirmation" -msgstr "" -"Autoriseren en vastleggen van het bedrag en bevestig de verkooporder bij " -"betalingsverwerker bevestiging" - -#: ../../ecommerce/shopper_experience/payment.rst:130 -msgid "" -"This is the default mode for payment acquirers. The amount is captured " -"automatically." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:133 -msgid "" -"For B2B: if you use a manual payment method like *Wire Transfer* and don't " -"expect any upfront payment to launch the delivery, switch to this mode as " -"well." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:137 -msgid "" -"Authorize & capture the amount, confirm the SO and auto-validate the invoice" -" on acquirer confirmation" -msgstr "" -"Autoriseren en vastleggen van het bedrag, bevestig de verkooporder en " -"valideer automatisch de factuur bij betalingsverwerker bevestiging" - -#: ../../ecommerce/shopper_experience/payment.rst:139 -msgid "" -"If you invoice upfront and not at the delivery, switch to this last mode to " -"automate everything. You are requested to select a Payment Journal to record" -" such payments (see " -":doc:`../../accounting/receivables/customer_payments/credit_cards`)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:144 -msgid "Custom payment acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:146 -msgid "" -"Odoo can submit payment requests and redirect to any payment acquirer. In " -"such a case, you need to confirm the sale manually in Odoo once you get paid" -" because Odoo cannot read any payment status sent by the acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:150 -msgid "To configure this:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:152 -msgid "switch to developer mode," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:154 -msgid "edit the *Custom* payment method," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:156 -msgid "" -"set up the payment form (S2S Form Template) as instructed by your payment " +"Set up the payment form (S2S Form Template) as instructed by your payment " "acquirer. You can start from *default_acquirer_button* that you can " "duplicate." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:160 -msgid "Recurring payments & Installment plans" -msgstr "" +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" +msgstr "Andere configuraties" -#: ../../ecommerce/shopper_experience/payment.rst:162 +#: ../../ecommerce/shopper_experience/payment.rst:98 msgid "" -"The Ingenico integration allows you to process and manage recurring payments" -" from Odoo Subscriptions app out-of-the-box (more information coming soon)." +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"`__)." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:165 +#: ../../ecommerce/shopper_experience/payment.rst:102 msgid "" -"With some customization, Odoo can also trigger installment plans if this is " -"permitted by your payment acquirer’s API:" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. `__" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:168 -msgid "" -"e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic" -"/paypal-payments-standard/integration-guide/installment_buttons)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:170 -msgid "" -"Such a service is made on-demand by our technical experts based on your own " -"requirements. Ask our business advisors at info@odoo.com." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:175 +#: ../../ecommerce/shopper_experience/payment.rst:109 msgid ":doc:`paypal`" msgstr ":doc:`paypal`" -#: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "How to collect payments with Paypal" +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr ":doc:`wire_transfer`" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr ":doc:`payment_acquirer`" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" msgstr "" +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:3 +msgid "How to get paid with Paypal" +msgstr "Hoe betaald worden met Paypal" + #: ../../ecommerce/shopper_experience/paypal.rst:5 msgid "" -"Paypal is the easiest payment method to configure. It is also the only one " -"without any subscription free." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:9 -msgid "Setup your Paypal account" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:11 +msgid "Set up your Paypal account" +msgstr "Zet uw Paypal account op" + +#: ../../ecommerce/shopper_experience/paypal.rst:13 msgid "" -"1. Create a business account at Paypal.com (see: https://www.paypal.com/in" -"/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-" -"outside) or upgrade your account to Business account (merchant) if you have " -"a basic account." +"Create a `Paypal Business Account `__ or upgrade " +"your account to *Business account* if you have a basic account." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:15 +#: ../../ecommerce/shopper_experience/paypal.rst:16 msgid "" -"2. Log in to your account at Paypal.com and go to :menuselection:`My Account" -" --> Profile --> My Selling Tools`. There click *PayPal button language " -"encoding* under *More Selling Tools* section. Then, click *More Options* and" -" replace the two default encoding formats by *UTF-8*." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:20 -msgid "Open Paypal setup form in Odoo and enter your *Email ID*." +"Log in to `Paypal `__ and open the settings of your " +"**Profile**." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:22 -msgid "" -"4. The Paypal Merchant ID is not mandatory (extra verification level). It is" -" provided in Paypal under :menuselection:`My Account --> Overview`." +msgid "Now enter the menu **My selling tools**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:25 -msgid "" -"5. Configure the IPN feedback (Paypal contacting your Odoo instance without " -"needing the redirection). The setting can be found in " -":menuselection:`Profile --> My Selling Tools --> Instant payment " -"notification`. Activate it and set it to " -"/payment/paypal/ipn." +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:30 +#: ../../ecommerce/shopper_experience/paypal.rst:29 msgid "" -"6. To test the workflow, you can create sandbox accounts by logging in at " -"https://developer.paypal.com/webapps/developer/applications/myapps with the " -"same Paypal credentials. Two default sandbox accounts are automatically " -"generated when you register to Paypal: one is a buyer, the other is a " -"shopper." +"Turn on **Auto Return** and enter the **Return URL**: " +"/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:35 +#: ../../ecommerce/shopper_experience/paypal.rst:36 msgid "" -"7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com " -"(same password than real account) and apply the same format change." +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:39 +#: ../../ecommerce/shopper_experience/paypal.rst:43 msgid "" -"To automatically redirect your customers when the payment is completed, go " -"to your Website Preferences and turn *Auto Return* on. Set *Return URL* to " -"/shop/confirmation. Verify that your *Notify URL* uses " -"the correct protocol (HTTP/HTTPS)." +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "" -"If you want your customers to pay without creating a Paypal account, *Paypal" -" Account Optional* needs to be turned on." +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: /payment/paypal/ipn" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:48 +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 msgid "Transaction fees" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:50 +#: ../../ecommerce/shopper_experience/paypal.rst:114 msgid "" "You can charge an extra to the customer to cover the transaction fees Paypal" " charges you. Once redirected to Paypal, your customer sees an extra applied" " to the order amount." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:53 +#: ../../ecommerce/shopper_experience/paypal.rst:117 msgid "" -"To activate this, go to the *Configuration* tab and check *Add Extra Fees*. " -"Default fees are the ones charged by Paypal." +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site `__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox `__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:3 -msgid "How customers can access their portal" +msgid "How customers can access their customer account" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:5 msgid "" -"It has never been so easy for your customers to access their documents " -"through a portal. Forget endless signup forms, Odoo makes it as easy as ABC." -" With eCommerce and Online Quotation apps, your customers are requested to " -"create a portal account (name, email, password only) from the very first " -"order confirmation or online quotation email they get from you." +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:12 +#: ../../ecommerce/shopper_experience/portal.rst:14 msgid "Sign up" msgstr "Aanmelden" -#: ../../ecommerce/shopper_experience/portal.rst:14 +#: ../../ecommerce/shopper_experience/portal.rst:16 msgid "" -"When clicking the link in the email or when clicking *Sign up* in the " -"checkout process, your customer is directed to the *Sign up* page." -msgstr "" - -#: ../../ecommerce/shopper_experience/portal.rst:21 -msgid "Customer account" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 msgid "" -"Once logged in the customer will access his account by clicking *My Account*" +"Once logged in the customer will access the account by clicking *My Account*" " in the login dropdown menu." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:29 +#: ../../ecommerce/shopper_experience/portal.rst:31 msgid "" -"From the portal menu all the customer history can be reviewed. The main " -"address (billing) can also be modified." +"THere they find all their history. The main address (billing) can also be " +"modified." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:36 +#: ../../ecommerce/shopper_experience/portal.rst:37 msgid "" -"If a portal user is a contact of a company (*Company* field set in customer " -"detail form), this last will see all the documents of the company and all " -"its other contacts through the portal." +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." msgstr "" #: ../../ecommerce/taxes.rst:3 diff --git a/locale/nl/LC_MESSAGES/general.po b/locale/nl/LC_MESSAGES/general.po index d9b587c1e..8cddb5253 100644 --- a/locale/nl/LC_MESSAGES/general.po +++ b/locale/nl/LC_MESSAGES/general.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Eric Geens , 2017\n" +"Last-Translator: Yenthe Van Ginneken , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -23,12 +23,12 @@ msgid "General" msgstr "Algemeen" #: ../../general/auth.rst:3 -msgid "Authentification" -msgstr "" +msgid "Authentication" +msgstr "Authenticatie" #: ../../general/auth/google.rst:3 msgid "How to allow users to sign in with their Google account" -msgstr "" +msgstr "Hoe gebruikers toestaan zich aan te melden met hun Google-account" #: ../../general/auth/google.rst:5 msgid "" @@ -41,10 +41,11 @@ msgstr "" msgid "" "Click on **Create Project** and enter the project name and other details." msgstr "" +"Klik op **Creëer Project** en voer een projectnaam en andere details in" #: ../../general/auth/google.rst:15 msgid "Click on **Use Google APIs**" -msgstr "" +msgstr "Klik op **Gebruik Google APIs**" #: ../../general/auth/google.rst:20 msgid "" @@ -56,7 +57,7 @@ msgstr "" msgid "" "Fill in your address, email and the product name (for example odoo) and then" " save." -msgstr "" +msgstr "Vul uw adres, e-mail en de productnaam in en sla het op." #: ../../general/auth/google.rst:30 msgid "" @@ -84,64 +85,198 @@ msgid "" msgstr "" #: ../../general/base_import.rst:3 -msgid "BASE IMPORT" +msgid "Data Import" +msgstr "Data Import" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "Hoe een importeer sjabloon te wijzigen" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "Hoe het bestand aanpassen" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "Waarom een \"ID\" kolom" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" +"Het instellen van een ID is niet verplicht bij invoer maar is in veel " +"gevallen handig:" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "Relatievelden importeren (zie hieronder)." + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "Hoe relatievelden importeren" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" #: ../../general/base_import/import_faq.rst:3 -msgid "Import CSV file to Odoo" +msgid "How to import data into Odoo" +msgstr "Hoe gegevens importeren in Odoo" + +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "Hoe starten" + +#: ../../general/base_import/import_faq.rst:7 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" msgstr "" -#: ../../general/base_import/import_faq.rst:8 -msgid "Frequently Asked Questions" -msgstr "Vaak gestelde vragen (FAQ)" - -#: ../../general/base_import/import_faq.rst:12 -msgid "Need to import data from an other application?" -msgstr "Wilt u gegevens uit een ander programma importeren?" - -#: ../../general/base_import/import_faq.rst:14 -msgid "" -"In order to re-create relationships between different records, you should " -"use the unique identifier from the original application and map it to the " -"**ID** (External ID) column in Odoo. When you import an other record that " -"links to the first one, use **XXX/ID** (XXX/External ID) to the original " -"unique identifier." +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." msgstr "" #: ../../general/base_import/import_faq.rst:16 msgid "" -"The **ID** (External ID) will also be used to update the original import if " -"you need to re-import modified data later, it's thus good practice to " -"specify it whenever possible." +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." msgstr "" -#: ../../general/base_import/import_faq.rst:21 -msgid "I cannot find the field I want to map my column to?" -msgstr "" +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" +msgstr "Hoe de template wijzigen" -#: ../../general/base_import/import_faq.rst:23 -msgid "" -"Odoo try to find with some heuristic, based on the first ten lines of the " -"files, the type of field for each columns inside your file. For example if " -"you have a column only containing numbers, only the fields that are of type " -"integer will be displayed for you to choose from. While this behaviour might" -" be good and easy for most cases scenarios, it is also possible that it goes" -" wrong sometimes or that you want to map your column to a field that is not " -"proposed by default." +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" #: ../../general/base_import/import_faq.rst:25 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:31 msgid "" -"If that happens, you just have to check the **Show all fields for completion" -" (advanced)** option, you will then be able to choose from the complete list" -" of fields for each columns." +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." msgstr "" -#: ../../general/base_import/import_faq.rst:30 +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "Hoe importeren vanuit een andere applicatie" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "Ik kan het veld niet vinden dat ik wens te koppelen aan mijn kolom" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 msgid "Where can I change the date import format?" -msgstr "" +msgstr "Waar kan ik het datum invoerformaat wijzigen?" -#: ../../general/base_import/import_faq.rst:32 +#: ../../general/base_import/import_faq.rst:81 msgid "" "Odoo can automatically detect if a column is a date and it will try to guess" " the date format from a set of most used date format. While this process can" @@ -151,7 +286,7 @@ msgid "" " day and which one is the month in a date like '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:34 +#: ../../general/base_import/import_faq.rst:83 msgid "" "To view which date format Odoo has found from your file you can check the " "**Date Format** that is shown when clicking on **Options** under the file " @@ -159,7 +294,7 @@ msgid "" " the *ISO 8601* to define the format." msgstr "" -#: ../../general/base_import/import_faq.rst:37 +#: ../../general/base_import/import_faq.rst:86 msgid "" "If you are importing an excel (.xls, .xlsx) file, you can use date cells to " "store dates as the display of dates in excel is different from the way it is" @@ -167,11 +302,11 @@ msgid "" "whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:42 +#: ../../general/base_import/import_faq.rst:91 msgid "Can I import numbers with currency sign (e.g.: $32.00)?" -msgstr "" +msgstr "Kan ik nummers importeren met een valuta-teken (bvb.: $ 32,00)?" -#: ../../general/base_import/import_faq.rst:44 +#: ../../general/base_import/import_faq.rst:93 msgid "" "Yes, we fully support numbers with parenthesis to represent negative sign as" " well as numbers with currency sign attached to them. Odoo also " @@ -181,56 +316,58 @@ msgid "" "crash." msgstr "" -#: ../../general/base_import/import_faq.rst:46 +#: ../../general/base_import/import_faq.rst:95 msgid "" "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:48 +#: ../../general/base_import/import_faq.rst:97 msgid "32.000,00" -msgstr "" +msgstr "32.000,00" -#: ../../general/base_import/import_faq.rst:49 +#: ../../general/base_import/import_faq.rst:98 msgid "32000,00" -msgstr "" +msgstr "32000,00" -#: ../../general/base_import/import_faq.rst:50 +#: ../../general/base_import/import_faq.rst:99 msgid "32,000.00" -msgstr "" +msgstr "32,000.00" -#: ../../general/base_import/import_faq.rst:51 +#: ../../general/base_import/import_faq.rst:100 msgid "-32000.00" -msgstr "" +msgstr "-32000.00" -#: ../../general/base_import/import_faq.rst:52 +#: ../../general/base_import/import_faq.rst:101 msgid "(32000.00)" -msgstr "" +msgstr "(32000.00)" -#: ../../general/base_import/import_faq.rst:53 +#: ../../general/base_import/import_faq.rst:102 msgid "$ 32.000,00" -msgstr "" +msgstr "€ 32.000,00" -#: ../../general/base_import/import_faq.rst:54 +#: ../../general/base_import/import_faq.rst:103 msgid "(32000.00 €)" -msgstr "" +msgstr "(32000.00 €)" -#: ../../general/base_import/import_faq.rst:56 +#: ../../general/base_import/import_faq.rst:105 msgid "Example that will not work:" -msgstr "" +msgstr "Voorbeeld dat niet werkt:" -#: ../../general/base_import/import_faq.rst:58 +#: ../../general/base_import/import_faq.rst:107 msgid "ABC 32.000,00" -msgstr "" +msgstr "ABC 32.000,00" -#: ../../general/base_import/import_faq.rst:59 +#: ../../general/base_import/import_faq.rst:108 msgid "$ (32.000,00)" -msgstr "" +msgstr "€ (32.000,00)" -#: ../../general/base_import/import_faq.rst:64 +#: ../../general/base_import/import_faq.rst:113 msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" +"Wat kan ik doen als de tabel Importeervoorbeeld niet correct wordt " +"weergegeven?" -#: ../../general/base_import/import_faq.rst:66 +#: ../../general/base_import/import_faq.rst:115 msgid "" "By default the Import preview is set on commas as field separators and " "quotation marks as text delimiters. If your csv file does not have these " @@ -238,20 +375,20 @@ msgid "" " CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:68 +#: ../../general/base_import/import_faq.rst:117 msgid "" "Note that if your CSV file has a tabulation as separator, Odoo will not " "detect the separations. You will need to change the file format options in " "your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:73 +#: ../../general/base_import/import_faq.rst:122 msgid "" "How can I change the CSV file format options when saving in my spreadsheet " "application?" msgstr "" -#: ../../general/base_import/import_faq.rst:75 +#: ../../general/base_import/import_faq.rst:124 msgid "" "If you edit and save CSV files in speadsheet applications, your computer's " "regional settings will be applied for the separator and delimiter. We " @@ -260,17 +397,17 @@ msgid "" "filter settings' > Save)." msgstr "" -#: ../../general/base_import/import_faq.rst:77 +#: ../../general/base_import/import_faq.rst:126 msgid "" "Microsoft Excel will allow you to modify only the encoding when saving (in " "'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." msgstr "" -#: ../../general/base_import/import_faq.rst:82 +#: ../../general/base_import/import_faq.rst:131 msgid "What's the difference between Database ID and External ID?" -msgstr "" +msgstr "Wat is het verschil tussen Database ID en Extern ID?" -#: ../../general/base_import/import_faq.rst:84 +#: ../../general/base_import/import_faq.rst:133 msgid "" "Some fields define a relationship with another object. For example, the " "country of a contact is a link to a record of the 'Country' object. When you" @@ -280,58 +417,60 @@ msgid "" "import." msgstr "" -#: ../../general/base_import/import_faq.rst:86 +#: ../../general/base_import/import_faq.rst:135 msgid "" "For example, to reference the country of a contact, Odoo proposes you 3 " "different fields to import:" msgstr "" +"Bijvoorbeeld, om te verwijzen naar het land van een contactpersoon, stelt " +"Odoo u 3 verschillende en importeerbare velden voor:" -#: ../../general/base_import/import_faq.rst:88 +#: ../../general/base_import/import_faq.rst:137 msgid "Country: the name or code of the country" msgstr "Land: de naam of code van het land" -#: ../../general/base_import/import_faq.rst:89 +#: ../../general/base_import/import_faq.rst:138 msgid "" "Country/Database ID: the unique Odoo ID for a record, defined by the ID " "postgresql column" msgstr "" -#: ../../general/base_import/import_faq.rst:90 +#: ../../general/base_import/import_faq.rst:139 msgid "" "Country/External ID: the ID of this record referenced in another application" " (or the .XML file that imported it)" msgstr "" -#: ../../general/base_import/import_faq.rst:92 +#: ../../general/base_import/import_faq.rst:141 msgid "For the country Belgium, you can use one of these 3 ways to import:" -msgstr "" +msgstr "Het land België kunt op één van deze drie manieren importeren:" -#: ../../general/base_import/import_faq.rst:94 +#: ../../general/base_import/import_faq.rst:143 msgid "Country: Belgium" msgstr "Land: België" -#: ../../general/base_import/import_faq.rst:95 +#: ../../general/base_import/import_faq.rst:144 msgid "Country/Database ID: 21" -msgstr "" +msgstr "Land/Database ID: 21" -#: ../../general/base_import/import_faq.rst:96 +#: ../../general/base_import/import_faq.rst:145 msgid "Country/External ID: base.be" msgstr "Land/Externe ID: base.be" -#: ../../general/base_import/import_faq.rst:98 +#: ../../general/base_import/import_faq.rst:147 msgid "" "According to your need, you should use one of these 3 ways to reference " "records in relations. Here is when you should use one or the other, " "according to your need:" msgstr "" -#: ../../general/base_import/import_faq.rst:100 +#: ../../general/base_import/import_faq.rst:149 msgid "" "Use Country: This is the easiest way when your data come from CSV files that" " have been created manually." msgstr "" -#: ../../general/base_import/import_faq.rst:101 +#: ../../general/base_import/import_faq.rst:150 msgid "" "Use Country/Database ID: You should rarely use this notation. It's mostly " "used by developers as it's main advantage is to never have conflicts (you " @@ -339,13 +478,13 @@ msgid "" "Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:102 +#: ../../general/base_import/import_faq.rst:151 msgid "" "Use Country/External ID: Use External ID when you import data from a third " "party application." msgstr "" -#: ../../general/base_import/import_faq.rst:104 +#: ../../general/base_import/import_faq.rst:153 msgid "" "When you use External IDs, you can import CSV files with the \"External ID\"" " column to define the External ID of each record you import. Then, you will " @@ -354,23 +493,23 @@ msgid "" "Products and their Categories." msgstr "" -#: ../../general/base_import/import_faq.rst:106 +#: ../../general/base_import/import_faq.rst:155 msgid "" "`CSV file for categories " "<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:108 +#: ../../general/base_import/import_faq.rst:157 msgid "" "`CSV file for Products " "<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:112 +#: ../../general/base_import/import_faq.rst:161 msgid "What can I do if I have multiple matches for a field?" msgstr "Wat moet ik doen als ik verschillende matches heb voor een veld?" -#: ../../general/base_import/import_faq.rst:114 +#: ../../general/base_import/import_faq.rst:163 msgid "" "If for example you have two product categories with the child name " "\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " @@ -381,20 +520,20 @@ msgid "" "the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:116 +#: ../../general/base_import/import_faq.rst:165 msgid "" "However if you do not wish to change your configuration of product " "categories, we recommend you use make use of the external ID for this field " "'Category'." msgstr "" -#: ../../general/base_import/import_faq.rst:121 +#: ../../general/base_import/import_faq.rst:170 msgid "" "How can I import a many2many relationship field (e.g. a customer that has " "multiple tags)?" msgstr "" -#: ../../general/base_import/import_faq.rst:123 +#: ../../general/base_import/import_faq.rst:172 msgid "" "The tags should be separated by a comma without any spacing. For example, if" " you want your customer to be linked to both tags 'Manufacturer' and " @@ -402,19 +541,19 @@ msgid "" " of your CSV file." msgstr "" -#: ../../general/base_import/import_faq.rst:125 +#: ../../general/base_import/import_faq.rst:174 msgid "" "`CSV file for Manufacturer, Retailer " "<../../_static/example_files/m2m_customers_tags.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:130 +#: ../../general/base_import/import_faq.rst:179 msgid "" "How can I import a one2many relationship (e.g. several Order Lines of a " "Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:132 +#: ../../general/base_import/import_faq.rst:181 msgid "" "If you want to import sales order having several order lines; for each order" " line, you need to reserve a specific row in the CSV file. The first order " @@ -425,41 +564,41 @@ msgid "" "you can import, based on demo data." msgstr "" -#: ../../general/base_import/import_faq.rst:135 +#: ../../general/base_import/import_faq.rst:184 msgid "" "`File for some Quotations " "<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:137 +#: ../../general/base_import/import_faq.rst:186 msgid "" "The following CSV file shows how to import purchase orders with their " "respective purchase order lines:" msgstr "" -#: ../../general/base_import/import_faq.rst:139 +#: ../../general/base_import/import_faq.rst:188 msgid "" "`Purchase orders with their respective purchase order lines " "<../../_static/example_files/o2m_purchase_order_lines.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:141 +#: ../../general/base_import/import_faq.rst:190 msgid "" "The following CSV file shows how to import customers and their respective " "contacts:" msgstr "" -#: ../../general/base_import/import_faq.rst:143 +#: ../../general/base_import/import_faq.rst:192 msgid "" "`Customers and their respective contacts " "<../../_static/example_files/o2m_customers_contacts.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:148 +#: ../../general/base_import/import_faq.rst:197 msgid "Can I import several times the same record?" msgstr "Kan ik meerdere malen hetzelfde record importeren?" -#: ../../general/base_import/import_faq.rst:150 +#: ../../general/base_import/import_faq.rst:199 msgid "" "If you import a file that contains one of the column \"External ID\" or " "\"Database ID\", records that have already been imported will be modified " @@ -469,17 +608,17 @@ msgid "" "depending if it's new or not." msgstr "" -#: ../../general/base_import/import_faq.rst:152 +#: ../../general/base_import/import_faq.rst:201 msgid "" "This feature allows you to use the Import/Export tool of Odoo to modify a " "batch of records in your favorite spreadsheet application." msgstr "" -#: ../../general/base_import/import_faq.rst:157 +#: ../../general/base_import/import_faq.rst:206 msgid "What happens if I do not provide a value for a specific field?" msgstr "" -#: ../../general/base_import/import_faq.rst:159 +#: ../../general/base_import/import_faq.rst:208 msgid "" "If you do not set all fields in your CSV file, Odoo will assign the default " "value for every non defined fields. But if you set fields with empty values " @@ -487,11 +626,11 @@ msgid "" "assigning the default value." msgstr "" -#: ../../general/base_import/import_faq.rst:164 +#: ../../general/base_import/import_faq.rst:213 msgid "How to export/import different tables from an SQL application to Odoo?" msgstr "" -#: ../../general/base_import/import_faq.rst:166 +#: ../../general/base_import/import_faq.rst:215 msgid "" "If you need to import data from different tables, you will have to recreate " "relations between records belonging to different tables. (e.g. if you import" @@ -499,7 +638,7 @@ msgid "" "person and the company they work for)." msgstr "" -#: ../../general/base_import/import_faq.rst:168 +#: ../../general/base_import/import_faq.rst:217 msgid "" "To manage relations between tables, you can use the \"External ID\" " "facilities of Odoo. The \"External ID\" of a record is the unique identifier" @@ -509,7 +648,7 @@ msgid "" "'company_1', 'person_1' instead of '1')" msgstr "" -#: ../../general/base_import/import_faq.rst:170 +#: ../../general/base_import/import_faq.rst:219 msgid "" "As an example, suppose you have a SQL database with two tables you want to " "import: companies and persons. Each person belong to one company, so you " @@ -519,27 +658,27 @@ msgid "" "PostgreSQL database)" msgstr "" -#: ../../general/base_import/import_faq.rst:172 +#: ../../general/base_import/import_faq.rst:221 msgid "" "We will first export all companies and their \"External ID\". In PSQL, write" " the following command:" msgstr "" -#: ../../general/base_import/import_faq.rst:178 +#: ../../general/base_import/import_faq.rst:227 msgid "This SQL command will create the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:185 +#: ../../general/base_import/import_faq.rst:234 msgid "" "To create the CSV file for persons, linked to companies, we will use the " "following SQL command in PSQL:" msgstr "" -#: ../../general/base_import/import_faq.rst:191 +#: ../../general/base_import/import_faq.rst:240 msgid "It will produce the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:199 +#: ../../general/base_import/import_faq.rst:248 msgid "" "As you can see in this file, Fabien and Laurence are working for the Bigees " "company (company_1) and Eric is working for the Organi company. The relation" @@ -549,7 +688,7 @@ msgid "" " who shared the same ID 1 in the orignial database)." msgstr "" -#: ../../general/base_import/import_faq.rst:201 +#: ../../general/base_import/import_faq.rst:250 msgid "" "The two files produced are ready to be imported in Odoo without any " "modifications. After having imported these two CSV files, you will have 4 " @@ -573,7 +712,7 @@ msgstr "" #: ../../general/odoo_basics/add_user.rst:9 msgid "Add individual users" -msgstr "" +msgstr "Voeg individuele gebruikers toe" #: ../../general/odoo_basics/add_user.rst:11 msgid "" @@ -624,7 +763,7 @@ msgstr "" #: ../../general/odoo_basics/choose_language.rst:3 msgid "Manage Odoo in your own language" -msgstr "" +msgstr "Beheer Odoo in uw eigen taal" #: ../../general/odoo_basics/choose_language.rst:5 msgid "" @@ -634,7 +773,7 @@ msgstr "" #: ../../general/odoo_basics/choose_language.rst:9 msgid "Load your desired language" -msgstr "" +msgstr "Laad uw gewenste taal" #: ../../general/odoo_basics/choose_language.rst:11 msgid "" @@ -677,7 +816,7 @@ msgstr "" #: ../../general/odoo_basics/choose_language.rst:45 msgid "Change another user's language" -msgstr "" +msgstr "Wijzig een andere gebruiker zijn taal" #: ../../general/odoo_basics/choose_language.rst:47 msgid "" @@ -697,4 +836,4 @@ msgstr "" #: ../../general/odoo_basics/choose_language.rst:61 msgid ":doc:`../../website/publish/translate`" -msgstr "" +msgstr ":doc:`../../website/publish/translate`" diff --git a/locale/nl/LC_MESSAGES/getting_started.po b/locale/nl/LC_MESSAGES/getting_started.po index 6492aef72..713604601 100644 --- a/locale/nl/LC_MESSAGES/getting_started.po +++ b/locale/nl/LC_MESSAGES/getting_started.po @@ -20,7 +20,7 @@ msgstr "" #: ../../getting_started/documentation.rst:5 msgid "Odoo Online Implementation" -msgstr "" +msgstr "Odoo online implementatie" #: ../../getting_started/documentation.rst:7 msgid "" @@ -733,6 +733,8 @@ msgid "" "You can find more information on how to manage your databases :ref:`here " "`." msgstr "" +"U kan :ref:`here ` meer informatie vinden over " +"hoe uw database te beheren." #: ../../getting_started/documentation.rst:375 msgid "Customer Success" diff --git a/locale/nl/LC_MESSAGES/inventory.po b/locale/nl/LC_MESSAGES/inventory.po index 452d29738..f11741710 100644 --- a/locale/nl/LC_MESSAGES/inventory.po +++ b/locale/nl/LC_MESSAGES/inventory.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Xavier Symons , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" @@ -772,6 +772,10 @@ msgid "" "values for a given product." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "Actief" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "If the active field is set to False, it will allow you to hide the " @@ -780,10 +784,18 @@ msgstr "" "Als het actief veld uit staat, kunt u de minimale voorraadregel verbergen " "zonder deze te verwijderen." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "Maateenheid product" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Default Unit of Measure used for all stock operation." msgstr "Standaard maateenheid voor alle voorraadhandelingen." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "Verwervingsgroep" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Moves created through this orderpoint will be put in this procurement group." @@ -795,6 +807,10 @@ msgstr "" "mutaties, gegenereerd door de verwervingsregel gegroepeerd in één grote " "levering." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "Minimale hoeveelheid" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity specified for this field," @@ -805,6 +821,10 @@ msgstr "" "gespecificeerd in dit veld, zal Odoo een verwervingsopdracht genereren om de" " verwachte voorraad aan te vullen tot de maximale hoeveelheid." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "Maximale hoeveelheid" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity, Odoo generates a " @@ -815,6 +835,10 @@ msgstr "" "gespecificeerd in dit veld, zal Odoo een verwervingsopdracht genereren om de" " verwachte voorraad aan te vullen tot de maximale hoeveelheid." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "Veelvoud" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "The procurement quantity will be rounded up to this multiple. If it is 0, " @@ -823,6 +847,10 @@ msgstr "" "De verwerving hoeveelheid zal worden afgerond op deze veelvoud. Bij 0 wordt " "de exacte hoeveelheid gebruikt." +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "Doorlooptijd" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Number of days after the orderpoint is triggered to receive the products or " diff --git a/locale/nl/LC_MESSAGES/legal.po b/locale/nl/LC_MESSAGES/legal.po deleted file mode 100644 index 6a7a5a19d..000000000 --- a/locale/nl/LC_MESSAGES/legal.po +++ /dev/null @@ -1,2021 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Cas Vissers , 2017\n" -"Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: nl\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../legal.rst:5 -msgid "Legal" -msgstr "" - -#: ../../legal.rst:15 ../../legal/licenses.rst:5 -#: ../../legal/licenses/licenses.rst:6 -msgid "Licenses" -msgstr "" - -#: ../../legal.rst:17 -msgid ":ref:`licenses`" -msgstr "" - -#: ../../legal.rst:20 ../../legal/terms.rst:5 -msgid "Terms and Conditions" -msgstr "Algemene verkoopvoorwaarden" - -#: ../../legal.rst:38 -msgid ":ref:`enterprise_agreement` |nbsp| |nbsp| |download_enterprise|" -msgstr "" - -#: ../../legal.rst:40 -msgid ":ref:`enterprise_agreement_fr` |nbsp| |nbsp| |download_enterprise_fr|" -msgstr "" - -#: ../../legal.rst:47 ../../legal/others.rst:5 -msgid "Other legal references" -msgstr "" - -#: ../../legal.rst:49 -msgid "" -"`Odoo Online Service Level Agreement `_" -msgstr "" - -#: ../../legal.rst:50 -msgid "" -"`Odoo Online Acceptable Use Policy `_" -msgstr "" - -#: ../../legal.rst:51 -msgid ":ref:`cla`" -msgstr "" - -#: ../../legal/licenses/licenses.rst:11 -msgid "Odoo 10 Community Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:13 -msgid "" -"Odoo 10 Community Edition is licensed under `LGPL version 3 " -"`_ (also known as LGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/licenses/licenses.rst:22 -msgid "Odoo 10 Enterprise Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:24 -msgid "" -"Odoo 10 Enterprise Edition is licensed under the Odoo Enterprise Edition " -"License v1.0, defined as follows:" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:1 -#: ../../legal/terms/i18n/enterprise_fr.rst:487 -msgid "Odoo Enterprise Edition License v1.0" -msgstr "Odoo enterprise licentie editie v1.0" - -#: ../../legal/licenses/enterprise_license.txt:3 -msgid "" -"This software and associated files (the \"Software\") can only be used " -"(executed, modified, executed after modifications) with a valid Odoo " -"Enterprise Subscription for the correct number of users." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:7 -msgid "" -"With a valid Partnership Agreement with Odoo S.A., the above permissions are" -" also granted, as long as the usage is limited to a testing or development " -"environment." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:11 -msgid "" -"You may develop Odoo modules based on the Software and distribute them under" -" the license of your choice, provided that it is compatible with the terms " -"of the Odoo Enterprise Edition License (For example: LGPL, MIT, or " -"proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:16 -msgid "" -"You may use Odoo modules published under any license along with the " -"Software, provided that their license is compatible with the terms of the " -"Odoo Enterprise License (Including, but not limited to, any module published" -" on the Odoo Apps Store on odoo.com/apps)" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:21 -#: ../../legal/licenses/licenses.rst:69 -msgid "" -"It is forbidden to publish, distribute, sublicense, or sell copies of the " -"Software or modified copies of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:24 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:27 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE" -" AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM," -" OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN " -"THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:43 -msgid "Odoo Apps" -msgstr "" - -#: ../../legal/licenses/licenses.rst:45 -msgid "" -"Unless otherwise stated, Odoo Apps by Odoo SA (including the website themes)" -" are published under the Odoo Proprietary License v1.0, defined as follows" -msgstr "" - -#: ../../legal/licenses/licenses.rst:54 -msgid "Odoo Proprietary License v1.0" -msgstr "Odoo Proprietary Licentie v1.0" - -#: ../../legal/licenses/licenses.rst:56 -msgid "" -"This software and associated files (the \"Software\") may only be used " -"(executed, modified, executed after modifications) if you have purchased a " -"valid license from the authors, typically via Odoo Apps, or if you have " -"received a written agreement from the authors of the Software (see the " -"COPYRIGHT file)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:62 -msgid "" -"You may develop Odoo modules that use the Software as a library (typically " -"by depending on it, importing it and using its resources), but without " -"copying any source code or material from the Software. You may distribute " -"those modules under the license of your choice, provided that this license " -"is compatible with the terms of the Odoo Proprietary License (For example: " -"LGPL, MIT, or proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:72 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/licenses.rst:75 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " -"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " -"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS" -" IN THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:91 -msgid "Odoo 9" -msgstr "" - -#: ../../legal/licenses/licenses.rst:93 -msgid "" -"The licenses for both editions of Odoo 9 were respectively the same as for " -":ref:`odoo_community_license` and :ref:`odoo_enterprise_license`." -msgstr "" - -#: ../../legal/licenses/licenses.rst:100 -msgid "Odoo 8" -msgstr "" - -#: ../../legal/licenses/licenses.rst:102 -msgid "" -"Odoo 8 is licensed under `AGPL version 3 " -"`_ (also known as AGPLv3). " -"See also the `GPL FAQ `_ and " -"the `compatibility matrix `_." -msgstr "" - -#: ../../legal/others/cla.rst:5 -msgid "Contributor License Agreement" -msgstr "" - -#: ../../legal/others/cla.rst:7 -msgid "" -"In order to contribute to any of the Odoo projects, companies and " -"individuals have to sign the Odoo Contributor License Agreement (CLA)." -msgstr "" - -#: ../../legal/others/cla.rst:10 -msgid "" -"More information about this requirement, the procedure to sign the " -"agreement, and a FAQ can be found on our `GitHub project page " -"`_." -msgstr "" - -#: ../../legal/others/privacy.rst:5 -msgid "Privacy Policy" -msgstr "" - -#: ../../legal/others/privacy.rst:7 -msgid "" -"Temporary version at ``__ " -"(needs cleanup)" -msgstr "" - -#: ../../legal/terms/enterprise.rst:6 -msgid "Odoo Enterprise Subscription Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:8 -msgid "Version 5b - Last revision: June 30, 2016." -msgstr "" - -#: ../../legal/terms/enterprise.rst:10 -msgid "" -"By subscribing to the Odoo Enterprise services (the \"Services\") provided " -"by Odoo SA and its affiliates (collectively, \"Odoo SA\") in relation with " -"Odoo Enterprise Edition or Odoo Community Edition (the \"Software\"), you " -"(the \"Customer\") are agreeing to be bound by the following terms and " -"conditions (the \"Agreement\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:18 -msgid "1 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:20 -msgid "" -"The duration of this Agreement (the “Term”) shall be minimally one year and " -"as specified in writing at the signature of this Agreement, beginning on the" -" date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term by registered mail to the other party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:28 -msgid "2 Definitions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:34 -msgid "User" -msgstr "Gebruiker" - -#: ../../legal/terms/enterprise.rst:31 -msgid "" -"Any active user account with access to the Software in creation and/or " -"edition mode. Deactivated user accounts and accounts used by external people" -" (or systems) who only have limited access to the Software through the " -"portal facilities (known as \"portal Users\") are not counted as Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:42 -#: ../../legal/terms/i18n/enterprise_fr.rst:55 -msgid "Bug" -msgstr "" - -#: ../../legal/terms/enterprise.rst:37 -msgid "" -"Is considered a Bug any failure of the Software that results in a complete " -"stop, error traceback or security breach, and is not directly caused by a " -"defective installation or configuration. Non-compliance with specifications " -"or requirements will be considered as Bugs at the discretion of Odoo SA " -"(typically, when the Software does not produce the results or performance it" -" was designed to produce, or when a country-specific feature does not meet " -"legal accounting requirements anymore)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:51 -msgid "Covered Versions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:45 -msgid "" -"All Services provided under this Agreement are applicable only to the " -"Covered Versions of the Software, which include the 3 (three) most recently " -"released major versions." -msgstr "" - -#: ../../legal/terms/enterprise.rst:48 -msgid "" -"To be covered by the current Agreement, Customer’s installations have to run" -" the most recent Covered Version at the time of this Agreement’s signature. " -"When this is not the case, additional costs are applicable, as described in " -":ref:`charges`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:56 ../../legal/terms/partnership.rst:42 -msgid "3 Access to Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/enterprise.rst:58 -msgid "" -"For the duration of this Agreement, Odoo SA gives the Customer a non-" -"exclusive, non-transferable license to use (execute, modify, execute after " -"modification) the Odoo Enterprise Edition software, under the terms set " -"forth in :ref:`appendix_a`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:62 -msgid "" -"The Customer agrees to take all necessary measures to guarantee the " -"unmodified execution of the part of the Software that verifies the validity " -"of the Odoo Enterprise Edition usage and collects statistics for that " -"purpose, including but not limited to the running of an instance and the " -"number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:67 -msgid "" -"Odoo SA commits not to disclose individual or named figures to third parties" -" without the consent of the Customer, and to deal with all collected data in" -" compliance with its official Privacy Policy, as published on `Odoo SA's " -"website `_." -msgstr "" - -#: ../../legal/terms/enterprise.rst:71 -msgid "" -"Upon expiration or termination of this Agreement, this license is revoked " -"immediately and the Customer agrees to stop using the Odoo Enterprise " -"Edition software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:74 -msgid "" -"Should the Customer breach the terms of this section, the Customer agrees to" -" pay Odoo SA an extra fee equal to 300% of the applicable list price for the" -" actual number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:81 -msgid "4 Included Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:84 -msgid "4.1 Bug Fixing Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:86 -msgid "" -"For the duration of this Agreement, Odoo SA commits to making all reasonable" -" efforts to remedy any Bug of the Software submitted by the Customer through" -" the appropriate channel (typically, Odoo SA's service desk email address or" -" website form), and to start handling such Customer submissions within 2 " -"business days." -msgstr "" - -#: ../../legal/terms/enterprise.rst:91 -msgid "" -"The Customer understands that Bugs caused by a modification or extension " -"that is not part of the official Software will not be covered by this " -"service." -msgstr "" - -#: ../../legal/terms/enterprise.rst:94 -msgid "" -"As soon as the Bug is fixed an appropriate remedy will be communicated to " -"the Customer. If the bug has been addressed in a more recent revision of the" -" Covered Version of the Software used by the Customer, the Customer agrees " -"to update its systems to that revision in order to obtain the correction. " -"The Customer will not be asked to upgrade to a more recent Covered Version " -"of the Software as a remedy to a Bug." -msgstr "" - -#: ../../legal/terms/enterprise.rst:100 -msgid "" -"When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the " -"Bug in all more recent Covered Versions of the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:103 -msgid "" -"Both parties acknowledge that as specified in the license of the Software " -"and in the :ref:`liability` section of this Agreement, Odoo SA cannot be " -"held liable for Bugs in the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:108 -msgid "4.2 Security Advisories Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:110 -msgid "" -"For the duration of this Agreement, Odoo SA commits to sending a \"Security " -"Advisory\" to the Customer for any security Bug that are discovered in the " -"Covered Versions of the Software, at least 2 weeks before making the " -"Security Advisory public, unless the Bug has already been disclosed publicly" -" by a third party. Security Advisories include a complete description of the" -" Bug, its cause, its possible impacts on the Customer's systems, and the " -"corresponding remedy for each Covered Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:117 -msgid "" -"The Customer understands that the Bug and the information in the Security " -"Advisory must be treated are Confidential Information as described in " -":ref:`confidentiality` during the embargo period prior to the public " -"disclosure." -msgstr "" - -#: ../../legal/terms/enterprise.rst:124 -msgid "4.3 Upgrade Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:129 -msgid "Upgrade Service for the Software" -msgstr "" - -#: ../../legal/terms/enterprise.rst:131 -msgid "" -"For the duration of this Agreement, the Customer can submit upgrade requests" -" through the appropriate channel (typically Odoo SA's upgrade service " -"website), in order to convert a database of the Software from one Covered " -"Version of the Software to a more recent Covered Version (the \"Target " -"Version\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:135 -msgid "" -"Upgrade requests must include a complete backup copy of the Customer's " -"database and the associated data (typically obtained from the Backup menu of" -" the Software). Where necessary for data security or regulation reasons, the" -" Upgrade Service includes an optional tool to anonymize identifiable data " -"inside a database before submitting the upgrade request, and a tool to " -"restore the anonymized data after the upgrade." -msgstr "" - -#: ../../legal/terms/enterprise.rst:141 -msgid "" -"This service provided through an automated platform in order to allow the " -"Customer to perform unattended upgrades once a previous version of the " -"Customer's database has been successfully upgraded for a Covered Version. " -"The Customer may submit successive upgrade requests for a database, and " -"agrees to submit at least 1 upgrade request for testing purposes before " -"submitting the final upgrade request." -msgstr "" - -#: ../../legal/terms/enterprise.rst:147 -msgid "" -"The Upgrade Service is limited to the technical conversion and adaptation of" -" the Customer's database to make it compatible with the Target Version, and " -"the correction of any Bug directly caused by the upgrade operation and not " -"normally occurring in the Target Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:151 -msgid "" -"It is the sole responsibility of the Customer to verify and validate the " -"upgraded database in order to detect Bugs, to analyze the impact of changes " -"and new features implemented in the Target Version, and to convert and adapt" -" for the Target Version any third-party extensions of the Software that were" -" installed in the database before the upgrade (except where applicable as " -"foreseen in section :ref:`upgrade_extra`). The Customer may submit multiple " -"upgrade requests for a database, until an acceptable result is achieved." -msgstr "" - -#: ../../legal/terms/enterprise.rst:162 -msgid "Upgrade Service for third-party extensions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:164 -msgid "" -"For the duration of this Agreement, the Customer may request optional " -"upgrade services for third-party extension modules of the Software, in " -"addition to the regular Upgrade Services. This optional service is subject " -"to additional fees (as described in charges_) and includes the technical " -"adaptation of third-party modules installed in the Customer's database and " -"their corresponding data in order to be compatible with the Target Version. " -"The Customer will receive an upgraded version of all installed third-party " -"modules along with the upgraded database." -msgstr "" - -#: ../../legal/terms/enterprise.rst:174 -msgid "5 Charges and Fees" -msgstr "" - -#: ../../legal/terms/enterprise.rst:179 -msgid "5.1 Standard charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:181 -msgid "" -"The standard charges for the Odoo Enterprise subscription, the Bug Fixing " -"Service, Security Advisories Service and the Upgrade Service are based on " -"the number of Users and the Software version used by the Customer, and " -"specified in writing at the signature of the Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:185 -msgid "" -"When during the Term, the Customer has more Users than specified at the time" -" of signature of this Agreement, the Customer agrees to pay an extra fee " -"equivalent to the applicable list price (at the beginning of the Term) for " -"the additional Users, for the remainder of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:189 -msgid "" -"If at the time of the signature of this Agreement, the Customer uses a " -"Covered Version that is not the most recent one, the standard charges will " -"be increased by 50% for the duration of the first Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:196 -msgid "5.2 Renewal charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:198 -msgid "" -"Upon renewal as covered in section :ref:`term`, if the per-User charges " -"applied during the previous Term are lower than the most current applicable " -"per-User list price, the per-User charges will increase by up to 7%, unless " -"Odoo SA provides written notice of a new price to the Customer at least 60 " -"days prior to the end of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:207 -msgid "5.3 Charges for Upgrade Services of third-party modules" -msgstr "" - -#: ../../legal/terms/enterprise.rst:211 -msgid "" -"The additional charge for the Upgrade Service for third-party modules is EUR" -" (€) 1000.00 (one thousand euros) per 1000 Lines of Code in the third-party " -"modules, rounded up to the next thousand lines. Lines of Code include all " -"text lines in the source code of those modules, regardless of the " -"programming language (Python, Javascript, etc.) or data format (XML, CSV, " -"etc.), excluding blank lines and comment lines." -msgstr "" - -#: ../../legal/terms/enterprise.rst:217 -msgid "" -"Odoo SA reserves the right to reject an upgrade request for third-party " -"modules under the above conditions if the quality of the source code of " -"those modules is too low, or if these modules constitute an interface with " -"third-party software or systems. The upgrade of such modules will subject to" -" a separate offer, outside of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:225 -msgid "5.4 Taxes" -msgstr "" - -#: ../../legal/terms/enterprise.rst:229 -msgid "" -"All fees and charges are exclusive of all applicable federal, provincial, " -"state, local or other governmental taxes, fees or charges (collectively, " -"\"Taxes\"). The Customer is responsible for paying all Taxes associated with" -" purchases made by the Customer under this Agreement, except when Odoo SA is" -" legally obliged to pay or collect Taxes for which the Customer is " -"responsible." -msgstr "" - -#: ../../legal/terms/enterprise.rst:238 -msgid "6 Conditions of Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:241 -msgid "6.1 Customer Obligations" -msgstr "" - -#: ../../legal/terms/enterprise.rst:245 -msgid "The Customer agrees to:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:247 -msgid "" -"pay Odoo SA any applicable charges for the Services of the present " -"Agreement, in accordance with the payment conditions specified in the " -"corresponding invoice ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:249 -msgid "" -"immediately notify Odoo SA when the actual number of Users exceeds the " -"number of Users specified at the signature of the Agreement, and in this " -"event, pay the applicable additional fee as described in section " -":ref:`charges_standard`;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:252 -msgid "" -"take all measures necessary to guarantee the unmodified execution of the " -"part of the Software that verifies the validity of the Odoo Enterprise " -"Edition usage, as described in :ref:`enterprise_access` ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:255 -msgid "" -"grant Odoo SA the necessary access to verify the validity of the Odoo " -"Enterprise Edition usage upon request (e.g. if the automatic validation is " -"found to be inoperant for the Customer);" -msgstr "" - -#: ../../legal/terms/enterprise.rst:257 -msgid "" -"appoint 1 dedicated Customer contact person for the entire duration of the " -"Agreement;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:258 -msgid "" -"take all reasonable measures to protect Customer’s files and databases and " -"to ensure Customer’s data is safe and secure, acknowledging that Odoo SA " -"cannot be held liable for any data loss;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:265 -msgid "6.2 No Soliciting or Hiring" -msgstr "" - -#: ../../legal/terms/enterprise.rst:267 -msgid "" -"Except where the other party gives its consent in writing, each party, its " -"affiliates and representatives agree not to solicit or offer employment to " -"any employee of the other party who is involved in performing or using the " -"Services under this Agreement, for the duration of the Agreement and for a " -"period of 12 months from the date of termination or expiration of this " -"Agreement. In case of any breach of the conditions of this section that " -"leads to the termination of said employee toward that end, the breaching " -"party agrees to pay to the other party an amount of EUR (€) 30 000.00 " -"(thirty thousand euros)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:279 -msgid "6.3 Publicity" -msgstr "" - -#: ../../legal/terms/enterprise.rst:281 -msgid "" -"Except where notified otherwise in writing, each party grants the other a " -"non-transferable, non-exclusive, royalty free, worldwide license to " -"reproduce and display the other party’s name, logos and trademarks, solely " -"for the purpose of referring to the other party as a customer or supplier, " -"on websites, press releases and other marketing materials." -msgstr "" - -#: ../../legal/terms/enterprise.rst:290 -msgid "6.4 Confidentiality" -msgstr "" - -#: ../../legal/terms/enterprise.rst:298 -msgid "Definition of \"Confidential Information\":" -msgstr "" - -#: ../../legal/terms/enterprise.rst:293 -msgid "" -"All information disclosed by a party (the \"Disclosing Party\") to the other" -" party (the \"Receiving Party\"), whether orally or in writing, that is " -"designated as confidential or that reasonably should be understood to be " -"confidential given the nature of the information and the circumstances of " -"disclosure. In particular any information related to the business, affairs, " -"products, developments, trade secrets, know-how, personnel, customers and " -"suppliers of either party should be regarded as confidential." -msgstr "" - -#: ../../legal/terms/enterprise.rst:300 -msgid "" -"For all Confidential Information received during the Term of this Agreement," -" the Receiving Party will use the same degree of care that it uses to " -"protect the confidentiality of its own similar Confidential Information, but" -" not less than reasonable care." -msgstr "" - -#: ../../legal/terms/enterprise.rst:304 -msgid "" -"The Receiving Party may disclose Confidential Information of the Disclosing " -"Party to the extent compelled by law to do so, provided the Receiving Party " -"gives the Disclosing Party prior notice of the compelled disclosure, to the " -"extent permitted by law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:311 -msgid "6.5 Termination" -msgstr "" - -#: ../../legal/terms/enterprise.rst:313 -msgid "" -"In the event that either Party fails to fulfill any of its obligations " -"arising herein, and if such breach has not been remedied within 30 calendar " -"days from the written notice of such breach, this Agreement may be " -"terminated immediately by the non-breaching Party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:317 -msgid "" -"Further, Odoo SA may terminate the Agreement immediately in the event the " -"Customer fails to pay the applicable fees for the Services within the due " -"date specified on the corresponding invoice." -msgstr "" - -#: ../../legal/terms/enterprise.rst:324 -msgid "Surviving Provisions:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:321 -msgid "" -"The sections \":ref:`confidentiality`”, “:ref:`disclaimers`”, " -"“:ref:`liability`”, and “:ref:`general_provisions`” will survive any " -"termination or expiration of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:329 -msgid "7 Warranties, Disclaimers, Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:334 -msgid "7.1 Warranties" -msgstr "" - -#: ../../legal/terms/enterprise.rst:338 -msgid "" -"For the duration of this Agreement, Odoo SA commits to using commercially " -"reasonable efforts to execute the Services in accordance with the generally " -"accepted industry standards provided that:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:341 -msgid "" -"the Customer’s computing systems are in good operational order and the " -"Software is installed in a suitable operating environment;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:343 -msgid "" -"the Customer provides adequate troubleshooting information and access so " -"that Odoo SA can identify, reproduce and address problems;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:345 -msgid "all amounts due to Odoo SA have been paid." -msgstr "" - -#: ../../legal/terms/enterprise.rst:347 -msgid "" -"The Customer's sole and exclusive remedy and Odoo SA's only obligation for " -"any breach of this warranty is for Odoo SA to resume the execution of the " -"Services at no additional charge." -msgstr "" - -#: ../../legal/terms/enterprise.rst:353 -msgid "7.2 Disclaimers" -msgstr "" - -#: ../../legal/terms/enterprise.rst:357 -msgid "" -"Except as expressly provided herein, neither party makes any warranty of any" -" kind, whether express, implied, statutory or otherwise, and each party " -"specifically disclaims all implied warranties, including any implied " -"warranty of merchantability, fitness for a particular purpose or non-" -"infringement, to the maximum extent permitted by applicable law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:362 -msgid "" -"Odoo SA does not warrant that the Software complies with any local or " -"international law or regulations." -msgstr "" - -#: ../../legal/terms/enterprise.rst:367 -msgid "7.3 Limitation of Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:369 -msgid "" -"To the maximum extent permitted by law, the aggregate liability of each " -"party together with its affiliates arising out of or related to this " -"Agreement will not exceed 50% of the total amount paid by the Customer under" -" this Agreement during the 12 months immediately preceding the date of the " -"event giving rise to such claim. Multiple claims shall not enlarge this " -"limitation." -msgstr "" - -#: ../../legal/terms/enterprise.rst:374 -msgid "" -"In no event will either party or its affiliates be liable for any indirect, " -"special, exemplary, incidental or consequential damages of any kind, " -"including but not limited to loss of revenue, profits, savings, loss of " -"business or other financial loss, costs of standstill or delay, lost or " -"corrupted data, arising out of or in connection with this Agreement " -"regardless of the form of action, whether in contract, tort (including " -"strict negligence) or any other legal or equitable theory, even if a party " -"or its affiliates have been advised of the possibility of such damages, or " -"if a party or its affiliates' remedy otherwise fails of its essential " -"purpose." -msgstr "" - -#: ../../legal/terms/enterprise.rst:385 -#: ../../legal/terms/i18n/enterprise_fr.rst:418 -msgid "7.4 Force Majeure" -msgstr "" - -#: ../../legal/terms/enterprise.rst:387 -msgid "" -"Neither party shall be liable to the other party for the delay in any " -"performance or failure to render any performance under this Agreement when " -"such failure or delay is caused by governmental regulations, fire, strike, " -"war, flood, accident, epidemic, embargo, appropriation of plant or product " -"in whole or in part by any government or public authority, or any other " -"cause or causes, whether of like or different nature, beyond the reasonable " -"control of such party as long as such cause or causes exist." -msgstr "" - -#: ../../legal/terms/enterprise.rst:398 -msgid "8 General Provisions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:403 -msgid "8.1 Governing Law" -msgstr "" - -#: ../../legal/terms/enterprise.rst:405 -msgid "" -"Both parties agree that the laws of Belgium will apply, should any dispute " -"arise out of or in connection with this Agreement, without regard to choice " -"or conflict of law principles. To the extent that any lawsuit or court " -"proceeding is permitted hereinabove, both parties agree to submit to the " -"sole jurisdiction of the Nivelles (Belgium) court for the purpose of " -"litigating all disputes." -msgstr "" - -#: ../../legal/terms/enterprise.rst:414 -msgid "8.2 Severability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:416 -msgid "" -"In case any one or more of the provisions of this Agreement or any " -"application thereof shall be invalid, illegal or unenforceable in any " -"respect, the validity, legality and enforceability of the remaining " -"provisions of this Agreement and any application thereof shall be in no way " -"thereby affected or impaired. Both parties undertake to replace any invalid," -" illegal or unenforceable provision of this Agreement by a valid provision " -"having the same effects and objectives." -msgstr "" - -#: ../../legal/terms/enterprise.rst:427 -msgid "9 Appendix A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:6 -msgid "Odoo Enterprise Subscription Agreement (FR)" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:9 -msgid "" -"Ceci est une traduction en français du contrat “Odoo Enterprise Subscription" -" Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera " -"sa compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes du contrat “Odoo Enterprise Subscription Agreement” " -"est la :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:15 -msgid "" -"This is a french translation of the \"Odoo Enterprise Subscription " -"Agreement”. This translation is provided in the hope that it will facilitate" -" understanding, but it has no legal value. The only official reference of " -"the terms and conditions of the “Odoo Enterprise Subscription Agreement” is " -"the :ref:`original english version `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:21 -msgid "Version 5b - Dernière modification: 30 juin 2016." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:23 -msgid "" -"En vous abonnant aux services de Odoo Enterprise (les \"Services\") fournis " -"par Odoo SA et ses filiales (collectivement, \"Odoo SA\") en relation avec " -"Odoo Enterprise Edition ou Odoo Community Edition (le \"Logiciel\"), vous " -"(le \"Client\") acceptez d'être lié par les conditions générales suivantes " -"(le \"Contrat\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:31 -msgid "1 Durée du Contrat" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:33 -msgid "" -"La durée du présent contrat (la \"Durée\") doit être au minimum d'un an et " -"telle que spécifiée par écrit à la signature du Contrat, à compter de la " -"date de la signature. Celui-ci est automatiquement reconduit pour une même " -"durée, à moins que l'une des parties n’envoie à l'autre partie un préavis " -"écrit de résiliation, par lettre recommandée, et au moins 30 jours avant la " -"date d'échéance du contrat ." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:41 -msgid "2 Définitions" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:47 -msgid "Utilisateur" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:44 -msgid "" -"Tout compte utilisateur actif donnant accès au Logiciel en mode création " -"et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des " -"personnes ou systèmes extérieur(e)s n'ayant qu'un accès limité au Logiciel " -"via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme " -"Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:50 -msgid "" -"Désigne toute défaillance du Logiciel qui se traduit par un arrêt complet, " -"un message d'erreur avec trace d'exécution, ou une brèche de sécurité, et " -"n'est pas directement causé par un problème d'installation ou une " -"configuration défectueuse. Un non-respect des spécifications ou des besoins " -"sera considéré comme un Bug à la discrétion d'Odoo SA (en général, lorsque " -"le Logiciel ne produit pas les résultats ou la performance pour lesquels il " -"a été conçu, ou lorsqu'une fonctionnalité spécifique à un pays ne répond " -"plus aux exigences comptables légales de ce pays)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:65 -msgid "Versions Couvertes" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:58 -msgid "" -"Tous les Services dans le cadre du présent contrat s'appliquent uniquement " -"aux Versions Couvertes du Logiciel, qui comprennent les trois (3) plus " -"récentes versions majeures." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:61 -msgid "" -"Afin d'être considérées comme couvertes par le Contrat, les installations du" -" client doivent utiliser la Version couverte la plus récente au moment de " -"la signature du Contrat. Dans le cas contraire, des frais supplémentaires " -"sont d'application, tels que décrit dans la section :ref:`charges_fr`" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:70 -msgid "3 Accès à Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:72 -msgid "" -"Pour toute la durée du présent Contrat, Odoo SA octroie au Client une " -"licence non exclusive, non transférable d'utilisation (exécution, " -"modification, exécution après modification) du logiciel Odoo Enterprise " -"Edition, conformément aux conditions énoncées à la section " -":ref:`appendix_a_fr`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:76 -msgid "" -"Le Client accepte de prendre toutes les mesures nécessaires pour garantir " -"l'exécution sans aucune modification de la partie du Logiciel qui vérifie la" -" validité de l'utilisation d'Odoo Enterprise Edition et recueille des " -"statistiques à cet effet, y compris mais sans s'y limiter, l'exécution du " -"Logiciel et le nombre d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:81 -msgid "" -"Odoo SA s'engage à ne pas divulguer à une tierce partie d'informations " -"chiffrées personnelles ou spécifiques sans le consentement du Client, et à " -"traiter toutes les données recueillies en respectant sa politique officielle" -" de confidentialité, telle que publiée sur `le site web d'Odoo SA " -"`_." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:86 -msgid "" -"À l'expiration ou la résiliation de ce Contrat, cette licence est " -"immédiatement révoquée et le Client accepte de cesser toute utilisation du " -"logiciel Odoo Enterprise Edition." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:89 -msgid "" -"Si le Client devait enfreindre les dispositions de la présente section, il " -"accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du " -"tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:97 -msgid "4 Services inclus" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:100 -msgid "4.1 Service de correction de Bugs" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:102 -msgid "" -"Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts " -"raisonnables pour corriger tout Bug du Logiciel qui pourrait être signalé " -"par le Client en suivant la procédure appropriée (généralement par le biais " -"d'un e-mail adressé au service d'assistance d'Odoo SA ou via le formulaire " -"correspondant sur le site web), et de commencer à traiter ces signalements " -"du Client dans un délai de 2 jours ouvrables." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:108 -msgid "" -"Le Client accepte que les Bugs causés par toute modification ou extension " -"qui ne fait pas partie de la version officielle du Logiciel ne seront pas " -"couverts par ce service." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:111 -msgid "" -"Dès que le Bug est remédié, un correctif approprié sera communiqué au " -"Client. Si le Bug a été résolu dans une nouvelle mise à jour de la Version " -"Couverte du Logiciel utilisée par le Client, ce dernier s'engage à " -"actualiser ses systèmes vers la nouvelle mise à jour, afin d'obtenir le " -"correctif. Il ne sera jamais demandé au Client de passer à une Version " -"Couverte plus récente pour obtenir un correctif." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:117 -msgid "" -"Lorsqu'un Bug est corrigé dans une Version Couverte, Odoo SA s'engage à le " -"corriger dans toutes les Versions Couvertes plus récentes du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:120 -msgid "" -"Les deux parties reconnaissent que comme spécifié dans la licence du " -"Logiciel et à la section :ref:`liability_fr` de ce Contrat, Odoo SA ne peut " -"être tenue responsable des Bugs du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:125 -msgid "4.2 Service d'alertes de sécurité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:127 -msgid "" -"Pour la durée du Contrat, Odoo SA s'engage à envoyer une \"alerte de " -"sécurité\"\" au Client pour tout Bug présentant un risque de sécurité qui " -"serait découvert dans les Versions Couvertes du Logiciel, au moins 2 " -"semaines avant de rendre ladite alerte de sécurité publique, et ce à moins " -"que le Bug ait déjà été rendu public par un tiers. Les alertes de sécurité " -"comprennent une description complète du Bug, de sa cause, ses conséquences " -"possibles sur les systèmes du Client, et le correctif correspondant pour " -"chaque Version Couverte." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:134 -msgid "" -"Le Client s'engage à traiter le Bug de sécurité et les informations figurant" -" dans l'alerte de sécurité comme des Informations Confidentielles telles que" -" décrites à la section :ref:`confidentiality_fr` pendant toute la période " -"d'embargo avant la divulgation publique." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:141 -msgid "4.3 Service de migration" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:146 -msgid "Service de migration du Logiciel" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:148 -msgid "" -"Pour la durée du présent Contrat, le Client peut soumettre des demandes de " -"migration en suivant les procédures appropriées (généralement, via le site " -"du service de migration d'Odoo SA), afin de convertir une base de données du" -" Logiciel d'une Version Couverte du Logiciel à une Version Couverte plus " -"récente (la \"Version Cible\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:153 -msgid "" -"Les demandes de migration doivent inclure une copie de sauvegarde complète " -"de la base de données du Client et les données associées (généralement " -"obtenues à partir du menu Backup du Logiciel). Lorsque cela est nécessaire " -"pour des raisons de sécurité des données ou de réglementation, le Service de" -" migration inclut un outil facultatif pour rendre anonymes les données " -"identifiables figurant dans la base de données, avant de soumettre la " -"demande de migration, et un outil pour restaurer les données rendues " -"anonymes après la migration." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:160 -msgid "" -"Ce service est fourni par le biais d'une plateforme automatisée, afin de " -"permettre au Client d'effectuer des migration sans intervention humain, dès " -"lors qu’une version précédente de la base de données du Client a été migrée " -"avec succès pour une Version Couverte donnée. Le client peut soumettre des " -"demandes de migration successives pour une base de données, et accepte de " -"soumettre au moins 1 demande de mifration de test avant de soumettre la " -"demande de migration finale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:167 -msgid "" -"Le service de migration est limité à la conversion et à l'adaptation " -"techniques de la base de données du Client pour la rendre compatible avec la" -" Version Cible, et à la correction de tout Bug directement causé par " -"l'opération de migration, et ne se produisant normalement pas dans la " -"Version Cible." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:172 -msgid "" -"Il incombe au Client de vérifier et valider la base de données migrée afin " -"de détecter tout Bug, d'analyser l'impact des changements et des nouvelles " -"fonctionnalités ajoutées dans la Version Cible, de convertir et d'adapter " -"pour la Version Cible les modules tiers du Logiciel qui auraient été " -"installées dans la base de données avant la migration (sauf le cas échéant, " -"comme prévu à la section :ref:`upgrade_extra_fr`). Le client peut soumettre " -"plusieurs demandes de migration pour une base de données, jusqu'à ce qu'un " -"résultat satisfaisant soit obtenu." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:183 -msgid "Service de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:185 -msgid "" -"Pour la durée du Contrat, le Client a la possibilité de faire une demande de" -" migration pour des modules d'extension tiers, en plus de la migration " -"normale du Logiciel. Ce service en option implique des frais supplémentaires" -" (décrits dans la section charges_fr_) et comprend l'adaptation technique " -"des modules tiers installés dans la base de données du Client et de leurs " -"données correspondantes afin qu'elles soient compatibles avec la Version " -"Cible. Le Client recevra une version migrée de tous les modules tiers " -"installés accompagnée de la base de données migrée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:196 -msgid "5 Tarifs et Frais" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:201 -msgid "5.1 Tarifs standards" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:203 -msgid "" -"Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise, le " -"service de correction de Bugs, le service d'alertes de sécurité et le " -"service de migration sont basés sur le nombre d'Utilisateurs et la version " -"du Logiciel utilisée par le Client, et précisés par écrit à la signature du " -"contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:208 -msgid "" -"Pendant la durée du contrat, si le Client a plus d'Utilisateurs que spécifié" -" au moment de la signature du présent Contrat, le Client accepte de payer un" -" supplément équivalent au tarif en vigueur applicable (au début du Contrat) " -"pour les utilisateurs supplémentaires, pour le reste de la durée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:213 -msgid "" -"Si, au moment de la signature du présent Contrat, le Client utilise une " -"Version Couverte qui n'est pas l'une des plus récentes, les tarifs standards" -" seront augmentés de 50% pour la première Durée du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:221 -msgid "5.2 Tarifs de reconduction" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:223 -msgid "" -"Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si " -"les tarifs par Utilisateur qui ont été appliqués pendant la Durée précédente" -" sont inférieurs aux tarifs par Utilisateur en vigueur les plus récents, les" -" tarifs par Utilisateur augmenteront automatiquement de maximum 7%, à moins " -"qu'Odoo SA ne notifie par écrit un nouveau tarif au client, au moins 60 " -"jours avant l’échéance du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:232 -msgid "5.3 Tarifs de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:234 -msgid "" -"Les frais supplémentaires pour le service de migration des modules tiers " -"sont de 1000,00- euros (€) (mille euros) pour 1000 lignes de code de modules" -" tiers, le nombre de lignes étant arrondi au millier de lignes supérieur. " -"Les lignes de code comprennent toutes les lignes de texte dans le code " -"source de ces modules, quel que soit le langage de programmation (Python, " -"Javascript, etc.) ou format de données (XML, CSV, etc.), à l'exclusion des " -"lignes vides et des lignes de commentaires." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:240 -msgid "" -"Odoo SA se réserve le droit de refuser une demande de migration pour des " -"modules tiers conformément aux conditions décrites ci-dessus, si la qualité " -"du code source de ces modules est trop faible, ou si ces modules font partie" -" d'une interface d'intégration avec des logiciels ou systèmes tiers. La " -"migration de ces modules sera soumise à une proposition distincte, non " -"couverte par le présent Contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:250 -msgid "5.4 Taxes et impôts" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:252 -msgid "" -"Tous les frais et tarifs sont indiqués hors taxes et hors impôts, frais et " -"charges fédérales, provinciales, locales ou autres taxes gouvernementales " -"applicables (collectivement, les \"Taxes\"). Le Client est responsable du " -"paiement de toutes les Taxes liées aux achats effectués par le Client en " -"vertu du présent Contrat, sauf lorsque Odoo SA est légalement tenue de payer" -" ou de percevoir les Taxes dont le client est responsable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:261 -msgid "6 Conditions des Services" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:264 -msgid "6.1 Obligations du Client" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:266 -msgid "Le Client accepte de / d':" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:268 -msgid "" -"Payer à Odoo SA les frais applicables pour les Services en vertu du présent " -"Contrat, conformément aux conditions de paiement spécifiées dans la facture " -"correspondante ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:270 -msgid "" -"Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs dépasse le " -"nombre d'Utilisateurs spécifiés à la signature du Contrat, et dans ce cas, " -"de régler les frais supplémentaires applicables telles que décrits à la " -"section :ref:`charges_standard_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:273 -msgid "" -"Prendre toutes les mesures nécessaires pour garantir l'exécution non " -"modifiée de la partie du Logiciel qui vérifie la validité de l'utilisation " -"de Odoo Enterprise Edition, comme décrit à la section " -":ref:`enterprise_access_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:276 -msgid "" -"Fournir tout accès nécessaire à Odoo SA pour vérifier la validité de " -"l'utilisation d'Odoo Enterprise Edition sur demande (par exemple, si la " -"validation automatique ne fonctionne pas pour le Client) ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:279 -msgid "" -"Désigner 1 personne de contact représentant le Client pour toute la durée du" -" contrat ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:280 -msgid "" -"Prendre toutes les mesures raisonnables pour protéger les fichiers et les " -"bases de données du Client et s'assurer que les données du Client sont en " -"sûreté et sécurisées, en reconnaissant qu'Odoo SA ne peut être tenue " -"responsable de toute perte de données ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:288 -msgid "6.2 Non solicitation ou embauche" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:290 -msgid "" -"Sauf si l'autre partie donne son consentement par écrit, chaque partie, ses " -"sociétés affiliées et ses représentants conviennent de ne pas solliciter ou " -"offrir un emploi à tout employé de l'autre partie qui est impliqué dans " -"l'exécution ou l'utilisation des Services en vertu du présent Contrat, " -"pendant la Durée du Contrat et pendant une période de 12 mois à compter de " -"la date de résiliation ou de l'expiration du présent Contrat. En cas de " -"violation des conditions de la présente section qui conduirait à la " -"démission dudit employé à cette fin, la partie ayant enfreint ces " -"dispositions accepte de payer à l'autre partie un montant forfaitaire de 30 " -"000,00 euros (€) (trente mille euros)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:303 -msgid "6.3 Publicité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:305 -msgid "" -"Sauf demande contraire par écrit, chaque partie accorde à l'autre partie une" -" licence mondiale libre de droits, non transférable, non exclusive pour " -"reproduire et afficher le nom, les logos et les marques de l'autre partie, " -"dans le seul but de citer l'autre partie en tant que client ou fournisseur, " -"sur les sites Web, dans des communiqués de presse et autres documents de " -"marketing." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:313 -msgid "6.4 Confidentialité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:324 -msgid "Définition des \"Informations Confidentielles\" :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:316 -msgid "" -"Désigne toutes les informations divulguées par une partie (la \"Partie " -"Communicante\") à l'autre partie (la \"Partie Bénéficiaire\"), que ce soit " -"oralement ou par écrit, qui sont désignées comme confidentielles ou qui " -"devraient raisonnablement être comprises comme étant confidentielles étant " -"donné la nature des informations et les circonstances de la divulgation. En " -"particulier, toute information liée aux activités, aux affaires, aux " -"produits, aux développements, aux secrets commerciaux, au savoir-faire, au " -"personnel, aux clients et aux fournisseurs de l'une des parties doit être " -"considérée comme confidentielle." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:326 -msgid "" -"Pour toute Information Confidentielle reçue pendant la durée du présent " -"contrat, la Partie Bénéficiaire utilisera le même degré de précaution " -"qu'elle utilise pour protéger la confidentialité de ses propres Informations" -" Confidentielles de même importance. Ce degré de précaution devra " -"correspondre au minimum à une précaution raisonnable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:331 -msgid "" -"La Partie Bénéficiaire peut divulguer les Informations Confidentielles de la" -" Partie Communicante dans la mesure où la loi l'y oblige, à condition que la" -" Partie Bénéficiaire avise au préalable par écrit la Partie Communicante de " -"son obligation de divulgation, dans la mesure permise par la loi." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:339 -msgid "6.5 Résiliation" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:341 -msgid "" -"Dans le cas où l'une des parties ne remplit pas ses obligations découlant du" -" présent contrat, et si une telle violation n’est pas résolue dans les 30 " -"jours civils à compter de la notification écrite de cette violation, le " -"présent contrat peut être résilié immédiatement par la partie qui n'a pas " -"commis la violation." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:347 -msgid "" -"En outre, Odoo SA peut résilier le contrat immédiatement dans le cas où le " -"Client ne paie pas les frais applicables pour les services à la date " -"d'échéance indiquée sur la facture correspondante." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:354 -msgid "Durée de l'applicabilité des dispositions:" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:352 -msgid "" -"Les sections \":ref:`confidentiality_fr`\", “:ref:`disclaimers_fr`\", " -"“:ref:`liability_fr`\", et “:ref:`general_provisions_fr`\" survivront la " -"résiliation ou l'expiration du présent contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:359 -msgid "7 Limitations de garantie et de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:364 -msgid "7.1 Garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:366 -msgid "" -"Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts" -" raisonnables sur le plan commercial pour exécuter les Services conformément" -" aux normes du secteur généralement acceptées à condition que :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:370 -msgid "" -"Les systèmes informatiques du Client soient en bon état de fonctionnement et" -" que le Logiciel soit installé dans un système d'exploitation approprié ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:372 -msgid "" -"Le Client fournisse les informations adéquates nécessaires au dépannage et à" -" l'accès, de telle sorte qu'Odoo SA puisse identifier, reproduire et gérer " -"les problèmes ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:374 -msgid "Tous les montants dus à Odoo SA aient été réglés." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:376 -msgid "" -"La reprise de l'exécution des Services par Odoo SA sans frais " -"supplémentaires constitue la seule et unique réparation pour le Client et la" -" seule obligation d'Odoo SA pour toute violation de cette garantie." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:383 -msgid "7.2 Limitation de garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:385 -msgid "" -"Mis à part les dispositions expresses du présent Contrat, aucune des parties" -" ne donne de garantie d'aucune sorte, expresse, implicite, légale ou autre, " -"et chaque partie décline expressément toutes garanties implicites, y compris" -" toute garantie implicite de qualité marchande, d'adéquation à un usage " -"particulier ou de non- contrefaçon, dans les limites autorisées par la loi " -"en vigueur." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:391 -msgid "" -"Odoo SA ne garantit pas que le Logiciel soit conforme à toute loi ou " -"réglementation locale ou internationale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:398 -msgid "7.3 Limitation de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:400 -msgid "" -"Dans la limite autorisée par la loi, la responsabilité globale de chaque " -"partie, ainsi que de ses filiales, découlant ou liée au présent Contrat ne " -"dépassera pas 50% du montant total réglé par le Client en vertu du présent " -"Contrat au cours des 12 mois précédant la date de l'événement donnant lieu à" -" une telle réclamation. Des réclamations multiples n'augmenteront pas cette " -"limite." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:405 -msgid "" -"Les parties et leurs filiales ne pourront en aucun cas être tenues " -"responsables des dommages indirects, spéciaux, accessoires ou consécutifs de" -" quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de " -"revenus, perte de profits, perte d’économies, perte commerciale ou toute " -"autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte " -"ou altération des données, découlant ou en relation avec le présent Contrat," -" quelle que soit la forme de l'action, qu'elle soit fondée sur une " -"obligation contractuelle, délictuelle (y compris la stricte négligence) ou " -"fondée sur toute autre règle de droit ou d'équité, même si la partie ou ses " -"filiales ont été informées du risque de tels dommages, ou si le recours " -"proposé par la partie ou ses filiales n'atteint pas son but essentiel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:420 -msgid "" -"Aucune des parties ne sera tenue pour responsable envers l'autre partie de " -"tout retard ou manquement d'exécution en vertu du présent Contrat, si ce " -"manquement ou retard est causé par une règlementation gouvernementale, un " -"incendie, une grève, une guerre, une inondation, un accident, une épidémie, " -"un embargo, la saisie d'une usine ou d'un produit dans son intégralité ou en" -" partie par un gouvernement ou une autorité publique, ou toute (s) autre (s)" -" cause (s), qu’elle (s) soit (soient) de nature similaire ou différente, " -"pour autant que cette cause soit hors du contrôle raisonnable de la partie " -"concernée, et tant qu'une telle cause existe." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:431 -msgid "8 Dispositions générales" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:436 -msgid "8.1 Droit applicable" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:438 -msgid "" -"Les parties conviennent que les lois de Belgique seront applicables en cas " -"de litige découlant ou en relation avec le présent Contrat, sans tenir " -"compte des règles ou dispositions en matière de compétence législative ou de" -" conflit de lois. Dans la mesure où une poursuite ou procédure judiciaire ou" -" administrative serait autorisée ci-avant, les parties conviennent de se " -"soumettre à la compétence exclusive du tribunal de Nivelles (Belgique) aux " -"fins de la procédure de tout litige." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:448 -msgid "8.2 Divisibilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:450 -msgid "" -"Dans le cas où une ou plusieurs des dispositions du présent contrat ou toute" -" autre application de celles-ci se trouvent non valables, illégales ou non " -"exécutoires, la validité, la légalité et le caractère exécutoire des autres " -"dispositions du présent contrat et toute application de celles-ci ne doivent" -" en aucun cas en être affectés ou compromis. Les parties s'engagent à " -"remplacer toute disposition non valable, illégale ou non exécutoire du " -"présent contrat par une disposition valable ayant les mêmes effets et " -"objectifs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:460 -msgid "9 Appendice A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:462 -msgid "" -"Odoo 9 Enterprise Edition est publié sous la licence Odoo Enterprise Edition" -" License v1.0, définie ci-dessous." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:466 -msgid "" -"Ceci est une traduction en français de la licence “Odoo Enterprise Edition " -"License”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa " -"compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes de la licence “Odoo Enterprise Edition License” est la" -" :ref:`version originale `." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:472 -msgid "" -"This is a french translation of the \"Odoo Enterprise Edition License”. This" -" translation is provided in the hope that it will facilitate understanding, " -"but it has no legal value. The only official reference of the terms of the " -"“Odoo Enterprise Edition License” is the :ref:`original english version " -"`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:489 -msgid "" -"Ce logiciel et les fichiers associés (le \"Logiciel\") ne peuvent être " -"utilisés (c'est-à-dire exécutés, modifiés, ou exécutés avec des " -"modifications) qu'avec un contrat Odoo Enterprise Subscription en ordre de " -"validité, et pour le nombre d'utilisateurs prévus dans ce contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:494 -msgid "" -"Un contrat de Partnariat avec Odoo S.A. en ordre de validité donne les mêmes" -" permissions que ci-dessus, mais uniquement pour un usage restreint à un " -"environnement de test ou de développement." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:498 -msgid "" -"Vous êtes autorisé à développer des modules Odoo basés sur le Logiciel et à " -"les distribuer sous la license de votre choix, pour autant que cette licence" -" soit compatible avec les conditions de la licence Odoo Enterprise Edition " -"Licence (Par exemple: LGPL, MIT ou d'autres licenses propriétaires " -"similaires à celle-ci)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:503 -msgid "" -"Vous êtes autorisé à utiliser des modules Odoo publiés sous n'importe quelle" -" licence, pour autant que leur licence soit compatible avec les conditions " -"de la licence Odoo Enterprise Edition License (Notamment tous les modules " -"publiés sur l'Odoo Apps Store sur odoo.com/apps)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:508 -msgid "" -"Il est interdit de publier, distribuer, accorder des sous-licences, ou " -"vendre tout copie du Logiciel ou toute copie modifiée du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:511 -msgid "" -"Toute copie du Logiciel ou d'une partie substantielle de celui-ci doit " -"inclure l'avis de droit d'auteur original ainsi que le texte de la présente " -"licence." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:514 -msgid "" -"LE LOGICIEL EST FOURNI \"EN L'ETAT\", SANS AUCUNE GARANTIE DE QUELQUE NATURE" -" QUE CE SOIT, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS Y ETRE LIMITE, LES" -" GARANTIES IMPLICITES DE COMMERCIABILITE, DE CONFORMITE A UNE UTILISATION " -"PARTICULIERE, OU DE NON INFRACTION AUX DROITS D'UN TIERS." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:519 -msgid "" -"EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE " -"TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES " -"RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU " -"LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION " -"RELATIVE AU LOGICIEL." -msgstr "" - -#: ../../legal/terms/online.rst:3 -msgid "Odoo Online Terms & Conditions" -msgstr "" - -#: ../../legal/terms/partnership.rst:6 -msgid "Odoo Partnership Agreement - Under Revision!" -msgstr "" - -#: ../../legal/terms/partnership.rst:8 -msgid "Version 5_work-in-progress - Last revision: March 02, 2016." -msgstr "" - -#: ../../legal/terms/partnership.rst:11 -msgid "BETWEEN:" -msgstr "" - -#: ../../legal/terms/partnership.rst:13 -msgid "" -"ODOO SA registered at the Trade and Companies Register of Nivelles under " -"number RCN 95656, having its registered office at Chaussée de Namur, 40 - " -"1367 Grand-Rosière, Belgium." -msgstr "" - -#: ../../legal/terms/partnership.rst:16 -msgid "" -"AND ________________________________, a company having its registered office" -" at _____________________ (Hereinafter referred to as “PARTNER”)" -msgstr "" - -#: ../../legal/terms/partnership.rst:22 -msgid "1 Purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:23 -msgid "" -"The purpose of this agreement is to set forth the conditions under which " -"ODOO provides services to PARTNER, and access to Odoo Enterprise Edition " -"software, and PARTNER complies with the obligations set out hereafter." -msgstr "" - -#: ../../legal/terms/partnership.rst:27 -msgid "" -"ODOO hereby appoints PARTNER, and PARTNER hereby accepts appointment, to be " -"a non-exclusive partner promoting and selling the Odoo Enterprise " -"Subscriptions to clients. PARTNER commits to do its best effort to sell Odoo" -" Enterprise Subscriptions to its clients. To support that, PARTNER will " -"market in priority the ‘Odoo Enterprise Edition’ version to prospects and " -"clients. PARTNER still has the option to sell services on other versions of " -"the software, like \"Odoo Community Edition\", should it be needed." -msgstr "" - -#: ../../legal/terms/partnership.rst:35 -msgid "2 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/partnership.rst:36 -msgid "" -"The duration of this Agreement (the “Term”) shall be one year beginning on " -"the date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term to the other party." -msgstr "" - -#: ../../legal/terms/partnership.rst:45 -msgid "3.1 Project platform access" -msgstr "" - -#: ../../legal/terms/partnership.rst:46 -msgid "" -"To help PARTNER promoting Odoo Enterprise, ODOO grants access to its Github " -"code repository to PARTNER for all ‘Enterprise Edition’ modules, under the " -"terms set forth in Exhibit A and the conditions restricted under this " -"agreement. This access will be granted as of the signature of this agreement" -" and be revoked should the partnership contract be revoked." -msgstr "" - -#: ../../legal/terms/partnership.rst:50 -msgid "3.2 Restrictions" -msgstr "" - -#: ../../legal/terms/partnership.rst:51 -msgid "" -"PARTNER commits to keep confidentiality of the source code of Odoo " -"Enterprise edition modules licensed under restricted rights (labelled as " -"‘Enterprise Edition’) within its staff. The access to clients is governed by" -" the Odoo Enterprise Contract (version 4.0 and above). PARTNER agrees to NOT" -" redistribute this code to 3rd parties without the explicit agreement of " -"ODOO. Notwithstanding the above, PARTNER commits to wholly preserve the " -"integrity of the Odoo Enterprise edition code that is required to verify the" -" validity of usage of Odoo Enterprise edition, collects statistics that are " -"needed for that purpose and enforce the payment of the subscription." -msgstr "" - -#: ../../legal/terms/partnership.rst:56 -msgid "4 Partnership Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:59 -msgid "4.1 Partnership levels" -msgstr "" - -#: ../../legal/terms/partnership.rst:60 -msgid "" -"The ODOO partner program consists of three partnership levels; Ready, Silver" -" and Gold with specific requirements and benefits for each level. " -"Partnership level granted to PARTNER depends on the annual new Odoo " -"Enterprise revenues generated for ODOO. Renewals of existing contracts does " -"not account for the partnership level, but the partner still get his " -"commission on these contracts as stated in 5.2 The table below summarizes " -"the requirement for each partnership level." -msgstr "" - -#: ../../legal/terms/partnership.rst:64 -msgid "" -"Ready Silver Gold Annual New Net Odoo Enterprise Revenues 1.000 € 12.000 € " -"25.000 €" -msgstr "" - -#: ../../legal/terms/partnership.rst:72 -msgid "" -"The level of partnerships will be reviewed quarterly by ODOO based on Odoo " -"Enterprise contracts sold by partners, over the preceeding 12 months. " -"Partners may be upgraded automatically to a higher level once they reach the" -" requirements for a higher level. Silver and Gold partners which are not " -"complying with their partnerships requirements will be assigned to a lower " -"level of partnership if they have not met their requirement at the end of " -"the annual period. For new partners, the initial partner level is granted " -"for one year." -msgstr "" - -#: ../../legal/terms/partnership.rst:77 -msgid "4.2 Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:78 -msgid "" -"The details of the benefits for each level of partnership are described in " -"the table below:" -msgstr "" - -#: ../../legal/terms/partnership.rst:81 -msgid "" -"Ready Silver Gold Recognition Visibility on odoo.com Ready Partner Silver " -"Partner Gold Partner Rights to use the Odoo trademark Ready logo Silver logo" -" Gold logo Learning benefits Yearly upgrades seminars Yes Yes Yes Sales " -"Training Yes Yes Yes Weekly functional training webinars Yes Yes Yes " -"Software Benefits Access to Odoo Enterprise source code Yes Yes Yes Sales " -"benefits Discount on all ODOO services 10% 15% 20% Discount on ODOO " -"Enterprise (Minimum 10 users per contract, applied then for all users). 10% " -"15% 20% Access to an Account Manager Yes Yes Yes Marketing Benefits Access " -"to marketing materials Yes Yes Yes Partner EVENT – ODOO Support & Promotion " -"No Yes Yes" -msgstr "" - -#: ../../legal/terms/partnership.rst:135 -msgid "4.3 Partner Recognition" -msgstr "" - -#: ../../legal/terms/partnership.rst:136 -msgid "" -"ODOO will promote PARTNER as an official partner on its website (odoo.com) " -"for agreed countries. ODOO grants to PARTNER, on a non-exclusive basis, the " -"right to use and reproduce only the ODOO Partner’s logo, and the Odoo name " -"in connection with this Agreement. Each Party undertakes to respect all the " -"rights of the other Party in all the items referred to in the previous " -"paragraph and, more particularly, each Party shall refrain from causing any " -"analogy or creating any confusion between their respective company in the " -"mind of the general public, for any reason whatsoever and by any means " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:141 -msgid "4.4 Learning Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:142 -msgid "" -"In order to train PARTNER, ODOO will organize online training sessions once " -"a week. Sessions are organized into discovery and advanced topics. A session" -" is usually 2 hours and cover an application of the Odoo Enterprise " -"software: sales and CRM, inventory management, project management, " -"eCommerce, human resources, manufacturing, advanced customizations, etc. " -"PARTNER can attend these training sessions at no additional cost and commit " -"to attend at least 20 sessions per year. ODOO will organize at least four " -"sales training session per year of a duration of one week. Each sales " -"training session is organized in one of the ODOO office. PARTNER can send " -"any employee to these training session. Once a new version of Odoo " -"Enterprise is released, ODOO must organize upgrade training session for " -"partners." -msgstr "" - -#: ../../legal/terms/partnership.rst:148 -msgid "4.5 Commission on Odoo Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:149 -msgid "" -"For every ODOO services directly purchased by a customer through PARTNER, " -"PARTNER shall receive retribution as follows For “ODOO Enterprise” contracts" -" sold to CUSTOMER: ODOO will invoice directly the CUSTOMER based on final " -"pricing agreed between ODOO, the PARTNER & the CUSTOMER. Then, PARTNER will " -"invoice his commission to ODOO based on Odoo Enteprise price, net of " -"possible rebates, and based on his current partnership level at the time of " -"signature. For Other Services; Partner invoice directly the CLIENT and ODOO " -"will invoice the PARTNER directly commission included. (as a discount) For " -"“ODOO Enterprise” contracts; PARTNER get a commission as long as the PARTNER" -" maintains a contractual relationship with the CUSTOMER." -msgstr "" - -#: ../../legal/terms/partnership.rst:156 -msgid "5 Miscellaneous" -msgstr "" - -#: ../../legal/terms/partnership.rst:159 -msgid "5.1 Communications" -msgstr "" - -#: ../../legal/terms/partnership.rst:160 -msgid "" -"No communications from either party to the other shall have any validity " -"under this Agreement unless made in writing by or on behalf of PARTNER or " -"ODOO, as the case may be, in accordance with the provisions of this " -"Agreement. Any notice whatsoever which either party hereto is required or " -"authorised by this Agreement to give or make to the other shall be given or " -"made either by post in a prepaid letter, or by hand delivery or facsimile " -"transmission or E-mail." -msgstr "" - -#: ../../legal/terms/partnership.rst:164 -msgid "5.2 BRAND IMAGE" -msgstr "" - -#: ../../legal/terms/partnership.rst:165 -msgid "" -"Both Parties shall refrain from harming the brand image and reputation of " -"the other Party, in any way whatsoever, in the performance of this " -"Agreement. Non-compliance to this provision shall be a cause for termination" -" of this Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:168 -msgid "5.3 Publicity" -msgstr "" - -#: ../../legal/terms/partnership.rst:169 -msgid "" -"ODOO shall publish any press release, advertisement or other public " -"announcement using the PARTNER’s name or trademarks without its prior " -"written consent. In particular, PARTNER accepts to be mentioned, and that " -"its logo and trademark is used for this purpose only, in the list of the " -"partners of ODOO." -msgstr "" - -#: ../../legal/terms/partnership.rst:172 -msgid "5.4 No SOLICITING" -msgstr "" - -#: ../../legal/terms/partnership.rst:173 -msgid "" -"Each party, its subsidiaries and any entity controlled indirectly agrees not" -" to solicit, offer employment to, or use the services of any employee of the" -" other party who is involved in performing the Services for the duration of " -"the Agreement and for a period of twenty four (24) Months from the date of " -"termination of this Agreement, except as expressly provided for in the " -"Agreement or where the other party gives its consent in writing to this. In " -"case of any breach of the terms of this article, the defaulting Party shall " -"pay an indemnity equivalent to 12 months of the gross salary of the employee" -" sought or dismissed, or to at least a minimum of € 30,000." -msgstr "" - -#: ../../legal/terms/partnership.rst:177 -msgid "5.5 Independent Contractor" -msgstr "" - -#: ../../legal/terms/partnership.rst:178 -msgid "" -"The Parties are independent contractors, and this Agreement shall not be " -"construed as constituting either Party as partner, joint venture or " -"fiduciary of the other, as creating any other form of legal association that" -" would impose liability on one Party for the act or failure to act of the " -"other or as providing either Party with the right, power or authority " -"(express or implied) to create any duty or obligation of the other." -msgstr "" - -#: ../../legal/terms/partnership.rst:181 -msgid "6 FEES AND CHARGES" -msgstr "" - -#: ../../legal/terms/partnership.rst:182 -msgid "" -"PARTNER shall pay the charges and the annual fee immediately upon receipt of" -" the invoice sent by ODOO.The annual partnership fees is 2950€. PARTNER " -"shall automatically pay a late payment interest at the rate equivalent to " -"the applicable interest rate of the principal instrument of re-financing of " -"the European Central Bank increased by 7% per year, which shall accrue on a " -"daily basis from the due date of payment; it not being necessary for such " -"accrual that ODOO request or claims the unpaid amount in any manner " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:186 -msgid "7 Termination" -msgstr "" - -#: ../../legal/terms/partnership.rst:187 -msgid "" -"In the event that either Party fails to fulfil one or more of its " -"obligations arising hereunder, and if such breach has not been remedied " -"within thirty (30) calendar days from the first presentation of a letter, " -"sent by the injured Party by registered letter with advice of receipt, " -"giving notice of the breaches, this Agreement may be terminated immediately " -"as of right at the request of the injured Party, without prejudice to any " -"damages that may be claimed from the defaulting Party." -msgstr "" - -#: ../../legal/terms/partnership.rst:189 -msgid "" -"On expiry or termination of this Agreement, PARTNER: shall not use anymore " -"the materials and/or the Odoo brand name or claim the existence of any " -"partnership or link with ODOO, shall during any notice period prior to such " -"termination comply with its obligations. shall not use Odoo Enterprise " -"anymore, for development, test or production purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:195 -msgid "8 Liability AND Indemnities" -msgstr "" - -#: ../../legal/terms/partnership.rst:196 -msgid "" -"Both Parties are bound by a best endeavours obligation hereunder. To the " -"maximum extent permitted by law, ODOO’s liability for any and all claims, " -"losses, damages or expenses from any cause whatsoever and howsoever arising " -"under this Agreement will be limited to the direct damages proven, but will " -"in no event exceed for all damage causing event or series of connected " -"events causing damages the total amount for the charges paid by PARTNER in " -"the course of the six (6) months immediately preceding the date of the event" -" giving rise to such claim. In no event will ODOO be liable for any indirect" -" or consequential damages, including but not limited third parties or " -"Customer claims, loss of revenue, profits, savings, loss of business or " -"other financial loss, costs of standstill or delay, lost or corrupted data " -"arising out of or in connection with the performance of its obligations. " -"PARTNER acknowledges that he has no expectation and has received no " -"assurances that any investment made in execution of this Agreement and the " -"ODOO Partners Program will be recovered or recouped or that he shall obtain " -"any anticipated amount of profits by virtue of this Agreement. Partner " -"waives any commitment whatsoever on behalf of ODOO regarding the evolution " -"of Software." -msgstr "" - -#: ../../legal/terms/partnership.rst:202 -msgid "" -"According to the terms of the Software license, ODOO will not be liable for " -"any bug or for the quality and the performance of the Software, ODOO’s " -"commitment being limited to the correction of bugs as defined in this " -"Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:205 -msgid "9 Governing Law and Jurisdiction" -msgstr "" - -#: ../../legal/terms/partnership.rst:206 -msgid "" -"This Agreement will be governed by and construed in accordance with the laws" -" of Belgium. All disputes arising in connection with the Agreement for which" -" no amicable settlement can be found shall be finally settled by the Courts " -"of Belgium in Nivelles." -msgstr "" - -#: ../../legal/terms/partnership.rst:208 -msgid "For Odoo SA," -msgstr "" - -#: ../../legal/terms/partnership.rst:213 -msgid "For _____________," -msgstr "" - -#: ../../legal/terms/partnership.rst:220 -msgid "10 Appendix A: Odoo Enterprise Edition License" -msgstr "" diff --git a/locale/nl/LC_MESSAGES/manufacturing.po b/locale/nl/LC_MESSAGES/manufacturing.po index 21e9e8aa4..fa0fc0cbb 100644 --- a/locale/nl/LC_MESSAGES/manufacturing.po +++ b/locale/nl/LC_MESSAGES/manufacturing.po @@ -10,7 +10,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-03-23 15:39+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Eric Geens , 2017\n" +"Last-Translator: Gunther Clauwaert , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -28,11 +28,11 @@ msgstr "Productie verwerkingen" #: ../../manufacturing/operations/replenishment.rst:3 msgid "Replenishment Strategies" -msgstr "" +msgstr "Bevoorrading Strategieën" #: ../../manufacturing/operations/replenishment/strategies.rst:3 msgid "How to select the right replenishment strategy" -msgstr "" +msgstr "Hoe de correcte bevoorrading strategie te kiezen" #: ../../manufacturing/operations/replenishment/strategies.rst:5 msgid "" @@ -40,6 +40,9 @@ msgid "" "different rules. They should be used depending on your manufacturing and " "delivery strategies." msgstr "" +"Minimale voorraadregels en Maak op Order hebben soortgelijke gevolgen maar " +"verschillende regels. Ze moeten worden gebruikt, afhankelijk van uw " +"productie- en levering- strategieën." #: ../../manufacturing/operations/replenishment/strategies.rst:10 msgid "Terminology" @@ -57,6 +60,12 @@ msgid "" " minimum the system will automatically generate a procurement order with the" " quantity needed to reach the maximum stock level." msgstr "" +"Minimum voorraadregels worden gebruikt om ervoor te zorgen dat u altijd het " +"minimale aantal producten op voorraad heeft om uw producten te kunnen " +"vervaardigen en / of te beantwoorden aan uw klantenbehoeften. Wanneer het " +"voorraadniveau van een product het minimum bereikt, zal het systeem " +"automatisch een inkooporder genereren met de hoeveelheid die nodig is om het" +" maximale voorraadniveau te bereiken." #: ../../manufacturing/operations/replenishment/strategies.rst:22 #: ../../manufacturing/operations/replenishment/strategies.rst:58 @@ -70,6 +79,10 @@ msgid "" "current stock. This means that a draft purchase order will be generated " "regardless of the quantity on hand of the product." msgstr "" +"Met de functie Maak op Order wordt een aankooporder geactiveerd dat gelijk " +"is aan het aantal bestelde producten. Het systeem zal de huidige voorraad **" +" niet ** controleren. Dit betekent dat een draft aankooporder wordt " +"gegenereerd, ongeacht de beschikbare hoeveelheid." #: ../../manufacturing/operations/replenishment/strategies.rst:30 #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:27 @@ -116,7 +129,7 @@ msgstr "" #: ../../manufacturing/operations/replenishment/strategies.rst:64 msgid "On the product form, under Inventory, click on \"Make To Order\"." -msgstr "" +msgstr "Klik in het product scherm onder Inventaris op \"Maak op Order\"." #: ../../manufacturing/operations/replenishment/strategies.rst:70 msgid "Choice between the two options" @@ -141,7 +154,7 @@ msgstr "Materiaallijst" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:3 msgid "How to Sell a Set of Products as a Kit" -msgstr "" +msgstr "Hoe een set van producten verkopen als een Kit" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:5 msgid "" @@ -154,7 +167,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:12 msgid "Manage Stock of Component Products" -msgstr "" +msgstr "Beheer de Voorraad van Componenten" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:14 msgid "" @@ -202,7 +215,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:53 msgid "Manage Stock of Kit Product and Component Products" -msgstr "" +msgstr "Beheer de Voorraad van Kits en Componenten" #: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:55 msgid "" @@ -230,7 +243,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/product_variants.rst:3 msgid "How to manage BoMs for product variants" -msgstr "" +msgstr "Hoe materiaallijsten (BoMs) beheren voor productvarianten?" #: ../../manufacturing/overview/bill_of_materials/product_variants.rst:5 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:125 @@ -239,6 +252,9 @@ msgid "" "same product. Simply enable variants from :menuselection:`Configuration --> " "Settings`." msgstr "" +"Odoo stelt u in staat om één materiaallijst te gebruiken voor meerdere " +"varianten van hetzelfde product. Schakel varianten in via: menuselectie " +"binnen Productie: Instellingen-> \"Instellingen\"." #: ../../manufacturing/overview/bill_of_materials/product_variants.rst:12 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:132 @@ -259,7 +275,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:3 msgid "How to manage semi-finished products" -msgstr "" +msgstr "Hoe half afgewerkte producten beheren" #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:5 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:83 @@ -283,7 +299,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:19 msgid "Configure the Top -Level Product BoM" -msgstr "" +msgstr "Configureer de materiaallijst (BoM) op Top-niveau " #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:21 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:99 @@ -296,7 +312,7 @@ msgstr "" #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:29 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:107 msgid "Configure the Subassembly Product Data" -msgstr "" +msgstr "Configureer de productgegevens van de subassemblage" #: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:31 #: ../../manufacturing/overview/getting_started/bill_configuration.rst:109 @@ -321,11 +337,11 @@ msgstr "Aan de slag" #: ../../manufacturing/overview/getting_started.rst:5 msgid "How to consume composents to make a finished product" -msgstr "" +msgstr "Hoe uw onderdelen verwerken om een afgewerkt product te maken" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:3 msgid "How to create a Bill of Materials" -msgstr "" +msgstr "Hoe een materiaallijst (BoM) maken" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:5 msgid "" @@ -343,7 +359,7 @@ msgstr "" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:14 msgid "Setting up a Basic BoM" -msgstr "" +msgstr "Maken van een eenvoudige materiaallijst (BoM)" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:16 msgid "" @@ -377,7 +393,7 @@ msgstr "" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:38 msgid "Adding a Routing to a BoM" -msgstr "" +msgstr "Routes toevoegen aan een materiaallijst (BoM)" #: ../../manufacturing/overview/getting_started/bill_configuration.rst:40 msgid "" @@ -442,7 +458,7 @@ msgstr "" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:3 msgid "How to process a manufacturing order" -msgstr "" +msgstr "Hoe een productieorder verwerken" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:6 msgid "Introduction" @@ -460,7 +476,7 @@ msgstr "" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:17 msgid "How to manage manufacturing without routings" -msgstr "" +msgstr "Hoe de productie beheren zonder routes" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:19 msgid "" @@ -475,11 +491,13 @@ msgid "" "Managing your operations in this way is the default behavior in Odoo. There " "are two basic phases from planning to production:" msgstr "" +"Het beheer van uw productie handelingen is op deze wijze standaardgedrag in " +"Odoo. Er zijn twee basisfasen van planning tot productie:" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:27 #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:52 msgid "Create manufacturing orders" -msgstr "" +msgstr "Maak productieorders" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:29 msgid "Record Production" @@ -487,7 +505,7 @@ msgstr "Productie vastleggen" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:32 msgid "How to manage manufacturing with routings and work orders" -msgstr "" +msgstr "Hoe uw productie beheren met routes en werkorders" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:34 msgid "" @@ -515,15 +533,15 @@ msgstr "" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:50 msgid "The workflow is thus divided into three basic phases, as follows:" -msgstr "" +msgstr "De workflow is dus verdeeld in drie basisfasen, als volgt:" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:54 msgid "Schedule the associated work orders." -msgstr "" +msgstr "Plan de bijbehorende werkorders" #: ../../manufacturing/overview/getting_started/manufacturing_order.rst:56 msgid "Perform the scheduled work and record production." -msgstr "" +msgstr "Voer de geplande werkzaamheden uit en registreer de productie" #: ../../manufacturing/overview/main_concepts.rst:3 msgid "Main Concepts" @@ -531,7 +549,7 @@ msgstr "Belangrijkste concepten" #: ../../manufacturing/overview/main_concepts/intro.rst:3 msgid "Introduction to Odoo Manufacturing" -msgstr "" +msgstr "Introductie Odoo Productie" #: ../../manufacturing/overview/main_concepts/intro.rst:11 msgid "Transcript" @@ -539,11 +557,11 @@ msgstr "Transcriptie" #: ../../manufacturing/overview/main_concepts/intro.rst:13 msgid "Work in progress." -msgstr "" +msgstr "Werk in uitvoering (WIP)" #: ../../manufacturing/overview/main_concepts/terminologies.rst:3 msgid "Manufacturing Terminologies" -msgstr "" +msgstr "Productie Terminologieën" #: ../../manufacturing/overview/main_concepts/terminologies.rst:9 msgid "" @@ -556,13 +574,15 @@ msgstr "" #: ../../manufacturing/overview/main_concepts/terminologies.rst:14 msgid "Cycle" -msgstr "" +msgstr "Cyclus" #: ../../manufacturing/overview/main_concepts/terminologies.rst:17 msgid "" "A production cycle is a frame of time during which an entire manufacturing " "process can be fulfilled." msgstr "" +"Een productiecyclus is een tijdsbestek waarin een volledig productieproces " +"kan worden afgewerkt." #: ../../manufacturing/overview/main_concepts/terminologies.rst:19 msgid "Downtime or Leave" @@ -577,7 +597,7 @@ msgstr "" #: ../../manufacturing/overview/main_concepts/terminologies.rst:25 msgid "Finished products" -msgstr "" +msgstr "Afgewerkte producten" #: ../../manufacturing/overview/main_concepts/terminologies.rst:28 msgid "" diff --git a/locale/nl/LC_MESSAGES/point_of_sale.po b/locale/nl/LC_MESSAGES/point_of_sale.po index f838e684a..01db94233 100644 --- a/locale/nl/LC_MESSAGES/point_of_sale.po +++ b/locale/nl/LC_MESSAGES/point_of_sale.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Cas Vissers , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" @@ -1586,7 +1586,7 @@ msgstr "" #: ../../point_of_sale/overview/setup.rst:255 msgid "``# usermod -a -G usbusers USERNAME``" -msgstr "" +msgstr "``# usermod -a -G usbusers USERNAME``" #: ../../point_of_sale/overview/setup.rst:257 msgid "" @@ -2326,18 +2326,34 @@ msgid "" "location,..." msgstr "U kan elke kassa configureren naar uw hardware, locatie,..." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "Kassa naam" + #: ../../point_of_sale/overview/start.rst:0 msgid "An internal identification of the point of sale" msgstr "Een interne identificatie van kassa" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "Verkoopboek" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to post sales entries." msgstr "Financieel dagboek gebruikt voor het maken van de verkoopboekingen." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "Factuur dagboek" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to create invoices." msgstr "Dagboek gebruikt voor het maken van facturen." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "Groepeer boekingen" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Check this if you want to group the Journal Items by Product while closing a" @@ -2346,6 +2362,10 @@ msgstr "" "Vink deze optie aan indien u alle boekingen wilt groeperen per product, bij " "het sluiten van een sessie." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "Barcodes" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Defines what kind of barcodes are available and how they are assigned to " @@ -2354,6 +2374,10 @@ msgstr "" "Definieert welke barcodes beschikbaar zijn en hoe ze worden toegewezen aan " "producten, klanten en kassières" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "Ordernummer reeks" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "This sequence is automatically created by Odoo but you can change it to " @@ -2362,18 +2386,35 @@ msgstr "" "Deze nummering zal automatisch gegenereerd worden door Odoo, maar u kunt ook" " uw eigen nummering samenstellen." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "Verkoopkanaal" + #: ../../point_of_sale/overview/start.rst:0 msgid "This Point of sale's sales will be related to this Sales Channel." msgstr "" +"Deze kassa zijn verkopen zullen gerelateerd zijn aan dit verkoopkanaal." + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "Virtueel Toetsenbord" #: ../../point_of_sale/overview/start.rst:0 msgid "Enables an integrated Virtual Keyboard" msgstr "Activeer het geïntegreerde virtuele toetsenbord" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "Facturatie" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables invoice generation from the Point of Sale" msgstr "Activeer het aanmaken van facturen door de kassa" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "Vooraf contante betaling invullen" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The payment input will behave similarily to bank payment input, and will be " @@ -2382,6 +2423,10 @@ msgstr "" "De betalingsingave gedraagt zich gelijkwaardig aan de bankafschrift ingave " "en wordt automatisch ingevuld met het exacte verschuldigde bedrag" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "Startcategorie" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The point of sale will display this product category by default. If no " @@ -2390,6 +2435,10 @@ msgstr "" "De kassa toont de productcategorieën standaard. Als er geen categorie is " "gespecificeerd worden alle producten getoond" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "Fooi product" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The product used to encode the customer tip. Leave empty if you do not " @@ -2398,6 +2447,10 @@ msgstr "" "Het product te encoderen voor de klantenfooi. Laat dit leeg als u geen " "fooien accepteert." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "Prijzen inclusief BTW" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The displayed prices will always include all taxes, even if the taxes have " @@ -2406,14 +2459,26 @@ msgstr "" "De weergegeven prijzen zijn altijd inclusief BTW, zelfs als de BTW anders " "zijn opgezet" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "Grote scrollbalken" + #: ../../point_of_sale/overview/start.rst:0 msgid "For imprecise industrial touchscreens" msgstr "Voor onnauwkeurige industriële touchscreens" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "Toon categorie afbeeldingen" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product categories will be displayed with pictures." msgstr "De productcategorieën worden getoond met afbeeldingen." +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "IP-adres" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The hostname or ip address of the hardware proxy, Will be autodetected if " @@ -2422,27 +2487,51 @@ msgstr "" "De hostnaam of het IP adres van de hardware proxy worden automatisch " "gedetecteerd als het veld leeg wordt gelaten." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "Barcode scanner" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enable barcode scanning with a remotely connected barcode scanner" msgstr "" "Activeer barcode scannen m.b.v. een op afstand verbonden barcode scanner" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "Electronisch weegschaal" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Electronic Scale integration" msgstr "Activeer de integratie met een electrische weegschaal" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "Kassalade" + #: ../../point_of_sale/overview/start.rst:0 msgid "Automatically open the cashdrawer" msgstr "Open de kassalade automatisch" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "Kassabonprinter" + #: ../../point_of_sale/overview/start.rst:0 msgid "Bypass browser printing and prints via the hardware proxy" msgstr "Niet via de browser afdrukken, maar via de hardware proxy" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "Automatisch kassabon afdrukken" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt will automatically be printed at the end of each order" msgstr "De kassabon wordt automatisch afgedrukt aan het einde van elke order" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "Sla kassabon scherm over" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The receipt screen will be skipped if the receipt can be printed " @@ -2451,32 +2540,60 @@ msgstr "" "Het kassabon scherm wordt overgeslagen als de kassabon automatisch afgedrukt" " kan worden." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "Kop" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a header in the printed receipt" msgstr "" "Een korte tekst die als koptekst in de afgedrukte bon zal worden ingevoegd" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "Voettekst" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a footer in the printed receipt" msgstr "" "Een korte tekst die als voettekst in de afgedrukte bon zal worden ingevoegd" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "Kas controle" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check the amount of the cashbox at opening and closing." msgstr "Controleer het bedrag van de kas bij het openen en sluiten." +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "Rekening splitsen" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Bill Splitting in the Point of Sale" msgstr "Sta splitsen van rekeningen toe in het verkooppunt" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "Rekening printen" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allows to print the Bill before payment" msgstr "Zorgt ervoor dat u de factuur kan afdrukken voor betaling" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "Orderregel notities" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allow custom notes on Orderlines" msgstr "Sta aangepaste notities toe op orderregels" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "Restaurantverdiepingen" + #: ../../point_of_sale/overview/start.rst:0 msgid "The restaurant floors served by this point of sale" msgstr "De restaurant verdiepingen bediend met deze kassa" @@ -3378,6 +3495,10 @@ msgstr "" "kan op alle producten gedaan worden of enkel op specifieke producten. Klik " "op **Item toevoegen**." +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "Actief" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "" "If unchecked, it will allow you to hide the pricelist without removing it." @@ -3385,6 +3506,10 @@ msgstr "" "Indien niet aangevinkt, kunt u de prijslijst verbergen, zonder deze te " "wissen." +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "Kiesbaar" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "Allow the end user to choose this price list" msgstr "Sta de eindgebruiker toe om de prijslijst te kiezen" diff --git a/locale/nl/LC_MESSAGES/practical.po b/locale/nl/LC_MESSAGES/practical.po index 3295a9e2f..39c03e98b 100644 --- a/locale/nl/LC_MESSAGES/practical.po +++ b/locale/nl/LC_MESSAGES/practical.po @@ -10,6 +10,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-03-23 15:39+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Yenthe Van Ginneken , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -19,4 +20,4 @@ msgstr "" #: ../../practical.rst:3 msgid "Practical Information" -msgstr "" +msgstr "Praktische informatie" diff --git a/locale/nl/LC_MESSAGES/purchase.po b/locale/nl/LC_MESSAGES/purchase.po index 6e3078f33..f5e19efa4 100644 --- a/locale/nl/LC_MESSAGES/purchase.po +++ b/locale/nl/LC_MESSAGES/purchase.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Eric Geens , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" @@ -1862,10 +1862,18 @@ msgid "" "date to which you wish to proceed to the actual order." msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "Ontvangst" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Incoming Shipments" msgstr "Inkomende leveringen" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "Leveranciers referentie" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the sales order or bid sent by the vendor. It's used to do the " @@ -1876,6 +1884,10 @@ msgstr "" "bedoelde om de koppeling te doen tussen ontvangen producten omdat deze " "referentie meestal geschreven is op de pakbon verzonden door uw leverancier." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "Orderdatum" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Depicts the date where the Quotation should be validated and converted into " @@ -1884,16 +1896,28 @@ msgstr "" "Geeft de datum aan waarop de offerte bevestigd en geconverteerd moet worden " "in een inkooporder." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "Brondocument" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the document that generated this purchase order request (e.g. a" " sales order or an internal procurement request)" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "Leveren aan" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "This will determine picking type of incoming shipment" msgstr "Dit bepaald de ontvangstwijze van de inkomende levering." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "Dropship afleveradres" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Put an address if you want to deliver directly from the vendor to the " @@ -1902,11 +1926,19 @@ msgstr "" "Geef een adres in, indien u direct vanaf de leverancier wilt leveren aan de " "klant. Laat leeg om te leveren aan uw eigen bedrijf." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "Bestemmingslocatie soort" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Technical field used to display the Drop Ship Address" msgstr "" "Technisch veld welke wordt gebruikt om het dropshipment adres weer te geven." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "Leveringscondities" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "International Commercial Terms are a series of predefined commercial terms " diff --git a/locale/nl/LC_MESSAGES/sales.po b/locale/nl/LC_MESSAGES/sales.po index 3971597ba..58564ed0d 100644 --- a/locale/nl/LC_MESSAGES/sales.po +++ b/locale/nl/LC_MESSAGES/sales.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Eric Geens , 2017\n" +"Last-Translator: Gunther Clauwaert , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -54,7 +54,7 @@ msgstr "" #: ../../sales/advanced/portal.rst:20 msgid "How to give portal access to customers?" -msgstr "Hoe geef ik portaal toegang aan mij gebruikers" +msgstr "Hoe geef ik portaal toegang aan mijn gebruikers" #: ../../sales/advanced/portal.rst:23 msgid "From Contacts Module" @@ -909,16 +909,11 @@ msgstr "" #: ../../sales/invoicing/services/support.rst:66 msgid "" -"There are different ways to track the service related to a sale order or " +"There are different ways to track the service related to a sales order or " "product sold. With the above configuration, you can only sell one support " "contract per order. If your customer orders several service contracts on " "timesheet, you will have to split the quotation into several orders." msgstr "" -"Er zijn verschillende manieren om de diensten gerelateerd aan een " -"verkooporder of verkocht product te volgen. Met de bovenstaande configuratie" -" kan u slechts één ondersteuningscontract per order verkopen. Indien uw " -"klant meerdere ondersteuningscontracten besteld op urenstaat moet u de " -"offerte uitsplitsen in meerdere orders." #: ../../sales/invoicing/services/support.rst:72 msgid "" @@ -937,20 +932,16 @@ msgid "Managing support contract" msgstr "Ondersteuningscontract beheren" #: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sale Orders" +msgid "Quotations and Sales Orders" msgstr "Offertes en verkooporders" #: ../../sales/invoicing/services/support.rst:83 msgid "" -"Once the product is created, you can create a quotation or a sale order with" -" the related product. Once the quotation is confirmed and transformed into a" -" sale order, your users will be able to record services related to this " -"support contract using the timesheet application." +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." msgstr "" -"Eenmaal het product is aangemaakt kan u een offerte of verkooporder aanmaken" -" met het gerelateerde product. Eenmaal de offerte bevestigd is en omgevormd " -"is in een verkooporder kan uw gebruiker de diensten gerelateerd aan het " -"ondersteuningscontract bewaren dankzij de urenstaten applicatie." #: ../../sales/invoicing/services/support.rst:93 msgid "Timesheets" @@ -970,8 +961,8 @@ msgstr "" "vanaf ze verkocht zijn." #: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sale order" -msgstr "Controleer geleverde ondersteuning op het verkooporder" +msgid "Control delivered support on the sales order" +msgstr "" #: ../../sales/invoicing/services/support.rst:106 msgid "" @@ -994,31 +985,14 @@ msgstr "Upselling en vernieuwing" #: ../../sales/invoicing/services/support.rst:118 msgid "" "If the number of hours you performed on the support contract is bigger or " -"equal to the number of hours the customer purchased, the sale order " -"**Invoicing Status** is automatically set to **Upselling**. This means you " -"have an opportunity to sell an extra contract to the customer since he used " -"all his quota of service." +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." msgstr "" -"Als het aantal uren dat u heeft gepresteerd op het ondersteuningscontract " -"groter of gelijk is aan het aantal uren dat de klant heeft aangekocht wordt " -"de verkooporder zijn **Facturatie status** automatisch ingesteld op " -"**Upselling**. Dit betekend dat u een opportuniteit heeft om een extra " -"contract te verkopen aan de klant aangezien hij zijn quota voor de dienst " -"heeft opgebruikt." -#: ../../sales/invoicing/services/support.rst:124 -msgid "" -"Periodically (ideally once every two weeks), you should check the sales " -"order that are in an upselling status. To do this, go to the " -":menuselection:`Sales --> Sales Order` menu and use the **Upselling** filter" -" to get all orders that are in upselling." -msgstr "" -"Periodiek (ideaal elke twee weken), zou u de verkooporders moeten " -"controleren die zich in de upselling status bevinden. Om dit te doen gaat u " -"naar :menuselection:`Verkopen --> Verkooporder` en gebruikt u de " -"**Upselling** filter om alle orders in deze fase te vinden." - -#: ../../sales/invoicing/services/support.rst:130 +#: ../../sales/invoicing/services/support.rst:127 msgid "" "If you use Odoo CRM, a good practice is to create an opportunity for every " "sale order in upselling invoice status so that you easily track your " @@ -1028,26 +1002,20 @@ msgstr "" "aan te maken voor elke verkooporder in de factuurstatus zodat u gemakkelijk " "uw upselling kan traceren." -#: ../../sales/invoicing/services/support.rst:134 +#: ../../sales/invoicing/services/support.rst:131 msgid "" "If you sell an extra support contract, you can either add a new line on the " -"existing sale order (thus, you continue to timesheet on the same order) or " +"existing sales order (thus, you continue to timesheet on the same order) or " "create a new order (thus, people will timesheet their hours on the new " -"contract). To unmark the sale order as **Upselling**, you can set the sale " -"order as done and it will disappear from your upselling list." +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." msgstr "" -"Indien u een extra ondersteuningscontract verkoopt kan u een nieuwe lijn " -"toevoegen aan het bestaande verkooporder (u bewaard dus nog steeds uw " -"urenstaten op hetzelfde order) of u maakt een nieuw order(mensen moeten hun " -"urenstaten op het nieuwe contract boeken). Om de verkooporder te demarkeren " -"als **Upselling** kan u de verkooporder naar de status verwerkt zetten en " -"het zal vervolgens verdwijnen uit uw upselling lijst." -#: ../../sales/invoicing/services/support.rst:141 +#: ../../sales/invoicing/services/support.rst:138 msgid "Special Configuration" msgstr "Speciale configuratie" -#: ../../sales/invoicing/services/support.rst:143 +#: ../../sales/invoicing/services/support.rst:140 msgid "" "When creating the product form, you may set a different approach to track " "the service:" @@ -1055,33 +1023,23 @@ msgstr "" "Wanneer u het productformulier aanmaakt kan u een andere aanpak instellen om" " de dienst op te volgen:" -#: ../../sales/invoicing/services/support.rst:146 +#: ../../sales/invoicing/services/support.rst:143 msgid "" "**Create task and track hours**: in this mode, a task is created for every " -"sale order line. Then when you do the timesheet, you don't record hours on a" -" sale order/contract, but you record hours on a task (that represents the " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " "contract). The advantage of this solution is that it allows to sell several " -"service contracts within the same sale order." +"service contracts within the same sales order." msgstr "" -"**Maak taken en traceer uren**: In deze modus wordt een taak aangemaakt voor" -" elke verkooporderlijn. Wanneer u vervolgens de urenstaat doet worden er " -"geen uren geregistreerd op de verkooporder / het contract, maar uren op een " -"taak (die het contract voorstelt). Het voordeel van deze oplossing is dat " -"het toestaat om meerdere dienst contracten te verkopen binnen hetzelfde " -"verkooporder." -#: ../../sales/invoicing/services/support.rst:153 +#: ../../sales/invoicing/services/support.rst:150 msgid "" "**Manually**: you can use this mode if you don't record timesheets in Odoo. " "The number of hours you worked on a specific contract can be recorded " -"manually on the sale order line directly, in the delivered quantity field." +"manually on the sales order line directly, in the delivered quantity field." msgstr "" -"**Manueel**: u kan deze modus gebruiken indien u geen urenstaten logt in " -"Odoo. Het aantal uren dat u werkt aan een specifiek contract kan direct " -"manueel genoteerd worden op de verkooporder, in het geleverde hoeveelheid " -"veld." -#: ../../sales/invoicing/services/support.rst:159 +#: ../../sales/invoicing/services/support.rst:156 msgid ":doc:`../../../inventory/settings/products/uom`" msgstr ":doc:`../../../inventory/settings/products/uom`" @@ -1349,15 +1307,11 @@ msgstr ":menuselection:`eCommerce Order --> Factuur`" #: ../../sales/overview/main_concepts/invoicing.rst:69 msgid "" -"An eCommerce order will also trigger the creation of the order when it is " +"An eCommerce order will also trigger the creation of the invoice when it is " "fully paid. If you allow paying orders by check or wire transfer, Odoo only " "creates an order and the invoice will be triggered once the payment is " "received." msgstr "" -"Een e-commerce order doet ook het aanmaken van het order afgaan wanneer deze" -" volledig betaald is. Indien u toestaat dat Orders betaald worden via cheque" -" of overschrijving zal Odoo enkel een order aanmaken en wordt de factuur " -"aangemaakt wanneer de betaling ontvangen is." #: ../../sales/overview/main_concepts/invoicing.rst:75 msgid "Creating an invoice manually" @@ -1421,15 +1375,17 @@ msgstr "Producten & Prijzen" #: ../../sales/products_prices/prices.rst:3 msgid "Manage your pricing" -msgstr "" +msgstr "Beheer uw prijzen" #: ../../sales/products_prices/prices/currencies.rst:3 msgid "How to sell in foreign currencies" -msgstr "" +msgstr "Hoe te verkopen in vreemde valuta" #: ../../sales/products_prices/prices/currencies.rst:5 msgid "Pricelists can also be used to manage prices in foreign currencies." msgstr "" +"Prijslijsten kunnen ook gebruikt worden om prijzen in vreemde valuta te " +"beheren." #: ../../sales/products_prices/prices/currencies.rst:7 msgid "" @@ -1454,10 +1410,11 @@ msgstr "" #: ../../sales/products_prices/prices/currencies.rst:17 msgid "Prices in foreign currencies can be defined in two fashions." msgstr "" +"De prijzen in vreemde valuta kunnen worden gedefinieerd op twee manieren." #: ../../sales/products_prices/prices/currencies.rst:20 msgid "Automatic conversion from public price" -msgstr "" +msgstr "Automatische omschakeling van de publieke prijs" #: ../../sales/products_prices/prices/currencies.rst:22 msgid "" @@ -1475,21 +1432,23 @@ msgstr "" #: ../../sales/products_prices/prices/currencies.rst:40 msgid "Set your own prices" -msgstr "" +msgstr "Stel uw eigen prijzen in" #: ../../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 "" +"Dit wordt geadviseerd als u niet wilt dat uw prijzen veranderen door " +"wisselkoersen" #: ../../sales/products_prices/prices/currencies.rst:49 msgid ":doc:`pricing`" -msgstr "" +msgstr ":doc:`prijzen`" #: ../../sales/products_prices/prices/pricing.rst:3 msgid "How to adapt your prices to your customers and apply discounts" -msgstr "" +msgstr "Hoe uw prijzen aan uw klanten aanpassen en kortingen toepassen" #: ../../sales/products_prices/prices/pricing.rst:5 msgid "" @@ -1504,7 +1463,7 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:16 msgid "Several prices per product" -msgstr "" +msgstr "Verschillende prijzen per product" #: ../../sales/products_prices/prices/pricing.rst:18 msgid "" @@ -1515,12 +1474,14 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:23 msgid "Prices per customer segment" -msgstr "" +msgstr "Prijzen per klantsegment" #: ../../sales/products_prices/prices/pricing.rst:25 msgid "" "Create pricelists for your customer segments: e.g. registered, premium, etc." msgstr "" +"Prijslijsten maken voor uw klantsegmenten: b.v. Partner, eindgebruiker, " +"distributeur enz." #: ../../sales/products_prices/prices/pricing.rst:30 msgid "" @@ -1531,11 +1492,13 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:38 msgid "Temporary prices" -msgstr "" +msgstr "Tijdelijke prijzen" #: ../../sales/products_prices/prices/pricing.rst:40 msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." msgstr "" +"Speciale prijs acties voor b.v. weekends, enz. Vul de start- en einddatums " +"in." #: ../../sales/products_prices/prices/pricing.rst:46 msgid "" @@ -1545,7 +1508,7 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:50 msgid "Prices per minimum quantity" -msgstr "" +msgstr "Prijzen per minimale hoeveelheid" #: ../../sales/products_prices/prices/pricing.rst:56 msgid "" @@ -1555,7 +1518,7 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:60 msgid "Discounts, margins, roundings" -msgstr "" +msgstr "Kortingen, marges, afrondingen" #: ../../sales/products_prices/prices/pricing.rst:62 msgid "" @@ -1590,22 +1553,24 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:86 msgid "Make sure at least one pricelist item covers all your products." msgstr "" +"Zorg ervoor dat tenminste één prijslijst van toepassing is voor alle " +"producten" #: ../../sales/products_prices/prices/pricing.rst:88 msgid "There are 3 modes of computation: fix price, discount & formula." -msgstr "" +msgstr "Er zijn 3 berekeningswijzen: vaste prijs, korting en formule." #: ../../sales/products_prices/prices/pricing.rst:93 msgid "Here are different price settings made possible thanks to formulas." -msgstr "" +msgstr "Hier zijn verschillende prijs instellingen mogelijk dankzij formules" #: ../../sales/products_prices/prices/pricing.rst:96 msgid "Discounts with roundings" -msgstr "" +msgstr "Kortingen met afrondingen" #: ../../sales/products_prices/prices/pricing.rst:98 msgid "e.g. 20% discounts with prices rounded up to 9.99." -msgstr "" +msgstr "bijv. 20% korting met prijzen afgerond tot 9,99" #: ../../sales/products_prices/prices/pricing.rst:104 msgid "Costs with markups (retail)" @@ -1617,7 +1582,7 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:112 msgid "Prices per country" -msgstr "" +msgstr "Prijzen per land" #: ../../sales/products_prices/prices/pricing.rst:113 msgid "" @@ -1626,18 +1591,26 @@ msgid "" "country. In case no country is set for the customer, Odoo takes the first " "pricelist without any country group." msgstr "" +"Prijslijsten kunnen worden ingesteld per landengroep. Elke nieuwe klant " +"krijgt een standaardprijslijst, dat wil zeggen de eerste in de lijst die " +"overeenkomt met het land. Als er geen land voor de klant is ingesteld, neemt" +" Odoo de eerste prijslijst zonder landengroep." #: ../../sales/products_prices/prices/pricing.rst:116 msgid "The default pricelist can be replaced when creating a sales order." msgstr "" +"De standaardprijslijst kan worden gewijzigd bij het maken van een " +"verkooporder" #: ../../sales/products_prices/prices/pricing.rst:118 msgid "You can change the pricelists sequence by drag & drop in list view." msgstr "" +"U kunt de volgorde van de prijslijst wijzigen door deze te verslepen in de " +"lijstweergave" #: ../../sales/products_prices/prices/pricing.rst:121 msgid "Compute and show discount % to customers" -msgstr "" +msgstr "Bereken en toon korting% aan klanten" #: ../../sales/products_prices/prices/pricing.rst:123 msgid "" @@ -1653,7 +1626,7 @@ msgstr "" #: ../../sales/products_prices/prices/pricing.rst:126 msgid "Apply the option in the pricelist setup form." -msgstr "" +msgstr "Pas deze optie toe door ze aan te vinken bij \"instellingen\"" #: ../../sales/products_prices/prices/pricing.rst:133 msgid ":doc:`currencies`" @@ -1665,143 +1638,81 @@ msgstr "" #: ../../sales/products_prices/products.rst:3 msgid "Manage your products" -msgstr "" +msgstr "Beheer uw producten" #: ../../sales/products_prices/products/import.rst:3 -msgid "How to import my products" -msgstr "" +msgid "How to import products with categories and variants" +msgstr "Hoe producten importeren met categorieën en varianten" -#: ../../sales/products_prices/products/import.rst:6 -msgid "How to start" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:8 -msgid "Download the following import templates:" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:10 +#: ../../sales/products_prices/products/import.rst:5 msgid "" -"Partners: customers, vendors (no relation field, can be imported as is)" +"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 "Products (no relation field, can be imported as is)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:12 -msgid "Product Website Categories" -msgstr "" +msgid "How to customize the file" +msgstr "Hoe het bestand aanpassen" #: ../../sales/products_prices/products/import.rst:13 -msgid "Product Attributes & Values" +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:14 -msgid "Products with Categories & Attributes (3 & 4 must be imported first)" +#: ../../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 "" -"Download link: " -"https://drive.google.com/drive/folders/0B1uIL9E_zXrrTEp5eGI2dXJSUjg?usp=sharing" +"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 "" -"You can open them with any spreadsheets software (Microsoft Office, " -"OpenOffice, Google Drive, etc.)." +"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:21 -msgid "How to customize the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:23 -msgid "" -"Remove columns you don't need. Don't remove the first one (called *ID*, see " -"why here below)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:25 -msgid "" -"Don't change labels of columns you want to import. Otherwse Odoo won't match" -" the columns automatically." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:27 -msgid "" -"Feel free to add new columns but the fields need to exist in Odoo. If Odoo " -"fails in matching the column name with a field, you can make it manually " -"when importing by browsing a list of available fields." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:30 -msgid "Once modified, keep your file in .csv format." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:33 -msgid "How to import the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:35 -msgid "Go to the Products menu in Sales, Purchase, Website Admin, etc." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:36 -msgid "Switch to list view (top-right corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:37 -msgid "Click the *Import* button (top-left corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:38 -msgid "" -"Make sure all the columns match an existing field. If not select it manually" -" from the drop-down list." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:40 -msgid "Press * Validate* to test the import." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:41 -msgid "" -"If you get \"Everything seems valid.\" as result message, press *Import* to " -"process the real import. Otherwise correct the issues spotted during the " -"test." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:45 +#: ../../sales/products_prices/products/import.rst:24 msgid "Why an “ID” column" -msgstr "" +msgstr "Waarom een \"ID\" kolom" -#: ../../sales/products_prices/products/import.rst:47 +#: ../../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:50 +#: ../../sales/products_prices/products/import.rst:29 msgid "" "Setting an ID is not mandatory when importing but it helps in many cases:" msgstr "" +"Het instellen van een ID is niet verplicht bij invoer maar is in veel " +"gevallen handig :" -#: ../../sales/products_prices/products/import.rst:52 +#: ../../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:53 +#: ../../sales/products_prices/products/import.rst:32 msgid "Import relation fields (see here below)." -msgstr "" +msgstr "Relatievelden importeren (zie hieronder)." -#: ../../sales/products_prices/products/import.rst:56 +#: ../../sales/products_prices/products/import.rst:35 msgid "How to import relation fields" -msgstr "" +msgstr "Hoe relatievelden importeren" -#: ../../sales/products_prices/products/import.rst:58 +#: ../../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 " @@ -1809,7 +1720,7 @@ msgid "" "their own list menu." msgstr "" -#: ../../sales/products_prices/products/import.rst:62 +#: ../../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 \" / " @@ -1819,7 +1730,7 @@ msgstr "" #: ../../sales/products_prices/taxes.rst:3 msgid "Set taxes" -msgstr "" +msgstr "Stel belastingtarieven in" #: ../../sales/quotation.rst:3 msgid "Quotation" @@ -1831,11 +1742,11 @@ msgstr "Online offerte" #: ../../sales/quotation/online/creation.rst:3 msgid "How to create and edit an online quotation?" -msgstr "" +msgstr "Hoe maak en bewerk je een online offerte?" #: ../../sales/quotation/online/creation.rst:9 msgid "Enable Online Quotations" -msgstr "" +msgstr "Online offertes inschakelen" #: ../../sales/quotation/online/creation.rst:11 msgid "" @@ -1852,7 +1763,7 @@ msgstr "" #: ../../sales/quotation/online/creation.rst:25 msgid "Edit Your Online Quotations" -msgstr "" +msgstr "Wijzig uw online offertes" #: ../../sales/quotation/online/creation.rst:27 msgid "" @@ -1893,13 +1804,15 @@ msgstr "" #: ../../sales/quotation/online/creation.rst:52 msgid "Using Online Quotations" -msgstr "" +msgstr "Online offertes gebruiken" #: ../../sales/quotation/online/creation.rst:54 msgid "" "To share an online quotation with your customer, copy the URL of the online " "quotation, then share it with customer." msgstr "" +"Als u een online offerte wilt delen, kopieer dan de URL en deel deze met uw " +"klant." #: ../../sales/quotation/online/creation.rst:60 msgid "" @@ -1909,6 +1822,10 @@ msgid "" "will also receive a notification in the chatter within Odoo whenever the " "customer views the quotation." msgstr "" +"Als alternatief kan uw klant toegang krijgen tot zijn online offertes door " +"in te loggen via het klantenportaal. Uw klant accepteert of weigert de " +"offerte, print ze of onderhandelt de voorwaarden in de chatbox. Wanneer de " +"klant de offerte tekent ontvangt U een melding in de chatter binnen Odoo." #: ../../sales/quotation/setup.rst:3 msgid "Setup" diff --git a/locale/nl/LC_MESSAGES/website.po b/locale/nl/LC_MESSAGES/website.po index eb8d5caee..cff9d6541 100644 --- a/locale/nl/LC_MESSAGES/website.po +++ b/locale/nl/LC_MESSAGES/website.po @@ -10,7 +10,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-04-20 15:45+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Martin Trigaux , 2017\n" +"Last-Translator: Gunther Clauwaert , 2017\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -24,11 +24,11 @@ msgstr "Website" #: ../../website/optimize.rst:3 msgid "Optimize" -msgstr "" +msgstr "Optimaliseren" #: ../../website/optimize/google_analytics.rst:3 msgid "How to track your website's traffic in Google Analytics" -msgstr "" +msgstr "Hoe het verkeer op uw website traceren in Google Analytics" #: ../../website/optimize/google_analytics.rst:5 msgid "To follow your website's traffic with Google Analytics:" @@ -39,6 +39,8 @@ msgid "" "`Create a Google Analytics account `__ if" " you don't have any." msgstr "" +"Maak een Google Analytics-account aan " +"`__ als je nog geen hebt." #: ../../website/optimize/google_analytics.rst:10 msgid "" @@ -48,13 +50,15 @@ msgstr "" #: ../../website/optimize/google_analytics.rst:15 msgid "Copy the tracking ID to insert it in Odoo." -msgstr "" +msgstr "Kopieer het tracking-ID om het in Odoo op te slaan" #: ../../website/optimize/google_analytics.rst:20 msgid "" "Go to the *Configuration* menu of your Odoo's Website app. In the settings, " "turn on Google Analytics and paste the tracking ID. Then save the page." msgstr "" +"Ga naar het menu *Instellingen* van uw Odoo's website app. In instellingen " +"kopieer-en-plak jouw Google Analytics tracking-ID. Sla daarna op." #: ../../website/optimize/google_analytics.rst:27 msgid "" diff --git a/locale/ru/LC_MESSAGES/accounting.po b/locale/ru/LC_MESSAGES/accounting.po new file mode 100644 index 000000000..99c4c4b0e --- /dev/null +++ b/locale/ru/LC_MESSAGES/accounting.po @@ -0,0 +1,10522 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Denis Baranov , 2017\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../accounting.rst:5 +msgid "Accounting" +msgstr "" + +#: ../../accounting/bank.rst:3 +msgid "Bank & Cash" +msgstr "" + +#: ../../accounting/bank/feeds.rst:3 +msgid "Bank Feeds" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:3 +msgid "Import Coda statement files (Belgium only)" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:5 +msgid "" +"CODA is a file format for bank statements in Belgium. Most Belgian banks, as" +" well as the Isabel software, allows to download a CODA file with all your " +"bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:9 +msgid "" +"With Odoo, you can download an CODA file from your bank or accounting " +"software and import it directly in Odoo. This will create all bank " +"statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:14 +msgid "" +"Test now the feature `with this sample CODA file " +"`__" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:17 +#: ../../accounting/bank/feeds/manual.rst:12 +#: ../../accounting/bank/feeds/ofx.rst:18 +#: ../../accounting/bank/feeds/paypal.rst:11 +#: ../../accounting/bank/feeds/qif.rst:19 +#: ../../accounting/bank/feeds/synchronize.rst:26 +#: ../../accounting/bank/misc/batch.rst:21 +#: ../../accounting/bank/misc/interbank.rst:14 +#: ../../accounting/bank/reconciliation/use_cases.rst:20 +#: ../../accounting/bank/setup/foreign_currency.rst:22 +#: ../../accounting/bank/setup/manage_cash_register.rst:9 +#: ../../accounting/others/adviser/assets.rst:24 +#: ../../accounting/others/adviser/budget.rst:18 +#: ../../accounting/others/analytic/purchases_expenses.rst:18 +#: ../../accounting/others/analytic/timesheets.rst:16 +#: ../../accounting/others/configuration.rst:3 +#: ../../accounting/others/multicurrencies/exchange.rst:16 +#: ../../accounting/others/multicurrencies/how_it_works.rst:15 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:22 +#: ../../accounting/others/taxes/B2B_B2C.rst:60 +#: ../../accounting/others/taxes/retention.rst:23 +#: ../../accounting/others/taxes/taxcloud.rst:12 +#: ../../accounting/payables/misc/employee_expense.rst:17 +#: ../../accounting/payables/pay/check.rst:11 +#: ../../accounting/payables/pay/sepa.rst:26 +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:30 +#: ../../accounting/payables/supplier_bills/manage.rst:31 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:15 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:24 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:20 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:19 +#: ../../accounting/receivables/customer_payments/check.rst:39 +#: ../../accounting/receivables/customer_payments/check.rst:103 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:40 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:113 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:31 +msgid "Configuration" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:20 +msgid "Install the CODA feature" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:22 +msgid "" +"If you have installed the Belgian Chart of Account provided with Odoo, the " +"CODA import feature is already installed by default. In such a case, you can" +" move directly to the next section `Import your first coda file " +"`_" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:27 +msgid "" +"If CODA is not activated yet, you need to do it first. In the Accounting " +"application, go to the menu :menuselection:`Configuration --> Settings`. " +"From the accounting settings, check the option **Import of Bank Statements " +"in .CODA Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:33 +msgid "Import your first CODA file" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:35 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"**Dashboard**, and click on the button **More** on the bank account card. " +"Then, click on **Import Statement** to load your first CODA file." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:43 +msgid "" +"Load your CODA file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:49 +#: ../../accounting/bank/feeds/ofx.rst:42 +#: ../../accounting/bank/feeds/qif.rst:43 +msgid "" +"If the file is successfully loaded, you will get redirected to the bank " +"reconciliation screen with all the transactions to reconcile." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:55 +msgid "Importing CODA files" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:57 +msgid "" +"After having imported your first file, the Odoo accounting dashboard will " +"automatically propose you to import more files for your bank. For the next " +"import, you don't need to go to the **More** button anymore, you can " +"directly click on the link **Import Statement**." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:65 +msgid "" +"Every time you get a statement related to a new customer / supplier, Odoo " +"will ask you to select the right contact to reconcile the transaction. Odoo " +"learns from that operation and will automatically complete the next payments" +" you get or make to these contacts. This will speed up a lot the " +"reconciliation process." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:72 +msgid "" +"Odoo is able to automatically detect if some files or transactions have " +"already been imported. So, you should not worry about avoiding to import two" +" times the same file: Odoo will check everything for you before creating new" +" bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:78 +#: ../../accounting/bank/feeds/qif.rst:65 +msgid ":doc:`ofx`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:79 +#: ../../accounting/bank/feeds/ofx.rst:64 +msgid ":doc:`qif`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:80 +#: ../../accounting/bank/feeds/ofx.rst:66 +#: ../../accounting/bank/feeds/qif.rst:67 +msgid ":doc:`synchronize`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:81 +#: ../../accounting/bank/feeds/ofx.rst:67 +#: ../../accounting/bank/feeds/qif.rst:68 +msgid ":doc:`manual`" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:3 +#: ../../accounting/bank/feeds/manual.rst:21 +msgid "Register bank statements manually" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:6 +#: ../../accounting/bank/reconciliation/configure.rst:6 +#: ../../accounting/bank/reconciliation/use_cases.rst:6 +#: ../../accounting/others/adviser/budget.rst:6 +#: ../../accounting/others/analytic/purchases_expenses.rst:6 +#: ../../accounting/others/multicurrencies.rst:3 +#: ../../accounting/others/multicurrencies/exchange.rst:6 +#: ../../accounting/others/multicurrencies/how_it_works.rst:6 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:6 +#: ../../accounting/others/reporting/customize.rst:6 +#: ../../accounting/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:8 +msgid "" +"With Odoo, you can import your bank statements, synchronize with your bank " +"but also register your bank statements manually." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:14 +msgid "" +"No special configuration is necessary to register invoices. All you need to " +"do is install the accounting app." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:24 +msgid "Create your Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:26 +msgid "" +"In the Dashboard, click on the button **New Statement** related to the bank " +"journal. If some reconciliations need to be done, the New Statement link " +"will be found underneath." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:33 +msgid "" +"Just fill in the fields according the the information written on your bank " +"statement. The reference can be filled in manually or you can leave it " +"empty. We recommend to fill in the partner to ease the reconciliation " +"process." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:38 +msgid "" +"The difference between the starting balance and the ending balance should be" +" equal to the computed balance." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:44 +msgid "When you are done, click on **Save**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:47 +msgid "Reconcile your Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:49 +msgid "" +"You can choose to directly reconcile the statement by clicking on the button" +" |manual04|" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:54 +msgid "" +"You can also start the reconciliation process from the dashboard by clicking" +" on **Reconcile # Items**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:60 +msgid "" +"Click on **Validate** to reconcile your bank statement. If the partner is " +"missing, Odoo will ask you to **select a partner**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:68 +msgid "Hit CTRL-Enter to reconcile all the balanced items on the sheets." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:71 +msgid "Close Bank Statements from the reconciliation" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:73 +msgid "" +"If the balance is correct, you can directly close the statement from the " +"reconciliation by clicking on |manual07|." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:78 +msgid "" +"Otherwise, click on |manual08| to open the statement and correct the issue." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:84 +msgid "Close Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:86 +msgid "" +"On the accounting dashboard, click on the More button of your bank journal, " +"then click on Bank Statements." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:92 +msgid "To close the bank statement, just click on **Validate**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:99 +msgid ":doc:`../reconciliation/use_cases`" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:100 +#: ../../accounting/bank/reconciliation/use_cases.rst:115 +msgid ":doc:`../feeds/synchronize`" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:3 +msgid "Import OFX statement files" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:5 +msgid "" +"Open Financial Exchange (OFX) is a unified specification for the electronic " +"exchange of financial data between financial institutions, businesses and " +"consumers via the Internet." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:9 +msgid "" +"With Odoo, you can download an OFX file from your bank or accounting " +"software and import it directly in your Odoo instance. This will create all " +"bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:15 +msgid "" +"Test now the feature `with this sample OFX file " +"`__" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:20 +msgid "" +"In order to import OFX statements, you need to activate the feature in Odoo." +" In the Accounting application, go to the menu :menuselection:`Configuration" +" --> Settings`. From the accounting settings, check the bank statements " +"option **Import in .OFX Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:28 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"Dashboard, and click on the **More** button of the bank account. Then, click" +" on **Import Statement** to load your first OFX file." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:36 +msgid "" +"Load your OFX file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:46 +msgid "Importing OFX files" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:48 +#: ../../accounting/bank/feeds/qif.rst:49 +msgid "" +"After having imported your first file, the Odoo accounting dashboard will " +"automatically propose you to import more files for your bank. For the next " +"import, you don't need to go to the **More** menu anymore, you can directly " +"click on the link **Import Statement**." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:56 +#: ../../accounting/bank/feeds/qif.rst:57 +msgid "" +"Every time you get a statement related to a new customer / supplier, Odoo " +"will ask you to select the right contact to reconcile the transaction. Odoo " +"learns from that operation and will automatically complete the next payments" +" you get or do to these contacts. This will speed up a lot the " +"reconciliation process." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:65 +#: ../../accounting/bank/feeds/qif.rst:66 +msgid ":doc:`coda`" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:3 +msgid "How to synchronize your PayPal account with Odoo?" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:5 +msgid "" +"With Odoo, you can synchronize your PayPal account. That way, you don't have" +" to record all your PayPal transaction in your favorite accounting software." +" The synchronization is done every 4 hours, and you can start reconciling " +"PayPal payments in just a click." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:14 +msgid "Install the account_yodlee module" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:16 +msgid "" +"Start by installing the **account_yodlee** module, if it is not already " +"installed. To do that, got the the menu :menuselection:`Accounting --> " +"Configuration --> Settings` of the accounting application. In the section " +"**Bank & Cash**, set the option **Bank Interface - Sync your bank feeds " +"automatically**." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:25 +msgid "Click on the apply button once it's done." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:28 +msgid "Setup your PayPal account" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:30 +msgid "" +"A PayPal account in Odoo is managed like a bank account. To setup your " +"PayPal account, use the menu :menuselection:`Configuration --> Bank " +"Accounts`. Create a new bank account and name it **PayPal**. In the bank " +"field, you can set **PayPal**." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:38 +msgid "" +"Once the PayPal account is created, go back to the **Accounting** dashboard " +"and click on the **Synchronize** button. In the dialog, choose **PayPal** as" +" the online institution and click on the configure button." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:45 +msgid "Then, you will have to provide your credentials to connect to PayPal." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:49 +msgid "" +"Your Paypal **must be in English** (if it is not the case you must change " +"the langage of your Paypal account) and if you use a Paypal business account" +" you must switch back to the old interface in order for it to work with " +"Online feeds (you can switch from new to old interface in your Paypal " +"account)." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:54 +msgid "" +"If you don't do this you will get a message either saying to put Paypal in " +"English or that the site is not supported." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:57 +msgid "" +"If you configured your Paypal account correctly you should get to the next " +"step of the Online feeds configuration. There you will have a screen with a " +"date to fetch transaction from and a list of account to choose. You must " +"choose the **Paypal balance** account." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:62 +msgid "" +"Once everything is done, you should see your PayPal transactions right in " +"Odoo and you can start reconciling your payments." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:65 +msgid "" +"Enjoy a full integration! You don't need to record transaction manually " +"anymore." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:69 +msgid "" +"You only have to provide your credentials the first time. Once done, Odoo " +"will synchronize with PayPal every 4 hours automatically." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:3 +msgid "Import QIF statement files" +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:5 +msgid "" +"Quicken Interchange Format (QIF) is an open specification for reading and " +"writing financial data to media (i.e. files). Although still widely used, " +"QIF is an older format than Open Financial Exchange (OFX) and you should use" +" the OFX version if you can export to both file formats." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:10 +msgid "" +"With Odoo, you can download a QIF file from your bank or accounting software" +" and import it directly in your Odoo instance. This will create all bank " +"statements." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:16 +msgid "" +"Test now the feature `with this sample QIF file " +"`__" +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:21 +msgid "" +"In order to import QIF statements, you need to activate the feature in Odoo." +" In the Accounting application, go to the menu :menuselection:`Configuration" +" --> Settings`. From the accounting settings, check the bank statements " +"option **Import in .QIF Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:29 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"Dashboard, and click on the **More** button of the bank account. Then, click" +" on **Import Statement** to load your first QIF file." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:37 +msgid "" +"Load your QIF file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:47 +msgid "Importing QIF files" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:3 +msgid "How to synchronize Odoo with your bank?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:5 +msgid "" +"Odoo is able to synchronize directly with your bank in order to get all bank" +" statements imported automatically in Odoo every 4 hours. Before moving " +"forward in this tutorial, you should check if your bank is supported. You " +"can find it out from the `Odoo Accounting Features " +"`__" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:13 +msgid "" +"Search for your bank name in the above page. If your bank appears in the " +"proposition, it means it is supported by Odoo. The countries which are fully" +" supported (meaning more than 95% of the banks) include: United States, " +"Canada, New Zealand, Austria. More than 30 countries are partially " +"supported, including: Colombia, India, France, Spain, etc." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:19 +msgid "In order to connect with the banks, Odoo uses two web-services:" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:21 +msgid "Plaid: for the main banks in the U.S." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:23 +msgid "Yodlee: for all other banks" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:29 +msgid "Odoo Online Users" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:31 +msgid "" +"If you we support banks of your country, the bank integration feature should" +" already been installed. If it's not installed, you can manually install the" +" module **account_yodlee**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:36 +msgid "Odoo Enterprise Users" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:38 +msgid "" +"If you plan to use a bank interface with your Odoo Enterprise subscription, " +"you don't have to do anything special, just make sure that your database is " +"registered with your Odoo Enterprise contract." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:42 +msgid "" +"you might want to check that you don't have a firewall/proxy blocking the " +"following addresses" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:44 +msgid "https://onlinesync.odoo.com/" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:45 +msgid "https://api.plaid.com/" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:49 +msgid "Sync your bank feeds" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:51 +msgid "" +"Once the Plaid or Yodlee interface is installed, you can connect Odoo to " +"your bank. To do that, click on **More** on the bank of your choice from the" +" accounting dashboard. In the menu, click on Settings to configure this bank" +" account." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:59 +msgid "" +"In the bank form, from the Bank Account tab, set the bank feeds option to " +"**Bank Synchronization**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:65 +msgid "" +"Once it's done, go back to your accounting dashboard. You should see a " +"**Online Synchronization** button on your bank card. Click on this button " +"and fill in your bank credentials." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:69 +msgid "" +"Once you filled in your credentials, your bank feeds will be synchronized " +"every 4 hours." +msgstr "" + +#: ../../accounting/bank/misc.rst:3 +#: ../../accounting/payables/misc/employee_expense.rst:187 +msgid "Miscellaneous" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:3 +msgid "How to manage batch deposits of checks?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:5 +msgid "" +"When your company's collections group receives checks from customers they " +"will often place this money into their bank account in batches. As this " +"money has been received in a physical form, someone in your company must " +"manually bring the checks to the bank." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:10 +msgid "" +"The bank will ask for a deposit ticket (also referred to as deposit slip) to" +" be filled-in with the details of the checks or cash to be included in the " +"transactions." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:14 +msgid "" +"The bank statement will reflect the total amount that was deposited and the " +"reference to the deposit ticket, not the individual checks." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:17 +msgid "" +"Odoo assists you to prepare and print your deposit tickets, and later on " +"reconcile them with your bank statement easily." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:24 +msgid "Install the batch deposit feature" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:26 +msgid "" +"In order to use the batch deposit feature, you need the module **Batch " +"Deposit** to be installed." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:31 +msgid "" +"Usually, this module is automatically installed if checks are widely used in" +" your country." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:34 +msgid "" +"To verify that the **Batch Deposit** feature is installed, go to the " +":menuselection:`Configuration --> Settings` menu of the accounting " +"application. Check the feature: **Allow batch deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:42 +msgid "Activate the feature on your bank accounts" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:44 +msgid "" +"Once you have installed this feature, Odoo automatically activate bank " +"deposits on your main bank accounts." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:47 +msgid "" +"To control which bank account can do batch deposit and which can not, go to " +"the journal that you defined to pay your checks, usually called 'Checks' or " +"'Bank' (see :doc:`../../receivables/customer_payments/check`, in the " +"Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:52 +msgid "" +"In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method" +" to **Batch Deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:58 +msgid "" +"If you check **Batch Deposit** in your debit method field, it means that " +"payments created using this Journal (called Payment method when you want to " +"make or receive a payment) will be applicable for the creation of Batch " +"Deposits afterwards." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:64 +msgid "From checks received to the bank" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:67 +msgid "Receive customer checks" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:69 +msgid "" +"Once your record checks received, record them on the bank account on which " +"you plan to deposit them. Once you select the bank account (or check journal" +" is you configured Odoo that way), Odoo proposes you to use a batch deposit." +" Select this option if you plan to deposit the check to your bank." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:78 +msgid "In the memo field, you can set the reference of the check." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:82 +msgid "" +"payments can be registered from the menu :menuselection:`Sales --> " +"Payments`, or directly on the related invoice, using the **Register " +"Payment** button." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:86 +msgid "Prepare a batch deposit" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:88 +msgid "" +"From the Accounting application, go to the menu :menuselection:`Sales --> " +"Batch Deposit`, and create a new **Batch Deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:94 +msgid "" +"Select the bank, then select the payments (checks) you want to add in this " +"deposit. By default, Odoo proposes you all the checks that have not been " +"deposit yet. That way, you can verify that you do not forget or lost a " +"check." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:102 +msgid "" +"You can then print the batch deposit, which will be very useful to prepare " +"the deposit slip that the bank usually requires to complete." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:106 +msgid "Reconciling the Deposit with the Bank Statement" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:108 +msgid "" +"When you process the bank statement reconciliation you will see the deposit " +"ticket number referenced in the statement. When the reconciliation process " +"is run, the user will be able to select the batch deposit that matches with " +"the bank statement line." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:116 +msgid "" +"If you select a batch deposit, Odoo will automatically fills all the checks " +"contained in this deposit for the matching. (2 checks were in this batch " +"deposit the example below)" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:124 +#: ../../accounting/payables/pay/sepa.rst:113 +msgid "Troubleshooting" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:127 +msgid "I don't see the batch deposit link on bank statements?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:129 +msgid "" +"If you don't have a batch deposit link in your bank statement, there could " +"be two reasons:" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:132 +msgid "" +"After having installed the batch deposit features, you need to reload the " +"page so that the browser is aware of this new feature. Just click the reload" +" button of your browser." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:136 +msgid "You do not have a batch deposit created for this bank account." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:139 +msgid "What happens if a check was refused?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:141 +msgid "" +"If you have a smaller amount in your bank statement than the actual amount " +"in your batch deposit, it probably means that one of your check has been " +"refused." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:145 +msgid "" +"In this case, click on the line related to this check to remove it from the " +"bank statement matching." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:3 +msgid "How to do a bank wire transfer from one bank to another?" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:5 +msgid "" +"A company might have several bank accounts or cash registers. Within odoo it" +" is possible to handle internal transfers of money with only a couple of " +"clicks." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:9 +msgid "" +"We will take the following example to illustrate. My company has two bank " +"accounts and I want to transfer 50.000 euros from one of our bank accounts " +"to the another one." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:17 +msgid "Check your Chart of Accounts and default transfer account" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:19 +msgid "" +"To handle internal transfers you need a transfer account in your charts of " +"account. Odoo will generate an account automatically based on the country of" +" your chart of account. To parameter your chart of account and check the " +"default transfer account go into your the accounting module, select " +":menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:25 +msgid "" +"Your chart of accounts will be pre-installed depending on the country " +"specified during your registration, it cannot be changed." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:31 +msgid "" +"The default transfer account will automatically be generated as well " +"depending on your country's legislation. If necessary it can be modified " +"from the same page." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:39 +msgid "Create a second bank account / Journal" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:41 +msgid "" +"Before we can register an internal transfer we need to add a new bank to our" +" accounting dashboard. To do so enter the accounting module, click on " +":menuselection:`Configuration --> Bank Accounts`. Create a new bank account." +" You should fill in the **Account Number**. You can also create and edit " +"your bank to specify your bank's details." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:50 +msgid "By saving the changes you now have 2 bank accounts." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:56 +msgid "Register an internal transfer from one bank to another." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:58 +msgid "" +"We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633 " +"9533 1498** account." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:62 +msgid "Log an internal transfer" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:64 +msgid "" +"The first step is to register the internal paiement. To do so, go into your " +"accounting dashboard. click on the **more** button of one of your banks and " +"select :menuselection:`New --> Internal transfer`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:71 +msgid "" +"Create a new payment. The payment type will automatically be set to internal" +" transfer. Select the **Bank** you want to transfer to, specify the " +"**Amount** and add a **Memo** if you wish." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:76 +msgid "" +"The memo is important if you wish to automatically reconcile (`see " +"`_)." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:81 +msgid "Save and confirm the changes to register the payment." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:83 +msgid "" +"In terms of accounting the money is now booked in the transfer account. " +"We'll need to import bank statements to book the money in the final " +"accounts." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:90 +msgid "Import bank statements and reconcile" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:92 +msgid "" +"Note that the bank balance computed by Odoo is different that the last " +"statement of your bank." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:98 +msgid "" +"That is because we did not import the bank statement confirming the " +"departure and arrival of the money. It's thus necessary to import your bank " +"statement and reconcile the payment with the correct bank statement line. " +"Once you receive your bank statements click the **new statement** button of " +"the corresponding bank to import them." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:107 +msgid "" +"Fill in your **Transactions line**. Once done, Odoo will display a " +"**Computed Balance**. that computed balance is the theorical end balance of " +"your bank account. If it's corresponding to the bank statement, it means " +"that no errors were made. Fill in the **Ending balance** and click on the " +"**Reconcile** button." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:115 +msgid "The following window will open:" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:120 +msgid "" +"You need to choose counterparts for the paiement. Select the correct bank " +"statement line corresponding to the paiement and click on the **reconcile** " +"button. Close the statement to finish the transaction" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:127 +msgid "" +"The same steps will need to be repeated once you receive your second bank " +"statement. Note that if you specify the correct amount, and the same memo in" +" both bank statement and payment transaction then the reconciliation will " +"happen automatically." +msgstr "" + +#: ../../accounting/bank/reconciliation.rst:3 +#: ../../accounting/others/reporting/main_reports.rst:153 +#: ../../accounting/overview/main_concepts/memento.rst:177 +#: ../../accounting/overview/main_concepts/terminologies.rst:19 +msgid "Bank Reconciliation" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:3 +msgid "Configure model of entries" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:8 +msgid "" +"In Odoo you have the possibility to pre-fill some accounting entries in " +"order to easily reconcile recurrent entries such as bank fees." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:11 +msgid "" +"We will take the following example to illustrate the concept : Every month " +"my company receives a bank fee cost, which depends of our bank account " +"current balance. This fee is thus variable." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:16 +msgid "Create Reconciliation Models" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:18 +msgid "" +"First, we need to configure two model reconciliation entries. To do so, go " +"to the accounting application dashboard. On your bank journal, click on " +":menuselection:`More --> Reconciliation Models`." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:25 +msgid "" +"We want to be able to book our bank fees easily. Our bank deducts fees " +"depending on our balance, meaning that it can vary every month." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:28 +msgid "" +"We create a button Label called Bank fees, select the correct account to " +"book those fees. Moreover we also need to specify that the amount type is " +"\"Percentage of balance\" with an Amount of 100%. This parameter will tell " +"Odoo to take the entire fee into account." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:36 +msgid "Save your changes when you are done." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:40 +msgid "" +"If the amount of your bank fee is fixed, you can as well select **Fixed** " +"under amount type and specify the amount in the amount tap." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:45 +msgid "" +"You can also use this functionality to handle discounts. Please refer to " +":doc:`../../receivables/customer_invoices/cash_discounts`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:49 +msgid "Register your payments based on a reconciliation model" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:51 +msgid "" +"Register your payment by importing your bank statements that will be " +"impacted by the payment of the bank fee." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:54 +msgid "" +"When doing the reconciliation, you can select an open balance and click the " +"**Reconciliation Model** button (in this case, **Bank Fees**) to get all the" +" relevant data instantly." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:61 +msgid "Finally, click on **Reconcile** to finish the process." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:65 +#: ../../accounting/bank/reconciliation/use_cases.rst:116 +msgid ":doc:`../feeds/manual`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:66 +#: ../../accounting/bank/reconciliation/use_cases.rst:114 +msgid ":doc:`../feeds/ofx`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:67 +msgid ":doc:`use_cases`" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:3 +msgid "Use cases in the bank reconciliation process?" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:8 +msgid "" +"Linking your bank statements with your accounting can be a lot of work. You " +"need to find invoices back, relate payments and that amount of " +"administration can cast a lot of time. Luckily, with Odoo you can very " +"easily link your invoices or any other payment with your bank statements." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:14 +msgid "Two reconciliation processes exist in Odoo." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:16 +msgid "We can directly register a payment on the invoices" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:17 +msgid "We can reconcile open invoices with bank statements" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:22 +msgid "" +"No special configuration is necessary to register invoices. All we need to " +"do is install the accounting app." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:29 +msgid "User cases" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:32 +msgid "Case 1: Payments registration" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:34 +msgid "" +"We received the payment proof for our invoice of 2100 euros issued to Smith " +"& Co." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:37 +msgid "" +"We start at our issued Invoice of 2100 euros for Smith & Co. Because the " +"sold product is a service we demand an immediate payment. Our accountant " +"only handles the bank statements at the end of week, so we have to mark the " +"invoice as paid so we can remember we can start the service with our " +"customer." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:43 +msgid "" +"Our customer send us a payment confirmation. We can thus register a payment " +"and mark the invoice as paid." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:49 +msgid "" +"By clicking on **register payment,** we are telling Odoo that our customer " +"paid the Invoice. We thus have to specify the amount and the payment method" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:56 +msgid "" +"We can always find the payment back from the Invoice by clicking on the " +":menuselection:`Info --> Open Payment`." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:62 +msgid "" +"The invoice has been paid and **the reconciliation has been done " +"automatically.**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:66 +msgid "Case 2: Bank statements reconciliations" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:68 +msgid "" +"We start at our issued Invoice of 3000 euros for Smith & Co. Let's also " +"assume that other Invoices are open for different customers." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:74 +msgid "" +"We receive our bank statement and not only the invoice of Smith & Co has " +"been paid, the one of Buzz of 92 euros as well." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:77 +msgid "" +"**Import** or **Create** the bank statements. Please refer to the documents " +"from the Bank Feeds section." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:83 +msgid "On the dashboard, click on **Reconcile # Items**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:88 +msgid "" +"If everything was right (correct partner name, right amount) odoo will do " +"the reconciliations **automatically**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:94 +msgid "If some issues are found, you will need to take **manual actions**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:96 +msgid "" +"For example, if the partner is missing from your bank statement, just fill " +"it in :" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:102 +msgid "" +"If the payment is done with a down payment, just check if it is all right " +"and validate all related payments :" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:110 +msgid "Hit CTRL-Enter to reconcile all the balanced items in the sheet." +msgstr "" + +#: ../../accounting/bank/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:3 +msgid "How to setup a new bank account?" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:5 +msgid "" +"In Odoo, you can manage multiple bank accounts. In this page, you will be " +"guided in the creation, modification or deletion of a bank or a credit card " +"account." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:10 +msgid "Edit a bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:12 +msgid "" +"To ease the process, a bank account is already there. We suggest you to edit" +" it first before filling your own bank information." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:15 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts` and " +"click on the **Bank** item. Edit it." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:23 +msgid "" +"Odoo will detect the bank account type (e.g. IBAN) to allow some payment " +"method like SEPA" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:28 +msgid "Create a bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:30 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts`. Click" +" on **create** and fill in the form. You can decide to show the bank account" +" number in you intend to send documents like sales orders or invoices. " +"Select the payments methods you support with this bank account." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:41 +msgid "" +"If you are working in a multi-company environnement, you'll have to switch " +"the company on your user preferences in order to add, edit or delete bank " +"accounts from another company." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:49 +msgid "View *Bank Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:60 +msgid "" +"The initial balance of a bank statement will be set to the closing balance " +"of the previous one within the same journal automatically." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:63 +msgid "Delete a bank account or credit card account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:65 +msgid "" +"From the list of bank accounts, select items to delete and delete them from " +"the action menu or go to the form and delete a single item from the action " +"menu" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:3 +msgid "How to manage a bank in a foreign currency?" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:5 +msgid "" +"In Odoo, every transaction is recorded in the default currency of the " +"company. Reports are all based on the currency of the company. But for " +"transactions occurring in another currency, Odoo stores both the value in " +"the currency of the company and the value in the currency of the " +"transaction." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:11 +msgid "" +"When you have a bank account in a foreign currencies, for every transaction," +" Odoo stores two values:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:14 +msgid "The debit/credit in the currency of the company" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:16 +msgid "The debit/credit in the currency of the bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:18 +msgid "" +"Currency rates are updated automatically using yahoo.com, or the European " +"Central bank web-services." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:25 +msgid "Activate the multi-currency feature" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:27 +msgid "" +"In order to allow your company to work with multiple currencies, you should " +"activate the multi-currency mode. In the accounting application, go into " +":menuselection:`Configuration --> Settings --> Accounting & Finance " +"Features` make sure the **Allow Multi-currencies** box is ticked. Provide a " +"**Currency Exchange Gain / Loss** account, then click on **Apply**." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:34 +msgid "Configure currencies" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:36 +msgid "" +"Once the Odoo is configured to support multiple currencies, you should " +"activate the currencies you plan to work with. To do that, go the menu " +":menuselection:`Configuration --> Currencies`. All the currencies are " +"created by default, but you should activate the ones you plan to support. " +"(to activate a currency, check his active field)" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:42 +msgid "" +"After having activated the currencies, you can configure the parameters to " +"automate the currency rate update. These options are also in the settings of" +" the Accounting application, in the bottom of the page:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:49 +msgid "Click on the **Update Now** link to update the currency rates now." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:52 +msgid "Create a new bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:54 +msgid "" +"In the accounting application, we first go to :menuselection:`Configuration " +"--> Accounting / Bank account`, and we create a new one." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:60 +msgid "" +"Once you save this bank account, Odoo will create all the documents for you:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:63 +msgid "An account in the trial balance" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:65 +msgid "A journal in your dashboard" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:67 +msgid "" +"Information about the bank account in the footer of your invoices if checked" +" the box **Show in Invoices Footer**" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:71 +msgid "Example: A vendor bill in a foreign currency" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:73 +msgid "" +"Based on the above example, let's assume we receive the following bill from " +"a supplier in China." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:76 +msgid "" +"In the :menuselection:`Purchase --> Vendor Bills` , this is what you could " +"see:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:81 +msgid "" +"Once you are ready to pay this bill, click on register payment on the bill " +"to record a payment." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:87 +msgid "" +"That's all you have to do. Odoo will automatically post the foreign exchange" +" gain or loss at the reconciliation of the payment with the invoice, " +"depending if the currency rate increased or decreased between the invoice " +"and the payment date." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:92 +msgid "" +"Note that you can pay a foreign bill with another currency. In such a case, " +"Odoo will automatically convert between the two currencies." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:96 +msgid "Customers Statements" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:98 +msgid "" +"Customers and vendor statements are managed in the currency of the invoice. " +"So, the amount due by your customer (to your vendor) is always expressed in " +"the currency of the invoice." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:102 +msgid "" +"If you have several invoices with different currencies for the same " +"customer, Odoo will split the customer statement by currency, as shown in " +"the report below." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:109 +msgid "" +"In the above report, the account receivable associated to Camptocamp is not " +"managed in a secondary currency, which means that it keeps every transaction" +" in his own currency. If you prefer, you can set the account receivable of " +"this customer with a secondary currency and all his debts will automatically" +" be converted in this currency." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:115 +msgid "" +"In such a case, the customer statement always has only one currency. In " +"general, this is not what the customer expect as he prefers to see the " +"amounts in the currency of the invoices he received;" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:3 +msgid "How to manage a cash register?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:5 +msgid "" +"The cash register is a journal to register receivings and payments " +"transactions. It calculates the total money in and out, computing the total " +"balance." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:14 +msgid "" +"Configure the Cash journal in :menuselection:`Accounting --> Configuration " +"--> Journals`." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:17 +msgid "" +"In the tab Journal Entries, the Default Debit and Credit Account can be " +"configured as well as the currency of the journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'Sale' for customer invoices journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'Purchase' for vendor bills journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Select 'Cash' or 'Bank' for journals that are used in customer or vendor " +"payments." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'General' for miscellaneous operations journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company related to this journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The journal entries of this journal will be named using this prefix." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Check this box if you don't want to share the same sequence for invoices and" +" refunds made from this journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field contains the information related to the numbering of the journal " +"entries of this journal." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field contains the information related to the numbering of the refund " +"entries of this journal." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for debit amount" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for credit amount" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The currency used to enter statement" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Means of payment for collecting money. Odoo modules offer various payments " +"handling facilities, but you can always use the 'Manual' payment method in " +"order to manage payments outside of the software." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Means of payment for sending money. Odoo modules offer various payments " +"handling facilities, but you can always use the 'Manual' payment method in " +"order to manage payments outside of the software." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"If this box is checked, the system will try to group the accounting lines " +"when generating them from invoices." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Used to register a profit when the ending balance of a cash register differs" +" from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Used to register a loss when the ending balance of a cash register differs " +"from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Whether this journal should be displayed on the dashboard or not" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Technical feature used to know whether check printing was enabled as payment" +" method." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Checks numbering sequence." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check this option if your pre-printed checks are not numbered." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Sequence number of the next printed check." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Check this box if this journal define a payment method that can be used in a" +" point of sale." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field depicts the maximum difference allowed between the ending balance" +" and the theoretical cash when closing a session, for non-POS managers. If " +"this maximum is reached, the user will have an error message at the closing " +"of his session saying that he needs to contact his manager." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:25 +msgid "Usage" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:28 +msgid "How to register cash payments?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:30 +msgid "" +"To register a cash payment specific to another customer, you should follow " +"these steps:" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:33 +msgid "" +"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register " +"Transactions`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:36 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:38 +msgid "" +"Register the transactions, specifying the customers linked to the " +"transaction" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:41 +msgid "Put money in" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:43 +msgid "" +"Put money in is used to placed your cash manually before starting your " +"transactions. From the Register Transactions window, go to " +":menuselection:`More --> Put money in`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:51 +msgid "Take money out" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:53 +msgid "" +"Take money out is used to collect/get yor your cash manually after ending " +"all your transactions. From the Register Transaction windows, go to " +":menuselection:`More --> Take money out`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:60 +msgid "" +"The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../accounting/others.rst:3 +#: ../../accounting/receivables/customer_invoices/overview.rst:108 +msgid "Others" +msgstr "" + +#: ../../accounting/others/adviser.rst:3 +msgid "Adviser" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:3 +msgid "Manage your fixed assets" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:5 +msgid "" +"The \"Assets\" module allows you to keep track of your fixed assets like " +"machinery, land and building. The module allows you to generate monthly " +"depreciation entries automatically, get depreciation board, sell or dispose " +"assets and perform reports on your company assets." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:10 +msgid "" +"As an example, you may buy a car for $36,000 (gross value) and you plan to " +"amortize it over 36 months (3 years). Every months (periodicity), Odoo will " +"create a depreciation entry automatically reducing your assets value by " +"$1,000 and passing $1,000 as an expense. After 3 years, this assets accounts" +" for $0 (salvage value) in your balance sheet." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:16 +msgid "" +"The different types of assets are grouped into \"Assets Types\" that " +"describe how to deprecate an asset. Here are two examples of assets types:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:20 +msgid "Building: 10 years, yearly linear depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:21 +msgid "Car: 5 years, monthly linear depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:27 +msgid "Install the Asset module" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:29 +msgid "Start by *installing the Asset module.*" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:31 +msgid "" +"Once the module is installed, you should see two new menus in the accounting" +" application:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:34 +msgid ":menuselection:`Adviser --> Assets`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:35 +msgid ":menuselection:`Configuration --> Asset Types`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:37 +msgid "" +"Before registering your first asset, you must :ref:`define your Asset Types " +"`." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:43 +msgid "Defining Asset Types" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:45 +msgid "" +"Asset type are used to configure all information about an assets: asset and " +"deprecation accounts, amortization method, etc. That way, advisers can " +"configure asset types and users can further record assets without having to " +"provide any complex accounting information. They just need to provide an " +"asset type on the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:51 +msgid "" +"You should create asset types for every group of assets you frequently buy " +"like \"Cars: 5 years\", \"Computer Hardware: 3 years\". For all other " +"assets, you can create generic asset types. Name them according to the " +"duration of the asset like \"36 Months\", \"10 Years\", ..." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:56 +msgid "" +"To define asset types, go to :menuselection:`Configuration --> Asset Types`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:63 +msgid "Create assets manually" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:65 +msgid "" +"To register an asset manually, go to the menu :menuselection:`Adviser --> " +"Assets`." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:71 +msgid "" +"Once your asset is created, don't forget to Confirm it. You can also click " +"on the Compute Depreciation button to check the depreciation board before " +"confirming the asset." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:77 +msgid "" +"if you create asset manually, you still need to create the supplier bill for" +" this asset. The asset document will only produce the depreciation journal " +"entries, not those related to the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:82 +msgid "Explanation of the fields:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "When an asset is created, the status is 'Draft'." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"If the asset is confirmed, the status goes in 'Running' and the depreciation" +" lines can be posted in the accounting." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"You can manually close an asset when the depreciation is over. If the last " +"line of depreciation is posted, the asset automatically goes in that status." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross value of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "It is the amount you plan to have that you cannot depreciate." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Choose the method to use to compute the amount of depreciation lines." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Linear: Calculated on basis of: Gross Value / Number of Depreciations" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Degressive: Calculated on basis of: Residual Value * Degressive Factor" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Choose the method to use to compute the dates and number of depreciation " +"lines." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Number of Depreciations: Fix the number of depreciation lines and the time" +" between 2 depreciations." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Ending Date: Choose the time between 2 depreciations and the date the " +"depreciations won't go beyond." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Indicates that the first depreciation entry for this asset have to be done " +"from the purchase date instead of the first January / Start date of fiscal " +"year" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The number of depreciations needed to depreciate your asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The amount of time between two depreciations, in months" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:88 +msgid "Try creating an *Asset* in our online demonstration" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:91 +msgid "Create assets automatically from a supplier bill" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:93 +msgid "" +"Assets can be automatically created from supplier bills. All you need to do " +"is to set an asset category on your bill line. When the user will validate " +"the bill, an asset will be automatically created, using the information of " +"the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:100 +msgid "" +"Depending on the information on the asset category, the asset will be " +"created in draft or directly validated\\ *.* It's easier to confirm assets " +"directly so that you won't forget to confirm it afterwards. (check the field" +" *Skip Draft State* on *Asset Category)* Generate assets in draft only when " +"you want your adviser to control all the assets before posting them to your " +"accounts." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:107 +msgid "" +"if you put the asset on the product, the asset category will automatically " +"be filled in the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:111 +msgid "How to deprecate an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:113 +msgid "" +"Odoo will create depreciation journal entries automatically at the right " +"date for every confirmed asset. (not the draft ones). You can control in the" +" depreciation board: a green bullet point means that the journal entry has " +"been created for this line." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:118 +msgid "" +"But you can also post journal entries before the expected date by clicking " +"on the green bullet and forcing the creation of related depreciation entry." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:125 +msgid "" +"In the Depreciation board, click on the red bullet to post the journal " +"entry. Click on the :guilabel:`Items` button on the top to see the journal " +"entries which are already posted." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:130 +msgid "How to modify an existing asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:132 +msgid "Click on :guilabel:`Modify Depreciation`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:133 +msgid "Change the number of depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:135 +msgid "Odoo will automatically recompute a new depreciation board." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:138 +msgid "How to record the sale or disposal of an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:140 +msgid "" +"If you sell or dispose an asset, you need to deprecate completly this asset." +" Click on the button :guilabel:`Sell or Dispose`. This action will post the " +"full costs of this assets but it will not record the sales transaction that " +"should be registered through a customer invoice." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:3 +msgid "How to manage a financial budget?" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:8 +msgid "" +"Managing budgets is an essential part of running a business. It allows you " +"to measure your actual financial performance against the planned one. Odoo " +"manages its budgets using both General and Analytic Accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:12 +msgid "" +"We will use the following example to illustrate. We just started a project " +"with Smith&Co and we would like to budget the incomes and expenses of that " +"project. We plan to have a revenue of 1000 and we don't want to spend more " +"than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:20 +msgid "" +"First we need to install the relevant apps to use budgeting. The main module" +" is the accounting app. Go in the app module and install the **Accounting " +"and Finance** app." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:27 +msgid "" +"Further configuration is as well necessary. Go to :menuselection:`Accounting" +" module --> Configuration --> Settings` and enable the **Budget management**" +" feature" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:34 +msgid "" +"If we want to be precise and point specific invoices and vendors bills to " +"our budget, you should enable the Analytic accounting as well. If we don't " +"we will only be able to budget the total amount of general accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:40 +msgid "Budgetary Positions" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:42 +msgid "" +"Budgetary positions are the general accounts for which you want to keep " +"budgets (typically expense or income accounts). They need to be defined so " +"Odoo can know it which accounts he needs to go get the budget information. " +"Some might be already installed with your chart of accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:48 +msgid "" +"To define the positions enter the :menuselection:`Accounting module --> " +"Configuration --> Budgetary Positions`." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:51 +msgid "" +"For our example we need to define what accounts relates to our project's " +"expenses. Create a position and add items to select the accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:57 +msgid "" +"In this case we select the three relevant accounts used wherein we will book" +" our expenses." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:63 +msgid "Click on *Select*." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:68 +msgid "Save the changes to confirm your Budgetary position." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:70 +msgid "" +"Repeat this steps to create a revenue budgetary position. Only in this case " +"select the relevant income accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:74 +msgid "Analytical account" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:76 +msgid "" +"If you wish to point specific invoices or vendor bills to your budget you " +"need to use analytical accounting. Odoo needs to know which costs or " +"expenses are relevant to a specified budget. To do so we need to link our " +"invoices and expenses to a defined analytical account. Create an analytical " +"account by entering the Accounting module and clicking " +":menuselection:`Advisers --> Analytic Accounts --> Open Charts`. Create a " +"new Account called Smith&Co project and select the related partner." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:88 +msgid "Set a budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:90 +msgid "" +"Let's now set our targets for our budget. We specified that we expect to " +"gain 1000 with this project and we would like not to spend more than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:94 +msgid "" +"To set those targets, enter the accounting app, select " +":menuselection:`Advisers --> Budgets` and create a new Budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:97 +msgid "" +"We have to give a name to the budget. In this case we'll call it \"Smith " +"Project\". Select the period wherein the budget will be applicable. Next add" +" an item to specify your targets in the Budget Line." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:104 +msgid "" +"Select the Budgetary Position related to the Budget Line. In other words, " +"select the position that points to the accounts you want to budget. In this " +"case we will start with our 700 maximum charge target. Select the \"Cost\" " +"Budgetary Position and specify the Planned Amount. As we are recording a " +"cost, we need to specify a **negative amount**. Finally, select the " +"corresponding analytic account." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:114 +msgid "" +"Click on **Save & new** to input the revenue budget. The Budgetary Position " +"is Revenue and the Planned Amount is 1000. Save and close" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:117 +msgid "You'll need to **Confirm** and **Approve** the budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:120 +msgid "Check your budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:122 +msgid "" +"You can check your budget at any time. To see the evolution, let's book some" +" Invoices and Vendors Bills." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:127 +msgid "" +"if you use analytical accounts remember that you need to specify the account" +" in the invoice and / or purchase line." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:131 +msgid "for more information about booking invoices and purchase orders see:" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:133 +msgid ":doc:`../../receivables/customer_invoices/overview`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:134 +msgid ":doc:`../../../purchase/overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:136 +msgid "Go back in the budget list and find the Smith Project." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:138 +msgid "" +"Via the analytical account, Odoo can account the invoice lines and purchase " +"lines booked in the accounts and will display them in the **Practical " +"Amount** column." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:147 +msgid "" +"The theoretical amount represents the amount of money you theoretically " +"could have spend / should have received in function of the date. When your " +"budget is 1200 for 12 months (january to december), and today is 31 of " +"january, the theoretical amount will be 1000, since this is the actual " +"amount that could have been realised." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:3 +msgid "How to do a year end in Odoo? (close a fiscal year)" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:5 +msgid "" +"Before going ahead with closing a fiscal year, there are a few steps one " +"should typically take to ensure that your accounting is correct, up to date," +" and accurate:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:9 +msgid "" +"Make sure you have fully reconciled your **bank account(s)** up to year end " +"and confirm that your ending book balances agree with your bank statement " +"balances." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:13 +msgid "Verify that all **customer invoices** have been entered and approved." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:15 +msgid "Confirm that you have entered and agreed all **vendor bills**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:17 +msgid "Validate all **expenses**, ensuring their accuracy." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:19 +msgid "" +"Corroborate that all **received payments** have been entered and recorded " +"accurately." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:23 +msgid "Year-end checklist" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:25 +msgid "Run a **Tax report**, and verify that your tax information is correct." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:27 +msgid "Reconcile all accounts on your **Balance Sheet**:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:29 +msgid "" +"Agree your bank balances in Odoo against your actual bank balances on your " +"statements. Utilize the **Bank Reconciliation** report to assist with this." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:33 +msgid "" +"Reconcile all transactions in your cash and bank accounts by running your " +"**Aged Receivables** and **Aged Payables** reports." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:36 +msgid "" +"Audit your accounts, being sure to fully understand the transactions " +"affecting them and the nature of the transactions, making sure to include " +"loans and fixed assets." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:40 +msgid "" +"Run the optional **Payments Matching** feature, under the **More** dropdown " +"on the dashboard, validating any open **Vendor Bills** and **Customer " +"Invoices** with their payments. This step is optional, however it may assist" +" the year-end process if all outstanding payments and invoices are " +"reconciled, and could lead finding errors or mistakes in the system." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:47 +msgid "" +"Your accountant/bookkeeper will likely verify your balance sheet items and " +"book entries for:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:50 +msgid "" +"Year-end manual adjustments, using the **Adviser Journal Entries** menu (For" +" example, the **Current Year Earnings** and **Retained Earnings** reports)." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:54 +msgid "**Work in Progress**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:56 +msgid "**Depreciation Journal Entries**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:58 +msgid "**Loans**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:60 +msgid "**Tax adjustments**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:62 +msgid "" +"If your accountant/bookkeeper is going through end of the year auditing, " +"they may want to have paper copies of all balance sheet items (such as " +"loans, bank accounts, prepayments, sales tax statements, etc...) to agree " +"these against your Odoo balances." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:67 +msgid "" +"During this process, it is good practice to set the **Lock date for Non-" +"Advisers** to the last day of the preceding financial year, which is set " +"under the accounting configuration. This way, the accountant can be " +"confident that nobody is changing the previous year transactions while " +"auditing the books." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:77 +msgid "Closing the fiscal year" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:79 +msgid "" +"In Odoo there is no need to do a specific year end closing entry in order to" +" close out income statement accounts. The reports are created in real-time, " +"meaning that the **Income statement** corresponds directly with the year-end" +" date you specify in Odoo. Therefore, any time you generate the **Income " +"Statement**, the beginning date will correspond with the beginning of the " +"**Fiscal Year** and the account balances will all be 0." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:86 +msgid "" +"Once the accountant/bookkeeper has created the journal entry to allocate the" +" **Current Year Earnings**, you should set the **Lock Date** to the last day" +" of the fiscal year. Making sure that before doing so, you confirm whether " +"or not the current year earnings in the **Balance Sheet** is correctly " +"reporting a 0 balance." +msgstr "" + +#: ../../accounting/others/analytic.rst:3 +msgid "Analytic" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:3 +msgid "How to track costs of purchases, expenses, subcontracting?" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:8 +msgid "" +"Thanks to analytical accounting we can track costs of purchases, expenses " +"and subcontracting in the accounting module." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:11 +msgid "" +"We'll take the following example. We sold a consulting package for a " +"customer. The package is all inclusive meaning no extra cost can be added. " +"We would however like to follow which cost were attached to this transaction" +" as we need to pay for purchases, expenses, and subcontracting costs related" +" to the project." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:20 +msgid "" +"The following modules needs to be installed to track cost. Enter the app " +"module and install the following apps:" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:28 +msgid "" +"Please note that the applications provided by these apps only allows us to " +"**track** the costs. We won't be able to automatically re invoice those " +"costs to our customers. To track and **re invoice costs** you should install" +" the Sales management app as well." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:37 +msgid "Enable Analytical accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:39 +msgid "" +"Next step is to activate the analytical accounting. In the accounting app, " +"select :menuselection:`Configuration --> Settings` and thick the Analytic " +"accounting box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:46 +msgid "" +"Moreover, scroll down and tick the **Analytic accounting for purchases** " +"box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:52 +msgid "Don't forget to save your changes." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:55 +msgid "Create an Analytical account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:57 +msgid "" +"First of all you should create an Analytical account on which you can point " +"all your expenses. Enter the accounting app, select " +":menuselection:`Configuration --> Analytic Accounts`. Create a new one. In " +"this case we will call it \"consulting pack\" for our customer Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:65 +msgid "We will point all our costs to this account to keep track of them." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:68 +msgid "Record an expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:70 +msgid "" +"We start by booking an expense. Our IT technician had to take a train to go " +"see our customer. He paid for his ticket himself." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:75 +msgid "Create an expense product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:77 +msgid "" +"We first need to create an expense product. Enter the **Expense** module, " +"Click on :menuselection:`Configuration --> Expense Products`. Create a new " +"product called Train ticket and set the cost price to 15.50 euros. Make sure" +" the **Can be expensed** box is ticked." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:86 +msgid "Book the expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:88 +msgid "" +"Enter the Expense module, click on :menuselection:`My expenses --> Create`. " +"Select the Train ticket product and link it to the analytical account " +"discussed above." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:95 +msgid "" +"Submit to manager and wait for the manager to approve and post the journal " +"entries." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:99 +msgid "Create a Purchase Order linked to the analytical account" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:102 +msgid "Purchase Product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:104 +msgid "" +"We also need to buy a software for our customers. In the purchase app create" +" a purchase order for the software product. (please refer to the following " +"document: :doc:`../../../purchase/overview/process/from_po_to_invoice`). " +"Within the line we can link the product's cost with the analytical account. " +"Specify the order line and select the correct analytical account. Confirm " +"the sale." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:114 +msgid "" +"Accept the delivery and enter the invoice. Once the invoice is entered the " +"cost price (**Vendor Price** field) will be booked in the analytical " +"account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:118 +msgid "Subcontracting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:120 +msgid "" +"The purchase module can be used in the same way as seen previously to handle" +" subcontracting. if we purchase a service from another company we can re " +"invoice this cost by linking the purchase order line to the correct " +"analytical account. We simply need to create the correct vendors product." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:128 +msgid "You can also track cost with timesheets, see: :doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:131 +msgid "Track costs in accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:133 +msgid "" +"Now that everything is booked and points to the analytical account. Simply " +"open it to check the costs related to that account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:136 +msgid "" +"Enter the accounting module, click on :menuselection:`Advisers --> Analytic " +"Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:139 +msgid "" +"Select \"consulting pack - Smith\" and click on the cost and revenue button " +"to have an overview of all cost linked to the account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:147 +msgid "" +"If you would like to have the revenue as well you should invoice the " +"Consulting Pack in the Invoice menu and link the invoice line to this same " +"analytical account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:3 +msgid "How to track costs of human resources with timesheets?" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:5 +msgid "" +"Human resource of course has a cost. It is interesting to see how much a " +"particular contract costs the company in term of human power in relation to " +"the invoiced amounts." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:9 +msgid "" +"We will take the following example: Our two employees **Harry Potter** and " +"**Cedric Digory** both work on a **Consultancy pack** for our customer " +"**Smith&Co**. Harry is paid 18€ p.h. and Cedric's salary is 12€ p.h. We " +"would like to track their timesheet costs within the accounting app, and " +"compare them with the revenue of the consultancy service." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:18 +msgid "" +"First, install the three applications necessary to use this functionality, " +"namely **Accounting**, **Sales** and **Timesheet**. Enter the apps module " +"name and install them." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:31 +msgid "" +"Next you will need to enable analytical accounting. To do so enter the " +"**Accounting app**. Select :menuselection:`Configuration --> Settings` and " +"tick the **Analytic accounting** option (see picture below)" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:38 +msgid "Apply your changes." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:41 +msgid "Create an employee" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:43 +msgid "" +"In order to check the revenue of an employee you need to have one. To create" +" an employee enter the **Employee** app. Select **Employees** and create a " +"new employee, fill in the name and the basic information." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:47 +msgid "" +"On the employee sheet enter the **HR settings** tab. Here you are able to " +"specify the **Timesheet Cost** of your employee. In this case Harry has a " +"cost of 18 euros / hours. We will thus fill in 18 in this field." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:55 +msgid "" +"If you want the employee to be able to enter timesheets he needs to be " +"related to a User." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:58 +msgid "" +"Repeat the operation to create the Cedric Digory employee. Don't forget to " +"specify its related user and **Timesheet Costs**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:62 +msgid "Issue a Sales Order" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:64 +msgid "" +"We created two employees called Harry Potter and Cedric Diggory in the " +"**Employee** app. Both of them will work on a consultancy contract for our " +"customer Smith&Co where they will point their hours on a timesheet." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:68 +msgid "" +"We thus need to create a **sales order** with a **service** product invoiced" +" **based on time and material** and tracked by timesheets with **hours** as " +"unit of measures." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:75 +msgid "" +"For more information on how to create a sales order based on time and " +"material please see: *How to invoice based on time and material* (Work in " +"Progress)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:82 +msgid "" +"We save a Sales Order with the service product **External Consulting**. An " +"analytical account will automatically be generated once the **Sales Order** " +"is confirmed. Our employees will have to point to that account (in this case" +" **SO002-Smith&Co**) in order to be able to invoice their hours (see picture" +" below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:92 +msgid "Fill in timesheet" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:94 +msgid "" +"As an employee linked to a user, Harry can enter the **Timesheet** app and " +"specify his timesheets for the contract. Logged on Harry's account we enter " +"the **Timesheet** app and enter a detailed line pointing to the **Analytical" +" Account** discussed above." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:99 +msgid "Harry worked three hours on a SWOT analysis for Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:104 +msgid "" +"In the meantime, Cedric discussed businesses needs with the customer for 1 " +"hour and specified it as well in his personal timesheet, pointing as well on" +" the **Analytic Account**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:108 +msgid "" +"In the **Sales Order** we notice that the delivered amounts of hours is " +"automatically computed (see picture below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:115 +msgid "Analytic accounting" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:117 +msgid "" +"Thanks to analytic accounts we are able to have an overview of HR cost and " +"revenues. All the revenues and cost of this transactions have been " +"registered in the **SO002-Smith&Co** account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:121 +msgid "We can use two methods to analyze this situation." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:124 +msgid "Without filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:126 +msgid "" +"If we pointed all our costs and revenues of the project on the correct " +"analytical account we can easily retrieve the cost and revenues related to " +"this analytical account. Enter the *Accounting* app, select " +":menuselection:`Adviser --> Analytic Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:131 +msgid "" +"Note : you can specify a period for **Analysis**. If you want to open the " +"current situation you should keep the fields empty. We can already note the " +"credit and debit balance of the account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:138 +msgid "" +"If we click on the account a special button is provided to have the details " +"of cost and revenues (see picture below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:144 +msgid "" +"Click the button **Cost/Revenue** to have an overview of cost and revenues " +"with the corresponding description." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:148 +msgid "With filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:150 +msgid "We can thus filter this information from the **Analytic Entries**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:152 +msgid "" +"Enter the **Accounting** app, and click on :menuselection:`Adviser --> " +"Analytic Entries`. In this menu we have several options to analyse the human" +" resource cost." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:155 +msgid "" +"We filter on the **Analytic account** so we can see the cost and revenues of" +" the project. Add a custom **Filter** where the **Analytic Account** " +"contains the **Sales Order** number." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:162 +msgid "" +"In the results we see timesheets activities and invoiced lines with the " +"corresponding costs and revenues." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:168 +msgid "" +"We can group the different analytical accounts together and check their " +"respective revenues. Simply group by **Analytic account** and select the " +"**Graph view** to have a clear overview." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:3 +msgid "Analytic account use cases" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:5 +msgid "The analytic accounting can be used for several purposes:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:7 +msgid "analyse costs of a company" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:9 +msgid "reinvoice time to a customer" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:11 +msgid "analyse performance of a service or a project" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:13 +msgid "" +"To manage analytic accounting, you have to activate it in " +":menuselection:`Configuration --> Settings`:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:19 +msgid "" +"To illustrate analytic accounts clearly, you will follow three use cases, " +"each in one of three different types of company:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:22 +msgid "Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:24 +msgid "Law Firm: reinvoice spent hours" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:26 +msgid "IT/Services Company: performance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:29 +msgid "Case 1: Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:31 +msgid "" +"In industry, you will often find analytic charts of accounts structured into" +" departments and products the company itself is built on." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:34 +msgid "" +"The objective is to examine the costs, sales and margins by " +"department/resources and by product. The first level of the structure " +"comprises the different departments, and the lower levels represent the " +"product ranges the company makes and sells." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:39 +msgid "" +"**Analytic Chart of Accounts for an Industrial Manufacturing Company**:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:41 +msgid "Marketing Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:43 +msgid "Commercial Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:45 +msgid "Administration Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:47 +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:80 +msgid "Production Range 1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:49 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "Production Range 2" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:51 +msgid "" +"In daily use, it is useful to mark the analytic account on each purchase " +"invoice. When the invoice is approved, it will automatically generate the " +"entries for both the general and the corresponding analytic accounts. For " +"each entry on the general accounts, there is at least one analytic entry " +"that allocates costs to the department which incurred them." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:58 +msgid "" +"Here is a possible breakdown of some general accounting entries for the " +"example above, allocated to various analytic accounts:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**General accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**Analytic accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Title**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Account**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Debit**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Credit**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +msgid "**Value**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "Purchase of Raw Material" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "2122" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "1500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "-1 500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +msgid "Subcontractors" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +msgid "-450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +msgid "Credit Note for defective materials" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:70 +msgid "200" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:72 +msgid "Transport charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "Staff costs" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "2121" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "10000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "Marketing" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:80 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "-2 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "Commercial" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "-3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Administrative" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +msgid "-1 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "PR" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "-400" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:87 +msgid "" +"The analytic representation by department enables you to investigate the " +"costs allocated to each department in the company. The analytic chart of " +"accounts shows the distribution of the company's costs using the example " +"above:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:94 +msgid "" +"In this example of a hierarchical structure in Odoo, you can analyse not " +"only the costs of each product range, but also the costs of the whole " +"production. A report that relates both general accounts and analytic " +"accounts enables you to get a breakdown of costs within a given department." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:103 +msgid "" +"The examples above are based on a breakdown of the costs of the company. " +"Analytic allocations can be just as effective for sales. That gives you the " +"profitability (sales - costs) of different departments." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:107 +msgid "" +"This analytic representation by department is generally used by trading " +"companies and industries." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:110 +msgid "" +"A variantion of this, is not to break it down by sales and marketing " +"departments, but to assign each cost to its corresponding product range. " +"This will give you an analysis of the profitability of each product range." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:115 +msgid "" +"Choosing one over the other depends on how you look at your marketing " +"effort. Is it a global cost allocated in some general way, or is each " +"product range responsible for its own marketing costs?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:120 +msgid "Case 2: Law Firm: costs of human resources?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:122 +msgid "" +"Law firms generally adopt management by case, where each case represents a " +"current client file. All of the expenses and products are then attached to a" +" given file/analytic account." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:126 +msgid "" +"A principal preoccupation of law firms is the invoicing of hours worked, and" +" the profitability by case and by employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:129 +msgid "" +"Mechanisms used for encoding the hours worked will be covered in detail in " +"timesheet documentation. Like most system processes, hours worked are " +"integrated into the analytic accounting. In the employee form, specify the " +"cost of the employee. The hourly charge is a function of the employee's " +"cost." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:135 +msgid "" +"So a law firm will opt for an analytic representation which reflects the " +"management of the time that employees work on the different customer cases." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:139 +msgid "" +"Billing for the different cases is a bit unusual. The cases do not match any" +" entry in the general account nor do they come from purchase or sales " +"invoices. They are represented by the various analytic operations and do not" +" have exact counterparts in the general accounts. They are calculated on the" +" basis of the hourly cost per employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:145 +msgid "" +"At the end of the month when you pay salaries and benefits, you integrate " +"them into the general accounts but not in the analytic accounts, because " +"they have already been accounted for in billing each account. A report that " +"relates data from the analytic and general accounts then lets you compare " +"the totals, so you can readjust your estimates of hourly cost per employee " +"depending on the time actually worked." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:153 +msgid "" +"The following table shows an example of different analytic entries that you " +"can find for your analytic account:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Amount**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**General Account**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "Study the file (1 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +#: ../../accounting/others/analytic/usage.rst:161 +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Case 1.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "-15" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "Search for information (3 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "-45" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Consultation (4 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Case 2.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "-60" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "Service charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:165 +msgid "280" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "705 – Billing services" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Stationery purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "-42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "601 – Furniture purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Fuel Cost -Client trip" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "-35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "613 – Transports" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "Staff salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "6201 – Salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:174 +msgid "" +"Such a structure allows you to make a detailed study of the profitability of" +" various transactions." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:177 +msgid "" +"For more details about profitablity, please read the following document: " +":doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:180 +msgid "" +"But analytical accounting is not limited to a simple analysis of the " +"profitability of different customer. The same data can be used for automatic" +" recharging of the services to the customer at the end of the month. To " +"invoice customers, just link the analytic account to a sale order and sell " +"products that manage timesheet or expenses ." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:187 +msgid "Case 3: IT Services Company: perfomance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:189 +msgid "Most IT service companies face the following problems:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:191 +msgid "project planning," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:193 +msgid "invoicing, profitability and financial follow-up of projects," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:195 +msgid "managing support contracts." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:197 +msgid "" +"To deal with these problems, you would use an analytic chart of accounts " +"structured by project and by sale order." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:200 +msgid "" +"The management of services, expenditures and sales is similar to that " +"presented above for lawyers. Invoicing and the study of profitability are " +"also similar." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:204 +msgid "" +"But now look at support contracts. These contracts are usually limited to a " +"prepaid number of hours. Each service posted in the analytic accounts shows " +"the remaining hours of support. To manage support contracts, you would " +"create a product configured to invoice on order and link the sale order to " +"an analytic account" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:210 +msgid "" +"In Odoo, each analytic line lists the number of units sold or used, as well " +"as what you would usually find there – the amount in currency units (USD or " +"GBP, or whatever other choice you make). So you can sum the quantities sold " +"and used on each sale order to determine whether any hours of the support " +"contract remain." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:217 +msgid "Conclusion" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:219 +msgid "" +"Analytic accounting helps you to analyse costs and revenues whatever the use" +" case. You can sell or purchase services, track time or analyse the " +"production performance." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:223 +msgid "" +"Analytic accounting is flexible and easy to use through all Odoo " +"applications (sales, purchase, timesheet, production, invoice, …)." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:3 +msgid "What is an account type and how do I configure it?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:6 +msgid "What is an account type ?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:8 +msgid "" +"An account type is a name or code given to an account that indicates the " +"account's purpose." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:11 +msgid "" +"In Odoo, Account Types are used for information purpose, to generate " +"country-specific legal reports, set the rules to close a fiscal year and " +"generate opening entries." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:15 +msgid "" +"Basically Account types categorize general account with some specific " +"category according to its behaviour or purpose." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:19 +msgid "Which are the account types in Odoo ?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:21 +msgid "" +"Odoo covers all accounting types. Therefore, you cannot create new account " +"types. Just pick the one related to your account." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:25 +msgid "**List of account types**" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:27 +msgid "Receivable" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:29 +msgid "Payable" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:31 +msgid "Bank and Cash" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:33 +msgid "Current Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:35 +msgid "Non-current Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:37 +msgid "Prepayments" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:39 +#: ../../accounting/overview/main_concepts/terminologies.rst:77 +msgid "Fixed Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:41 +msgid "Current Liabilities" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:43 +msgid "Non-current Liabilities" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:45 +msgid "Equity" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:47 +msgid "Current Year Earnings" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:49 +msgid "Other Income" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:51 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 +msgid "Income" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:53 +msgid "Depreciation" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:55 +msgid "Expenses" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:57 +msgid "Direct Costs" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:61 +msgid "How do I configure my accounts?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:63 +msgid "" +"Account types are automatically created when installing a chart of account. " +"By default, Odoo provides a lot of chart of accounts, just install the one " +"related to your country." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:67 +msgid "" +"It will install generic accounts. But if it does not cover all your cases, " +"you can create your own accounts too." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:72 +msgid "" +"If you are a Saas User, your country chart of account is automatically " +"installed." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:75 +msgid "" +"To create a new accounts, go to the Accounting application. Open the menu " +":menuselection:`Adviser --> Chart of Accounts`, the click on the **Create** " +"button." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"Account Type is used for information purpose, to generate country-specific " +"legal reports, and set the rules to close a fiscal year and generate opening" +" entries." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Optional tags you may want to assign for custom reporting" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Forces all moves for this account to have this account currency." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"The 'Internal Type' is used for features available on different types of " +"accounts: liquidity type is for cash or bank accounts, payable/receivable is" +" for vendor/customer accounts." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"Check this box if this account allows invoices & payments matching of " +"journal items." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:86 +msgid "View *Create Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/others/inventory.rst:3 +msgid "Inventory" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:3 +msgid "Impact on the average price valuation when returning goods" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:5 +msgid "" +"As stated in the `*inventory valuation page* " +"`__, one of " +"the possible costing method you can use in perpetual stock valuation, is the" +" average cost." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:10 +msgid "" +"This document answers to one recurrent question for companies using that " +"method to make their stock valuation: how does a shipping returned to its " +"supplier impact the average cost and the accounting entries? This document " +"is **only** for the specific use case of a perpetual valuation (as opposed " +"to the periodic one) and in average price costing method (as opposed to " +"standard of FIFO)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:18 +msgid "Definition of average cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:20 +msgid "" +"The average cost method calculates the cost of ending inventory and cost of " +"goods sold on the basis of weighted average cost per unit of inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:24 +msgid "" +"The weighted average cost per unit is calculated using the following " +"formula:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:27 +msgid "" +"When new products arrive in a warehouse, the new average cost is recomputed " +"as:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:33 +msgid "" +"When products leave the warehouse: the average cost **does not** change" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:36 +msgid "Defining the purchase price" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:38 +msgid "" +"The purchase price is estimated at the reception of the products (you might " +"not have received the vendor bill yet) and reevaluated at the reception of " +"the vendor bill. The purchase price includes the cost you pay for the " +"products, but it may also includes additional costs, like landed costs." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:45 +msgid "Average cost example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Operation" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +msgid "Delta Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Inventory Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Qty On Hand" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Avg Cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +msgid "0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +msgid "+8\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "8" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +msgid "+4\\*$16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "$144" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +msgid "-10\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "$24" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:60 +msgid "" +"At the beginning, the Avg Cost is set to 0 set as there is no product in the" +" inventory. When the first reception is made, the average cost becomes " +"logically the purchase price." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:64 +msgid "" +"At the second reception, the average cost is updated because the total " +"inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, " +"the average price per unit is ``$144 / 12 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:68 +msgid "" +"By definition, the delivery of 10 products does not change the average cost." +" Indeed, the inventory value is now $24 as we have only 2 units remaining of" +" each ``$24 / 2 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:73 +msgid "Purchase return use case" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:75 +msgid "" +"In case of a product returned to its supplier after reception, the inventory" +" value is reduced using the average cost formulae (not at the initial price " +"of these products!)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:79 +msgid "Which means that the above table will be updated as follow:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "Return of 1 Product initially bought at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "-1\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "1" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:90 +msgid "Explanation: counter example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:92 +msgid "" +"Remember the definition of **Average Cost**, saying that we do not update " +"the average cost of a product leaving the inventory. If you break this rule," +" you may lead to inconsistencies in your inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:96 +msgid "" +"As an example, here is the scenario when you deliver one piece to the " +"customer and return the other one to your supplier (at the cost you " +"purchased it). Here is the operation:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +msgid "Customer Shipping 1 product" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +msgid "-1\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$2**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:110 +msgid "" +"As you can see in this example, this is not correct: an inventory valuation " +"of $2 for 0 pieces in the warehouse." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:113 +msgid "" +"The correct scenario should be to return the goods at the current average " +"cost:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**$0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:126 +msgid "" +"On the other hand, using the average cost to value the return ensure a " +"correct inventory value at all times." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:130 +msgid "Further thoughts on anglo saxon mode" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:132 +msgid "" +"For people in using the **anglo saxon accounting** principles, there is " +"another concept to take into account: the stock input account of the " +"product, which is intended to hold at any time the value of vendor bills to " +"receive. So the stock input account will increase on reception of incoming " +"shipments and will decrease when receiving the related vendor bills." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:139 +msgid "" +"Back to our example, we see that when the return is valued at the average " +"price, the amount booked in the stock input account is the original purchase" +" price:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "stock input" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "price diff" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "($80)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "($64)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$10**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$12**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:163 +msgid "" +"This is because the vendor refund will be made using the original purchase " +"price, so to zero out the effect of the return in the stock input in last " +"operation, we need to reuse the original price. The price difference account" +" located on the product category is used to book the difference between the " +"average cost and the original purchase price." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:3 +msgid "Record exchange rates at payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:8 +msgid "" +"Any company doing international trade faces the case where the payments are " +"in a different currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:11 +msgid "" +"After receiving their payments, you have the option to convert the amount " +"into your company currency. Multi currency payment implies rates " +"fluctuations. The rate differences are automatically recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:19 +msgid "Enable multi-currencies" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:21 +msgid "" +"In the accounting module, Go to :menuselection:`Configuration --> Settings` " +"and flag **Allow multi currencies**, then click on **apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:27 +msgid "" +"Configure the currency rates in :menuselection:`Configuration --> " +"Currencies`. Write down the rate and make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:33 +msgid "" +"In this document, the base currency is **Euro** and we will record payments " +"in **Dollars**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:40 +msgid "" +"You can automatically fetch the currency rates from the **European Central " +"Bank** or from **Yahoo**. Please read the document : :doc:`how_it_works`." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:45 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:31 +msgid "Configure your journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:47 +msgid "" +"In order to register payments in other currencies, you have to **remove the " +"currency constraint** on the journal. Go to the accounting application, " +"Click on **More** on the journal and **Settings**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:54 +msgid "" +"Check if the **Currency** field is empty or in the foreign currency in which" +" you will register the payments. If a currency is filled in, it means that " +"you can register payments only in this currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:62 +msgid "Record a payment in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:64 +msgid "" +"In the **Accounting** application, go to :menuselection:`Sales --> " +"Payments`. Register the payment and indicate that it was done in the foreign" +" currency. Then click on **confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:71 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:83 +msgid "The journal entry has been posted but not allocated." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:73 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:85 +msgid "" +"Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and " +"click on **Add** to allocate the payment." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:80 +msgid "Record a bank statement in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:82 +msgid "" +"Create or import the bank statement of your payment. The **Amount** is in " +"the company currency. There are two complementary fields, the **Amount " +"currency**, which is the amount that was actually paid and the **Currency** " +"in which it was paid." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:89 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"**Invoice**. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:97 +msgid "Check the exchange rate differences" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:99 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the " +"**Exchange difference** journal entries. All the exchange rates differences " +"are recorded in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:106 +msgid "" +"The Exchange difference journal can be changed in your accounting settings." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:109 +#: ../../accounting/payables/pay/multiple.rst:153 +msgid ":doc:`../../bank/reconciliation/configure`" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:110 +#: ../../accounting/payables/pay/multiple.rst:103 +msgid ":doc:`../../bank/reconciliation/use_cases`" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:3 +#: ../../accounting/others/multicurrencies/how_it_works.rst:111 +msgid "How is Odoo's multi-currency working?" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:8 +msgid "" +"Choosing to use the multi-currency option in Odoo will allow you to send " +"sales invoices, quotes and purchase orders or receive bills and payments in " +"currencies other than your own. With multi-currency, you can also set up " +"bank accounts in other currencies and run reports on your foreign currency " +"activities." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:18 +msgid "Turn on multi-currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:20 +msgid "" +"In the accounting module, Go to :menuselection:`Configuration --> Settings` " +"and flag **Allow multi currencies**, then click on **Apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:27 +#: ../../accounting/others/multicurrencies/how_it_works.rst:160 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:109 +msgid "Exchange Rate Journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:29 +msgid "" +"The **Rate Difference Journal** records the differences between the payment " +"registration and the expected amount. For example, if a payment is paid 1 " +"month after the invoice was issued, the exchange rate has probably changed. " +"The fluctuation implies some loss or profit that are recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:35 +msgid "You can change it in the settings:" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:41 +msgid "View or edit rate being used" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:43 +msgid "" +"You can manually configure the currency rates in " +":menuselection:`Configuration --> Currencies`. Open the currencies you want " +"to use in Odoo and edit it. Make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:50 +msgid "Click on **View Rates** to edit it and to see the history :" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:55 +msgid "" +"Click on **Create** to add the rate. Fill in the date and the rate. Click on" +" **Save** when you are done." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:62 +msgid "Live Currency Rate" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:64 +msgid "" +"By default, the currencies need to be updated manually. But you can " +"synchronize it with `Yahoo `__ or the `European Central Bank `__. " +"In :menuselection:`Configuration --> Settings`, go to the **Live Currency " +"Rate** section." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:69 +msgid "" +"Choose the interval : Manually, Daily, Weekly or Monthly. You can always " +"force the update by clicking on **Update Now**. Select the provider, and you" +" are set !" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:78 +msgid "Only the **active** currencies are updated" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:81 +msgid "Configure your charts of account" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:83 +msgid "" +"In the accounting application, go to :menuselection:`Adviser --> Charts of " +"Accounts`. On each account, you can set a currency. It will force all moves " +"for this account to have the account currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:87 +msgid "" +"If you leave it empty, it means that it can handle all currencies that are " +"Active." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:94 +msgid "Configure your journals" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:96 +msgid "" +"In order to register payments in other currencies, you have to remove the " +"currency constraint on the journal. Go to the accounting application, Click " +"on **More** on the journal and **Settings**." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:103 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:40 +msgid "" +"Check if the currency field is empty or in the foreign currency in which you" +" will register the payments. If a currency is filled in, it means that you " +"can register payments only in this currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:113 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:50 +msgid "" +"Now that you are working in a multi-currency environment, all accountable " +"items will be linked to a currency, domestic or foreign." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:117 +msgid "Sales Orders and Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:119 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:56 +msgid "" +"You are now able to set a different currency than the company one on your " +"sale orders and on your invoices. The currency is set for the whole " +"document." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:127 +msgid "Purchases orders and Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:129 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:66 +msgid "" +"You are now able to set a different currency than the company one on your " +"purchase orders and on your vendor bills. The currency is set for the whole " +"document." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:137 +msgid "Payment Registrations" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:139 +msgid "" +"In the accounting application, go to **Sales > Payments**. Register the " +"payment and set the currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:146 +msgid "Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:148 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:94 +msgid "" +"When creating or importing bank statements, the amount is in the company " +"currency. But there are now two complementary fields, the amount that was " +"actually paid and the currency in which it was paid." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:155 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"Invoice. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:162 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange" +" difference journal entries. All the exchange rates differences are recorded" +" in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:170 +msgid ":doc:`invoices_payments`" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:171 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:120 +msgid ":doc:`exchange`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:3 +msgid "How to manage invoices & payment in multiple currencies?" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:8 +msgid "" +"Odoo provides multi-currency support with automatic currency gross or loss " +"entry adjustment. There are a few things Odoo has been to ease the user's " +"life." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:12 +msgid "" +"All the account transactions will be done using the company currency. " +"However you can see two extra fields with the journal entry where secondary " +"currency and amount will visible. You can create multi-currency journals of " +"force a specific currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:17 +msgid "" +"When creating an invoice, the currency can be changed very easily; however " +"Odoo takes the company currency as a default assignment. It will convert all" +" the amounts automatically using that currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:25 +msgid "Enable Multi-Currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:27 +msgid "" +"For information about enabling Multi-Currency, please read the document: " +":doc:`how_it_works`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:33 +msgid "" +"In order to register payments in other currencies, you have to remove the " +"currency constraint on the journal. Go to the accounting application, on the" +" journal, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:48 +msgid "Multi-currency invoices & Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:54 +msgid "Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 +msgid "Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:74 +msgid "Multi-currency Payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:76 +msgid "" +"In the accounting application, go to :menuselection:`Sales --> Payments`. " +"Register the payment and indicate that it was done in the foreign currency. " +"Then click on **Confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:92 +msgid "Multi- Currency Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:101 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"invoice. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:111 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the " +"**Exchange Difference** journal entries. All the exchange rates differences " +"are recorded in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:119 +msgid ":doc:`how_it_works`" +msgstr "" + +#: ../../accounting/others/reporting.rst:3 +#: ../../accounting/overview/process_overview/supplier_bill.rst:124 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:106 +msgid "Reporting" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:3 +msgid "How to create a customized reports with your own formulas?" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:8 +msgid "" +"Odoo 9 comes with a powerful and easy-to-use reporting framework. Creating " +"new reports (such as a tax report or a balance sheet for a specific country)" +" to suit your needs is now easier than ever." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:13 +msgid "Activate the developer mode" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:15 +msgid "" +"In order to have access to the financial report creation interface, the " +"**developer mode** needs to be activated. To do that, first click on the " +"user profile in the top right menu, then **About**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:22 +msgid "Click on : **Activate the developer mode**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:28 +msgid "Create your financial report" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:30 +msgid "" +"First, you need to create your financial report. To do that, go to " +":menuselection:`Accounting --> Configuration --> Financial Reports`" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:36 +msgid "" +"Once the name is filled, there are two other parameters that need to be " +"configured:" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:39 +msgid "**Show Credit and Debit Columns**" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:41 +msgid "**Analysis Period** :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:43 +msgid "Based on date ranges (eg Profit and Loss)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:45 +msgid "Based on a single date (eg Balance Sheet)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:47 +msgid "" +"Based on date ranges with 'older' and 'total' columns and last 3 months (eg." +" Aged Partner Balances)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:50 +msgid "Bases on date ranges and cash basis method (eg Cash Flow Statement)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:54 +msgid "Add lines in your custom reports" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:56 +msgid "" +"After you've created the report, you need to fill it with lines. They all " +"need a **name**, a **code** (that is used to refer to the line), a " +"**sequence number** and a **level** (Used for the line rendering)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:63 +msgid "" +"In the **formulas** field you can add one or more formulas to assign a value" +" to the balance column (and debit and credit column if applicable – " +"separated by ;)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:67 +msgid "You have several objects available in the formula :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:69 +msgid "" +"``Ndays`` : The number of days in the selected period (for reports with a " +"date range)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:72 +msgid "" +"Another report, referenced by its code. Use ``.balance`` to get its balance " +"value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:76 +msgid "" +"A line can also be based on the sum of account move lines on a selected " +"domain. In which case you need to fill the domain field with an Odoo domain " +"on the account move line object. Then an extra object is available in the " +"formulas field, namely ``sum``, the sum of the account move lines in the " +"domain. You can also use the group by field to group the account move lines " +"by one of their columns." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:83 +msgid "Other useful fields :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:85 +msgid "**Type** : Type of the result of the formula." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:87 +msgid "" +"**Is growth good when positive** : Used when computing the comparison " +"column. Check if growth is good (displayed in green) or not." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:90 +msgid "" +"**Special date changer** : If a specific line in a report should not use the" +" same dates as the rest of the report." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:93 +msgid "" +"**Show domain** : How the domain of a line is displayed. Can be foldable " +"(``default``, hidden at the start but can be unfolded), ``always`` (always " +"displayed) or ``never`` (never shown)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:98 +msgid ":doc:`main_reports`" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:3 +msgid "What are the main reports available?" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:5 +msgid "" +"Besides the reports created specifically in each localisation module, a few " +"very useful **generic** and **dynamic reports** are available for all " +"countries :" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:9 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:10 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:11 +msgid "**Chart of Account**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:12 +msgid "**Executive Summary**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:13 +msgid "**General Ledger**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:14 +msgid "**Aged Payable**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:15 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:16 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:17 +msgid "**Tax Report**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:18 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:20 +msgid "" +"You can annotate every reports to print them and report to your adviser. " +"Export to xls to manage extra analysis. Drill down in the reports to see " +"more details (payments, invoices, journal items, etc.)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:24 +msgid "" +"You can also compare values with another period. Choose how many periods you" +" want to compare the chosen time period with. You can choose up to 12 " +"periods back from the date of the report if you don't want to use the " +"default **Previous 1 Period** option." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:30 +msgid "Balance Sheet" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:32 +msgid "" +"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity" +" of your organisation as at a particular date." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:39 +msgid "Profit and Loss" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:41 +msgid "" +"The **Profit and Loss** report (or **Income Statement**) shows your " +"organisation's net income, by deducting expenses from revenue for the report" +" period." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:49 +msgid "Chart of account" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:51 +msgid "A listing of all your accounts grouped by class." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:57 +msgid "Executive Summary" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:59 +msgid "" +"The **Executive Summary** allows for a quick look at all the important " +"figures you need to run your company." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:62 +msgid "" +"In very basic terms, this is what each of the items in this section is " +"reporting :" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "**Performance:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:68 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:67 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales (things like labour, materials, etc)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:74 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:71 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales, as well as any fixed overheads your " +"company has (things like rent, electricity, taxes you need to pay as a " +"result of those sales)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "" +"The ratio of net profit made, to the amount of assets the company used to " +"make those profits." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:97 +msgid "**Position:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:81 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:81 +msgid "" +"The average number of days it takes your customers to pay you (fully), " +"across all your customer invoices." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:84 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:84 +msgid "" +"The average number of days it takes you to pay your suppliers (fully) across" +" all your bills." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:89 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:87 +msgid "" +"How much cash is expected in or out of your organisation in the next month " +"i.e. balance of your **Sales account** for the month less the balance of " +"your **Purchases account** for the month." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:97 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:92 +msgid "" +"Also referred to as **current ratio**, this is the ratio of current assets " +"(assets that could be turned into cash within a year) to the current " +"liabilities (liabilities which will be due in the next year). This is " +"typically used as as a measure of a company's ability to service its debt." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:103 +msgid "General Ledger" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:105 +msgid "" +"The **General Ledger Report** shows all transactions from all accounts for a" +" chosen date range. The initial summary report shows the totals for each " +"account and from there you can view a detailed transaction report or any " +"exceptions. This report is useful for checking every transaction that " +"occurred during a certain period of time." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:115 +msgid "Aged Payable" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:117 +msgid "" +"Run the **Aged Payable Details** report to display information on individual" +" bills, credit notes and overpayments owed by you, and how long these have " +"gone unpaid." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:125 +msgid "Aged Receivable" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:127 +msgid "" +"The **Aged Receivables** report shows the sales invoices that were awaiting " +"payment during a selected month and several months prior." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:134 +msgid "Cash Flow Statement" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:136 +msgid "" +"The **Cash Flow Statement** shows how changes in balance sheet accounts and " +"income affect cash and cash equivalents, and breaks the analysis down to " +"operating, investing and financing activities." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:144 +msgid "Tax Report" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:146 +msgid "" +"This report allows you to see the **net** and **tax amounts** for all the " +"taxes grouped by type (sale/purchase)." +msgstr "" + +#: ../../accounting/others/taxes.rst:3 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "Taxes" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:3 +msgid "How to manage prices for B2B (tax excluded) and B2C (tax included)?" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:5 +msgid "" +"When working with consumers, prices are usually expressed with taxes " +"included in the price (e.g., in most eCommerce). But, when you work in a B2B" +" environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:9 +msgid "" +"Odoo manages both use cases easily, as long as you register your prices on " +"the product with taxes excluded or included, but not both together. If you " +"manage all your prices with tax included (or excluded) only, you can still " +"easily do sales order with a price having taxes excluded (or included): " +"that's easy." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:15 +msgid "" +"This documentation is only for the specific use case where you need to have " +"two references for the price (tax included or excluded), for the same " +"product. The reason of the complexity is that there is not a symmetrical " +"relationship with prices included and prices excluded, as shown in this use " +"case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:25 +msgid "" +"But for the same use case, if you register the price without taxes on the " +"product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:31 +msgid "" +"So, depending on how you register your prices on the product form, you will " +"have different results for the price including taxes and the price excluding" +" taxes:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:40 +msgid "" +"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You " +"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** " +"Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:45 +msgid "" +"This documentation explains how to handle the very specific use case where " +"you need to handle the two prices (tax excluded and included) on the product" +" form within the same company." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:50 +msgid "" +"In terms of finance, you have no more revenues selling your product at 10€ " +"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the " +"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in " +"Belgium, make your customer a favor and set your price at 9.99€ instead of " +"10€. Please note that this does not apply to 20€ or 30€, or other tax rates," +" or a quantity >1. You will also make you a favor since you can manage " +"everything tax excluded, which is less error prone and easier for your " +"salespeople." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:63 +msgid "Introduction" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:65 +msgid "" +"The best way to avoid this complexity is to choose only one way of managing " +"your prices and stick to it: price without taxes or price with taxes " +"included. Define which one is the default stored on the product form (on the" +" default tax related to the product), and let Odoo compute the other one " +"automatically, based on the pricelist and fiscal position. Negotiate your " +"contracts with customers accordingly. This perfectly works out-of-the-box " +"and you have no specific configuration to do." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:73 +msgid "" +"If you can not do that and if you really negotiate some prices with tax " +"excluded and, for other customers, others prices with tax included, you " +"must:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:77 +msgid "" +"always store the default price TAX EXCLUDED on the product form, and apply a" +" tax (price included on the product form)" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:80 +msgid "create a pricelist with prices in TAX INCLUDED, for specific customers" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:83 +msgid "" +"create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:86 +msgid "" +"assign both the pricelist and the fiscal position to customers who want to " +"benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ price excluded" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, price included, in our shops or eCommerce " +"website" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:97 +msgid "Setting your products" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:99 +msgid "" +"Your company must be configured with price excluded by default. This is " +"usually the default configuration, but you can check your **Default Sale " +"Tax** from the menu :menuselection:`Configuration --> Settings` of the " +"Accounting application." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:107 +msgid "" +"Once done, you can create a **B2C** pricelist. You can activate the " +"pricelist feature per customer from the menu: :menuselection:`Configuration " +"--> Settings` of the Sale application. Choose the option **different prices " +"per customer segment**." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:112 +msgid "" +"Once done, create a B2C pricelist from the menu " +":menuselection:`Configuration --> Pricelists`. It's also good to rename the " +"default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:116 +msgid "" +"Then, create a product at 8.26€, with a tax of 21% (defined as tax not " +"included in price) and set a price on this product for B2C customers at 10€," +" from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:125 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:127 +msgid "" +"From the accounting application, create a B2C fiscal position from this " +"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal " +"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax " +"included in price)" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:136 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:138 +msgid "" +"Create a quotation from the Sale application, using the " +":menuselection:`Sales --> Quotations` menu. You should have the following " +"result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:145 +msgid "" +"Then, create a quotation but **change the pricelist to B2C and the fiscal " +"position to B2C** on the quotation, before adding your product. You should " +"have the expected result, which is a total price of 10€ for the customer: " +"8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:153 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:156 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:158 +msgid "" +"If you negotiate a contract with a customer, whether you negotiate price " +"included or price excluded, you can set the pricelist and the fiscal " +"position on the customer form so that it will be applied automatically at " +"every sale of this customer." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:163 +msgid "" +"The pricelist is in the **Sales & Purchases** tab of the customer form, and " +"the fiscal position is in the accounting tab." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:166 +msgid "" +"Note that this is error prone: if you set a fiscal position with tax " +"included in prices but use a pricelist that is not included, you might have " +"wrong prices calculated for you. That's why we usually recommend companies " +"to only work with one price reference." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:3 +msgid "How to adapt taxes to my customer status or localization" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:5 +msgid "" +"Most often sales tax rates depend on your customer status or localization. " +"To map taxes, Odoo brings the so-called *Fiscal Positions*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:9 +msgid "Create tax mapping" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:11 +msgid "" +"A fiscal position is just a set of rules that maps default taxes (as defined" +" on product form) into other taxes. In the screenshot below, foreign " +"customers get a 0% tax instead of the default 15%, for both sales and " +"purchases." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:18 +msgid "" +"The main fiscal positions are automatically created according to your " +"localization. But you may have to create fiscal positions for specific use " +"cases. To define fiscal positions, go to " +":menuselection:`Invoicing/Accounting --> Configuration --> Fiscal " +"Positions`." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:24 +msgid "" +"If you use Odoo Accounting, you can also map the Income/Expense accounts " +"according to the fiscal position. For example, in some countries, revenues " +"from sales are not posted in the same account than revenues from sales in " +"foreign countries." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:29 +msgid "Adapt taxes to your customer status" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:31 +msgid "" +"If a customer falls into a specific taxation rule, you need to apply a tax-" +"mapping. To do so, create a fiscal position and assign it to your customers." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:37 +msgid "" +"Odoo will use this specific fiscal position for any order/invoice recorded " +"for the customer." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:40 +msgid "" +"If you set the fiscal position in the sales order or invoice manually, it " +"will only apply to this document and not to future orders/invoices of the " +"same customer." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:44 +msgid "Adapt taxes to your customer address (destination-based)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:46 +msgid "" +"Depending on your localization, sales taxes may be origin-based or " +"destination-based. Most states or countries require you to collect taxes at " +"the rate of the destination (i.e. your buyer’s address) while some others " +"require to collect them at the rate effective at the point of origin (i.e. " +"your office or warehouse)." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:51 +msgid "" +"If you are under the destination-based rule, create one fiscal position per " +"tax-mapping to apply." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:53 +msgid "Check the box *Detect Automatically*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:54 +msgid "" +"Select a country group, country, state or city to trigger the tax-mapping." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:59 +msgid "" +"This way if no fiscal position is set on the customer, Odoo will choose the " +"fiscal position matching the shipping address on creating an order." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:63 +msgid "" +"For eCommerce orders, the tax of the visitor's cart will automatically " +"update and apply the new tax after the visitor has logged in or filled in " +"his shipping address." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:68 +msgid "Specific use cases" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:70 +msgid "" +"If, for some fiscal positions, you want to remove a tax, instead of " +"replacing by another, just keep the *Tax to Apply* field empty." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:76 +msgid "" +"If, for some fiscal positions, you want to replace a tax by two other taxes," +" just create two lines having the same *Tax on Product*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:82 +#: ../../accounting/others/taxes/default_taxes.rst:27 +#: ../../accounting/others/taxes/retention.rst:70 +msgid ":doc:`create`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:83 +#: ../../accounting/others/taxes/default_taxes.rst:29 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:84 +#: ../../accounting/others/taxes/create.rst:70 +#: ../../accounting/others/taxes/default_taxes.rst:31 +msgid ":doc:`tax_included`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:85 +#: ../../accounting/others/taxes/default_taxes.rst:30 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:3 +msgid "How to create new taxes" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:5 +msgid "" +"Odoo's tax engine is very flexible and support many different type of taxes:" +" value added taxes (VAT), eco-taxes, federal/states/city taxes, retention, " +"withholding taxes, etc. For most countries, your system is pre-configured " +"with the right taxes." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:10 +msgid "" +"This section details how you can define new taxes for specific use cases." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:12 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Taxes`. From this " +"menu, you get all the taxes you can use: sales taxes and purchase taxes." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:18 +msgid "Choose a scope: Sales, Purchase or None (e.g. deprecated tax)." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:20 +msgid "Select a computation method:" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:22 +msgid "**Fixed**: eco-taxes, etc." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:24 +msgid "**Percentage of Price**: most common (e.g. 15% sales tax)" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:26 +msgid "**Percentage of Price Tax Included**: used in Brazil, etc." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:28 +msgid "**Group of taxes**: allows to have a compound tax" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:34 +msgid "" +"If you use Odoo Accounting, set a tax account (i.e. where the tax journal " +"item will be posted). This field is optional, if you keep it empty, Odoo " +"posts the tax journal item in the income account." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:39 +msgid "" +"If you want to avoid using a tax, you can not delete it because the tax is " +"probably used in several invoices. So, in order to avoid users to continue " +"using this tax, you should set the field *Tax Scope* to *None*." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:44 +msgid "" +"If you need more advanced tax mechanism, you can install the module " +"**account_tax_python** and you will be able to define new taxes with Python " +"code." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:49 +msgid "Advanced configuration" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:51 +msgid "" +"**Label on Invoices**: a short text on how you want this tax to be printed " +"on invoice line. For example, a tax named \"15% on Services\" can have the " +"following label on invoice \"15%\"." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:55 +msgid "" +"**Tax Group**: defines where this tax is summed in the invoice footer. All " +"the tax belonging to the same tax group will be grouped on the invoice " +"footer. Examples of tax group: VAT, Retention." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:59 +msgid "" +"**Include in Analytic Cost**: the tax is counted as a cost and, thus, " +"generate an analytic entry if your invoice uses analytic accounts." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:63 +msgid "" +"**Tags**: are used for custom reports. Usually, you can keep this field " +"empty." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:69 +#: ../../accounting/others/taxes/default_taxes.rst:28 +#: ../../accounting/others/taxes/taxcloud.rst:87 +msgid ":doc:`application`" +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:3 +msgid "How to set default taxes" +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:5 +msgid "" +"Taxes applied in your country are installed automatically for most " +"localizations." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:7 +msgid "" +"Default taxes set in orders and invoices come from each product's Invoicing " +"tab. Such taxes are used when you sell to companies that are in the same " +"country/state than you." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:13 +msgid "" +"To change the default taxes set for any new product created go to " +":menuselection:`Invoicing/Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:20 +msgid "" +"If you work in a multi-companies environment, the sales and purchase taxes " +"may have a different value according to the company you work for. You can " +"login into two different companies and change this field for each company." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:3 +msgid "How to manage withholding taxes?" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:5 +msgid "" +"A withholding tax, also called a retention tax, is a government requirement " +"for the payer of a customer invoice to withhold or deduct tax from the " +"payment, and pay that tax to the government. In most jurisdictions, " +"withholding tax applies to employment income." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:10 +msgid "" +"With normal taxes, the tax is added to the subtotal to give you the total to" +" pay. As opposed to normal taxes, withholding taxes are deducted from the " +"amount to pay, as the tax will be paid by the customer." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:14 +msgid "As, an example, in Colombia you may have the following invoice:" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:19 +msgid "" +"In this example, the **company** who sent the invoice owes $20 of taxes to " +"the **government** and the **customer** owes $10 of taxes to the " +"**government**." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:25 +msgid "" +"In Odoo, a withholding tax is defined by creating a negative tax. For a " +"retention of 10%, you would configure the following tax (accessible through " +":menuselection:`Configuration --> Taxes`):" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:32 +msgid "" +"In order to make it appear as a retention on the invoice, you should set a " +"specific tax group **Retention** on your tax, in the **Advanced Options** " +"tab." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:39 +msgid "" +"Once the tax is defined, you can use it in your products, sales order or " +"invoices." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:43 +msgid "" +"If the retention is a percentage of a regular tax, create a Tax with a **Tax" +" Computation** as a **Tax Group** and set the two taxes in this group " +"(normal tax and retention)." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:48 +msgid "Applying retention taxes on invoices" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:50 +msgid "" +"Once your tax is created, you can use it on customer forms, sales order or " +"customer invoices. You can apply several taxes on a single customer invoice " +"line." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:58 +msgid "" +"When you see the customer invoice on the screen, you get only a **Taxes " +"line** summarizing all the taxes (normal taxes & retentions). But when you " +"print or send the invoice, Odoo does the correct grouping amongst all the " +"taxes." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:63 +msgid "The printed invoice will show the different amounts in each tax group." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:3 +msgid "How to set tax-included prices" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:5 +msgid "" +"In most countries, B2C prices are tax-included. To do that in Odoo, check " +"*Included in Price* for your sales taxes in :menuselection:`Accounting --> " +"Configuration --> Taxes`." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:12 +msgid "" +"This way the price set on the product form includes the tax. As an example, " +"let's say you have a product with a sales tax of 10%. The sales price on the" +" product form is $100." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:16 +msgid "If the tax is not included in the price, you will get:" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:18 +msgid "Price without tax: $100" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:20 +msgid "Taxes: $10" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:22 +msgid "Total to pay: $110" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:24 +msgid "If the tax is included in the price" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:26 +msgid "Price without tax: 90.91" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:28 +msgid "Taxes: $9.09" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:30 +msgid "Total to pay: $100" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:32 +msgid "" +"You can rely on following documentation if you need both tax-included (B2C) " +"and tax-excluded prices (B2B): :doc:`B2B_B2C`." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:36 +msgid "Show tax-included prices in eCommerce catalog" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:38 +msgid "" +"By default prices displayed in your eCommerce catalog are tax-excluded. To " +"display it in tax-included, check *Show line subtotals with taxes included " +"(B2C)* in :menuselection:`Sales --> Configuration --> Settings` (Tax " +"Display)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:3 +msgid "How to get correct tax rates in the US thanks to TaxCloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:5 +msgid "" +"The **TaxCloud** integration allows you to calculate the sales tax for every" +" address in the United States and keeps track of which product types are " +"exempt from sales tax and in which states each exemption applies. TaxCloud " +"calculates sales tax in real-time for every state, city, and special " +"jurisdiction in the United States." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:15 +msgid "In Tax Cloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:16 +msgid "" +"Create a free account on `*TaxCloud* `__ " +"website." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:18 +msgid "Register your website on TaxCloud to get an *API ID* and an *API Key*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:24 +msgid "In Odoo" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:25 +msgid "" +"Go to :menuselection:`Invoicing/Accounting --> Configuration --> Settings` " +"and check *Compute sales tax automatically using TaxCloud*. Click *Apply*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:31 +msgid "Still in those settings, enter your TaxCloud credentials." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:32 +msgid "" +"Hit *Sync TaxCloud Categories (TIC)* to import TIC product categories from " +"TaxCloud (Taxability Information Codes). Some categories may imply specific " +"rates." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:39 +msgid "" +"Set default *TIC Code* and taxe rates. This will apply to any new product " +"created. A default sales tax is needed to trigger the tax computation." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:43 +msgid "" +"For products under a specific category, select it in its detail form (in " +"*Sales* tab)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:46 +msgid "" +"Make sure your company address is well defined (especially the state and the" +" zip code). Go to :menuselection:`Settings --> General Settings` and click " +"*Configure your company data*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:51 +msgid "How it works" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:53 +msgid "" +"Automatic tax assignation works thanks to fiscal positions (see " +":doc:`application`). A specific fiscal position is created when installing " +"*TaxCloud*. Everything works out-of-the-box." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:58 +msgid "" +"This fiscal position is set on any sales order, web order, or invoice when " +"the customer country is *United States*. This is triggering the automated " +"tax computation." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:65 +msgid "" +"Add a product with a default sales tax. Odoo will automatically send a " +"request to TaxCloud, get the correct tax percentage based on the customer " +"location (state and zip code) and product TIC category, create a new tax " +"rate if that tax percentage does not already exist in your system and return" +" it in the order item line (e.g. 7.0%)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:75 +msgid "How to create specific tax mappings using TaxCloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:77 +msgid "" +"You can create several fiscal positions using TaxCloud. Check *Use TaxCloud " +"API* to do so. Such fiscal postions can be assigned to customers in their " +"detail form in order to get them by default whenever they buy you something." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:86 +msgid ":doc:`default_taxes`" +msgstr "" + +#: ../../accounting/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:3 +msgid "How to setup Odoo Accounting?" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:5 +msgid "" +"The Odoo Accounting application has an implementation guide that you should " +"follow to configure it. It's a step-by-step wizard with links to the " +"different screens you will need." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:9 +msgid "" +"Once you have `installed the Accounting application " +"`__, you " +"should click on the top-right progressbar to get access to the " +"implementation guide." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:17 +msgid "The implementation guide will help you through the following steps:" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:19 +msgid "Completing your company settings" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:20 +msgid "Entering in your bank accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:21 +msgid "Selecting your chart of accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:22 +msgid "Confirming your usual tax rates" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:23 +msgid "Setting up any foreign currencies" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:24 +msgid "Importing your customers" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:25 +msgid "Importing your suppliers" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:26 +msgid "Importing your products" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:27 +msgid "Importing your outstanding transactions" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:28 +msgid "Importing your starting balances" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:29 +msgid "Define the users for accounting" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:34 +msgid "" +"Once a step is done, you can click on the \"Mark as Done\" button, in the " +"bottom of the screen. That way, you can track the progress of your overall " +"configuration of Odoo." +msgstr "" + +#: ../../accounting/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:3 +msgid "The Accounting behind Odoo" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:5 +msgid "" +"This page summarises the way Odoo deals with typical accounts and " +"transactions." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:9 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:11 +msgid "" +"Odoo automatically creates all the behind-the-scenes journal entries for " +"each of your accounting transactions: customer invoices, point of sale " +"order, expenses, inventory moves, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:15 +msgid "" +"Odoo uses the rules of double-entry bookkeeping system: all journal entries " +"are automatically balanced (sum of debits = sum of credits)." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:20 +msgid "" +"`Understand Odoo's accounting transactions per document " +"`__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:23 +msgid "Accrual and Cash Basis Methods" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:25 +msgid "" +"Odoo support both accrual and cash basis reporting. This allows you to " +"report income / expense at the time transactions occur (i.e., accrual " +"basis), or when payment is made or received (i.e., cash basis)." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:30 +msgid "Multi-companies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:32 +msgid "" +"Odoo allows to manage several companies within the same database. Each " +"company has its own chart of accounts and rules. You can get consolidation " +"reports following your consolidation rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:36 +msgid "" +"Users can access several companies but always work in one company at a time." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:40 +msgid "Multi-currencies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:42 +msgid "" +"Every transaction is recorded in the default currency of the company. For " +"transactions occurring in another currency, Odoo stores both the value in " +"the currency of the company and the value in the currency of the " +"transaction. Odoo can generate currencies gains and losses after the " +"reconciliation of the journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:48 +msgid "" +"Currency rates are updated once a day using a yahoo.com online web-service." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:52 +msgid "International Standards" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:54 +msgid "" +"Odoo accounting support more than 50 countries. The Odoo core accounting " +"implement accounting standards that is common to all countries and specific " +"modules exists per country for the specificities of the country like the " +"chart of accounts, taxes, or bank interfaces." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:60 +msgid "In particular, Odoo's core accounting engine supports:" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:62 +msgid "" +"Anglo-Saxon Accounting (U.S., U.K.,, and other English-speaking countries " +"including Ireland, Canada, Australia, and New Zealand) where cost of good " +"sold are reported when products are sold/delivered." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:66 +msgid "European accounting where expenses are accounted at the supplier bill." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:68 +msgid "" +"Storno accounting (Italy) where refund invoices have negative credit/debit " +"instead of a reverting the original journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:71 +msgid "Odoo also have modules to comply with IFRS rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:74 +msgid "Accounts Receivable & Payable" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:76 +msgid "" +"By default, Odoo uses a single account for all account receivable entries " +"and one for all accounts payable entries. You can create separate accounts " +"per customers/suppliers, but you don't need to." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:81 +msgid "" +"As transactions are associated to customers or suppliers, you get reports to" +" perform analysis per customer/supplier such as the customer statement, " +"revenues per customers, aged receivable/payables, ..." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:86 +msgid "Wide range of financial reports" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:88 +msgid "" +"In Odoo, you can generate financial reports in real time. Odoo's reports " +"range from basic accounting reports to advanced management reports. Odoo's " +"reports include:" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:92 +msgid "Performance reports (such as Profit and Loss, Budget Variance)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:93 +msgid "" +"Position reports (such as Balance Sheet, Aged Payables, Aged Receivables)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:95 +msgid "Cash reports (such as Bank Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:96 +msgid "Detail reports (such as Trial Balance and General Ledger)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:97 +msgid "Management reports (such as Budgets, Executive Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:99 +msgid "" +"Odoo's report engine allows you to customize your own report based on your " +"own formulae." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:103 +msgid "Import bank feeds automatically" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:105 +msgid "" +"Bank reconciliation is a process that matches your bank statement lines, as " +"supplied by the bank, to your accounting transactions in the general ledger." +" Odoo makes bank reconciliation easy by frequently importing bank statement " +"lines from your bank directly into your Odoo account. This means you can " +"have a daily view of your cashflow without having to log into your online " +"banking or wait for your paper bank statements." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:113 +msgid "" +"Odoo speeds up bank reconciliation by matching most of your imported bank " +"statement lines to your accounting transactions. Odoo also remembers how " +"you've treated other bank statement lines and provides suggested general " +"ledger transactions." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:119 +msgid "Calculates the tax you owe your tax authority" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:121 +msgid "" +"Odoo totals all your accounting transactions for your tax period and uses " +"these totals to calculate your tax obligation. You can then check your sales" +" tax by running Odoo's Tax Report." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:126 +msgid "Inventory Valuation" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:128 +msgid "" +"Odoo support both periodic (manual) and perpetual (automated) inventory " +"valuations. The available methods are standard price, average price, LIFO " +"(for countries allowing it) and FIFO." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:134 +msgid "" +"`View impact of the valuation method on your transactions " +"`__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:137 +msgid "Easy retained earnings" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:139 +msgid "" +"Retained earnings is the portion of income retained by your business. Odoo " +"automatically calculates your current year earnings in real time so no year-" +"end journal or rollover is required. This is calculated by reporting the " +"profit and loss balance to your balance sheet report automatically." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:3 +msgid "Introduction to Odoo Accounting" +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:13 +msgid "" +"Odoo is beautiful accounting software designed for the needs of the 21st " +"century." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:15 +msgid "" +"Odoo connects directly to your bank or paypal account. Transactions are " +"synchronized every hour and reconciliation is blazing fast. It's like magic." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:18 +msgid "" +"Instantly create invoices and send them with just a click. No need to print " +"them." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:20 +msgid "Odoo can send them for you by email or regular mail." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:22 +msgid "Your customers pay online, meaning you get your money right away." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:24 +msgid "" +"Odoo accounting is connected with all Odoo our apps such as sale, purchase, " +"inventory and subscriptions." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:27 +msgid "" +"This way, recording vendor bills is also super quick. Set a vendor, select " +"the purchase order and Odoo fills in everything for you automatically." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:30 +msgid "" +"Then, just use the SEPA protocol or print checks to pay vendors in batches." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:33 +msgid "It's that easy with Odoo." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:35 +msgid "" +"Wait, there is more. You will love the Odoo reports. From legal statements " +"to executive summaries, they are fast and dynamic. Use Odoo's business " +"intelligence feature to navigate through all your companies data." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:39 +msgid "" +"Of course, Odoo is mobile too. You can use it to check your accounts on the " +"go." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:41 +msgid "Try Odoo now, and join 2 millions of happy users." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:5 +msgid "Accounting Memento For Entrepreneurs (US GAAP)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:11 +msgid "" +"The **Profit and Loss** (P&L) report shows the performance of the company " +"over a specific period (usually the current year)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:16 +msgid "" +"The **Gross Profit** equals the revenues from sales minus the cost of goods " +"sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:21 +msgid "" +"**Operating Expenses** (OPEX) include administration, sales and R&D salaries" +" as well as rent and utilities, miscellaneous costs, insurances, … anything " +"beyond the costs of products sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:27 +msgid "" +"The **Balance Sheet** is a snapshot of the company's finances at a specific " +"date (as opposed to the Profit and Loss which is an analysis over a period)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:32 +msgid "" +"**Assets** represent the company's wealth, things it owns. Fixed assets " +"includes building and offices, current assets include bank accounts and " +"cash. A client owing money is an asset. An employee is not an asset." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:38 +msgid "" +"**Liabilities** are obligations from past events that the company will have " +"to pay in the future (utility bills, debts, unpaid suppliers)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:43 +msgid "" +"**Equity** is the amount of the funds contributed by the owners (founders or" +" shareholders) plus previously retained earnings (or losses)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:48 +msgid "Each year, net profits (or losses) are reported to retained earnings." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:54 +msgid "" +"What is owned (an asset) has been financed through debts to reimburse " +"(liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:57 +msgid "" +"A difference is made between buying an assets (e.g. a building) and expenses" +" (e.g. fuel). Assets have an intrinsic value over time, versus expenses " +"having value in them being consumed for the company to \"work\"." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:64 +msgid "Assets = Liabilities + Equity" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:67 +msgid "Chart of Accounts" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:69 +msgid "" +"The **chart of accounts** lists all the accounts, whether they are balance " +"sheet accounts or P&L accounts. Every financial transaction (e.g. a payment," +" an invoice) impacts accounts by moving value from one account (credit) to " +"an other account (debit)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:76 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:84 +msgid "Journal Entries" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:86 +msgid "" +"Every financial document of the company (e.g. an invoice, a bank statement, " +"a pay slip, a capital increase contract) is recorded as a journal entry, " +"impacting several accounts." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:90 +msgid "" +"For a journal entry to be *balanced*, the sum of all its debits must be " +"equal to the sum of all its credits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:95 +msgid "examples of accounting entries for various transactions. Example:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:97 +msgid "Example 1: Customer Invoice:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:99 +#: ../../accounting/overview/main_concepts/memento.rst:117 +msgid "Explanation:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:101 +msgid "You generate a revenue of $1,000" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:102 +msgid "You have a tax to pay of $90" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:103 +msgid "The customer owes $1,090" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:105 +#: ../../accounting/overview/main_concepts/memento.rst:122 +msgid "Configuration:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:107 +msgid "Income: defined on the product, or the product category" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:108 +#: ../../accounting/overview/main_concepts/memento.rst:125 +msgid "Account Receivable: defined on the customer" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:109 +msgid "Tax: defined on the tax set on the invoice line" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:111 +msgid "" +"The fiscal position used on the invoice may have a rule that replaces the " +"Income Account or the tax defined on the product by another one." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:115 +msgid "Example 2: Customer Payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:119 +msgid "Your customer owes $1,090 less" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:120 +msgid "Your receive $1,090 on your bank account" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:124 +msgid "Bank Account: defined on the related bank journal" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:130 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/overview/main_concepts/terminologies.rst:26 +msgid "Reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:132 +msgid "" +"Reconciliation is the process of linking journal items of a specific " +"account, matching credits and debits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:135 +msgid "" +"Its primary purpose is to link payments to their related invoices in order " +"to mark invoices that are paid and clear the customer statement. This is " +"done by doing a reconciliation on the *Accounts Receivable* account." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:139 +msgid "" +"An invoice is marked as paid when its Accounts Receivable journal items are " +"reconciled with the related payment journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:142 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:144 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:145 +msgid "" +"the links between the payments and the invoices are detected at the bank " +"matching process" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Accounts Receivable" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Debit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Credit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:158 +msgid "Invoice 1" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:158 +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:244 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 +msgid "100" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:160 +msgid "Payment 1.1" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:160 +msgid "70" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +msgid "Invoice 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "65" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "Payment 1.2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "30" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "Payment 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +msgid "Invoice 3" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "50" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "Total To Pay" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:179 +msgid "" +"Bank reconciliation is the matching of bank statement lines (provided by " +"your bank) with transactions recorded internally (payments to suppliers or " +"from customers). For each line in a bank statement, it can be:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "matched with a previously recorded payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "" +"a payment is registered when a check is received from a customer, then " +"matched when checking the bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:188 +msgid "recorded as a new payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:187 +msgid "" +"the payment's journal entry is created and :ref:`reconciled " +"` with the related invoice when processing the " +"bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "recorded as another transaction:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "bank transfer, direct charge, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:193 +msgid "" +"Odoo should automatically reconcile most transactions, only a few of them " +"should need manual review. When the bank reconciliation process is finished," +" the balance on the bank account in Odoo should match the bank statement's " +"balance." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:201 +msgid "Checks Handling" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:203 +msgid "There are two approaches to manage checks and internal wire transfer:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:205 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:206 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:210 +msgid "" +"The first journal entry is created by registering the payment on the " +"invoice. The second one is created when registering the bank statement." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Account" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:244 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +#: ../../accounting/receivables/customer_payments/check.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +msgid "Account Receivable" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:244 +msgid "Invoice ABC" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Undeposited funds" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Check 0123" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/receivables/customer_payments/check.rst:85 +#: ../../accounting/receivables/customer_payments/check.rst:135 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 +msgid "Bank" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:235 +msgid "" +"A journal entry is created by registering the payment on the invoice. When " +"reconciling the bank statement, the statement line is linked to the existing" +" journal entry." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:242 +msgid "Bank Statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:246 +msgid "Statement XYZ" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:3 +msgid "Accounting Terminologies" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:6 +msgid "Journal" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:9 +msgid "" +"A journal is like a folder in which you record all transactions of the same " +"type: all the statements of a bank account, all customer invoices, all " +"supplier bills. It's used to organize similar transactions together." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:13 +msgid "Payment Terms" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:16 +msgid "" +"Payment terms describe how and when a customer invoice (or supplier bill) " +"should be paid over the time. Example: 30% direct payment, balance due in " +"two months." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:22 +msgid "" +"Bank reconciliation is the process of matching transactions from your bank " +"records with existing journal items or creating new journal items on the " +"fly. It is a process of verification to ensure that your bank and your " +"records in Odoo say the same thing." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:29 +msgid "" +"Journal items reconciliation is the process of linking several journal items" +" together like an invoice and a payment. This allows you to mark invoices as" +" paid. It is also useful when comparing values of 'goods received not " +"invoiced' and 'goods shipped not billed' accounts." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:33 +msgid "Deposit Ticket" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:36 +msgid "" +"Deposit tickets group several payment orders (usually checks) that are " +"deposited together at the bank at the same time. This allows an easy " +"reconciliation with the bank statement line if the line has one line per " +"deposit." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:40 +msgid "Journal Entry" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:43 +msgid "" +"A journal entry is an accounting transaction, usually related to a financial" +" document: invoice, payment, receipt, etc. A journal entry always consists " +"of at least two lines, described here as journal items, which credit or " +"debit specific accounts. The sum of the credits of all journal items of a " +"journal entry must be equal to the sum of their debits for the entry to be " +"valid." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:50 +msgid "Journal Item" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:53 +msgid "" +"A line of a journal entry, with a monetary debit or credit associated with a" +" specific account." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:55 +msgid "Analytic Accounts" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:58 +msgid "" +"Sometimes called **Cost Accounts**, are accounts that are not part of the " +"chart of accounts and that allow you to track costs and revenues. Analytic " +"accounts are usually grouped by projects, departments, etc. for analysis of " +"a company's expenditures. Every journal item is posted in a regular account " +"in the chart of account and can be posted to an analytic account for the " +"purpose of reporting or analysis." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:65 +msgid "Analytic Entries" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:68 +msgid "" +"Costs or revenues posted to analytic accounts, usually related to journal " +"entries." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:70 +msgid "Sales Receipt" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:73 +msgid "" +"A receipt or other slip of paper issued by a store or other vendor " +"describing the details of a purchase (amount, date, department, etc.). Sales" +" receipt are usually used instead of invoices if the sale is paid in cash in" +" a store." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:80 +msgid "" +"Property owned by the company, usually with a useful life greater than one " +"reporting period. Odoo Asset management is used to manage the depreciation /" +" amortization of the asset over the time. Typical examples would be capital " +"equipment, vehicles, and real estate." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:84 +msgid "Deferred Revenues" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:87 +msgid "" +"Are used to recognize revenues for sales of services that are provided over " +"a long period of time. If you sell a 3 year maintenance contract, you can " +"use the deferred revenue mechanism to recognize 1/36 of the revenue every " +"month until the contract expires, rather than taking it all initially or at " +"the end." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:93 +msgid "Fiscal Position" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:96 +msgid "" +"Define the taxes that should be applied for a specific customer/vendor or " +"invoice. Example: If some customers benefit from specific taxes (government," +" construction companies, EU companies that are VAT subjected,…), you can " +"assign a fiscal position to them and the right tax will be selected " +"according to the products they buy." +msgstr "" + +#: ../../accounting/overview/process_overview.rst:3 +msgid "Process overview" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:3 +msgid "From Invoice to Payment Collection" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:5 +msgid "" +"Odoo supports multiple invoicing and payment workflows, so you can choose " +"and use the ones that match your business needs. Whether you want to accept " +"a single payment for a single invoice, or process a payment spanning " +"multiple invoices and taking discounts for early payments, you can do so " +"efficiently and accurately." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:12 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:14 +msgid "" +"If we pick up at the end of a typical 'order to cash' scenario, after the " +"goods have been shipped, you will: issue an invoice; receive payment; " +"deposit that payment at the bank; make sure the Customer Invoice is closed; " +"follow up if Customers are late; and finally present your Income on the " +"Profit and Loss report and show the decrease in Assets on the Balance Sheet " +"report." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:21 +msgid "" +"Invoicing in most countries occurs when a contractual obligation is met. If " +"you ship a box to a customer, you have met the terms of the contract and can" +" bill them. If your supplier sends you a shipment, they have met the terms " +"of that contract and can bill you. Therefore, the terms of the contract is " +"fulfilled when the box moves to or from the truck. At this point, Odoo " +"supports the creation of what is called a Draft Invoice by Warehouse staff." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:30 +msgid "Invoice creation" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:32 +msgid "" +"Draft invoices can be manually generated from other documents such as Sales " +"Orders, Purchase Orders,etc. Although you can create a draft invoice " +"directly if you would like." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:36 +msgid "" +"An invoice must be provided to the customer with the necessary information " +"in order for them to pay for the goods and services ordered and delivered. " +"It must also include other information needed to pay the invoice in a timely" +" and precise manner." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:42 +msgid "Draft invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:44 +msgid "" +"The system generates invoice which are initially set to the Draft state. " +"While these invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:47 +msgid "" +"remain unvalidated, they have no accounting impact within the system. There " +"is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:50 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:52 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:53 +msgid "Product: iMac" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:54 +msgid "Quantity: 1" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:55 +msgid "Unit Price: 100" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:56 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:64 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:66 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:67 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:68 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:71 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:73 +msgid "" +"An invoice will usually include the quantity and price the of goods and/or " +"services, the date, any parties involved, the unique invoice number, and any" +" tax information." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:77 +msgid "" +"\"Validate\" the invoice when you are ready to approve it. The invoice then " +"moves from the Draft state to the Open state." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:80 +msgid "" +"When you have validated an invoice, Odoo gives it a unique number from a " +"defined, and modifiable, sequence." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:86 +msgid "" +"Accounting entries corresponding to this invoice are automatically generated" +" when you validate the invoice. You can see the details by clicking on the " +"entry in the Journal Entry field in the \"Other Info\" tab." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:95 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:97 +msgid "" +"After validating the customer invoice, you can directly send it to the " +"customer via the 'Send by email' functionality." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:103 +msgid "" +"A typical journal entry generated from a validated invoice will look like as" +" follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "115" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "15" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/overview.rst:16 +msgid "Sales" +msgstr "Продажи" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:117 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:89 +msgid "Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:119 +msgid "" +"In Odoo, an invoice is considered to be paid when the associated accounting " +"entry has been reconciled with the payment entries. If there has not been a " +"reconciliation, the invoice will remain in the Open state until you have " +"entered the payment." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:124 +msgid "" +"A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:138 +msgid "" +"You can manually enter your bank statements in Odoo, or you can import them " +"in from a csv file or from several other predefined formats according to " +"your accounting localisation." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:142 +msgid "" +"Create a bank statement from the accounting dashboard with the related " +"journal and enter an amount of $100 ." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:149 +msgid "Reconcile" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:151 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:156 +msgid "" +"You can now go through every transaction and reconcile them or you can mass " +"reconcile with instructions at the bottom." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:158 +msgid "" +"After reconciling the items in the sheet, the related invoice will now " +"display \"You have outstanding payments for this customer. You can reconcile" +" them to pay this invoice. \"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:168 +msgid "" +"Apply the payment. Below, you can see that the payment has been added to the" +" invoice." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:175 +msgid "Payment Followup" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:177 +msgid "" +"There's a growing trend of customers paying bills later and later. " +"Therefore, collectors must make every effort to collect money and collect it" +" faster." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:181 +msgid "" +"Odoo will help you define your follow-up strategy. To remind customers to " +"pay their outstanding invoices, you can define different actions depending " +"on how severely overdue the customer is. These actions are bundled into " +"follow-up levels that are triggered when the due date of an invoice has " +"passed a certain number of days. If there are other overdue invoices for the" +" same customer, the actions of the most overdue invoice will be executed." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:189 +msgid "" +"By going to the customer record and diving into the \"Overdue Payments\" you" +" will see the follow-up message and all overdue invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:199 +msgid "Customer aging report:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:201 +msgid "" +"The customer aging report will be an additional key tool for the collector " +"to understand the customer credit issues, and to prioritize their work." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:205 +msgid "" +"Use the aging report to determine which customers are overdue and begin your" +" collection efforts." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:212 +msgid "Profit and loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:214 +msgid "" +"The Profit and Loss statement displays your revenue and expense details. " +"Ultimately, this gives you a clear image of your Net Profit and Loss. It is " +"sometimes referred to as the \"Income Statement\" or \"Statement of Revenues" +" and Expenses.\"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:223 +msgid "Balance sheet" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:225 +msgid "" +"The balance sheet summarizes the your company's liabilities, assets and " +"equity at a specific moment in time." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:234 +msgid "" +"For example, if you manage your inventory using the perpetual accounting " +"method, you should expect a decrease in account \"Current Assets\" once the " +"material has been shipped to the customer." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:3 +msgid "From Vendor Bills to Payments" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:5 +msgid "" +"Once vendor bills are registered in Odoo, you can easily pay vendors for the" +" correct amount and at the right time (not too late, not too early; " +"depending on your vendor policy). Odoo also offers reports to track your " +"aged payable balances." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:10 +msgid "" +"If you want to control vendor bills received from your vendors, you can use " +"the Odoo Purchase application that allows you to control and pre-complete " +"them automatically based on past purchase orders." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:15 +msgid "From Vendor Bill to Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:18 +msgid "Record a new vendor bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:20 +msgid "" +"When a vendor bill is received, you can record it from " +":menuselection:`Purchases --> Vendor Bills` in the Accounting application. " +"As a shortcut, you can also use the **New Bill** feature on the accounting " +"dashboard." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:27 +msgid "" +"To register a new vendor bill, start by selecting a vendor and inputting " +"their invoice as the **Vendor Reference**, then add and confirm the product " +"lines, making sure to have the right product quantities, taxes and prices." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:35 +msgid "" +"Save the invoice to update the pre tax and tax amounts at the bottom of the " +"screen. You will most likely need to configure the prices of your products " +"without taxes as Odoo will compute the tax for you." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:40 +msgid "" +"On the bottom left corner, Odoo shows a summary table of all taxes on the " +"vendor bill. In several countries, different methods are accepted to round " +"the totals (round per line, or round globally). The default rounding method " +"in Odoo is to round the final prices per line (as you may have different " +"taxes per product. E.g. Alcohol and cigarettes). However if your vendor has " +"a different tax amount on their bill, you can change the amount in the " +"bottom left table to adjust and match." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:48 +msgid "Validate The Vendor Bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:50 +msgid "" +"Once the vendor bill is validated, a journal entry will be generated based " +"on the configuration on the invoice. This journal entry may differ depending" +" on the the accounting package you choose to use." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:54 +msgid "" +"For most European countries, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:57 +#: ../../accounting/overview/process_overview/supplier_bill.rst:66 +msgid "**Accounts Payable:** defined on the vendor form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:59 +#: ../../accounting/overview/process_overview/supplier_bill.rst:68 +msgid "**Taxes:** defined on the products and per line" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:61 +msgid "**Expenses:** defined on the line item product used" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:63 +msgid "" +"For Anglo-Saxon (US) accounting, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:70 +msgid "**Goods Received:** defined on the product form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:72 +msgid "" +"You can check your Profit & Loss or the Balance Sheet reports after having " +"validated a couple of vendor bills to see the impact on your general ledger." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:77 +msgid "Pay a bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:79 +msgid "" +"To create a payment for an open vendor bill directly, you can click on " +"**Register a Payment** at the top of the form." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:82 +msgid "" +"From there, you select the payment method (i.e. Checking account, credit " +"card, check, etc…) and the amount you wish to pay. By default, Odoo will " +"propose the entire remaining balance on the bill for payment. In the memo " +"field, we recommend you set the vendor invoice number as a reference (Odoo " +"will auto fill this field from the from the vendor bill if set it " +"correctly)." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:94 +msgid "" +"You can also register a payment to a vendor directly without applying it to " +"a vendor bill. To do that, :menuselection:`Purchases --> Payments`. Then, " +"from the vendor bill you will be able to reconcile this payment with " +"directly." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:99 +msgid "Printing vendor Checks" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:101 +msgid "" +"If you choose to pay your vendor bills by check, Odoo offers a method to do " +"so directly from your vendor payments within Odoo. Whether you do so on a " +"daily basis or prefer to do so at the end of the week, you can print in " +"checks in batches." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:106 +msgid "" +"If you have checks to print, Odoo's accounting dashboard acts as a to do " +"list and reminds you of how many checks you have left to be printed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:112 +msgid "" +"By selecting the amount of checks to be printed, you can dive right into a " +"list of all payments that are ready to be processed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:115 +msgid "" +"Select all the checks you wish to print (use the first checkbox to select " +"them all) and set the action to **Print Checks**. Odoo will ask you to set " +"the next check number in the sequence and will then print all the checks at " +"once." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:127 +msgid "Aged payable balance" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:129 +msgid "" +"In order to get a list of open vendor bills and their related due dates, you" +" can use the **Aged Payable** report, under the reporting menu, (in " +":menuselection:`Reporting --> Business Statement --> Aged payable`) to get a" +" visual of all of your outstanding bills." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:137 +msgid "" +"From here, you can click directly on a vendors name to open up the details " +"of all outstanding bills and the amounts due, or you can annotate any line " +"for managements information. At any point in time while you're looking " +"through the report, you can print directly to Excel or PDF and get exactly " +"what you see on the screen." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:144 +msgid ":doc:`customer_invoice`" +msgstr "" + +#: ../../accounting/payables.rst:3 +msgid "Account Payables" +msgstr "" + +#: ../../accounting/payables/misc.rst:3 +msgid "Misc" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:3 +msgid "How to keep track of employee expenses?" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:5 +msgid "" +"Employee expenses are charges incurred on behalf of the company. The company" +" then reimburses these expenses to the employee. The receipts encountered " +"most frequently are:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:9 +msgid "car travel, reimbursed per unit of distance (mile or kilometer)," +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:11 +msgid "subsistence expenses, reimbursed based on the bill," +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:13 +msgid "" +"other purchases, such as stationery and books, destined for the company but " +"carried out by the employee." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:19 +msgid "" +"To manage expenses, you need to install the **Expense Tracker** application " +"from the Apps module." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:22 +msgid "" +"You will also need to install the **Sales Management** module in order to " +"re-invoice your expenses to your customers." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:25 +msgid "" +"Once these applications are installed you can configure the different " +"products that represent the types of expenses. To create the firsts " +"products, go to the menu :menuselection:`Configuration --> Expenses " +"Products` in the **Expenses** application." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:30 +msgid "Some examples of products can be:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:32 +msgid "**Travel (car)**" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:34 +#: ../../accounting/payables/misc/employee_expense.rst:50 +msgid "Product Type: Service" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:36 +#: ../../accounting/payables/misc/employee_expense.rst:52 +msgid "Invoicing Policy: Invoice based on time and material" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:38 +msgid "Expense Invoice Policy: At sales price" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:40 +msgid "Sale Price: 0.32" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:42 +msgid "" +"Unit of Measure: Km or mile (you will need to enable the **Multiple Unit of " +"Measures** option from :menuselection:`Sales module --> Configuration`)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:48 +msgid "**Hotel**" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:54 +msgid "Expense Invoice Policy: At cost" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:56 +msgid "Unit of Measure: Unit" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:58 +msgid "" +"In these examples, the first product will be an expense we reimburse to the " +"employee based on the number of km he did with his own car (e.g. to visit a " +"customer): 0.32€ / km. The hotel is reimbursed based on the real cost of the" +" hotel." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:63 +msgid "" +"Be sure that all these products have the checkbox **Can be expensed** " +"checked and the invoicing policy set to **Invoice Based on time and " +"material**. This invoicing policy means that, if the expense is related to a" +" customer project/sale order, Odoo will re-invoice this expense to the " +"customer." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:69 +msgid "Odoo support two types of expenses:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:71 +msgid "expenses paid by employee with their own money" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:73 +msgid "expenses paid with a company credit card" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:76 +msgid "The expenses workflow" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:79 +msgid "Record a new expense" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:81 +msgid "" +"Every employee of the company can register their expenses from " +":menuselection:`Expenses application --> My Expenses`. The workflow for " +"personal expenses work that way:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:85 +msgid "an employee record his expense, and submit it to the manager" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:87 +msgid "the manager approve or refuse the expense" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:89 +msgid "the accountant post journal entries" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:91 +msgid "" +"the company reimburse the employee expense (the employee is like a vendor, " +"with a payable account)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:94 +msgid "" +"if the expense is linked to an analytic account, the company can reinvoice " +"the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:97 +msgid "For every expense, the employee should record at least:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:99 +msgid "a description: that should include the reference of the ticket / bill" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:101 +msgid "a product: the expense type" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:103 +msgid "" +"a price (e.g. hotel) or a quantity (e.g. reimburse km if travel with his own" +" car)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:106 +msgid "" +"Depending of the policy of the company, he might have to attach a scan or a " +"photo of the expense. To do that, just a write a message in the bottom of " +"the expense with the scan of the bill/ticket in attachment." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:113 +msgid "" +"If the expense is linked to a customer project, you should not forget to set" +" an analytic account, related to the customer project or sale order (you " +"might have to activate analytic accounts in the accounting settings to get " +"this feature)." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:118 +msgid "" +"Once the expense is fully recorded, the employee has to click the button " +"**Submit to Manager**. In some companies, employees should submit their " +"expenses grouped at the end of the month, or at the end of a business trip." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:123 +msgid "" +"An employee can submit all his expenses in batch, using the Submit Expenses " +"action from the list view of expenses, or the small icons in the list view." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:128 +msgid "Validation by the manager" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:130 +msgid "" +"Managers should receive an email for every expense to be approved (the " +"manager of an employee is defined on the employee form). They can use the " +"menu **To Approve** to check all expenses that are waiting for validation." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:135 +msgid "The manager can:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:137 +msgid "" +"discuss on an expense to ask for more information (e.g., if a scan of the " +"bill is missing);" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:140 +msgid "reject an expense;" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:142 +msgid "approve an expense." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:145 +msgid "Control by the accountant" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:147 +msgid "" +"Then, all expenses that have been validated by the manager should be posted " +"by the accountant. When an expense is posted, the related journal entry is " +"created and posted in your accounting." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:151 +msgid "" +"If the accountant wants to create only one journal entry for a batch of " +"expenses, he can post expenses in batch from the list view of all expenses." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:156 +msgid "Reinvoice expenses to customers" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:158 +msgid "" +"If the expense was linked to an analytic account related to a sale order, " +"the sale order has a new line related to the expense. This line is not " +"invoiced to the customer yet and will be included in the next invoice that " +"will be send to the customer (charge travel and accommodations on a customer" +" project)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:164 +msgid "" +"To invoice the customer, just click on the invoice button on his sale order." +" (or it will be done automatically at the end of the week/month if you " +"invoice all your orders in batch)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:176 +msgid "Reimburse the employee" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:178 +msgid "" +"If the expense was paid with the employee's own money, the company should " +"reimburse the employee. In such a case, the employee will appear in the aged" +" payable balance until the company reimburse him his expenses." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:183 +msgid "" +"All you have to do is to create a payment to this employee for the amount " +"due." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:190 +msgid "Expenses that are not reinvoiced to customers" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:192 +msgid "" +"If some expenses should not be reinvoiced to customers, you have two " +"options:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:195 +msgid "" +"if the decision to invoice or not is related to the product, change the " +"invoicing policy on the product:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:198 +msgid "**based on time and material**: reinvoice the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:200 +msgid "**based on sale orders**: do not reinvoice the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:202 +msgid "" +"if you have to make an exception for one invoice that should not be " +"reinvoiced to the customer, do not set the related analytic account for this" +" invoice." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:208 +msgid ":doc:`forecast`" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:3 +msgid "How to forecast future bills to pay?" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:5 +msgid "" +"When you get hundreds of vendor bills per month with each of them having " +"different payment terms, it could be complex to follow what you have to pay " +"and when. Paying your vendors too early can decrease your cash " +"availabilities and paying too late can lead to extra charges." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:10 +msgid "" +"Fortunately, Odoo provides you the right tools to manage payment orders to " +"vendors efficiently." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:14 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:16 +msgid "" +"In order to track the vendor conditions, we use payment terms in Odoo. " +"Payment terms allow to keep track of the conditions to compute the due date " +"on an invoice. As an example, a payment term can be:" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:20 +msgid "50% within 30 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:22 +msgid "50% within 45 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:24 +msgid "" +"To create your most common payment terms, use the menu: " +":menuselection:`Configuration --> Management --> Payment Terms` in the " +"**Accounting** application. The following example show a payment term of 30%" +" directly and the balance after 30 days." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:32 +msgid "" +"Once payment terms are defined, you can assign them to your vendor by " +"default. Set the Vendor Payment Term field on the Accounting tab of a vendor" +" form. That way, every time you will purchase to this vendor, Odoo will " +"propose you automatically the right payment term." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:42 +msgid "" +"If you do not set a specific payment term on a vendor, you will still be " +"able to set a specific payment term on the vendor bill." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:46 +msgid "Forecast bills to pay with the Aged Payables report" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:48 +msgid "" +"In order to track amounts to be paid to the vendors, use the Aged Payable " +"report. You can get it from the Reports menu of the Accounting application. " +"This report gives you a summary per vendor of the amounts to pay, compared " +"to their due date (the due date being computed on each bill using the " +"payment term)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:57 +msgid "" +"This reports tells you how much you will have to pay within the next months." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:61 +msgid "Select bills to pay" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:63 +msgid "" +"Using the menu :menuselection:`Purchases --> Vendor Bills`, you can get a " +"list of vendor bills. Using the advanced filters, you can list all the bills" +" that you should pay or the bills that are overdue (you are late on the " +"payment)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:70 +msgid "" +"From this screen, you can also switch to the pivot table or the graph view " +"to get statistics on the amount due over the next month, using the group by " +"\"Due Date\" feature." +msgstr "" + +#: ../../accounting/payables/pay.rst:3 +msgid "Pay supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:3 +msgid "Pay by Checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:5 +msgid "" +"Once you decide to pay a supplier bill, you can select to pay by check. " +"Then, at the end of the day, the manager can print all checks by batch. " +"Finally, the bank reconciliation process will match the checks you sent to " +"suppliers with actual bank statements." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:14 +#: ../../accounting/payables/pay/sepa.rst:29 +msgid "Install the required module" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:16 +msgid "" +"To record supplier payments by checks, you must install the **Check " +"Writing** module. This module handle the process of recording checks in " +"Odoo. Others modules are necessary to print checks, according to the " +"country. As an example, the **U.S. Check Printing** module is required to " +"print U.S. checks." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:24 +msgid "" +"According to your country and the chart of account you use, those modules " +"may be installed by default. (example: United States users have nothing to " +"install, it's configured by default)." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:29 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:31 +msgid "" +"In order to allow payments by checks, you must activate the payment method " +"on related bank journals. From the accounting dashboard (the screen you get " +"when you enter the accounting application), click on your bank account on " +":menuselection:`More --> Settings` option. On the **Payment Method** field, " +"set **Check**." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:41 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:44 +msgid "United States" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:46 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:48 +msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:49 +msgid "**Peachtree**: check in the middle, stubs on top and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:50 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:52 +msgid "" +"It is also possible to customize your own check format through " +"customizations." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:55 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:57 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:59 +msgid "registering a payment you'd like to do on the bill" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:60 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:61 +msgid "reconcile bank statements" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:64 +msgid "Register a payment by check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:66 +msgid "" +"To register a payment on a bill, open any supplier bill from the menu " +":menuselection:`Purchases --> Supplier Bills`. Once the supplier bill is " +"validated, you can register a payment. Set the **Payment Method** to " +"**Check** and validate the payment dialog." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:74 +msgid "Explanation of the fields of the payment screen:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field used for usability purposes" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to hide the payment method if the selected journal has " +"only one available which is 'manual'" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to adapt the interface to the payment type selected." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"The selected journal is configured to print check numbers. If your pre-" +"printed check paper already has numbers or if the current numbering is " +"wrong, you can change it in the journal configuration page." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:80 +msgid "Try paying a supplier bill with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:85 +msgid "Print checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:87 +msgid "" +"From the accounting dashboard, on your bank account, you should see a link " +"\"X checks to print\". Click on this link and you will get the list of all " +"checks that are not printed yet. From this screen, you can print all checks " +"in batch or review them one by one." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:92 +msgid "" +"If you want to review every payment one by one before printing the check, " +"open on the payment and click on **Print Check** if you accept it. A dialog " +"will ask you the number of the check. It automatically proposes you the next" +" number, but you can change it if it does not match your next check number." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:98 +msgid "" +"To print all checks in batch, select all payments from the list view and " +"Print Check from the top \"print\" menu." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:107 +msgid "Reconcile Bank Statements" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:109 +msgid "" +"Once you process your bank statement, when the check is credited from your " +"bank account, Odoo will propose you automatically to match it with the " +"payment. This will mark the payment as **Reconciled**." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:115 +msgid "" +"to review checks that have not been credited, open the list of payments and " +"filter on the Sent state. Review those payments that have a date more than 2" +" weeks ago." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:120 +msgid "Pay anything with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:122 +msgid "" +"You can register a payment that is not related to a supplier bill. To do so," +" use the top menu :menuselection:`Purchases --> Payments`. Register your " +"payment and select a payment method by check." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:126 +msgid "" +"If you pay a specific supplier bill, put the reference of the bill in the " +"**Memo** field." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:132 +msgid "" +"Once your payment by check is registered, don't forget to **Confirm** it. " +"Once confirmed, you can use **Print Check** directly or follow the preceding" +" flow to print checks in batch:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:136 +msgid "`Print checks `_" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:138 +msgid "`Reconcile bank statements `_" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:3 +msgid "How to pay several bills at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:5 +msgid "" +"Odoo provides a simple and effective way to handle several bills at once, " +"with various quick or complex options. With one single process, anyone is " +"able to handle bills and payment in just a few clicks." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:10 +msgid "Pay multiple bills with one payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:13 +msgid "Record several payments" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:15 +msgid "" +"In the following example, we will generate some bills. You can control the " +"whole process from your accounting dashboard (first screen you get when you " +"open the accounting application)." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:22 +msgid "" +"To create a bill, open the Dashboard menu and click on **Vendor Bills**. In " +"the Vendor Bills window, click on **Create**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:28 +msgid "" +"Choose the vendor from which you wish to purchase the product, and click on " +"Add an item to add one (or more) product(s). Click on **Save** and then " +"**Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:33 +msgid "Pay supplier bills, one after the other" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:38 +msgid "" +"We will now record a payment for one bill only. Open the bill, then click on" +" **Register Payment**. Insert the Payment Method, Date and Amount, and click" +" on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:45 +msgid "" +"Once you have validated the payment, the system will automatically reconcile" +" the payment with the bill, and set the bill as **Paid**. The system will " +"also generate a move from the payment account and reconcile it with the " +"expense transaction." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:51 +msgid "Pay several bills altogether" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:53 +msgid "" +"In order to illustrate the process thoroughly, create at least 2 more bills " +"following the above standing guide. **Make sure all bills come from the same" +" vendor.**" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:60 +msgid "" +"In the Vendors Bills, select the new bills you have just created by checking" +" the box next to each of them. In the Action menu located in the middle of " +"the page, click on **Register Payment**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:67 +msgid "" +"Insert the details of the payment. The system calculated the total amount " +"for both bills, but you can modify it freely. Click on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:71 +msgid "Record the payment, reconcile afterwards" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:73 +msgid "" +"You can also reconcile a payment with bills after the payment has been " +"recorded." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:76 +msgid "First, we need to create a payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:78 +msgid "" +"This will handle from :menuselection:`Dashboard --> Bank journal --> More " +"Option --> Send Money`" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:84 +msgid "" +"Creating payment order with check payment method. Selecting related Vendor " +"and amount which remain to pay. After filling all details, we will confirm " +"the payment order which will generate payment transaction with the system." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:92 +msgid "" +"As you can see, bill payment status show what is posted and what is " +"remaining to reconcile." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:95 +msgid "" +"After receiving bank statement from the bank with payment detail, you can " +"reconcile the transaction from the Dashboard. It will automatically map the " +"transaction amount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:101 +msgid "For more detail on the bank reconciliation process, please read:" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:106 +msgid "Partial payments of several supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:109 +msgid "How to pay several supplier bills having cash discounts at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:111 +msgid "" +"You already learned how to pay bills in various way but what about partial " +"payment? We are taking another example where we will do partial payment for " +"various bills." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:115 +msgid "" +"We are creating multiple bills and partially pay them through bank " +"statements." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:118 +msgid "" +"We are adding payment terms which allow some cash discount where vendor " +"offer us early payment discount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:124 +msgid "" +"We are creating the following bills with the assignment of the above payment" +" term." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:130 +msgid "We have created the following bills:" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:135 +msgid "" +"We will pay the invoices by creating bank statement where we will adjust the" +" cash discount our vendor provided under payment terms." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:141 +msgid "" +"Before reconciling this bank statement, we need to create one statement " +"model for cash discount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:147 +msgid "Now we are going back to bank statement and opening reconcile view." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:151 +msgid "For bank statement reconciliation with model option, see" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:3 +#: ../../accounting/payables/pay/sepa.rst:67 +msgid "Pay with SEPA" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European union for simplification of bank transfers denominated in EURO." +" SEPA allows you to send payment orders to your bank to automate bank wire " +"transfer." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:10 +msgid "" +"SEPA is supported by the banks of the 28 EU member states as well as " +"Iceland, Norway, Switzerland, Andorra, Monaco and San Marino." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:13 +msgid "" +"With Odoo, once you decide to pay a vendor, you can select to pay the bill " +"with SEPA. Then, at the end of the day, the manager can generate the SEPA " +"file containing all bank wire transfers and send it to the bank. The file " +"follows the SEPA Credit Transfer 'PAIN.001.001.03' specifications. This is a" +" well-defined standard that makes consensus among banks." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:20 +msgid "" +"Once the payments are processed by your bank, you can directly import the " +"account statement inside Odoo. The bank reconciliation process will " +"seamlessly match the SEPA orders you sent to your bank with actual bank " +"statements." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:31 +msgid "" +"To pay suppliers with SEPA, you must install the **SEPA Credit Transfer** " +"module. This module handle the process of generating SEPA files based on " +"Odoo payments." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:37 +msgid "" +"According to your country and the chart of account you use, this module may " +"be installed by default." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:41 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:43 +msgid "" +"In order to allow payments by SEPA, you must activate the payment method on " +"related bank journals. From the accounting dashboard (the screen you get " +"when you enter the accounting application), click on \"More\" on your bank " +"account and select the \"Settings\" option." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:48 +msgid "" +"To activate SEPA, click the **Advanced Settings** tab and, in the **Payment " +"Methods** part of the **Miscellaneous** section, check the box **Sepa Credit" +" Transfer**." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:52 +msgid "" +"Make sure to specify the IBAN account number (domestic account number won't " +"work with SEPA) and the BIC (bank identifier code) on your bank journal." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:58 +msgid "" +"By default, the payments you send using SEPA will use your company name as " +"initiating party name. This is what appears on the recipient's bank " +"statement in the **payment from** field. You can customize it in your " +"company settings, in the tab **Configuration**, under the **SEPA** section." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:70 +msgid "Register your payments" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:72 +msgid "" +"You can register a payment that is not related to a supplier bill. To do so," +" use the top menu :menuselection:`Purchases --> Payments`. Register your " +"payment and select a payment method by Sepa Credit Transfer." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:76 +msgid "" +"If it's the first time you pay this vendor, you will have to fill in the " +"Recipient Bank Account field with, at least, the bank name, IBAN and BIC " +"(Bank Identifier Code). Odoo will automatically verify the IBAN format." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:80 +msgid "" +"For future payments to this vendor, Odoo will propose you automatically the " +"bank accounts but you will be able to select another one or create a new " +"one." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:84 +msgid "" +"If you pay a specific supplier bill, put the reference of the bill in the " +"**memo** field." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:90 +msgid "" +"Once your payment is registered, don't forget to Confirm it. You can also " +"pay vendor bills from the bill directly using the Register Payment button on" +" top of a vendor bill. The form is the same, but the payment is directly " +"linked to the bill and will be automatically reconciled to it." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:96 +msgid "Generate SEPA files" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:98 +msgid "" +"From your accounting dashboard, you should see if there are SEPA files to " +"generate for every bank account." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:104 +msgid "" +"Click on the link to check all the payments that are ready to transfer via " +"SEPA. Then, select all the payments you want to send (or check the top box " +"to select all payment at once) and click on :menuselection:`More --> " +"Download SEPA Payments`." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:116 +msgid "The bank refuses my SEPA file" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:118 +msgid "" +"Ask your bank if they support **PAIN.001.001.03 SEPA Credit Transfers**. If " +"they don't, or cannot provide relevant informations, please forward the " +"error message to your Odoo partner." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:123 +msgid "There is no Bank Identifier Code recorded for bank account ..." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:125 +msgid "" +"In order to send a SEPA payment, the recipient must be identified by a valid" +" IBAN and BIC. If this message appear, you probably encoded an IBAN account " +"for the partner you are paying but forgot to fill in the BIC field." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:132 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:168 +#: ../../accounting/receivables/customer_payments/followup.rst:168 +#: ../../accounting/receivables/customer_payments/recording.rst:129 +msgid ":doc:`check`" +msgstr "" + +#: ../../accounting/payables/supplier_bills.rst:3 +msgid "Supplier Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3 +msgid "When should I use supplier bills or purchase receipts?" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:5 +msgid "" +"Purchase receipts are different than vendor bills. Vendor bills are requests" +" for payment. If I issue a Purchase Order my vendor will in most business " +"cases send me a Vendor Bill. Depending on his invoice policy I then have a " +"defined amount of time to pay the Bill. A Purchase receipts are " +"confirmations of received payments. They are my day-to-day ticket receipts." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:12 +msgid "" +"From an accounting point of view this makes a difference as a Vendor Bill " +"will first credit a debt account before reconciling with the bank account. " +"On the other hand we usually immediately pay the purchase receipts, which " +"means no debt account is necessary." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:17 +msgid "" +"Moreover purchase receipts can have a different tax amount per product line," +" as vendors bills apply one tax amount over the entire bill." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:20 +msgid "" +"If my company's bank account is used to pay for goods where only a purchase " +"receipt are issued I should use the purchase receipts function in Odoo to " +"handle them in accounting." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:24 +msgid "" +"Let's take the following example: we need to buy tea for our customers from " +"a local tea store that doesn't issue bills. We go every week buy 50 euros " +"worth of tea and a teapot worth 20 euros. We pay with the company's bank " +"account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:32 +msgid "" +"To handle purchase receipts in Odoo one module and one app has to be " +"installed. Go into the app module and install the accounting app." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:38 +msgid "" +"Then, go in the search bar, delete the default module search, and search for" +" \"purchase\". Install the **Sale & Purchase Vouchers** module." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:45 +msgid "Register a receipt" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:47 +msgid "" +"By installing the **Sale & Purchase Vouchers** I've made the new **Purchase " +"Receipts** drop down menu visible in the accounting app." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:50 +msgid "" +"To import our 50 euros worth of tea purchase receipt, enter the accounting " +"app, select :menuselection:`Purchases --> Purchase Receipts`." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:53 +msgid "" +"Create a new Purchase Receipt and fill in all the necessary information. " +"Note that you have the choice in the Payment field between **Pay Later** or " +"**Pay Now**. It's a significant difference as Pay Later will generate a debt" +" accounting entry whereas Pay Now will immediately credit the Bank account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:59 +msgid "" +"In most cases you immediately pay, we will thus select the Pay Directly " +"option. Add the products, the related account and the appropriate taxe. For " +"the example we suppose the tea is a 12% taxe and the Tea Pott 21%." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:66 +msgid "" +"Validate the Purchase Receipt to post it. Don't forget you need to " +":doc:`reconcile payments <../../bank/reconciliation/use_cases>` in order to " +"completely close the transaction in your accounting." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:3 +msgid "How to manage vendor Bills?" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:5 +msgid "" +"The **Purchase** application allows you to manage your purchase orders, " +"incoming products, and vendor bills all seamlessly in one place." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:8 +msgid "" +"If you want to set up a vendor bill control process, the first thing you " +"need to do is to have purchase data in Odoo. Knowing what has been purchased" +" and received is the first step towards understanding your purchase " +"management processes." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:13 +msgid "Here is the standard work flow in Odoo:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:15 +msgid "" +"You begin with a **Request for Quotation (RFQ)** to send out to your " +"vendor(s)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:18 +msgid "" +"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase " +"Order (PO)**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:21 +msgid "" +"Confirming the PO generates an **Incoming Shipment** if you purchased any " +"stockable products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:24 +msgid "" +"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with " +"products received in the previous step to ensure accuracy." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:27 +msgid "" +"This process may be done by three different people within the company, or " +"only one." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:34 +msgid "Installing the Purchase and Inventory applications" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:36 +msgid "" +"From the **Apps** application, search for the **Purchase** module and " +"install it. Due to certain dependencies, Installing Purchase will " +"automatically install the **Inventory** and **Accounting** applications." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:41 +msgid "Creating products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:43 +msgid "" +"Creating products in Odoo is essential for quick and efficient purchasing " +"within Odoo. Simply navigate to the Products submenu under Purchase, and " +"click create." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:50 +msgid "" +"When creating the product, Pay attention to the **Product Type** field, as " +"it is important:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:53 +msgid "" +"Products that are set as **Stockable or Consumable** will allow you to keep " +"track of their inventory levels. These options imply stock management and " +"will allow for receiving these kinds of products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:58 +msgid "" +"Conversely, products that are set as a **Service or Digital Product** will " +"not imply stock management, simply due to the fact that there is no " +"inventory to manage. You will not be able to receive products under either " +"of these designations." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:65 +msgid "" +"It is recommended that you create a **Miscellaneous** product for all " +"purchases that occur infrequently and do not require inventory valuation or " +"management. If you create such a product, it is recommend to set the product" +" type to **Service**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:70 +msgid "Managing your Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:73 +msgid "Purchasing products or services" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:75 +msgid "" +"From the purchase application, you can create a purchase order with as many " +"products as you need. If the vendor sends you a confirmation or quotation " +"for an order, you may record the order reference number in the **Vendor " +"Reference** field. This will enable you to easily match the PO with the the " +"vendor bill later (as the vendor bill will probably include the Vendor " +"Reference)" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:85 +msgid "" +"Validate the purchase order and receive the products from the Inventory " +"application." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:89 +msgid "Receiving Products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:91 +msgid "" +"If you purchased any stockable products that you manage the inventory of, " +"you will need to receive the products from the Inventory application after " +"you confirm a Purchase Order. From the **Inventory dashboard**, you should " +"see a button linking you directly to the transfer of products. This button " +"is outlined in red below:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:100 +msgid "" +"Navigating this route will take you to a list of all orders awaiting to be " +"received." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:106 +msgid "" +"If you have a lot of awaiting orders, apply a filter using the search bar in" +" the upper right. With this search bar, you may filter based on the Vendor " +"(Partner), the product, or the source document, also known as the reference " +"of your purchase order. You also have the capability to group the orders by " +"different criteria under **Group By**. Selecting an item from this list will" +" open the following screen where you then will receive the products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:117 +msgid "Purchasing service products does not trigger a delivery order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:120 +msgid "Managing Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:122 +msgid "" +"When you receive a Vendor Bill for a previous purchase, be sure to record it" +" in the Purchases application under the **Control Menu**. You need to create" +" a new vendor bill even if you already registered a purchase order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:130 +msgid "" +"The first thing you will need to do upon creating a Vendor Bill is to select" +" the appropriate Vendor as this will also pull up any associated accounting " +"or pricelist information. From there, you can choose to specify any one or " +"multiple Purchase Orders to populate the Vendor Bill with. When you select a" +" Purchase Order from the list, Odoo will pull any uninvoiced products " +"associated to that Purchase Order and automatically populate that " +"information below. If you are having a hard time finding the appropriate " +"Vendor bill, you may search through the list by inputting the vendor " +"reference number or your internal purchase order number." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:144 +msgid "" +"While the invoice is in draft state, you can make any modifications you need" +" (i.e. remove or add product lines, modify quantities, and change prices)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:150 +msgid "Your vendor may send you several bills for the same Purchase Order if:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:152 +msgid "" +"Your vendor is in back-order and is sending you invoices as they ship the " +"products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:153 +msgid "Your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:155 +msgid "" +"Every time you record a new vendor bill, Odoo will automatically populate " +"the product quantities based on what has been received from the vendor. If " +"this value is showing a zero, this means that you have not yet received this" +" product and simply serves as a reminder that the product is not in hand and" +" you may need to inquire further into this. At any point in time, before you" +" validate the Vendor Bill, you may override this zero quantity." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:164 +msgid "Vendor Bill Matching" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:167 +msgid "What to do if your vendor bill does not match what you received" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:169 +msgid "" +"If the bill you receive from the vendor has different quantities than what " +"Odoo automatically populates as quantities, this could be due to several " +"reasons:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:173 +msgid "" +"the vendor is incorrectly charging you for products and/or services that you" +" have not ordered," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:176 +msgid "" +"the vendor is billing you for products that you might not have received yet," +" as the invoicing control may be based on ordered or received quantities," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:180 +msgid "or the vendor did not bill you for previously purchased products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:182 +msgid "" +"In these instances it is recommended that you verify that the bill, and any " +"associated purchase order to the vendor, are accurate and that you " +"understand what you have ordered and what you have already received." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:186 +msgid "" +"If you are unable to find a purchase order related to a vendor bill, this " +"could be due to one of a few reasons:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:189 +msgid "" +"the vendor has already invoiced you for this purchase order, therefore it is" +" not going to appear anywhere in the selection," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:192 +msgid "" +"someone in the company forgot to record a purchase order for this vendor," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:195 +msgid "or the vendor is charging you for something you did not order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:200 +msgid "How product quantities are managed" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:202 +msgid "" +"By default, services are managed based on ordered quantities, while " +"stockables and consumables are managed based on received quantities." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:205 +msgid "" +"If you need to manage products based on ordered quantities over received " +"quantities, you will need to belong to the group **Purchase Manager**. Ask " +"your system administrator to enable these access on :menuselection:`Settings" +" --> Users --> Users --> Access Rights`. Once you belong to the correct " +"group, select the product(s) you wish to modify, and you should see a new " +"field appear, labeled **Control Purchase Bills**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:215 +msgid "" +"You can then change the default management method for the selected product " +"to be based on either:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:218 +msgid "Ordered quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:220 +msgid "or Received quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:223 +msgid "Batch Billing" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:225 +msgid "" +"When creating a vendor bill and selecting the appropriate purchase order, " +"you may continue to select additional purchase orders and Odoo will add the " +"additional line items from that purchase order.. If you have not deleted the" +" previous line items from the first purchase order the bill will be linked " +"to all the appropriate purchase orders." +msgstr "" + +#: ../../accounting/receivables.rst:3 +msgid "Account Receivables" +msgstr "" + +#: ../../accounting/receivables/customer_invoices.rst:3 +msgid "Customer Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3 +msgid "How to setup cash discounts?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5 +msgid "" +"Cash discounts are an incentive (usually a small percentage) that you offer " +"to customers in return for paying a bill owed before the scheduled due date." +" If used properly, cash discounts improve the Days Sales Outstanding aspect " +"of a business's cash conversion cycle." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:10 +msgid "" +"For example, a typical cash discount would be: you offer a 2% discount on an" +" invoice due in 30 days if the customer were to pay within the first 5 days " +"of receiving the invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:18 +msgid "Payment terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:20 +msgid "" +"In order to manage cash discounts, we will use the payment terms concept of " +"Odoo (From the Accounting module, go to :menuselection:`Configuration --> " +"Management --> Payment terms --> Create`)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:24 +msgid "" +"Let's start with the above example: a 2% discount on an invoice due in 30 " +"days if the customer were to pay within the first 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27 +msgid "" +"A typical payment term of 30 days would have only one installment: balance " +"in 30 days. But, in order to configure the cash discount, you can configure " +"the payment term with two installments:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:31 +msgid "98% within 5 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:32 +msgid "balance within 30 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:37 +msgid "" +"To make it clear that it's not a payment term but a cash discount, don't " +"forget to set a clear description that will appear on the invoice: Invoice " +"is due within 30 days, but you can benefit from a 2% cash discount if you " +"pay within 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:43 +msgid "Bank reconciliation model" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:45 +msgid "" +"In order to speed up the bank reconciliation process, we can create a model " +"of entry for all cash discounts. To do that, from the Accounting application" +" dashboard, click on the \"More\" link on the bank and choose the option " +"\"Reconciliation Models\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:53 +msgid "Create a new model for cash discounts as follow:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:55 +msgid "**Button Label**: Cash Discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:56 +msgid "**Account**: Cash Discount (according to your country)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:57 +msgid "**Amount Type**: Percentage" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58 +msgid "**Amount**: 100%" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "**Taxes**: depending on your country, you may put a tax on the cash" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "discount if taxes have to be deduced" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:67 +msgid "" +"Even if it's a 2% cash discount, set a 100% amount on the reconciliation " +"model as it means 100% of the remaining balance (the 2%). You can use the " +"same reconciliation model for all your cash discount. No need to create a " +"model per payment term." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:73 +msgid "Creating an invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:75 +msgid "" +"When you create a customer invoice, set the right payment term \"30 days, 2%" +" cash discount\" right after having selected the customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:81 +msgid "" +"Once the invoice is validated, Odoo will automatically split the account " +"receivable part of the journal entry with two installments having a " +"different due date: 98% within 5 days, 2% within 30 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:92 +msgid "Paying the invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:94 +msgid "" +"If the customer pays with a cash discount, when processing the bank " +"statement, you will match the payment (98%) with the related line in the " +"journal entry." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:101 +msgid "" +"As you can see in the above screenshot, when selecting the customer, you " +"also see the 2% remaining of 3$. If you want to accept the cash discount (if" +" the customer paid within the 5 days), you can click on this line with 2%, " +"click on \"Open Balance\", and select your \"Cash Discount\" reconciliation " +"model. That way, the invoice is marked as fully paid." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:109 +msgid "" +"from now on, matching the remaining 2% has to be done manually. In the " +"future, we plan to automate the reconciliation of the 2% if the 98% are paid" +" on time." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:113 +msgid "Paying the invoice in full" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:115 +msgid "" +"If the customer pays the invoice fully, without benefiting from the cash " +"discount, you will reconcile the payment (in full) with the two lines from " +"the invoice (98% and 2%). Just click on the two lines to match them with the" +" payment." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:125 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:116 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 +msgid ":doc:`overview`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues: how to automate them?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:5 +msgid "" +"Deferred/unearned revenue is an advance payment recorded on the recipient's " +"balance sheet as a liability account until either the services have been " +"rendered or the products have been delivered. Deferred revenue is a " +"liability account because it refers to revenue that has not yet been earned," +" but represents products or services that are owed to the customer. As the " +"products or services are delivered over time, the revenue is recognized and " +"posted on the income statement." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:13 +msgid "" +"For example: let's say you sell a 2 year support contract for $24,000 that " +"begins next month for a period of 24 months. Once you validate the customer " +"invoice, the $24.000 should be posted into a deferred revenues account. This" +" is because the $24,000 you received has not yet been earned." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:19 +msgid "" +"Over the next 24 months, you will be reducing the deferred revenues account " +"by $1,000 ($24,000/24) on a monthly basis and recognizing that amount as " +"revenue." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:27 +msgid "Module installation" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:29 +msgid "" +"In order to automate deferred revenues, go to the settings menu under the " +"application :menuselection:`Accounting --> Configuration` and activate the " +"**Assets management & revenue recognition** option. This will install the " +"**Revenue Recognition Management** module." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:36 +msgid "" +"In some version of Odoo 9, besides checking this option, you need to install" +" the \"Revenue Recognition Management\" module. If you are using Odoo 9, you" +" might check if the module is correctly installed." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:41 +msgid "Define deferred revenue types" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:43 +msgid "" +"Once the module is installed, you need to create deferred revenue types. " +"From the Accounting application, go to the menu " +":menuselection:`Configuration --> Deferred Revenues Types`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:51 +msgid "Example: 12 months maintenance contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:53 +msgid "Some example of deferred revenues types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:55 +msgid "1 year service contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:56 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 +msgid "3 years service contracts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:59 +msgid "Set deferred revenues on products" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:61 +msgid "" +"Once deferred revenues types are defined, you can set them on the related " +"products. On the product form, in the Accounting tab, you can set a deferred" +" revenue type." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:65 +msgid "" +"Here are some examples of products and their related deferred revenue types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Product" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Deferred Revenue Type" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 +msgid "Support Contract: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 +msgid "Netflix subscription: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "Flowers every month" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "1 year product contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:79 +msgid "Sell and invoice products" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:81 +msgid "" +"Once the products are configured, you can create a customer invoice using " +"this product. Once the customer invoice is validated, Odoo will " +"automatically create a deferred revenue for you, and the related journal " +"entry." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Dr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Cr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +msgid "Accounts receivable" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +msgid "24000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +msgid "Deferred revenue account" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:94 +msgid "" +"Then, every month, Odoo will post a journal entry for the revenue " +"recognition." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "1000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "Service revenue account" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:108 +msgid "" +"To analyze all your current contracts having a deferred revenue, you can use" +" the menu Reporting > Deferred Revenue Analysis." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:3 +msgid "How to define an installment plan on customer invoices?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:4 +msgid "" +"In order to manage installment plans related to an invoice, you should use " +"payment terms in Odoo. They apply on both customer invoices and supplier " +"bills." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:8 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:8 +msgid "Example, for a specific invoice:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:10 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10 +msgid "Pay 50% within 10 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:11 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:12 +msgid "Pay the remaining balance within 30 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:15 +msgid "" +"payment terms are not to be confused with a payment in several parts. If, " +"for a specific order, you invoice the customer in two parts, that's not a " +"payment term but an invoice policy." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:22 +msgid "" +"Configure your usual installment plans from the application " +":menuselection:`Accounting --> Configuration > Payment Terms`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:25 +msgid "" +"A payment term may have one line (ex: 21 days) or several lines (10% within " +"3 days and the balance within 21 days). If you create a payment term with " +"several lines, make sure the latest one is the balance. (avoid doing 50% in " +"10 days and 50% in 21 days because, with the rounding, it may not compute " +"exactly 100%)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:36 +msgid "" +"The description of the payment term will appear on the invoice or the sale " +"order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:39 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:38 +msgid "Payment terms for customers" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:41 +msgid "You can set payment terms on:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:43 +msgid "" +"**a customer**: the payment term automatically applies on new sales orders " +"or invoices for this customer. Set payment terms on customers if you grant " +"this payment term for all future orders for this customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:48 +msgid "" +"**a quotation**: the payment term will apply on all invoices created from " +"this quotation or sale order, but not on other quotations" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:51 +msgid "**an invoice**: the payment term will apply on this invoice only" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:53 +msgid "" +"If an invoice contains a payment term, the journal entry related to the " +"invoice is different. Without payment term, an invoice of $100 will produce " +"the following journal entry (for the clarity of the example, we did not set " +"any tax on the invoice):" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +msgid "Due date" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:66 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:65 +msgid "" +"If you do an invoice the 1st of January with a payment term of 10% within 3 " +"days and the balance within 30 days, you get the following journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "Jan 03" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "10" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +msgid "Jan 30" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +msgid "90" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:80 +msgid "" +"On the customer statement, you will see two lines with different due dates. " +"To get the customer statement, use the menu Sales > Customers Statement." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:87 +msgid ":doc:`payment_terms`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:3 +msgid "How to modify a validated invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:5 +msgid "" +"In most accounting legislation over the word, it's not allowed to modify an " +"invoice that is validated and sent to the customer. However, you sometimes " +"need to change an invoice for different reasons: the sale has changed, the " +"made a mistake while recording the invoice, etc." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:10 +msgid "Thus, the right way to modify an invoice is to:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:12 +msgid "Refund the original invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:13 +msgid "Create a new invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:15 +msgid "" +"Odoo's refund mechanism helps you handle the whole process in just a few " +"clicks." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:19 +msgid "Modify an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:21 +msgid "" +"If your invoice is still in draft, you can modify it the way you want. " +"However, if your invoice is validated, you can not change it anymore. If you" +" need to modify it, the right operations to do are:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:25 +msgid "Refund the original invoice;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:26 +msgid "Reconcile the original invoice with the refund to void them;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:27 +msgid "Create a new draft invoice, a copy of the original;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:28 +msgid "Validate the new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:30 +msgid "" +"All those steps are automated by Odoo. All you have to do is to click on the" +" Refund button on an invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:36 +msgid "" +"In the refund dialog, select the option \"Modify: create a refund, reconcile" +" and create a draft invoice\". Once you click on the \"Create Refund\" " +"button, Odoo will void your existing invoice and create a new draft invoice " +"that is a duplicate of the original one." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:41 +msgid "Edit this new draft invoice and validate it when it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:45 +msgid "" +"if you already sent the original invoice to your customer, you should send " +"the new invoice and the refund to the customer so that he gets all the " +"documents." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:50 +msgid ":doc:`refund`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:3 +msgid "Overview of the invoicing process" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:21 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:25 +msgid "" +"Invoice manually: use a button on the sale order to trigger the draft " +"invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:28 +msgid "" +"Invoice before delivery: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:33 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:37 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice the " +"whole order, invoice a percentage (advance), invoice some lines, invoice a " +"fixed advance." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:47 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:49 +msgid "" +"Retailers and eCommerce usually invoice based on delivery orders, instead of" +" sales order. This approach is suitable for businesses where the quantities " +"you deliver may differs from the ordered quantities: foods (invoice based on" +" actual Kg)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:54 +msgid "" +"This way, if you deliver a partial order, you only invoice for what you " +"really delivered. If you do back orders (deliver partially and the rest " +"later), the customer will receive two invoices, one for each delivery order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:62 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:64 +msgid "" +"An eCommerce order will also trigger the creation of the order when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:70 +msgid "Contracts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:73 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:75 +msgid "" +"If you use contracts, you can trigger invoice based on time and material " +"spent, expenses or fixed lines of services/products. Every month, the " +"salesperson will trigger invoice based on activities on the contract." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:79 +msgid "Activities can be:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:81 +msgid "" +"fixed products/services, coming from a sale order linked to this contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:83 +msgid "materials purchased (that you will re-invoiced)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:85 +msgid "time and material based on timesheets or purchases (subcontracting)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:87 +msgid "" +"expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:89 +msgid "" +"You can invoice at the end of the contract or trigger intermediate invoices." +" This approach is used by services companies that invoice mostly based on " +"time and material. For services companies that invoice on fix price, they " +"use a regular sales order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:101 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:111 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:113 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:118 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:121 +msgid "if you need to create a refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:123 +msgid "If you need to give a discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:125 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:127 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:130 +msgid "Specific modules" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:132 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:134 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:136 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:3 +msgid "How to setup and use payment terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:5 +msgid "" +"Payment terms define the conditions to pay an invoice. They apply on both " +"customer invoices and supplier bills." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:14 +msgid "" +"Payment terms are different from invoicing in several areas. If, for a " +"specific order, you invoice the customer in two parts, that's not a payment " +"term but invoice conditions." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:21 +msgid "" +"Configure your usual payment terms from the Configuration menu of the " +"Account application. The description of the payment term is the one that " +"appear on the invoice or the sale order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:25 +msgid "" +"A payment term may have one line (ex: 21 days) or several lines (10% within " +"3 days and the balance within 21 days). If you create a payment term with " +"several lines, be sure the latest one is the balance. (avoid doing 50% in 10" +" days and 50% in 21 days because, with the rounding, it may not do exactly " +"100%)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:35 +msgid "Using Payment Terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:40 +msgid "Payment terms can be set on:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:42 +msgid "" +"**a customer**: to apply this payment term automatically on new sale orders " +"or invoices for this customer. Set payment terms on customers if you grant " +"this payment term for all future orders of this customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:47 +msgid "" +"**a quotation**: to apply this payment term on all invoices created from " +"this quotation or sale order, but not on other quotations" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:51 +msgid "**an invoice**: to apply the payment term on this invoice only" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:53 +msgid "" +"If an invoice has a payment term, the journal entry related to the invoice " +"is different. Without payment term or tax, an invoice of $100 will produce " +"this journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:79 +msgid "" +"In the customer statement, you will see two lines with different due dates." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:83 +msgid "Payment terms for vendor bills" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:85 +msgid "" +"The easiest way to manage payment terms for vendor bills is to record a due " +"date on the bill. You don't need to assign a payment term, just the due date" +" is enough." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:89 +msgid "" +"But if you need to manage vendor terms with several installments, you can " +"still use payment terms, exactly like in customer invoices. If you set a " +"payment term on the vendor bill, you don't need to set a due date. The exact" +" due date for all installments will be automatically created." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:3 +msgid "How to edit or refund an invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:4 +msgid "" +"In Odoo, it's not possible to modify an invoice that has been validated and " +"sent to the customer. If a mistake was made on a validated invoice, the " +"legal way to handle that is to refund the invoice, reconcile it with the " +"original invoice to close them and create a new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:10 +msgid "Modifying a validated invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:12 +msgid "" +"If you need to modify an existing invoice, use the Refund Invoice button on " +"the invoice. In the refund method field, select \"Modify: create a refund, " +"reconcile, and create a new draft invoice\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:19 +#: ../../accounting/receivables/customer_invoices/refund.rst:37 +msgid "Odoo will automatically:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:21 +#: ../../accounting/receivables/customer_invoices/refund.rst:39 +msgid "Create a refund for your invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:22 +#: ../../accounting/receivables/customer_invoices/refund.rst:40 +msgid "" +"Reconcile the refund invoice with the original invoice (marking both as " +"Paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:23 +msgid "Create a new draft invoice you can modify" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:25 +msgid "" +"Then, you can modify the draft invoice and validate it once it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:28 +msgid "Cancelling an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:30 +msgid "" +"If you need to cancel an existing invoice, use the Refund Invoice button on " +"the invoice. In the refund method field, select \"Cancel: create a refund " +"and reconcile\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:42 +msgid "" +"Nothing else needs to be done. You can send the refund by regular mail or " +"email to your customer, if you already sent the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:46 +msgid "Refunding part of an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:48 +msgid "" +"If you need to refund an existing invoice partially, use the Refund Invoice " +"button on the invoice. In the refund method field, select \"Create a draft " +"refund\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:55 +msgid "" +"Odoo will automatically create a draft refund. You may modify the refund " +"(example: remove the lines you do not want to refund) and validate it. Then," +" send the refund by regular mail or email to your customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:61 +msgid "" +"Refunding an invoice is different from refunding a payment. Usually, a " +"refund invoice is sent before the customer has done a payment. If the " +"customer has already paid, they should be reimbursed by doing a customer " +"payment refund." +msgstr "" + +#: ../../accounting/receivables/customer_payments.rst:3 +msgid "Customer Payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:3 +msgid "How to register customer payments by checks?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:5 +msgid "" +"There are two ways to handle payments received by checks. Odoo support both " +"approaches so that you can use the one that better fits your habits." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:9 +msgid "" +"**Undeposited Funds:** once you receive the check, you record a payment by " +"check on the invoice. (using a Check journal and posted on the Undeposited " +"Fund account) Then, once the check arrives in your bank account, move money " +"from Undeposited Funds to your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:16 +msgid "" +"**One journal entry only:** once your receive the check, you record a " +"payment on your bank, paid by check, without going through the **Undeposited" +" Funds**. Once you process your bank statement, you do the matching with " +"your bank feed and the check payment, without creating a dedicated journal " +"entry." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:23 +msgid "" +"We recommend the first approach as it is more accurate (your bank account " +"balance is accurate, taking into accounts checks that have not been cashed " +"yet). Both approaches require the same effort." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:27 +msgid "" +"Even if the first method is cleaner, Odoo support the second approach " +"because some accountants are used to it (quickbooks and peachtree users)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:32 +msgid "" +"You may have a look at the *Deposit Ticket feature* if you deposit several " +"checks to your bank accounts in batch." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:36 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:37 +msgid "Option 1: Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:41 +msgid "Create a journal **Checks**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:43 +msgid "Set **Undeposited Checks** as a defaut credit/debit account" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:45 +msgid "" +"Set the bank account related to this journal as **Allow Reconciliation**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:48 +#: ../../accounting/receivables/customer_payments/check.rst:109 +msgid "From check payments to bank statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:50 +msgid "" +"The first way to handle checks is to create a check journal. Thus, checks " +"become a payment method in itself and you will record two transactions." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:54 +#: ../../accounting/receivables/customer_payments/check.rst:111 +msgid "" +"Once you receive a customer check, go to the related invoice and click on " +"**Register Payment**. Fill in the information about the payment:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:57 +msgid "" +"Payment method: Check Journal (that you configured with the debit and credit" +" default accounts as **Undeposited Funds**)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:60 +msgid "Memo: write the Check number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:65 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:74 +msgid "This operation will produce the following journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Statement Match" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +#: ../../accounting/receivables/customer_payments/check.rst:85 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/check.rst:135 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 +msgid "100.00" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +msgid "Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:75 +#: ../../accounting/receivables/customer_payments/check.rst:121 +msgid "The invoice is marked as paid as soon as you record the check." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:77 +msgid "" +"Then, once you get the bank statements, you will match this statement with " +"the check that is in Undeposited Funds." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:83 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +msgid "X" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:89 +msgid "" +"If you use this approach to manage received checks, you get the list of " +"checks that have not been cashed in the **Undeposit Funds** account " +"(accessible, for example, from the general ledger)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:94 +msgid "" +"Both methods will produce the same data in your accounting at the end of the" +" process. But, if you have checks that have not been cashed, this one is " +"cleaner because those checks have not been reported yet on your bank " +"account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:100 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:110 +msgid "Option 2: One journal entry only" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:105 +msgid "" +"These is nothing to configure if you plan to manage your checks using this " +"method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:114 +msgid "**Payment method:** the bank that will be used for the deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:116 +msgid "Memo: write the check number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:123 +msgid "" +"Once you will receive the bank statements, you will do the matching with the" +" statement and this actual payment. (technically: point this payment and " +"relate it to the statement line)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:127 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:137 +msgid "" +"With this approach, you will get the following journal entry in your books:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:139 +msgid "" +"You may also record the payment directly without going on the customer " +"invoice, using the menu :menuselection:`Sales --> Payments`. This method may" +" be more convenient if you have a lot of checks to record in a batch but you" +" will have to reconcile entries afterwards (matching payments with invoices)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:145 +msgid "" +"If you use this approach to manage received checks, you can use the report " +"**Bank Reconciliation Report** to verify which checks have been received or " +"paid by the bank. (this report is available from the **More** option from " +"the Accounting dashboard on the related bank account)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:3 +msgid "How to register credit card payments on invoices?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:5 +msgid "" +"There are two ways to handle payments received by credit cards. Odoo support" +" both approaches so that you can use the one that better fits your habits." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:9 +msgid "" +"**Undeposited Funds** (mostly used in european countries): once you receive " +"the credit card payment authorization, you record a payment by credit card " +"on the invoice (using a Credit card journal and posted on the Undeposited " +"Fund account). Then, once the credit card payments arrives in your bank " +"account, move money from Undeposited Funds to your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:16 +msgid "" +"**One journal entry only** (mostly used in the U.S.): once your receive the " +"credit card payment, you record a payment on your bank, paid by credit card," +" without going through the Undeposited Funds. Once you process your bank " +"statement, you do the matching with your bank feed and the credit card " +"payment, without creating a dedicated journal entry ." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:23 +msgid "" +"We recommend the first approach as it is more accurate (your bank account " +"balance is accurate, taking into accounts credit cards that have not been " +"cashed yet). Both approaches require the same effort." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:27 +msgid "" +"If you use eCommerce and an automated payment gateway, you will only need to" +" take care of the bank reconciliation part as paid invoice will be " +"automatically recorded in the right journal. You will use the second " +"approach." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:32 +msgid "" +"Even if the first method is cleaner, Odoo support the second approach " +"because some accountants are used to it (*QuickBooks* and *Peachtree* " +"users)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:42 +msgid "" +"On the Accounting module, go to :menuselection:`Configuration --> Journals " +"--> Create`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:44 +msgid "" +"Create a Journal called 'Credit card payments' with the following data:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:46 +msgid "**Journal Name**: Credit card" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:47 +msgid "**Default debit account**: Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:48 +msgid "**Default credit account**: Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:50 +msgid "" +"Once it's done, don't forget to set the \"Credit cards\" account as \"Allow " +"Reconciliation\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:57 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:119 +msgid "From credit card payments to bank statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:59 +msgid "" +"The first way to handle credit cards is to create a credit card journal. " +"Thus, credit cards become a payment method in itself and you will record two" +" transactions." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:63 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:121 +msgid "" +"Once you receive a customer credit card payment, go to the related invoice " +"and click on Register Payment. Fill in the information about the payment:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:67 +msgid "**Payment method**: Credit card" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:69 +msgid "**Memo**: write the invoice reference" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 +msgid "Credit Cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:84 +msgid "" +"The invoice is marked as paid as soon as you record the credit card payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:87 +msgid "" +"Then, once you get the bank statements, you will match this statement with " +"the credit card that is in the 'Credit card' account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +msgid "Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:98 +msgid "" +"If you use this approach to manage credit cards payments, you get the list " +"of credit cards payments that have not been cashed in the \"Credit card\" " +"account (accessible, for example, from the general ledger)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:104 +msgid "" +"Both methods will produce the same data in your accounting at the end of the" +" process. But, if you have credit cards that have not been cashed, this one " +"is cleaner because those credit cards have not been reported yet on your " +"bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:115 +msgid "" +"There is nothing to configure if you plan to manage your credit cards using " +"this method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:125 +msgid "**Payment method**: the bank that will be used for the deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:127 +msgid "**Memo**: write the credit card transaction number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:132 +msgid "" +"The invoice is marked as paid as soon as the credit card payment has been " +"recorded. Once you receive the bank statements, you will do the matching " +"with the statement and this actual payment (technically: point this payment " +"and relate it to the statement line)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:150 +msgid "" +"You may also record the payment directly without going on the customer " +"invoice, using the top menu :menuselection:`Sales --> Payments`. This method" +" may be more convenient if you have a lot of credit cards to record in a " +"batch but you will have to reconcile entries afterwards (matching payments " +"with invoices)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:155 +msgid "" +"If you use this approach to manage received credit cards, you can use the " +"report \"Bank Reconciliation Report\" to verify which credit cards have been" +" received or paid by the bank (this report is available from the \"More\" " +"option from the Accounting dashboard on the related bank account)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:166 +#: ../../accounting/receivables/customer_payments/followup.rst:167 +msgid ":doc:`recording`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:167 +#: ../../accounting/receivables/customer_payments/recording.rst:128 +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:169 +#: ../../accounting/receivables/customer_payments/recording.rst:130 +msgid ":doc:`followup`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:3 +msgid "How to get paid and organize customer follow-ups?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:5 +msgid "" +"Getting paid and organizing customer reminders is always a difficult task, " +"however it is critical for the health of the company to stay diligent about " +"outstanding receivables. Fortunately, Odoo provides the right tools to track" +" receivables, automate customer statements, and measure your performance." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:12 +msgid "Customer follow-ups: A step by step guide" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:15 +msgid "Cleaning up outstanding payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:17 +msgid "" +"If you have any unreconciled transactions in your bank account, you will " +"need to process them first before you begin analyzing your customers " +"statements. This ensures that you have recorded all of the latest customer " +"payments before sending out reminders to any customers with outstanding " +"balances." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:27 +msgid "Checking the Aged Receivables report" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:29 +msgid "" +"After you have reconciled all of your bank accounts, you can then generate " +"an accurate Aged Receivables Report from the Reports menu. This report will " +"display all of the customers and their outstanding balances on open " +"invoices." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:37 +msgid "" +"The report displays this information in time increments to better paint a " +"picture of the outstanding balances your customers hold and for how long " +"they have held these outstanding balances. You can then appropriately focus " +"your efforts on the appropriate customers." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:42 +msgid "" +"You can then select any of the customers on this list and Odoo will open up " +"their invoice details in the form of the Customer Follow-Up letter, also " +"known as the **Customer Statement**." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:49 +msgid "From the customer statement, you can:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:51 +msgid "Change and customize the message that is sent to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:53 +msgid "Send a reminder email to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:55 +msgid "Send a printed reminder letter to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:57 +msgid "Send automated printed reminders by utilizing our Docsaway integration" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:60 +msgid "Zoom in on the different open invoices or payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:62 +msgid "Remove an invoice or payment from the report (in case of conflict)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:64 +msgid "Log any call notes made to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:66 +msgid "" +"Schedule your next follow up task to stay on top of customer payments (e.g. " +"call back in 15 days if not payments are made)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:69 +msgid "" +"You can set reminders for when you would like to next contact the particular" +" customer. Selecting **Manual** will open up the follow up scheduling tool, " +"while selecting **Auto** will automatically recommend that you contact the " +"customer 15 days from then if the customer has not yet paid for the invoice." +" Installing the **Follow-Up Plans** module will allow you to define " +"automated actions and intervals to send reminders." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:79 +msgid "" +"If you have already sent out a reminder to a customer a few days ago, a " +"warning message will appear at the top of the screen, reminding you that you" +" should not send another reminder so soon since one was already sent " +"recently. Every time you log a note, Odoo will automatically set the next " +"reminder date, unless you choose to manually set it by selecting the next " +"reminder button at the top right of the screen." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:88 +msgid "" +"You can also specify the expected payment date on an invoice line directly, " +"therefore defining the next reminder in case the invoice has not been paid." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:92 +msgid "Sending customer statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:94 +msgid "" +"Send your customers reminders in batches in the menu :menuselection:`Sales " +"--> Customer Statements`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:97 +msgid "" +"Here Odoo will open all the statements awaiting to be processed, which is " +"determined by the last reminder they received. You can choose to process " +"them one by one, send multiple letters or emails in batches, or set a next " +"action date for the next time they'll be contacted." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:104 +msgid "" +"If an invoice has not yet been paid, Odoo will remind you to contact at " +"particular customer based after their next action date." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:107 +msgid "" +"You can access the customer statement report daily and Odoo will only " +"display the customers you need to contact on any given day. This is based " +"on:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:111 +msgid "Customers you have not yet received a payment from" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:113 +msgid "" +"Customers that have not been reminded over the last X days (\"X\" being " +"defined as the overdue date of the invoice after the first reminder, then " +"the next action date set at every reminder)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:118 +msgid "Setting up your dunning process" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:120 +msgid "" +"The **Payment Follow-up Management** module allows you to define reminder " +"plans. After installing it from the **Apps** menu, go to the **Follow-up " +"Levels** menu in the accounting configuration to set up your dunning " +"process." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:125 +msgid "Some Examples are:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:127 +msgid "**Email**: 3 days before overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:129 +msgid "**Email+Letter**: at the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:131 +msgid "**Email+Call**: 15 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:133 +msgid "**Email+Letter**: 60 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:138 +msgid "" +"Thanks to this module, you can send every email and letters in batches for " +"all your customers at once. The next reminder will automatically be computed" +" based on your configured follow-up plan." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:142 +msgid "" +"The module will also add a red/green dot on each customer, this will allow " +"you to easily mark customer status's with the following options: \"Good " +"Debtor, Normal Debtor, or bad debtors." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:150 +msgid "DSO: Measuring your performance" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:152 +msgid "" +"The DSO (Days of Outstanding Sales) is a measure of the average number of " +"days that a company takes to collect revenue after a sale has been made. DSO" +" is calculated by dividing the amount of accounts receivable during a given " +"period by the total value of credit sales during the same period, and " +"multiplying the result by the number of days in the period measured." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:159 +msgid "" +"You can get the DSO of your company from the Executive Summary report under " +"Reporting (check the KPI average debtors days)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:3 +msgid "What are the different ways to record a payment?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:5 +msgid "" +"In Odoo, a payment can either be linked directly to an invoice or be a stand" +" alone record for use on a later date:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:8 +msgid "" +"If a payment is linked to an invoice, it reduces the amount due of the " +"invoice. You can have multiple payments linked to the same invoice." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:12 +msgid "" +"If a payment is not linked to an invoice, the customer has an outstanding " +"credit with your company, or your company as an outstanding balance with a " +"vendor. You can use this outstanding credit/debit to pay future invoices or " +"bills." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:18 +msgid "Paying an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:20 +msgid "" +"If you register a payment on a customer invoice or a vendor bill, the " +"payment is automatically reconciled with the invoice reducing the amount " +"due." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:27 +msgid "" +"The green icon near the payment line will display more information about the" +" payment. From there you can choose to open the journal entry or reconcile " +"the payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:33 +msgid "" +"If you unreconcile a payment, it is still registered in your books but not " +"linked to the specific invoice any longer. If you unreconcile a payment in a" +" different currency, Odoo will create a journal entry to reverse the " +"Currency Exchange Loss/Gain posted at the time of reconciliation." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:39 +msgid "Payments not tied to an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:42 +msgid "Registering a payment" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:44 +msgid "" +"In the Accounting application, you can create a new payment from the Sales " +"menu (register a customer payment) or the Purchases menu (pay a vendor). If " +"you use these menus, the payment is not linked to an invoice, but can easily" +" be reconciled on an invoice later on." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:52 +msgid "" +"When registering a new payment, you must select a customer or vendor, the " +"payment method, and the amount of the payment. The currency of the " +"transaction is defined by the payment method. If the payment refers to a " +"document (sale order, purchase order or invoice), set the reference of this " +"document in the memo field." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:58 +msgid "" +"Once confirmed, a journal entry will be posted reflecting the transaction " +"just made in the accounting application." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:62 +msgid "Reconciling invoice payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:64 +msgid "" +"The easiest way of reconciling a payment with an invoice is to do so on the " +"invoice directly." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:67 +msgid "" +"When validating a new invoice, Odoo will warn you that an outstanding " +"payment for this customer or vendor is available. In this case, you can " +"reconcile this payment to the invoice near the totals at the bottom, under " +"\"Outstanding Payments\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:76 +msgid "Reconciling all your outstanding payments and invoices" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:78 +msgid "" +"If you want to reconcile all outstanding payments and invoices at once " +"(instead of doing so one by one), you can use the batch reconciliation " +"feature within Odoo." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:82 +msgid "" +"The batch reconciliation feature is available from the dashboard on the " +"Customer Invoices card and the Vendor Bills card for reconciling Accounts " +"Receivable and Payable, respectively." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:89 +msgid "" +"The payments matching tool will open all unreconciled customers or vendors " +"and will give you the opportunity to process them all one by one, doing the " +"matching of all their payments and invoices at once." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:96 +msgid "" +"During the reconciliation, if the sum of the debits and credits do not " +"match, it means there is still a remaining balance that either needs to be " +"reconciled at a later date, or needs to be written off directly." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:101 +msgid "Transferring money from one bank account to another" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:103 +msgid "" +"Just like making a customer or vendor payment, you transfer cash internally " +"between your bank accounts from the dashboard or from the menus up top." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:110 +msgid "" +"This will take you to the same screen you have for receiving and making " +"payments." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:118 +msgid "" +"When making an internal transfer from one bank account to another, select " +"the bank you want to apply the transfer from in the dashboard, and in the " +"register payments screen, you select the transfer to account. Do not go " +"through this process again in the other bank account or else you will end up" +" with two journal entries for the same transaction." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr "" + +#: ../../accounting/receivables/getting_paid.rst:3 +msgid "How to get paid?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:3 +msgid "How to automate customer follow-ups with plans?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:5 +msgid "" +"With the Odoo Accounting application, you get a dynamic aged receivable " +"report, customer statements and you can easily send them to customers." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:8 +msgid "" +"If you want to go further in the automation of the credit collection " +"process, you can use follow-up plans. They will help you automate all the " +"steps to get paid, by triggering them at the right time: send customer " +"statements by emails, send regular letter (through the Docsaway " +"integration), create a task to manually call the customer, etc..." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:14 +msgid "Here is an example of a plan:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "When?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "What?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "Who?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "3 days before due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "Email" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "automated" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "1 day after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "Email + Regular Letter" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "15 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "Call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "John Mac Gregor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "35 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "Email + Letter + Call" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "60 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Formal notice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Bailiff" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:34 +msgid "Install Reminder Module" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:36 +msgid "" +"You must start by activating the feature, using the menu " +":menuselection:`Configuration --> Settings` of the Accounting application. " +"From the settings screen, activate the feature **Enable payment follow-up " +"management**." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:44 +msgid "Define Payment Follow-ups Levels" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:46 +msgid "" +"To automate customer follow ups, you must configure your follow–up levels " +"using the menu :menuselection:`Accounting --> Configuration --> Payment " +"Follow-ups`. You should define one and only one follow-up plan per company." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:50 +msgid "" +"The levels of follow-up are relative to the due date; when no payment term " +"is specified, the invoice date will be considered as the due date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:53 +msgid "" +"For each level, you should define the number of days and create a note which" +" will automatically be added into the reminder letter." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:59 +msgid "Odoo defines several actions for every reminder:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:61 +msgid "" +"**Manual Action:** assign a responsible that will have to call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:62 +msgid "**Send an Email:** send an email to customer using the provided text" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:63 +msgid "" +"**Send a Letter:** send a letter by regular mail, using the provided note" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:69 +msgid "" +"As you need to provide a number of days relative to the due date, you can " +"use a negative number. As an example, if an invoice is issued the January " +"1st but the due date is January 20, if you set a reminder 3 days before the " +"due date, the customer may receive an email in January 17." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:76 +msgid "Doing your weekly follow-ups" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:78 +msgid "" +"Once everything is setup, Odoo will prepare follow-up letters and emails " +"automatically for you. All you have to do is to the menu " +":menuselection:`Sales --> Customers Statement` in the accounting " +"application." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:85 +msgid "" +"Odoo will automatically propose you actions based on the follow-up plan you " +"defined, invoices to pay and payment received." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:88 +msgid "" +"You can use this menu every day, once a week or once a month. You do not " +"risk to send two times the same reminder to your customer. Odoo only " +"proposes you the action you have to do. If you do it every day, you will " +"have a few calls to do per day. If you do it once a month, you will have " +"much more work once you do it." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:94 +msgid "" +"It's up to you to organize the way you want to work. But it's a good " +"practice to reconcile your bank statements before launching the follow-ups. " +"That way, all paid invoices will be reconciled and you will not send a " +"follow-up letter to a customer that already paid his invoice." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:99 +msgid "From a customer follow-up proposition, you can:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:101 +msgid "Get the customer information to contact him" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:103 +msgid "Drill down to the customer information form by clicking on its name" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:105 +msgid "Change the text (or the email or letter) and adapt to the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:107 +msgid "" +"Change the colored dot to mark the customer as being a good, normal or bad " +"debtor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:110 +msgid "Log a note is you called the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:112 +msgid "Exclude some invoices from the statement table (litigation)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:114 +msgid "Send an email with the statement" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:116 +msgid "" +"Print a letter, or send a regular mail (if you installed the Docsaway " +"integration)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:119 +msgid "" +"Plan the next reminder (but it's better to keep in automatic mode so that " +"Odoo will stick to the follow-up plan of the company)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:122 +msgid "Drill down to an invoice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:124 +msgid "" +"Change the expected payment date of an invoice (thus, impacting the next " +"time Odoo will propose you to send a reminder)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:128 +msgid "" +"You can force a customer statement, even if Odoo do not proposes you to do " +"it, because it's not the right date yet. To do this, you should go to the " +"Aged Receivable report (in the report menu of the Accounting application). " +"From this report, you can click on a customer to get to his customer " +"statement." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:135 +msgid "How to exclude an invoice from auto follow up?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:137 +msgid "To see all **overdue invoices** or **on need of action**," +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:139 +msgid "Go to :menuselection:`Accounting --> Sales --> Customers Statement`" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:145 +msgid "Exclude a specific invoice for a specific date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:147 +msgid "" +"Odoo can exclude an invoice from follow-ups actions for specific date by " +"clicking on **Log a Note**, then choose one of the ready options (*one " +"week*, *two weeks*, *one month*, *two months*), So Odoo will calculate the " +"required date according to the current date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:155 +msgid "" +"Another way to achieve it is the following: click on the required invoice, " +"then choose **Change expected payment date/note**, then enter a new payment " +"date and note." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:162 +msgid "Exclude a specific invoice forever" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:164 +msgid "" +"Odoo can exclude an invoice for a specific customer by clicking on the " +"checkbox **Excluded**" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:168 +msgid "If you click on **History**, you can see all follow ups actions." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/applications.po b/locale/ru/LC_MESSAGES/applications.po new file mode 100644 index 000000000..67f8d7004 --- /dev/null +++ b/locale/ru/LC_MESSAGES/applications.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../applications.rst:3 +msgid "Applications" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/crm.po b/locale/ru/LC_MESSAGES/crm.po new file mode 100644 index 000000000..4500495b6 --- /dev/null +++ b/locale/ru/LC_MESSAGES/crm.po @@ -0,0 +1,2487 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../crm.rst:5 +msgid "CRM" +msgstr "" + +#: ../../crm/calendar.rst:3 +msgid "Calendar" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:3 +msgid "How to synchronize your calendar with Google Calendar" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:5 +msgid "" +"Connect on your google account and go to " +"`https://console.developers.google.com/ " +"`_." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:7 +msgid "" +"Click on **Create a project...** and enter a project name and change your id" +" if you want. Don't forget to accept the Terms of Services" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:13 +msgid "" +"In the menu on left side, select the sub menu APIs (from menu APIs and auth)" +" and click on 'Calendar API'. Activate the Calendar API by clicking on the " +"blue button 'Enable API'. When it's done, the Calendar API overview will be " +"available" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:26 +msgid "" +"In the menu on left side, select the sub menu 'Credentials' (from menu APIs " +"and auth) and click on button 'Create new Client ID'" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:32 +msgid "" +"Check that the Application type is set on 'Web Application', then click on " +"'Configure consent screen'. Specify an email address and a product name, " +"then save." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:41 +msgid "" +"You should now configure the allowed pages on which you will be redirected. " +"To do it, you need to complete the field \"Authorized redirect URI\" and set" +" as value (your own domain followed by '/google_account/authentication'): " +"==> http://mydomain.odoo.com/google_account/authentication You can now click" +" on 'Create Client ID'" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:48 +msgid "" +"Once done, you will have the both informations (Client ID and Client Secret)" +" that you need to insert in the 2 fields below!" +msgstr "" + +#: ../../crm/leads.rst:3 +msgid "Leads" +msgstr "" + +#: ../../crm/leads/generate.rst:3 +msgid "Generate leads" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:3 +msgid "How to generate leads from incoming emails?" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:5 +msgid "" +"There are several ways for your company to :doc:`generate leads with Odoo " +"CRM `. One of them is using your company's generic email address as " +"a trigger to create a new lead in the system. In Odoo, each one of your " +"sales teams is linked to its own email address from which prospects can " +"reach them. For example, if the personal email address of your Direct team " +"is **direct@mycompany.example.com**, every email sent will automatically " +"create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:14 +#: ../../crm/leads/generate/website.rst:73 +#: ../../crm/leads/manage/automatic_assignation.rst:30 +#: ../../crm/leads/manage/lead_scoring.rst:19 +#: ../../crm/overview/started/setup.rst:10 ../../crm/reporting/review.rst:23 +#: ../../crm/salesteam/manage/reward.rst:12 +msgid "Configuration" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:16 +msgid "" +"The first thing you need to do is to configure your **outgoing email " +"servers** and **incoming email gateway** from the :menuselection:`Settings " +"module --> General Settings`." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:19 +msgid "" +"Then set up your alias domain from the field shown here below and click on " +"**Apply**." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:26 +msgid "Set up team alias" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:28 +msgid "" +"Go on the Sales module and click on **Dashboard**. You will see that the " +"activation of your domain alias has generated a default email alias for your" +" existing sales teams." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:35 +msgid "" +"You can easily personalize your sales teams aliases. Click on the More " +"button from the sales team of your choice, then on **Settings** to access " +"the sales team form. Into the **Email Alias** field, enter your email alias " +"and click on **Save**. Make sure to allow receiving emails from everyone." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:41 +msgid "" +"From there, each email sent to this email address will generate a new lead " +"into the related sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:48 +msgid "Set up catch-all email domain" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:50 +msgid "" +"Additionally to your sales team aliases, you can also create a generic email" +" alias (e.g. *contact@* or *info@* ) that will also generate a new contact " +"in Odoo CRM. Still from the Sales module, go to " +":menuselection:`Configuration --> Settings` and set up your catch-all email " +"domain." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:57 +msgid "" +"You can choose whether the contacts generated from your catch-all email " +"become leads or opportunities using the radio buttons that you see on the " +"screenshot here below. Note that, by default, the lead stage is not " +"activated in Odoo CRM." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:67 +#: ../../crm/leads/generate/import.rst:89 +#: ../../crm/leads/generate/website.rst:194 +msgid ":doc:`manual`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:68 +#: ../../crm/leads/generate/manual.rst:69 +#: ../../crm/leads/generate/website.rst:195 +msgid ":doc:`import`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:69 +#: ../../crm/leads/generate/import.rst:91 +#: ../../crm/leads/generate/manual.rst:73 +msgid ":doc:`website`" +msgstr "" + +#: ../../crm/leads/generate/import.rst:3 +msgid "How to import contacts to the CRM?" +msgstr "" + +#: ../../crm/leads/generate/import.rst:5 +msgid "" +"In Odoo CRM, you can import a database of potential customers, for instance " +"for a cold emailing or cold calling campaign, through a CSV file. You may be" +" wondering if the best option is to import your contacts as leads or " +"opportunities. It depends on your business specificities and workflow:" +msgstr "" + +#: ../../crm/leads/generate/import.rst:11 +msgid "" +"Some companies may decide to not use leads, but instead to keep all " +"information directly in an opportunity. For some companies, leads are merely" +" an extra step in the sales process. You could call this extended (start " +"from lead) versus simplified (start from opportunity) customer relationship " +"management." +msgstr "" + +#: ../../crm/leads/generate/import.rst:17 +msgid "" +"Odoo perfectly allows for either one of these approaches to be chosen. If " +"your company handles its sales from a pre qualification step, feel free to " +"activate first the lead stage as described below in order to import your " +"database as leads" +msgstr "" + +#: ../../crm/leads/generate/import.rst:23 +#: ../../crm/leads/generate/manual.rst:9 +#: ../../crm/leads/generate/website.rst:38 +#: ../../crm/salesteam/setup/organize_pipeline.rst:62 +msgid "Activate the lead stage" +msgstr "" + +#: ../../crm/leads/generate/import.rst:25 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. If you want to " +"import your contacts as leads rather than opportunities, go to " +":menuselection:`Configuration --> Settings`, select the option **use leads " +"if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/import.rst:33 +msgid "" +"This activation will create a new submenu :menuselection:`Sales --> Leads` " +"from which you will be able to import your contacts from the **Import** " +"button (if you want to create a lead manually, :doc:`click here `)" +msgstr "" + +#: ../../crm/leads/generate/import.rst:41 +msgid "Import your CSV file" +msgstr "" + +#: ../../crm/leads/generate/import.rst:43 +msgid "" +"On the new submenu :menuselection:`Sales --> Leads`, click on **Import** and" +" select your Excel file to import from the **Choose File** button. Make sure" +" its extension is **.csv** and don't forget to set up the correct File " +"format options (**Encoding** and **Separator**) to match your local settings" +" and display your columns properly." +msgstr "" + +#: ../../crm/leads/generate/import.rst:50 +msgid "" +"If your prospects database is provided in another format than CSV, you can " +"easily convert it to the CSV format using Microsoft Excel, OpenOffice / " +"LibreOffice Calc, Google Docs, etc." +msgstr "" + +#: ../../crm/leads/generate/import.rst:58 +msgid "Select rows to import" +msgstr "" + +#: ../../crm/leads/generate/import.rst:60 +msgid "" +"Odoo will automatically map the column headers from your CSV file to the " +"corresponding fields if you tick *The first row of the file contains the " +"label of the column* option. This makes imports easier especially when the " +"file has many columns. Of course, you can remap the column headers to " +"describe the property you are importing data into (First Name, Last Name, " +"Email, etc.)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:72 +msgid "" +"If you want to import your contacts as opportunities rather than leads, make" +" sure to add the *Type* column to your csv. This column is used to indicate " +"whether your import will be flagged as a Lead (type = Lead) or as an " +"opportunity (type = Opportunity)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:77 +msgid "" +"Click the **Validate** button if you want to let Odoo verify that everything" +" seems okay before importing. Otherwise, you can directly click the Import " +"button: the same validations will be done." +msgstr "" + +#: ../../crm/leads/generate/import.rst:83 +msgid "" +"For additional technical information on how to import contacts into Odoo " +"CRM, read the **Frequently Asked Questions** section located below the " +"Import tool on the same window." +msgstr "" + +#: ../../crm/leads/generate/import.rst:90 +#: ../../crm/leads/generate/manual.rst:71 +#: ../../crm/leads/generate/website.rst:196 +msgid ":doc:`emails`" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:3 +msgid "How to create a contact into Odoo CRM?" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:5 +msgid "" +"Odoo CRM allows you to manually add contacts into your pipeline. It can be " +"either a lead or an opportunity." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:11 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. To activate it, go " +"to :menuselection:`Sales --> Configuration --> Settings`, select the option " +"\"\"use leads if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:18 +msgid "" +"This activation will create a new submenu **Leads** under **Sales** that " +"gives you access to a list of all your leads from which you will be able to " +"create a new contact." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:26 +msgid "Create a new lead" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:28 +msgid "" +"Go to :menuselection:`Sales --> Leads` and click the **Create** button." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:33 +msgid "" +"From the contact form, provide all the details in your possession (contact " +"name, email, phone, address, etc.) as well as some additional information in" +" the **Internal notes** field. You can also link the lead to an existing " +"company by editing the**Customer** field. Click on save and the contact will" +" be visible as a lead in your pipeline ." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:41 +msgid "" +"your lead can be directly handed over to specific sales team and salesperson" +" by clicking on **Convert to Opportunity** on the upper left corner of the " +"screen." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:45 +msgid "Create a new opportunity" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:47 +msgid "" +"You can also directly add a contact into a specific sales team without " +"having to convert the lead first. On the Sales module, go to your dashboard " +"and click on the **Pipeline** button of the desired sales team. If you don't" +" have any sales team yet, :doc:`you need to create one first " +"<../../salesteam/setup/create_team>`. Then, click on **Create** and fill in " +"the contact details as shown here above. By default, the newly created " +"opportunity will appear on the first stage of your sales pipeline." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:55 +msgid "" +"Another way to create an opportunity is by adding it directly on a specific " +"stage. For example, if you have have spoken to Mr. Smith at a meeting and " +"you want to send him a quotation right away, you can add his contact details" +" on the fly directly into the **Proposition** stage. From the Kanban view of" +" your sales team, just click on the **+** icon at the right of your stage to" +" create the contact. The new opportunity will then pop up into the " +"corresponding stage and you can then fill in the contact details by clicking" +" on it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:3 +msgid "How to generate leads from my website?" +msgstr "" + +#: ../../crm/leads/generate/website.rst:5 +msgid "" +"Your website should be your company's first lead generation tool. With your " +"website being the central hub of your online marketing campaigns, you will " +"naturally drive qualified traffic to feed your pipeline. When a prospect " +"lands on your website, your objective is to capture his information in order" +" to be able to stay in touch with him and to push him further down the sales" +" funnel." +msgstr "" + +#: ../../crm/leads/generate/website.rst:12 +msgid "This is how a typical online lead generation process work :" +msgstr "" + +#: ../../crm/leads/generate/website.rst:14 +msgid "" +"Your website visitor clicks on a call-to action (CTA) from one of your " +"marketing materials (e.g. an email newsletter, a social media message or a " +"blog post)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:18 +msgid "" +"The CTA leads your visitor to a landing page including a form used to " +"collect his personal information (e.g. his name, his email address, his " +"phone number)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:22 +msgid "" +"The visitor submits the form and automatically generates a lead into Odoo " +"CRM" +msgstr "" + +#: ../../crm/leads/generate/website.rst:27 +msgid "" +"Your calls-to-action, landing pages and forms are the key pieces of the lead" +" generation process. With Odoo Website, you can easily create and optimize " +"those critical elements without having to code or to use third-party " +"applications. Learn more `here `__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:32 +msgid "" +"In Odoo, the Website and CRM modules are fully integrated, meaning that you " +"can easily generate leads from various ways through your website. However, " +"even if you are hosting your website on another CMS, it is still possible to" +" fill Odoo CRM with leads generated from your website." +msgstr "" + +#: ../../crm/leads/generate/website.rst:40 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. Therefore, new " +"leads automatically become opportunities. You can easily activate the option" +" of adding the lead step. If you want to import your contacts as leads " +"rather than opportunities, from the Sales module go to " +":menuselection:`Configuration --> Settings`, select the option **use leads " +"if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:50 +msgid "" +"Note that even without activating this step, the information that follows is" +" still applicable - the lead generated will land in the opportunities " +"dashboard." +msgstr "" + +#: ../../crm/leads/generate/website.rst:55 +msgid "From an Odoo Website" +msgstr "" + +#: ../../crm/leads/generate/website.rst:57 +msgid "" +"Let's assume that you want to get as much information as possible about your" +" website visitors. But how could you make sure that every person who wants " +"to know more about your company's products and services is actually leaving " +"his information somewhere? Thanks to Odoo's integration between its CRM and " +"Website modules, you can easily automate your lead acquisition process " +"thanks to the **contact form** and the **form builder** modules" +msgstr "" + +#: ../../crm/leads/generate/website.rst:67 +msgid "" +"another great way to generate leads from your Odoo Website is by collecting " +"your visitors email addresses thanks to the Newsletter or Newsletter Popup " +"CTAs. These snippets will create new contacts in your Email Marketing's " +"mailing list. Learn more `here `__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:75 +msgid "" +"Start by installing the Website builder module. From the main dashboard, " +"click on **Apps**, enter \"**Website**\" in the search bar and click on " +"**Install**. You will be automatically redirected to the web interface." +msgstr "" + +#: ../../crm/leads/generate/website.rst:84 +msgid "" +"A tutorial popup will appear on your screen if this is the first time you " +"use Odoo Website. It will help you get started with the tool and you'll be " +"able to use it in minutes. Therefore, we strongly recommend you to use it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:89 +msgid "Create a lead by using the Contact Form module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:91 +msgid "" +"You can effortlessly generate leads via a contact form on your **Contact " +"us** page. To do so, you first need to install the Contact Form module. It " +"will add a contact form in your **Contact us** page and automatically " +"generate a lead from forms submissions." +msgstr "" + +#: ../../crm/leads/generate/website.rst:96 +msgid "" +"To install it, go back to the backend using the square icon on the upper-" +"left corner of your screen. Then, click on **Apps**, enter \"**Contact " +"Form**\" in the search bar (don't forget to remove the **Apps** tag " +"otherwise you will not see the module appearing) and click on **Install**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:104 +msgid "" +"Once the module is installed, the below contact form will be integrated to " +"your \"Contact us\" page. This form is linked to Odoo CRM, meaning that all " +"data entered through the form will be captured by the CRM and will create a " +"new lead." +msgstr "" + +#: ../../crm/leads/generate/website.rst:112 +msgid "" +"Every lead created through the contact form is accessible in the Sales " +"module, by clicking on :menuselection:`Sales --> Leads`. The name of the " +"lead corresponds to the \"Subject\" field on the contact form and all the " +"other information is stored in the corresponding fields within the CRM. As a" +" salesperson, you can add additional information, convert the lead into an " +"opportunity or even directly mark it as Won or Lost." +msgstr "" + +#: ../../crm/leads/generate/website.rst:123 +msgid "Create a lead using the Form builder module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:125 +msgid "" +"You can create fully-editable custom forms on any landing page on your " +"website with the Form Builder snippet. As for the Contact Form module, the " +"Form Builder will automatically generate a lead after the visitor has " +"completed the form and clicked on the button **Send**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:130 +msgid "" +"From the backend, go to Settings and install the \"**Website Form " +"Builder**\" module (don't forget to remove the **Apps** tag otherwise you " +"will not see the modules appearing). Then, back on the website, go to your " +"desired landing page and click on Edit to access the available snippets. The" +" Form Builder snippet lays under the **Feature** section." +msgstr "" + +#: ../../crm/leads/generate/website.rst:140 +msgid "" +"As soon as you have dropped the snippet where you want the form to appear on" +" your page, a **Form Parameters** window will pop up. From the **Action** " +"drop-down list, select **Create a lead** to automatically create a lead in " +"Odoo CRM. On the **Thank You** field, select the URL of the page you want to" +" redirect your visitor after the form being submitted (if you don't add any " +"URL, the message \"The form has been sent successfully\" will confirm the " +"submission)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:151 +msgid "" +"You can then start creating your custom form. To add new fields, click on " +"**Select container block** and then on the blue **Customize** button. 3 " +"options will appear:" +msgstr "" + +#: ../../crm/leads/generate/website.rst:158 +msgid "" +"**Change Form Parameters**: allows you to go back to the Form Parameters and" +" change the configuration" +msgstr "" + +#: ../../crm/leads/generate/website.rst:161 +msgid "" +"**Add a model field**: allows you to add a field already existing in Odoo " +"CRM from a drop-down list. For example, if you select the Field *Country*, " +"the value entered by the lead will appear under the *Country* field in the " +"CRM - even if you change the name of the field on the form." +msgstr "" + +#: ../../crm/leads/generate/website.rst:167 +msgid "" +"**Add a custom field**: allows you to add extra fields that don't exist by " +"default in Odoo CRM. The values entered will be added under \"Notes\" within" +" the CRM. You can create any field type : checkbox, radio button, text, " +"decimal number, etc." +msgstr "" + +#: ../../crm/leads/generate/website.rst:172 +msgid "Any submitted form will create a lead in the backend." +msgstr "" + +#: ../../crm/leads/generate/website.rst:175 +msgid "From another CMS" +msgstr "" + +#: ../../crm/leads/generate/website.rst:177 +msgid "" +"If you use Odoo CRM but not Odoo Website, you can still automate your online" +" lead generation process using email gateways by editing the \"Submit\" " +"button of any form and replacing the hyperlink by a mailto corresponding to " +"your email alias (learn how to create your sales alias :doc:`here " +"`)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:183 +msgid "" +"For example if the alias of your company is **salesEMEA@mycompany.com**, add" +" ``mailto:salesEMEA@mycompany.com`` into the regular hyperlink code (CTRL+K)" +" to generate a lead into the related sales team in Odoo CRM." +msgstr "" + +#: ../../crm/leads/manage.rst:3 +msgid "Manage leads" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:3 +msgid "Automate lead assignation to specific sales teams or salespeople" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:5 +msgid "" +"Depending on your business workflow and needs, you may need to dispatch your" +" incoming leads to different sales team or even to specific salespeople. " +"Here are a few example:" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:9 +msgid "" +"Your company has several offices based on different geographical regions. " +"You will want to assign leads based on the region;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:12 +msgid "" +"One of your sales teams is dedicated to treat opportunities from large " +"companies while another one is specialized for SMEs. You will want to assign" +" leads based on the company size;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:16 +msgid "" +"One of your sales representatives is the only one to speak foreign languages" +" while the rest of the team speaks English only. Therefore you will want to " +"assign to that person all the leads from non-native English-speaking " +"countries." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:21 +msgid "" +"As you can imagine, manually assigning new leads to specific individuals can" +" be tedious and time consuming - especially if your company generates a high" +" volume of leads every day. Fortunately, Odoo CRM allows you to automate the" +" process of lead assignation based on specific criteria such as location, " +"interests, company size, etc. With specific workflows and precise rules, you" +" will be able to distribute all your opportunities automatically to the " +"right sales teams and/or salesman." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:32 +msgid "" +"If you have just started with Odoo CRM and haven't set up your sales team " +"nor registered your salespeople, :doc:`read this documentation first " +"<../../overview/started/setup>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:36 +msgid "" +"You have to install the module **Lead Scoring**. Go to :menuselection:`Apps`" +" and install it if it's not the case already." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:40 +msgid "Define rules for a sales team" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:42 +msgid "" +"From the sales module, go to your dashboard and click on the **More** button" +" of the desired sales team, then on **Settings**. If you don't have any " +"sales team yet, :doc:`you need to create one first " +"<../../salesteam/setup/create_team>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:50 +msgid "" +"On your sales team menu, use in the **Domain** field a specific domain rule " +"(for technical details on the domain refer on the `Building a Module " +"tutorial " +"`__ or " +"`Syntax reference guide " +"`__) which will allow only the leads matching the team domain." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:56 +msgid "" +"For example, if you want your *Direct Sales* team to only receive leads " +"coming from United States and Canada, your domain will be as following :" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:59 +msgid "``[[country_id, 'in', ['United States', 'Canada']]]``" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:66 +msgid "" +"you can also base your automatic assignment on the score attributed to your " +"leads. For example, we can imagine that you want all the leads with a score " +"under 100 to be assigned to a sales team trained for lighter projects and " +"the leads over 100 to a more experienced sales team. Read more on :doc:`how " +"to score leads here `." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:72 +msgid "Define rules for a salesperson" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:74 +msgid "" +"You can go one step further in your assignment rules and decide to assign " +"leads within a sales team to a specific salesperson. For example, if I want " +"Toni Buchanan from the *Direct Sales* team to receive only leads coming from" +" Canada, I can create a rule that will automatically assign him leads from " +"that country." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:80 +msgid "" +"Still from the sales team menu (see here above), click on the salesperson of" +" your choice under the assignment submenu. Then, enter your rule in the " +"*Domain* field." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:89 +msgid "" +"In Odoo, a lead is always assigned to a sales team before to be assigned to " +"a salesperson. Therefore, you need to make sure that the assignment rule of " +"your salesperson is a child of the assignment rule of the sales team." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:95 +#: ../../crm/salesteam/manage/create_salesperson.rst:67 +msgid ":doc:`../../overview/started/setup`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:3 +msgid "How to do efficient Lead Scoring?" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:5 +msgid "" +"Odoo's Lead Scoring module allows you to give a score to your leads based on" +" specific criteria - the higher the value, the more likely the prospect is " +"\"ready for sales\". Therefore, the best leads are automatically assigned to" +" your salespeople so their pipe are not polluted with poor-quality " +"opportunities." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:12 +msgid "" +"Lead scoring is a critical component of an effective lead management " +"strategy. By helping your sales representative determine which leads to " +"engage with in order of priority, you will increase their overall conversion" +" rate and your sales team's efficiency." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:22 +msgid "Install the Lead Scoring module" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:24 +msgid "Start by installing the **Lead Scoring** module." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:26 +msgid "" +"Once the module is installed, you should see a new menu " +":menuselection:`Sales --> Leads Management --> Scoring Rules`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:33 +msgid "Create scoring rules" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:35 +msgid "" +"Leads scoring allows you to assign a positive or negative score to your " +"prospects based on any demographic or behavioral criteria that you have set " +"(country or origin, pages visited, type of industry, role, etc.). To do so " +"you'll first need to create rules that will assign a score to a given " +"criteria." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:43 +msgid "" +"In order to assign the right score to your various rules, you can use these " +"two methods:" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:45 +msgid "" +"Establish a list of assets that your ideal customer might possess to " +"interest your company. For example, if you run a local business in " +"California, a prospect coming from San Francisco should have a higher score " +"than a prospect coming from New York." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:49 +msgid "" +"Dig into your data to uncover characteristics shared by your closed " +"opportunities and most important clients." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:52 +msgid "" +"Please note that this is not an exact science, so you'll need time and " +"feedback from your sales teams to adapt and fine tune your rules until " +"getting the desired result." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:56 +msgid "" +"In the **Scoring Rules** menu, click on **Create** to write your first rule." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:61 +msgid "" +"First name your rule, then enter a value and a domain (refer on the " +"`official python documentation `__ for " +"more information). For example, if you want to assign 8 points to all the " +"leads coming from **Belgium**, you'll need to give ``8`` as a **value** and " +"``[['country\\_id',=,'Belgium']]`` as a domain." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:68 +msgid "Here are some criteria you can use to build a scoring rule :" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:70 +msgid "country of origin : ``'country_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:72 +msgid "stage in the sales cycle : ``'stage_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:74 +msgid "" +"email address (e.g. if you want to score the professional email addresses) :" +" ``'email_from'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:76 +msgid "page visited : ``'score_pageview_ids.url'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:78 +msgid "name of a marketing campaign : ``'campaign_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:80 +msgid "" +"After having activated your rules, Odoo will give a value to all your new " +"incoming leads. This value can be found directly on your lead's form view." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:88 +msgid "Assign high scoring leads to your sales teams" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:90 +msgid "" +"The next step is now to automatically convert your best leads into " +"opportunities. In order to do so, you need to decide what is the minimum " +"score a lead should have to be handed over to a given sales team. Go to your" +" **sales dashboard** and click on the **More** button of your desired sales " +"team, then on **Settings**. Enter your value under the **Minimum score** " +"field." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:100 +msgid "" +"From the example above, the **Direct Sales** team will only receive " +"opportunities with a minimum score of ``50``. The prospects with a lower " +"score can either stay in the lead stage or be assigned to another sales team" +" which has set up a different minimum score." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:106 +msgid "" +"Organize a meeting between your **Marketing** and **Sales** teams in order " +"to align your objectives and agree on what minimum score makes a sales-ready" +" lead." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:110 +msgid ":doc:`automatic_assignation`" +msgstr "" + +#: ../../crm/leads/voip.rst:3 +msgid "Odoo VOIP" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:3 +msgid "Installation and Setup" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:9 +msgid "Dependencies" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:13 +msgid "wget" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:14 +msgid "gcc" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:15 +msgid "g++" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:37 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:43 +msgid "**run:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:49 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:57 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:63 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:69 +msgid "**The result should be:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:86 +msgid "Asterisk" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:88 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there `_." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:90 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:96 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:102 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:108 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:114 +msgid "" +"In the menuselect, go to the resources option and ensure that res_srtp is " +"enabled. If there are 3 x’s next to res_srtp, there is a problem with the " +"srtp library and you must reinstall it. Save the configuration (press x). " +"You should also see stars in front of the res_pjsip lines." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:116 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:122 +msgid "" +"If you need the sample configs you can run 'make samples' to install the " +"sample configs. If you need to install the Asterisk startup script you can " +"run 'make config'." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:125 +msgid "DTLS Certificates" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:127 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:133 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:139 +msgid "" +"Create the DTLS certificates (replace pbx.mycompany.com with your ip address" +" or dns name, replace My Super Company with your company name):" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:146 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:148 +msgid "" +"For WebRTC, a lot of the settings that are needed MUST be in the peer " +"settings. The global settings do not flow down into the peer settings very " +"well. By default, Asterisk config files are located in /etc/asterisk/. Start" +" by editing http.conf and make sure that the following lines are " +"uncommented:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:158 +msgid "" +"Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and " +"icesupport to be enabled. In most cases, directmedia should be disabled. " +"Also under the WebRTC client, the transport needs to be listed as ‘ws’ to " +"allow websocket connections. All of these config lines should be under the " +"peer itself; setting these config lines globally might not work:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:186 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:193 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:202 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:204 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:206 +msgid "" +"The SIP Login/Browser's Extension is the number you configured previously in" +" the sip.conf file. In our example, 1060. The SIP Password is the secret you" +" chose in the sip.conf file. The extension of your office's phone is not a " +"required field but it is used if you want to transfer your call from Odoo to" +" an external phone also configured in the sip.conf file." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:212 +msgid "" +"The configuration should also be done in the sale settings under the title " +"\"PBX Configuration\". You need to put the IP you define in the http.conf " +"file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part " +"\"127.0.0.1\" needs to be the same as the IP defined previously and the " +"\"8088\" is the port you defined in the http.conf file." +msgstr "" + +#: ../../crm/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../crm/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo CRM" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:13 +msgid "" +"Hi, my name is Nicholas, I'm a business manager in the textile industry. I " +"sell accessories to retailers. Do you know the difference between a good " +"salesperson and an excellent salesperson? The key is to be productive and " +"organized to do the job. That's where Odoo comes in. Thanks to a well " +"structured organization you'll change a good team into an exceptional team." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:21 +msgid "" +"With Odoo CRM, the job is much easier for me and my entire team. When I log " +"in into Odoo CRM, I have a direct overview of my ongoing performance. But " +"also the activity of the next 7 days and the performance of the last month. " +"I see that I overachieved last month when compared to my invoicing target of" +" $200,000. I have a structured approach of my performance." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:28 +msgid "" +"If I want to have a deeper look into the details, I click on next actions " +"and I can see that today I have planned a call with Think Big Systems. Once " +"I have done my daily review, I usually go to my pipeline. The process is the" +" same for everyone in the team. Our job is to find resellers and before " +"closing any deal we have to go through different stages. We usually have a " +"first contact to qualify the opportunity, then move into offer & negotiation" +" stage, and closing by a 'won'..Well, that's if all goes well." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:38 +msgid "" +"The user interface is really smooth, I can drag and drop any business " +"opportunity from one stage to another in just a few clicks." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:42 +msgid "" +"Now I'd like to go further with an interesting contact: a department store. " +"I highlighted their file by changing the color. For each contact, I have a " +"form view where I can access to all necessary information about the contact." +" I see here my opportunity Macy's has an estimated revenue of $50,000 and a " +"success rate of 10%. I need to discuss about this partnership, so I will " +"schedule a meeting straight from the contact form: Macy's partnership " +"meeting. It's super easy to create a new meeting with any contact. I can as " +"well send an email straight from the opportunity form and the answer from " +"the prospect will simply pop up in the system too. Now, let's assume that " +"the meeting took place, therefore I can mark it as done. And the system " +"automatically suggests a next activity. Actually, we configured Odoo with a " +"set of typical activities we follow for every opportunity, and it's great to" +" have a thorough followup. The next activity will be a follow-up email. " +"Browsing from one screen to the other is really simple and adapting to the " +"view too! I can see my opportunitities as a to-do list of next activities " +"for example." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:62 +msgid "" +"With Odoo CRM I have a sales management tool that is really efficient and me" +" and my team can be well organized. I have a clear overview of my sales " +"pipeline, meetings, revenues, and more." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:67 +msgid "" +"I go back to my pipeline. Macy's got qualified successfully, which mean I " +"can move their file to the next step and I will dapt the expected revenue as" +" discussed. Once I have performed the qualification process, I will create a" +" new quotation based on the feedback I received from my contact. For my " +"existing customers, I can as well quickly discover the activity around them " +"for any Odoo module I use, and continue to discuss about them. It's that " +"simple." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:76 +msgid "" +"We have seen how I can manage my daily job as business manager or " +"salesperson. At the end of the journey I would like to have a concrete view " +"of my customer relationships and expected revenues. If I go into the reports" +" in Odoo CRM, I have the possibility to know exactly what's the evolution of" +" the leads over the past months, or have a look at the potential revenues " +"and the performance of the different teams in terms of conversions from " +"leads to opportunities for instance. So with Odoo I can have a clear " +"reporting of every activity based on predefined metrics or favorites. I can " +"search for other filters too and adapt the view. If I want to go in the " +"details, I choose the list view and can click on any item" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:90 +msgid "" +"Odoo CRM is not only a powerful tool to achieve our sales goals with " +"structured activities, performance dashboard, next acitivities and more, but" +" also allows me to:" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:94 +msgid "" +"Use leads to get in the system unqualified but targeted contacts I may have " +"gathered in a conference or through a contact form on my website. Those " +"leads can then be converted into opportunities." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:99 +msgid "" +"Manage phone calls from Odoo CRM by using the VoIP app. Call customers, " +"manage a call queue, log calls, schedule calls and next actions to perform." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:103 +msgid "" +"Integrate with Odoo Sales to create beautiful online or PDF quotations and " +"turn them into sales orders." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:106 +msgid "" +"Use email marketing for marketing campaigns to my customers and prospects." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:109 +msgid "" +"Manage my business seamlessly, even on the go. Indeed, Odoo offers a mobile " +"app that lets every business organize key sales activities from leads to " +"quotes." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:113 +msgid "" +"Odoo CRM is a powerful, yet easy-to-use app. I firstly used the sales " +"planner to clearly state my objectives and set up our CRM. It will help you " +"getting started quickly too." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:3 +msgid "Odoo CRM Terminologies" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:10 +msgid "**CRM (Customer relationship management)**:" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:6 +msgid "" +"System for managing a company's interactions with current and future " +"customers. It often involves using technology to organize, automate, and " +"synchronize sales, marketing, customer service, and technical support." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:14 +msgid "**Sales cycle** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:13 +msgid "" +"Sequence of phases used by a company to convert a prospect into a customer." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:20 +msgid "**Pipeline :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:17 +msgid "" +"Visual representation of your sales process, from the first contact to the " +"final sale. It refers to the process by which you generate, qualify and " +"close leads through your sales cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:24 +msgid "**Sales stage** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:23 +msgid "" +"In Odoo CRM, a stage defines where an opportunity is in your sales cycle and" +" its probability to close a sale." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:29 +msgid "**Lead :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:27 +msgid "" +"Someone who becomes aware of your company or someone who you decide to " +"pursue for a sale, even if they don't know about your company yet." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:34 +msgid "**Opportunity :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:32 +msgid "" +"A lead that has shown an interest in knowing more about your " +"products/services and therefore has been handed over to a sales " +"representative" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:39 +msgid "**Customer :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:37 +msgid "" +"In Odoo CRM, a customer refers to any contact within your database, whether " +"it is a lead, an opportunity, a client or a company." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:45 +msgid "**Key Performance Indicator (KPI)** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:42 +msgid "" +"A KPI is a measurable value that demonstrates how effectively a company is " +"achieving key business objectives. Organizations use KPIs to evaluate their " +"success at reaching targets." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:51 +msgid "**Lead scoring** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:48 +msgid "" +"System assigning a positive or negative score to prospects according to " +"their web activity and personal informations in order to determine whether " +"they are \"ready for sales\" or not." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:62 +msgid "**Kanban view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:54 +msgid "" +"In Odoo, the Kanban view is a workflow visualisation tool halfway between a " +"`list view `__ and a non-editable `form view " +"`__ and displaying records as \"cards\". Records may be grouped " +"in columns for use in workflow visualisation or manipulation (e.g. tasks or " +"work-progress management), or ungrouped (used simply to visualize records)." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:66 +msgid "**List view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:65 +msgid "" +"View allowing you to see your objects (contacts, companies, tasks, etc.) " +"listed in a table." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:71 +msgid "**Lead generation:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:69 +msgid "" +"Process by which a company collects relevant datas about potential customers" +" in order to enable a relationship and to push them further down the sales " +"cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:76 +msgid "**Campaign:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:74 +msgid "" +"Coordinated set of actions sent via various channels to a target audience " +"and whose goal is to generate leads. In Odoo CRM, you can link a lead to the" +" campaign which he comes from in order to measure its efficiency." +msgstr "" + +#: ../../crm/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:3 +msgid "Generating leads with Odoo CRM" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:6 +msgid "What is lead generation?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:8 +msgid "" +"Lead generation is the process by which a company acquires leads and " +"collects relevant datas about potential customers in order to enable a " +"relationship and to turn them into customers." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:12 +msgid "" +"For example, a website visitor who fills in your contact form to know more " +"about your products and services becomes a lead for your company. Typically," +" a Customer Relationship Management tool such as Odoo CRM is used to " +"centralize, track and manage leads." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:18 +msgid "Why is lead generation important for my business?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:20 +msgid "" +"Generating a constant flow of high-quality leads is one of the most " +"important responsibility of a marketing team. Actually, a well-managed lead " +"generation process is like the fuel that will allow your company to deliver " +"great performances - leads bring meetings, meetings bring sales, sales bring" +" revenue and more work." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:27 +msgid "How to generate leads with Odoo CRM?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:29 +msgid "" +"Leads can be captured through many sources - marketing campaigns, " +"exhibitions and trade shows, external databases, etc. The most common " +"challenge is to successfully gather all the data and to track any lead " +"activity. Storing leads information in a central place such as Odoo CRM will" +" release you of these worries and will help you to better automate your lead" +" generation process, share information with your teams and analyze your " +"sales processes easily." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:37 +msgid "Odoo CRM provides you with several methods to generate leads:" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:39 +msgid ":doc:`../../leads/generate/emails`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:41 +msgid "" +"An inquiry email sent to one of your company's generic email addresses can " +"automatically generate a lead or an opportunity." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:44 +msgid ":doc:`../../leads/generate/manual`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:46 +msgid "" +"You may want to follow up with a prospective customer met briefly at an " +"exhibition who gave you his business card. You can manually create a new " +"lead and enter all the needed information." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:50 +msgid ":doc:`../../leads/generate/website`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:52 +msgid "" +"A website visitor who fills in a form automatically generates a lead or an " +"opportunity in Odoo CRM." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:55 +msgid ":doc:`../../leads/generate/import`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:57 +msgid "" +"You can provide your salespeople lists of prospects - for example for a cold" +" emailing or a cold calling campaign - by importing them from any CSV file." +msgstr "" + +#: ../../crm/overview/started.rst:3 +msgid "Getting started" +msgstr "" + +#: ../../crm/overview/started/setup.rst:3 +msgid "How to setup your teams, sales process and objectives?" +msgstr "" + +#: ../../crm/overview/started/setup.rst:5 +msgid "" +"This quick step-by-step guide will lead you through Odoo CRM and help you " +"handle your sales funnel easily and constantly manage your sales funnel from" +" lead to customer." +msgstr "" + +#: ../../crm/overview/started/setup.rst:12 +msgid "" +"Create your database from `www.odoo.com/start " +"`__, select the CRM icon as first app to install," +" fill in the form and click on *Create now*. You will automatically be " +"directed to the module when the database is ready." +msgstr "" + +#: ../../crm/overview/started/setup.rst:22 +msgid "" +"You will notice that the installation of the CRM module has created the " +"submodules Chat, Calendar and Contacts. They are mandatory so that every " +"feature of the app is running smoothly." +msgstr "" + +#: ../../crm/overview/started/setup.rst:27 +msgid "Introduction to the Sales Planner" +msgstr "" + +#: ../../crm/overview/started/setup.rst:29 +msgid "" +"The Sales Planner is a useful step-by-step guide created to help you " +"implement your sales funnel and define your sales objectives easier. We " +"strongly recommend you to go through every step of the tool the first time " +"you use Odoo CRM and to follow the requirements. Your input are strictly " +"personal and intended as a personal guide and mentor into your work. As it " +"does not interact with the backend, you are free to adapt any detail " +"whenever you feel it is needed." +msgstr "" + +#: ../../crm/overview/started/setup.rst:37 +msgid "" +"You can reach the Sales Planner from anywhere within the CRM module by " +"clicking on the progress bar located on the upper-right side of your screen." +" It will show you how far you are in the use of the Sales Planner." +msgstr "" + +#: ../../crm/overview/started/setup.rst:46 +msgid "Set up your first sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:49 +msgid "Create a new team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:51 +msgid "" +"A Direct Sales team is created by default on your instance. You can either " +"use it or create a new one. Refer to the page " +":doc:`../../salesteam/setup/create_team` for more information." +msgstr "" + +#: ../../crm/overview/started/setup.rst:56 +msgid "Assign salespeople to your sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:58 +msgid "" +"When your sales teams are created, the next step is to link your salespeople" +" to their team so they will be able to work on the opportunities they are " +"supposed to receive. For example, if within your company Tim is selling " +"products and John is selling maintenance contracts, they will be assigned to" +" different teams and will only receive opportunities that make sense to " +"them." +msgstr "" + +#: ../../crm/overview/started/setup.rst:65 +msgid "" +"In Odoo CRM, you can create a new user on the fly and assign it directly to " +"a sales team. From the **Dashboard**, click on the button **More** of your " +"selected sales team, then on **Settings**. Then, under the **Assignation** " +"section, click on **Create** to add a new salesperson to the team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:71 +msgid "" +"From the **Create: salesman** pop up window (see screenshot below), you can " +"assign someone on your team:" +msgstr "" + +#: ../../crm/overview/started/setup.rst:74 +msgid "" +"Either your salesperson already exists in the system and you will just need " +"to click on it from the drop-down list and it will be assigned to the team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:77 +msgid "" +"Or you want to assign a new salesperson that doesn't exist into the system " +"yet - you can do it by creating a new user on the fly from the sales team. " +"Just enter the name of your new salesperson and click on Create (see below) " +"to create a new user into the system and directly assign it to your team. " +"The new user will receive an invite email to set his password and log into " +"the system. Refer to :doc:`../../salesteam/manage/create_salesperson` for " +"more information about that process" +msgstr "" + +#: ../../crm/overview/started/setup.rst:90 +msgid "Set up your pipeline" +msgstr "" + +#: ../../crm/overview/started/setup.rst:92 +msgid "" +"Now that your sales team is created and your salespeople are linked to it, " +"you will need to set up your pipeline -create the process by which your team" +" will generate, qualify and close opportunities through your sales cycle. " +"Refer to the document :doc:`../../salesteam/setup/organize_pipeline` to " +"define the stages of your pipeline." +msgstr "" + +#: ../../crm/overview/started/setup.rst:99 +msgid "Set up incoming email to generate opportunities" +msgstr "" + +#: ../../crm/overview/started/setup.rst:101 +msgid "" +"In Odoo CRM, one way to generate opportunities into your sales team is to " +"create a generic email address as a trigger. For example, if the personal " +"email address of your Direct team is `direct@mycompany.example.com " +"`__\\, every email sent will " +"automatically create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:108 +msgid "Refer to the page :doc:`../../leads/generate/emails` to set it up." +msgstr "" + +#: ../../crm/overview/started/setup.rst:111 +msgid "Automate lead assignation" +msgstr "" + +#: ../../crm/overview/started/setup.rst:113 +msgid "" +"If your company generates a high volume of leads every day, it could be " +"useful to automate the assignation so the system will distribute all your " +"opportunities automatically to the right department." +msgstr "" + +#: ../../crm/overview/started/setup.rst:117 +msgid "" +"Refer to the document :doc:`../../leads/manage/automatic_assignation` for " +"more information." +msgstr "" + +#: ../../crm/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../crm/reporting/analysis.rst:3 +msgid "" +"How to analyze the sales performance of your team and get customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:5 +msgid "" +"As a manager, you need to constantly monitor your team's performance in " +"order to help you take accurate and relevant decisions for the company. " +"Therefore, the **Reporting** section of **Odoo Sales** represents a very " +"important tool that helps you get a better understanding of where your " +"company's strengths, weaknesses and opportunities are, showing you trends " +"and forecasts for key metrics such as the number of opportunities and their " +"expected revenue over time , the close rate by team or the length of sales " +"cycle for a given product or service." +msgstr "" + +#: ../../crm/reporting/analysis.rst:14 +msgid "" +"Beyond these obvious tracking sales funnel metrics, there are some other " +"KPIs that can be very valuable to your company when it comes to judging " +"sales funnel success." +msgstr "" + +#: ../../crm/reporting/analysis.rst:19 +msgid "Review pipelines" +msgstr "" + +#: ../../crm/reporting/analysis.rst:21 +msgid "" +"You will have access to your sales funnel performance from the **Sales** " +"module, by clicking on :menuselection:`Sales --> Reports --> Pipeline " +"analysis`. By default, the report groups all your opportunities by stage " +"(learn more on how to create and customize stage by reading " +":doc:`../salesteam/setup/organize_pipeline`) and expected revenues for the " +"current month. This report is perfect for the **Sales Manager** to " +"periodically review the sales pipeline with the relevant sales teams. Simply" +" by accessing this basic report, you can get a quick overview of your actual" +" sales performance." +msgstr "" + +#: ../../crm/reporting/analysis.rst:30 +msgid "" +"You can add a lot of extra data to your report by clicking on the " +"**measures** icon, such as :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:33 +msgid "Expected revenue." +msgstr "" + +#: ../../crm/reporting/analysis.rst:35 +msgid "overpassed deadline." +msgstr "" + +#: ../../crm/reporting/analysis.rst:37 +msgid "" +"Delay to assign (the average time between lead creation and lead " +"assignment)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:40 +msgid "Delay to close (average time between lead assignment and close)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:42 +msgid "the number of interactions per opportunity." +msgstr "" + +#: ../../crm/reporting/analysis.rst:44 +msgid "etc." +msgstr "" + +#: ../../crm/reporting/analysis.rst:50 +msgid "" +"By clicking on the **+** and **-** icons, you can drill up and down your " +"report in order to change the way your information is displayed. For " +"example, if I want to see the expected revenues of my **Direct Sales** team," +" I need to click on the **+** icon on the vertical axis then on **Sales " +"Team**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:55 +msgid "" +"Depending on the data you want to highlight, you may need to display your " +"reports in a more visual view. Odoo **CRM** allows you to transform your " +"report in just a click thanks to 3 graph views : **Pie Chart**, **Bar " +"Chart** and **Line Chart**. These views are accessible through the icons " +"highlighted on the screenshot below." +msgstr "" + +#: ../../crm/reporting/analysis.rst:65 +msgid "Customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:67 +msgid "" +"You can easily customize your analysis reports depending on the **KPIs** " +"(see :doc:`../overview/main_concepts/terminologies`) you want to access. To " +"do so, use the **Advanced search view** located in the right hand side of " +"your screen, by clicking on the magnifying glass icon at the end of the " +"search bar button. This function allows you to highlight only selected data " +"on your report. The **filters** option is very useful in order to display " +"some categories of opportunities, while the **Group by** option improves the" +" readability of your reports according to your needs. Note that you can " +"filter and group by any existing field from your CRM, making your " +"customization very flexible and powerful." +msgstr "" + +#: ../../crm/reporting/analysis.rst:82 +msgid "" +"You can save and reuse any customized filter by clicking on **Favorites** " +"from the **Advanced search view** and then on **Save current search**. The " +"saved filter will then be accessible from the **Favorites** menu." +msgstr "" + +#: ../../crm/reporting/analysis.rst:87 +msgid "" +"Here are a few examples of customized reports that you can use to monitor " +"your sales' performances :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:91 +msgid "Evaluate the current pipeline of each of your salespeople" +msgstr "" + +#: ../../crm/reporting/analysis.rst:93 +msgid "" +"From your pipeline analysis report, make sure first that the **Expected " +"revenue** option is selected under the **Measures** drop-down list. Then, " +"use the **+** and **-** icons and add **Salesperson** and **Stage** to your " +"vertical axis, and filter your desired salesperson. Then click on the " +"**graph view** icon to display a visual representation of your salespeople " +"by stage. This custom report allows you to easily overview the sales " +"activities of your salespeople." +msgstr "" + +#: ../../crm/reporting/analysis.rst:105 +msgid "Forecast monthly revenue by sales team" +msgstr "" + +#: ../../crm/reporting/analysis.rst:107 +msgid "" +"In order to predict monthly revenue and to estimate the short-term " +"performances of your teams, you need to play with two important metrics : " +"the **expected revenue** and the **expected closing**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:111 +msgid "" +"From your pipeline analysis report, make sure first that the **Expected " +"revenue** option is selected under the **Measures** drop-down list. Then " +"click on the **+** icon from the vertical axis and select **Sales team**. " +"Then, on the horizontal axis, click on the **+** icon and select **Expected " +"closing.**" +msgstr "" + +#: ../../crm/reporting/analysis.rst:121 +msgid "" +"In order to keep your forecasts accurate and relevant, make sure your " +"salespeople correctly set up the expected closing and the expected revenue " +"for each one of their opportunities" +msgstr "" + +#: ../../crm/reporting/analysis.rst:126 +msgid ":doc:`../salesteam/setup/organize_pipeline`" +msgstr "" + +#: ../../crm/reporting/review.rst:3 +msgid "How to review my personal sales activities (new sales dashboard)" +msgstr "" + +#: ../../crm/reporting/review.rst:5 +msgid "" +"Sales professionals are struggling everyday to hit their target and follow " +"up on sales activities. They need to access anytime some important metrics " +"in order to know how they are performing and better organize their daily " +"work." +msgstr "" + +#: ../../crm/reporting/review.rst:10 +msgid "" +"Within the Odoo CRM module, every team member has access to a personalized " +"and individual dashboard with a real-time overview of:" +msgstr "" + +#: ../../crm/reporting/review.rst:13 +msgid "" +"Top priorities: they instantly see their scheduled meetings and next actions" +msgstr "" + +#: ../../crm/reporting/review.rst:16 +msgid "" +"Sales performances : they know exactly how they perform compared to their " +"monthly targets and last month activities." +msgstr "" + +#: ../../crm/reporting/review.rst:26 +msgid "Install the CRM application" +msgstr "" + +#: ../../crm/reporting/review.rst:28 +msgid "" +"In order to manage your sales funnel and track your opportunities, you need " +"to install the CRM module, from the **Apps** icon." +msgstr "" + +#: ../../crm/reporting/review.rst:35 +msgid "Create opportunities" +msgstr "" + +#: ../../crm/reporting/review.rst:37 +msgid "" +"If your pipeline is empty, your sales dashboard will look like the " +"screenshot below. You will need to create a few opportunities to activate " +"your dashboard (read the related documentation " +":doc:`../leads/generate/manual` to learn more)." +msgstr "" + +#: ../../crm/reporting/review.rst:45 +msgid "" +"Your dashboard will update in real-time based on the informations you will " +"log into the CRM." +msgstr "" + +#: ../../crm/reporting/review.rst:49 +msgid "" +"you can click anywhere on the dashboard to get a detailed analysis of your " +"activities. Then, you can easily create favourite reports and export to " +"excel." +msgstr "" + +#: ../../crm/reporting/review.rst:54 +msgid "Daily tasks to process" +msgstr "" + +#: ../../crm/reporting/review.rst:56 +msgid "" +"The left part of the sales dashboard (labelled **To Do**) displays the " +"number of meetings and next actions (for example if you need to call a " +"prospect or to follow-up by email) scheduled for the next 7 days." +msgstr "" + +#: ../../crm/reporting/review.rst:64 +msgid "Meetings" +msgstr "" + +#: ../../crm/reporting/review.rst:66 +msgid "" +"In the example here above, I see that I have no meeting scheduled for today " +"and 3 meeting scheduled for the next 7 days. I just have to click on the " +"**meeting** button to access my calendar and have a view on my upcoming " +"appointments." +msgstr "" + +#: ../../crm/reporting/review.rst:75 +msgid "Next actions" +msgstr "" + +#: ../../crm/reporting/review.rst:77 +msgid "" +"Back on the above example, I have 1 activity requiring an action from me. If" +" I click on the **Next action** green button, I will be redirected to the " +"contact form of the corresponding opportunity." +msgstr "" + +#: ../../crm/reporting/review.rst:84 +msgid "" +"Under the **next activity** field, I see that I had planned to send a " +"brochure by email today. As soon as the activity is completed, I can click " +"on **done** (or **cancel**) in order to remove this opportunity from my next" +" actions." +msgstr "" + +#: ../../crm/reporting/review.rst:90 +msgid "" +"When one of your next activities is overdue, it will appear in orange in " +"your dashboard." +msgstr "" + +#: ../../crm/reporting/review.rst:94 +msgid "Performances" +msgstr "" + +#: ../../crm/reporting/review.rst:96 +msgid "" +"The right part of your sales dashboard is about my sales performances. I " +"will be able to evaluate how I am performing compared to my targets (which " +"have been set up by my sales manager) and my activities of the last month." +msgstr "" + +#: ../../crm/reporting/review.rst:105 +msgid "Activities done" +msgstr "" + +#: ../../crm/reporting/review.rst:107 +msgid "" +"The **activities done** correspond to the next actions that have been " +"completed (meaning that you have clicked on **done** under the **next " +"activity** field). When I click on it, I will access a detailed reporting " +"regarding the activities that I have completed." +msgstr "" + +#: ../../crm/reporting/review.rst:116 +msgid "Won in opportunities" +msgstr "" + +#: ../../crm/reporting/review.rst:118 +msgid "" +"This section will sum up the expected revenue of all the opportunities " +"within my pipeline with a stage **Won**." +msgstr "" + +#: ../../crm/reporting/review.rst:125 +msgid "Quantity invoiced" +msgstr "" + +#: ../../crm/reporting/review.rst:127 +msgid "" +"This section will sum up the amount invoiced to my opportunities. For more " +"information about the invoicing process, refer to the related documentation:" +" :doc:`../../accounting/receivables/customer_invoices/overview`" +msgstr "" + +#: ../../crm/reporting/review.rst:132 +msgid ":doc:`analysis`" +msgstr "" + +#: ../../crm/salesteam.rst:3 ../../crm/salesteam/setup.rst:3 +msgid "Sales Team" +msgstr "" + +#: ../../crm/salesteam/manage.rst:3 +msgid "Manage salespeople" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:3 +msgid "How to create a new salesperson?" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:6 +msgid "Create a new user" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:8 +msgid "" +"From the Settings module, go to the submenu :menuselection:`Users --> Users`" +" and click on **Create**. Add first the name of your new salesperson and his" +" professional email address - the one he will use to log in to his Odoo " +"instance - and a picture." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:16 +msgid "" +"Under \"Access Rights\", you can choose which applications your user can " +"access and use. Different levels of rights are available depending on the " +"app. For the Sales application, you can choose between three levels:" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:20 +msgid "**See own leads**: the user will be able to access his own data only" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:22 +msgid "" +"**See all leads**: the user will be able to access all records of every " +"salesman in the sales module" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:25 +msgid "" +"**Manager**: the user will be able to access the sales configuration as well" +" as the statistics reports" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:28 +msgid "" +"When you're done editing the page and have clicked on **Save**, an " +"invitation email will automatically be sent to the user, from which he will " +"be able to log into his personal account." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:36 +msgid "Register your user into his sales team" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:38 +msgid "" +"Your user is now registered in Odoo and can log in to his own session. You " +"can also add him to the sales team of your choice. From the sales module, go" +" to your dashboard and click on the **More** button of the desired sales " +"team, then on **Settings**." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:49 +msgid "" +"If you need to create a new sales team first, refer to the page " +":doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:51 +msgid "" +"Then, under \"Team Members\", click on **Add** and select the name of your " +"salesman from the list. The salesperson is now successfully added to your " +"sales team." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:60 +msgid "" +"You can also add a new salesperson on the fly from your sales team even " +"before he is registered as an Odoo user. From the above screenshot, click on" +" \"Create\" to add your salesperson and enter his name and email address. " +"After saving, the salesperson will receive an invite containing a link to " +"set his password. You will then be able to define his accesses rights under " +"the :menuselection:`Settings --> Users` menu." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:69 +msgid ":doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:5 +msgid "" +"Challenging your employees to reach specific targets with goals and rewards " +"is an excellent way to reinforce good habits and improve your salespeople " +"productivity. The **Gamification** app of Odoo gives you simple and creative" +" ways to motivate and evaluate your employees with real-time recognition and" +" badges inspired by game mechanics." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:14 +msgid "" +"From the **Apps** menu, search and install the **Gamification** module. You " +"can also install the **CRM gamification** app, which will add some useful " +"data (goals and challenges) that can be used related to the usage of the " +"**CRM/Sale** modules." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:23 +msgid "Create a challenge" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:25 +msgid "" +"You will now be able to create your first challenge from the menu " +":menuselection:`Settings --> Gamification Tools --> Challenges`." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:29 +msgid "" +"As the gamification tool is a one-time technical setup, you will need to " +"activate the technical features in order to access the configuration. In " +"order to do so, click on the interrogation mark available from any app " +"(upper-right) and click on **About** and then **Activate the developer " +"mode**." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:38 +msgid "" +"A challenge is a mission that you will send to your salespeople. It can " +"include one or several goals and is set up for a specific period of time. " +"Configure your challenge as follows:" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:42 +msgid "Assign the salespeople to be challenged" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:44 +msgid "Assign a responsible" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:46 +msgid "Set up the periodicity along with the start and the end date" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:48 +msgid "Select your goals" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:50 +msgid "Set up your rewards (badges)" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:53 +msgid "" +"Badges are granted when a challenge is finished. This is either at the end " +"of a running period (eg: end of the month for a monthly challenge), at the " +"end date of a challenge (if no periodicity is set) or when the challenge is " +"manually closed." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:58 +msgid "" +"For example, on the screenshot below, I have challenged 2 employees with a " +"**Monthly Sales Target**. The challenge will be based on 2 goals: the total " +"amount invoiced and the number of new leads generated. At the end of the " +"month, the winner will be granted with a badge." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:67 +msgid "Set up goals" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:69 +msgid "" +"The users can be evaluated using goals and numerical objectives to reach. " +"**Goals** are assigned through **challenges** to evaluate (see here above) " +"and compare members of a team with each others and through time." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:74 +msgid "" +"You can create a new goal on the fly from a **Challenge**, by clicking on " +"**Add new item** under **Goals**. You can select any business object as a " +"goal, according to your company's needs, such as :" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:78 +msgid "number of new leads," +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:80 +msgid "time to qualify a lead or" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:82 +msgid "" +"total amount invoiced in a specific week, month or any other time frame " +"based on your management preferences." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:89 +msgid "" +"Goals may include your database setup as well (e.g. set your company data " +"and a timezone, create new users, etc.)." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:93 +msgid "Set up rewards" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:95 +msgid "" +"For non-numerical achievements, **badges** can be granted to users. From a " +"simple *thank you* to an exceptional achievement, a badge is an easy way to " +"exprimate gratitude to a user for their good work." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:99 +msgid "" +"You can easily create a grant badges to your employees based on their " +"performance under :menuselection:`Gamification Tools --> Badges`." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:106 +msgid ":doc:`../../reporting/analysis`" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:3 +msgid "How to create a new team?" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:5 +msgid "" +"In the Sales module, your sales teams are accessible from the **Dashboard** " +"menu. If you start from a new instance, you will find a sales team installed" +" by default : Direct sales. You can either start using that default sales " +"team and edit it (refer to the section *Create and Organize your stages* " +"from the page :doc:`organize_pipeline`) or create a new one from scratch." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:12 +msgid "" +"To create a new team, go to :menuselection:`Configuration --> Sales Teams` " +"and click on **Create**." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:18 +msgid "Fill in the fields :" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:20 +msgid "Enter the name of your team" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:22 +msgid "Select your team leader" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:24 +msgid "Select your team members" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:26 +msgid "" +"Don't forget to tick the \"Opportunities\" box if you want to manage " +"opportunities from it and to click on SAVE when you're done. Your can now " +"access your new team from your Dashboard." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:35 +msgid "" +"If you started to work on an empty database and didn't create new users, " +"refer to the page :doc:`../manage/create_salesperson`." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:3 +msgid "Set up and organize your sales pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:5 +msgid "" +"A well structured sales pipeline is crucial in order to keep control of your" +" sales process and to have a 360-degrees view of your leads, opportunities " +"and customers." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:9 +msgid "" +"The sales pipeline is a visual representation of your sales process, from " +"the first contact to the final sale. It refers to the process by which you " +"generate, qualify and close leads through your sales cycle. In Odoo CRM, " +"leads are brought in at the left end of the sales pipeline in the Kanban " +"view and then moved along to the right from one stage to another." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:16 +msgid "" +"Each stage refers to a specific step in the sale cycle and specifically the " +"sale-readiness of your potential customer. The number of stages in the sales" +" funnel varies from one company to another. An example of a sales funnel " +"will contain the following stages: *Territory, Qualified, Qualified Sponsor," +" Proposition, Negotiation, Won, Lost*." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:26 +msgid "" +"Of course, each organization defines the sales funnel depending on their " +"processes and workflow, so more or fewer stages may exist." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:30 +msgid "Create and organize your stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:33 +msgid "Add/ rearrange stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:35 +msgid "" +"From the sales module, go to your dashboard and click on the **PIPELINE** " +"button of the desired sales team. If you don't have any sales team yet, you " +"need to create one first." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:46 +msgid "" +"From the Kanban view of your pipeline, you can add stages by clicking on " +"**Add new column.** When a column is created, Odoo will then automatically " +"propose you to add another column in order to complete your process. If you " +"want to rearrange the order of your stages, you can easily do so by dragging" +" and dropping the column you want to move to the desired location." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:58 +msgid "" +"You can add as many stages as you wish, even if we advise you not having " +"more than 6 in order to keep a clear pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:64 +msgid "" +"Some companies use a pre qualification step to manage their leads before to " +"convert them into opportunities. To activate the lead stage, go to " +":menuselection:`Configuration --> Settings` and select the radio button as " +"shown below. It will create a new submenu **Leads** under **Sales** that " +"gives you access to a listview of all your leads." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:74 +msgid "Set up stage probabilities" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:77 +msgid "What is a stage probability?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:79 +msgid "" +"To better understand what are the chances of closing a deal for a given " +"opportunity in your pipe, you have to set up a probability percentage for " +"each of your stages. That percentage refers to the success rate of closing " +"the deal." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:84 +msgid "" +"Setting up stage probabilities is essential if you want to estimate the " +"expected revenues of your sales cycle" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:88 +msgid "" +"For example, if your sales cycle contains the stages *Territory, Qualified, " +"Qualified Sponsor, Proposition, Negotiation, Won and Lost,* then your " +"workflow could look like this :" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:92 +msgid "" +"**Territory** : opportunity just received from Leads Management or created " +"from a cold call campaign. Customer's Interest is not yet confirmed." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:96 +msgid "*Success rate : 5%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:98 +msgid "" +"**Qualified** : prospect's business and workflow are understood, pains are " +"identified and confirmed, budget and timing are known" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:101 +msgid "*Success rate : 15%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:103 +msgid "" +"**Qualified sponsor**: direct contact with decision maker has been done" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:106 +msgid "*Success rate : 25%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:108 +msgid "**Proposition** : the prospect received a quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:110 +msgid "*Success rate : 50%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:112 +msgid "**Negotiation**: the prospect negotiates his quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:114 +msgid "*Success rate : 75%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:116 +msgid "" +"**Won** : the prospect confirmed his quotation and received a sales order. " +"He is now a customer" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:119 +msgid "*Success rate : 100%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:121 +msgid "**Lost** : the prospect is no longer interested" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:123 +msgid "*Success rate : 0%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:127 +msgid "" +"Within your pipeline, each stage should correspond to a defined goal with a " +"corresponding probability. Every time you move your opportunity to the next " +"stage, your probability of closing the sale will automatically adapt." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:131 +msgid "" +"You should consider using probability value as **100** when the deal is " +"closed-won and **0** for deal closed-lost." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:135 +msgid "How to set up stage probabilities?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:137 +msgid "" +"To edit a stage, click on the **Settings** icon at the right of the desired " +"stage then on EDIT" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:143 +msgid "" +"Select the Change probability automatically checkbox to let Odoo adapt the " +"probability of the opportunity to the probability defined in the stage. For " +"example, if you set a probability of 0% (Lost) or 100% (Won), Odoo will " +"assign the corresponding stage when the opportunity is marked as Lost or " +"Won." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:151 +msgid "" +"Under the requirements field you can enter the internal requirements for " +"this stage. It will appear as a tooltip when you place your mouse over the " +"name of a stage." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/db_management.po b/locale/ru/LC_MESSAGES/db_management.po new file mode 100644 index 000000000..680b84ce9 --- /dev/null +++ b/locale/ru/LC_MESSAGES/db_management.po @@ -0,0 +1,521 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../db_management/db_online.rst:8 +msgid "Online Database management" +msgstr "" + +#: ../../db_management/db_online.rst:13 +msgid "Duplicating a database" +msgstr "" + +#: ../../db_management/db_online.rst:15 +msgid "" +"Database duplication, renaming, custom DNS, etc. is not available to free " +"customers of our Online platform." +msgstr "" + +#: ../../db_management/db_online.rst:18 +msgid "" +"Access the `database management page `__ " +"(you will have to sign in). Next, make sure you are connected as the " +"administrator of the database you want to duplicate. After that, click on " +"the **Manage Your Databases** button." +msgstr "" + +#: ../../db_management/db_online.rst:26 +msgid "" +"In the line of the database you want to duplicate, you will have a few " +"buttons. To duplicate your database, just click **Duplicate**. You will have" +" to give a name to your duplicate, then click **Duplicate Database**." +msgstr "" + +#: ../../db_management/db_online.rst:36 +msgid "A duplicated database has the same behaviour as a real one:" +msgstr "" + +#: ../../db_management/db_online.rst:38 +msgid "Emails are sent" +msgstr "" + +#: ../../db_management/db_online.rst:40 +msgid "Payments are processed (in the e-commerce, for example)" +msgstr "" + +#: ../../db_management/db_online.rst:42 +msgid "Delivery orders (shipping providers) are sent" +msgstr "" + +#: ../../db_management/db_online.rst:44 +msgid "Etc." +msgstr "" + +#: ../../db_management/db_online.rst:46 +msgid "" +"It is **strongly** advised to test behaviour using sample customers/products" +" (with a `disposable e-mail `__ address, for " +"example)" +msgstr "" + +#: ../../db_management/db_online.rst:50 +msgid "" +"After a few seconds, you will be logged in your duplicated database. Notice " +"that the url uses the name you chose for your duplicated database." +msgstr "" + +#: ../../db_management/db_online.rst:54 +msgid "Duplicate databases expire automatically after 15 days." +msgstr "" + +#: ../../db_management/db_premise.rst:7 +msgid "On-premise Database management" +msgstr "" + +#: ../../db_management/db_premise.rst:10 +msgid "Register a database" +msgstr "" + +#: ../../db_management/db_premise.rst:12 +msgid "" +"To register your database, you just need to enter your Subscription Code in " +"the banner in the App Switcher. Make sure you do not add extra spaces before" +" or after your subscription code. If the registration is successful, it will" +" turn green and will provide you with the Expiration Date of your freshly-" +"registered database. You can check this Epiration Date in the About menu " +"(Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../db_management/db_premise.rst:20 +msgid "Registration Error Message" +msgstr "" + +#: ../../db_management/db_premise.rst:22 +msgid "" +"If you are unable to register your database, you will likely encounter this " +"message:" +msgstr "" + +#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97 +#: ../../db_management/db_premise.rst:130 +msgid "Solutions" +msgstr "" + +#: ../../db_management/db_premise.rst:33 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../db_management/db_premise.rst:35 +msgid "" +"Check if your subscription details get the tag \"In Progress\" on your `Odoo" +" Account `__ or with your Account " +"Manager" +msgstr "" + +#: ../../db_management/db_premise.rst:39 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../db_management/db_premise.rst:41 +msgid "" +"You can link only one database per subscription. (Need a test or a " +"development database? `Find a partner `__)" +msgstr "" + +#: ../../db_management/db_premise.rst:45 +msgid "" +"You can unlink the old database yourself on your `Odoo Contract " +"`__ with the button \"Unlink " +"database\"" +msgstr "" + +#: ../../db_management/db_premise.rst:52 +msgid "" +"A confirmation message will appear; make sure this is the correct database " +"as it will be deactivated shortly:" +msgstr "" + +#: ../../db_management/db_premise.rst:59 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../db_management/db_premise.rst:61 +#: ../../db_management/db_premise.rst:190 +msgid "" +"From July 2016 onward, Odoo 9 now automatically change the uuid of a " +"duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../db_management/db_premise.rst:64 +msgid "" +"If it's not the case, you may have multiple databases sharing the same UUID." +" Please check on your `Odoo Contract " +"`__, a short message will appear " +"specifying which database is problematic:" +msgstr "" + +#: ../../db_management/db_premise.rst:73 +msgid "" +"In this case, you need to change the UUID on your test databases to solve " +"this issue. You will find more information about this in :ref:`this section " +"`." +msgstr "" + +#: ../../db_management/db_premise.rst:76 +msgid "" +"For your information, we identify database with UUID. Therefore, each " +"database should have a distinct UUID to ensure that registration and " +"invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../db_management/db_premise.rst:82 +msgid "Too much users error message" +msgstr "" + +#: ../../db_management/db_premise.rst:84 +msgid "" +"If you have more users in your local database than provisionned in your Odoo" +" Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../db_management/db_premise.rst:93 +msgid "" +"When the message appears you have 30 days before the expiration. The " +"countdown is updated everyday." +msgstr "" + +#: ../../db_management/db_premise.rst:99 +msgid "" +"**Add more users** on your subscription: follow the link and Validate the " +"upsell quotation and pay for the extra users." +msgstr "" + +#: ../../db_management/db_premise.rst:102 +msgid "or" +msgstr "" + +#: ../../db_management/db_premise.rst:104 +msgid "" +"**Deactivate users** as explained in this `Documentation " +"`__ and **Reject** the upsell quotation." +msgstr "" + +#: ../../db_management/db_premise.rst:109 +msgid "" +"Once your database has the correct number of users, the expiration message " +"will disappear automatically after a few days, when the next verification " +"occurs. We understand that it can be a bit frightening to see the countdown," +" so you can :ref:`force an Update Notification ` to make the " +"message disappear right away." +msgstr "" + +#: ../../db_management/db_premise.rst:116 +msgid "Database expired error message" +msgstr "" + +#: ../../db_management/db_premise.rst:118 +msgid "" +"If your database reaches its expiration date before your renew your " +"subscription, you will encounter this message:" +msgstr "" + +#: ../../db_management/db_premise.rst:126 +msgid "" +"This **blocking** message appears after a non-blocking message that lasts 30" +" days. If you fail to take action before the end of the countdown, the " +"database is expired." +msgstr "" + +#: ../../db_management/db_premise.rst:134 +msgid "" +"Renew your subscription: follow the link and renew your subscription - note " +"that" +msgstr "" + +#: ../../db_management/db_premise.rst:133 +msgid "" +"if you wish to pay by Wire Transfer, your subscription will effectively be " +"renewed only when the payment arrives, which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../db_management/db_premise.rst:136 +msgid "Contact our `Support `__" +msgstr "" + +#: ../../db_management/db_premise.rst:138 +msgid "" +"None of those solutions worked for you? Please contact our `Support " +"`__" +msgstr "" + +#: ../../db_management/db_premise.rst:145 +msgid "Force an Update Notification" +msgstr "" + +#: ../../db_management/db_premise.rst:147 +msgid "" +"Update Notifications happen once every 7 days and keep your database up-to-" +"date with your Odoo Enterprise subscription. If you modify your subscription" +" (i.e. add more users, renew it for a year, etc.), your local database will " +"only be made aware of the change once every 7 days - this can cause " +"discrepancies between the state of your subscription and some notifications " +"in your App Switcher. When doing such an operation on your subscription, you" +" can force an Update using the following procedure:" +msgstr "" + +#: ../../db_management/db_premise.rst:154 +msgid "Connect to the database with the **Administrator** account" +msgstr "" + +#: ../../db_management/db_premise.rst:155 +msgid "" +"Switch to the Developer mode by using the **About** option in the top-right " +"menu (in V9) / in **Settings** (in V10): click on **Activate the developer" +" mode**" +msgstr "" + +#: ../../db_management/db_premise.rst:158 +msgid "" +"Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > " +"\"Scheduled Actions\"" +msgstr "" + +#: ../../db_management/db_premise.rst:160 +msgid "" +"Find \"Update Notification\" in the list, click on it, and finally click on " +"the button \"**RUN MANUALLY**\"" +msgstr "" + +#: ../../db_management/db_premise.rst:162 +msgid "Refresh the page, the \"Expiration\" notification should be gone" +msgstr "" + +#: ../../db_management/db_premise.rst:165 +msgid "" +"You may have kept the same UUID on different databases and we receive " +"information from those databases too. So please read :ref:`this " +"documentation ` to know how to change the UUID. After the" +" change you can force a ping to speed up the verification, your production " +"database will then be correctly identified." +msgstr "" + +#: ../../db_management/db_premise.rst:174 +msgid "Duplicate a database" +msgstr "" + +#: ../../db_management/db_premise.rst:176 +msgid "" +"You can duplicate your database by accessing the database manager on your " +"server (/web/database/manager). In this page, you can easily " +"duplicate your database (among other things)." +msgstr "" + +#: ../../db_management/db_premise.rst:184 +msgid "" +"When you duplicate a local database, it is **strongly** advised to change " +"the duplicated database's uuid (Unniversally Unique Identifier), since this " +"uuid is how your database identifies itself with our servers. Having two " +"databases with the same uuid could result in invoicing problems or " +"registration problems down the line." +msgstr "" + +#: ../../db_management/db_premise.rst:193 +msgid "" +"The database uuid is currently accessible from the menu **Settings > " +"Technical > System Parameters**, we advise you to use a `uuid generator " +"`__ or to use the unix command ``uuidgen`` to" +" generate a new uuid. You can then simply replace it like any other record " +"by clicking on it and using the edit button." +msgstr "" + +#: ../../db_management/documentation.rst:7 +msgid "Users and Features" +msgstr "" + +#: ../../db_management/documentation.rst:9 +msgid "" +"As the administrator of your database, you are responsible for its usage. " +"This includes the Apps you install as well as the number of users currently " +"in use." +msgstr "" + +#: ../../db_management/documentation.rst:13 +msgid "" +"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) " +"but it is *not* a smartphone. You should apply caution when adding/removing " +"features (especially Apps) on your database since this may impact your " +"subscription amount significantly (or switch you from a free account to a " +"paying one on our online platform)." +msgstr "" + +#: ../../db_management/documentation.rst:19 +msgid "" +"This page contains some information as to how you can manage your Odoo " +"instances. Before carrying any of these procedures, we **strongly** advise " +"to test them on a duplicate of your database first. That way, if something " +"goes wrong, your day-to-day business is not impacted." +msgstr "" + +#: ../../db_management/documentation.rst:24 +msgid "" +"You can find guides on how to duplicate your databases both for :ref:`online" +" ` and :ref:`on premise ` " +"installations." +msgstr "" + +#: ../../db_management/documentation.rst:28 +msgid "" +"If you have questions about the content of this page or if you encounter an " +"issue while carrying out these procedures, please contact us through our " +"`support form `__." +msgstr "" + +#: ../../db_management/documentation.rst:34 +msgid "Deactivating Users" +msgstr "" + +#: ../../db_management/documentation.rst:36 +msgid "" +"Make sure you have sufficient **administrative rights** if you want to " +"change the status of any of your users." +msgstr "" + +#: ../../db_management/documentation.rst:39 +msgid "" +"In your Odoo instance, click on **Settings**. You will have a section " +"showing you the active users on your database. Click on **Manage access " +"rights.**" +msgstr "" + +#: ../../db_management/documentation.rst:44 +#: ../../db_management/documentation.rst:82 +msgid "|settings|" +msgstr "" + +#: ../../db_management/documentation.rst:44 +msgid "|browse_users|" +msgstr "" + +#: ../../db_management/documentation.rst:47 +msgid "You'll then see the list of your users." +msgstr "" + +#: ../../db_management/documentation.rst:52 +msgid "" +"The pre-selected filter *Internal Users* shows your paying users (different " +"from the *Portal Users* which are free). If you remove this filter, you'll " +"get all your users (the ones you pay for and the portal ones)" +msgstr "" + +#: ../../db_management/documentation.rst:57 +msgid "" +"In your list of users, click on the user you want to deactivate. As soon as " +"you are on the userform, go with your mouse cursor on the status **Active** " +"(top right). Click on Active and you will notice that the status will change" +" to **Inactive** immediately." +msgstr "" + +#: ../../db_management/documentation.rst:66 +msgid "The user is now deactivated." +msgstr "" + +#: ../../db_management/documentation.rst:68 +msgid "**Never** deactivate the main user (*admin*)" +msgstr "" + +#: ../../db_management/documentation.rst:71 +msgid "Uninstalling Apps" +msgstr "" + +#: ../../db_management/documentation.rst:73 +msgid "" +"Make sure you first test what you are about to do on a :ref:`duplicate " +"` of your database before making any changes (*especially* " +"installing/uninstalling apps)." +msgstr "" + +#: ../../db_management/documentation.rst:77 +msgid "" +"In your Odoo instance click on **Settings**; in this app, you will be able " +"to see how many applications you have installed. Click on **Browse Apps** to" +" access the list of your installed applications." +msgstr "" + +#: ../../db_management/documentation.rst:82 +msgid "|browse_apps|" +msgstr "" + +#: ../../db_management/documentation.rst:85 +msgid "" +"In your applications' dashboard, you will see all the icons of your " +"applications. Click on the application you want to uninstall. Then, on the " +"form of the application, click on **Uninstall**." +msgstr "" + +#: ../../db_management/documentation.rst:92 +msgid "" +"Some applications have dependencies, like Invoicing, eCommerce, etc. " +"Therefore, the system will give you a warning message to advise you of what " +"is about to be removed. If you uninstall your application, all its " +"dependencies will be uninstalled as well (and the data in them will " +"permanently disappear). If you are sure you still want to uninstall it, then" +" click **Confirm**." +msgstr "" + +#: ../../db_management/documentation.rst:99 +msgid "" +"Last, after having checked the warning message (if any), click **Confirm**." +msgstr "" + +#: ../../db_management/documentation.rst:104 +msgid "You have finished uninstalling your application." +msgstr "" + +#: ../../db_management/documentation.rst:107 +msgid "Good to know" +msgstr "" + +#: ../../db_management/documentation.rst:109 +msgid "" +"**Uninstalling apps, managing users, etc. is up to you**: no one else can " +"know if your business flow is broken better than you. If we were to " +"uninstall applications for you, we would never be able to tell if relevant " +"data had been removed or if one of your business flow was broken because we " +"*do not know how you work* and therefore cannot validate these kinds of " +"operations." +msgstr "" + +#: ../../db_management/documentation.rst:115 +msgid "" +"**Odoo Apps have dependencies**: this means that you may need to install " +"modules that you do not actively use to access some features of Odoo you " +"might need. For example, the Website Builder app is needed to be able to " +"show your customer their Quotes in a web page. Even though you might not " +"need or use the Website itself, it is needed for the Online Quotes feature " +"to work properly." +msgstr "" + +#: ../../db_management/documentation.rst:122 +msgid "" +"**Always test app installation/removal on a duplicate** (or on a free trial " +"database): that way you can know what other apps may be required, etc. This " +"will avoid surprises when uninstalling or when receiving your invoices." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/discuss.po b/locale/ru/LC_MESSAGES/discuss.po new file mode 100644 index 000000000..822ee3d2b --- /dev/null +++ b/locale/ru/LC_MESSAGES/discuss.po @@ -0,0 +1,562 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../discuss.rst:5 +msgid "Discuss" +msgstr "" + +#: ../../discuss/email_servers.rst:3 +msgid "How to use my own email servers to send and receive email in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:6 +msgid "When is it needed" +msgstr "" + +#: ../../discuss/email_servers.rst:7 +msgid "" +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." +msgstr "" + +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" +msgstr "" + +#: ../../discuss/email_servers.rst:15 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." +msgstr "" + +#: ../../discuss/email_servers.rst:21 +msgid "" +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:26 +msgid "Set an outgoing email server for outbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:27 +msgid "" +"You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " +"etc.) as well as your admin credentials. Once all the information has been " +"filled out, click on *Test Connection*." +msgstr "" + +#: ../../discuss/email_servers.rst:35 +msgid "Set an incoming email server for inbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:36 +msgid "" +"Fill out the form according to your email provider’s settings. Leave the " +"*Actions to Perform on Incoming Mails* blank. Once all the information has " +"been filled out, click on *TEST & CONFIRM*." +msgstr "" + +#: ../../discuss/email_servers.rst:43 +msgid "" +"By default inbound messages are fetched every 5 minutes. You can change this" +" value in developer mode. Go to :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." +msgstr "" + +#: ../../discuss/email_servers.rst:49 +msgid "Set the domain name" +msgstr "" + +#: ../../discuss/email_servers.rst:50 +msgid "" +"Enter the domain name of your email servers (e.g. mycompany.com) in General " +"Settings." +msgstr "" + +#: ../../discuss/email_servers.rst:57 +msgid "Create a catchall address" +msgstr "" + +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 +msgid "" +"Create a catchall address in your email server settings. We advise you to " +"use \"catchall@\" so that everything works out straight away. If you want to" +" use another alias, you have extra steps in Odoo:" +msgstr "" + +#: ../../discuss/email_servers.rst:67 +msgid "Activate the developer mode from your Settings Dashboard." +msgstr "" + +#: ../../discuss/email_servers.rst:72 +msgid "" +"Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` and enter your custom catchall alias in " +"*mail.catchall.alias*." +msgstr "" + +#: ../../discuss/email_servers.rst:79 +msgid "You can edit the email alias used for bounced messages the same way." +msgstr "" + +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" +msgstr "" + +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here `__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 +msgid "" +"Odoo Discuss is a perfect tool to send and read messages related to business" +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +"both systems without mingling them: What is related to Odoo business objects" +" or applications goes into Odoo; What is not can be managed into your " +"external email box." +msgstr "" + +#: ../../discuss/email_servers.rst:150 +msgid "" +"To do so, create specific email aliases to use in Odoo (to generate leads or" +" opportunities, helpdesk tickets, etc.). If you take an email alias already " +"used for messaging outside of Odoo, incoming messages will land into both " +"systems. This will negatively impact your productivity." +msgstr "" + +#: ../../discuss/mail_twitter.rst:3 +msgid "How to follow Twitter feed from Odoo" +msgstr "" + +#: ../../discuss/mail_twitter.rst:8 +msgid "" +"You can follow specific hashtags on Twitter and see the tweets within the " +"Odoo Discuss channels of your choice. The tweets are retrieved periodically " +"from Twitter. An authenticated user can retweet the messages." +msgstr "" + +#: ../../discuss/mail_twitter.rst:13 +msgid "Setting up the App on Twitter's side" +msgstr "" + +#: ../../discuss/mail_twitter.rst:15 +msgid "" +"Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks" +" for tweets, and through which a user can retweet. To set up this app, go to" +" http://apps.twitter.com/app/new and put in the values:" +msgstr "" + +#: ../../discuss/mail_twitter.rst:19 +msgid "Name: this is the name of the application on Twitter" +msgstr "" + +#: ../../discuss/mail_twitter.rst:21 +msgid "" +"Website: this is the external url of your Odoo database, with \"/web\" " +"added. For example, if your Odoo instance is hosted at " +"\"http://www.example.com\", you should put \"http://www.example.com/web\" in" +" this field." +msgstr "" + +#: ../../discuss/mail_twitter.rst:25 +msgid "" +"Callback URL: this is the address on which Twitter will respond. Following " +"the previous example you should write " +"\"http://www.example.com/web/twitter/callback\"." +msgstr "" + +#: ../../discuss/mail_twitter.rst:28 +msgid "" +"Do not forget to accept the terms **Developer agreement** of use and click " +"on **Create your Twitter application** at the bottom of the page." +msgstr "" + +#: ../../discuss/mail_twitter.rst:33 +msgid "Getting the API key and secret" +msgstr "" + +#: ../../discuss/mail_twitter.rst:35 +msgid "" +"When on the App dashboard, switch to the **Keys and Access Tokens** tab." +msgstr "" + +#: ../../discuss/mail_twitter.rst:40 +msgid "" +"And copy those values in Odoo in :menuselection:`Settings--> General " +"Settings--> Twitter discuss integration` and click on **Save** to save the " +"settings." +msgstr "" + +#: ../../discuss/mentions.rst:3 +msgid "How to grab attention of other users in my messages" +msgstr "" + +#: ../../discuss/mentions.rst:5 +msgid "" +"You can **mention** a user in a channel or chatter by typing **@user-name**." +" Mentioning a user in the chatter will set them as a follower of the item " +"(if they are not already) and send a message to their inbox. The item " +"containing the mention will also be bolded in the list view. Mentioning a " +"user in a channel will send a message to their inbox. You cannot mention a " +"user in a channel who is not subscribed to the channel. Typing **#channel-" +"name** will provide a link to the mentioned channel in either a chatter or " +"another channel." +msgstr "" + +#: ../../discuss/mentions.rst:15 +msgid "Direct messaging a user" +msgstr "" + +#: ../../discuss/mentions.rst:17 +msgid "" +"**Direct messages** are private messages viewable only by the sender and " +"recipient. You can send direct messages to other users from within the " +"Discuss module by creating a new conversation or selecting an existing one " +"from the sidebar. Direct messages can be sent from anywhere in Odoo using " +"the speech bubble icon in the top bar. The online status of other users is " +"displayed to the left of their name. A **green dot** indicates that a user " +"is Online, an **orange dot** that they are Idle, and a **grey dot** that " +"they are offline." +msgstr "" + +#: ../../discuss/mentions.rst:28 +msgid "Desktop notifications from Discuss" +msgstr "" + +#: ../../discuss/mentions.rst:30 +msgid "" +"You can choose to see **desktop notifications** when you receive a new " +"direct message. The notification shows you the sender and a brief preview of" +" the message contents. These can be configured or disabled by clicking on " +"the gear icon in the corner of the notification.." +msgstr "" + +#: ../../discuss/monitoring.rst:3 +msgid "How to be responsive at work thanks to my Odoo inbox" +msgstr "" + +#: ../../discuss/monitoring.rst:5 +msgid "" +"Use the **Inbox** in Discuss app to monitor updates and progress on " +"everything you do in Odoo. Notifications and messages from everything you " +"follow or in which you are mentioned appear in your inbox." +msgstr "" + +#: ../../discuss/monitoring.rst:13 +msgid "You can keep an eye on your **Inbox** from any screen." +msgstr "" + +#: ../../discuss/monitoring.rst:18 +msgid "" +"Marking an item with a check marks the message as **read** and removes it " +"from your inbox. If you would like to save an item for future reference or " +"action, mark it with a star to add it to the **Starred** box. You can star " +"any message or notification in Discuss or any of the item-specific chatters " +"throughout Odoo to keep tabs on it here." +msgstr "" + +#: ../../discuss/overview.rst:3 +msgid "Why to use Odoo Discuss" +msgstr "" + +#: ../../discuss/overview.rst:5 +msgid "" +"Odoo Discuss is an easy to use messaging app for teams that brings all your " +"organization's communication into one place and seamlessly integrates with " +"the Odoo platform. Discuss lets you send and receive messages from wherever " +"you are in Odoo as well as manage your messages and notifications easily " +"from within the app. Discuss allows you to create **channels** for team " +"chats, conversations about projects, meeting coordination, and more in one " +"simple and searchable interface." +msgstr "" + +#: ../../discuss/team_communication.rst:3 +msgid "How to efficiently communicate in team using channels" +msgstr "" + +#: ../../discuss/team_communication.rst:5 +msgid "" +"You can use **channels** to organize discussions between individual teams, " +"departments, projects, or any other group that requires regular " +"communication. By having conversations that everyone in the channel can see," +" it's easy to keep the whole team in the loop with the latest developments." +msgstr "" + +#: ../../discuss/team_communication.rst:12 +msgid "Creating a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:14 +msgid "" +"In Discuss there are two types of channels - **public** and **private**." +msgstr "" + +#: ../../discuss/team_communication.rst:17 +msgid "" +"A **public channel** can only be created by an administrator with write " +"privileges and can be seen by everyone in the organization. By contrast, a " +"**private channel** can be created by any user and by default is only " +"visible to users who have been invited to this channel." +msgstr "" + +#: ../../discuss/team_communication.rst:24 +msgid "" +"A public channel is best used when many employees need to access information" +" (such as interdepartmental communication or company announcements), whereas" +" a private channel should be used whenever information should be limited to " +"specific users/employees (such as department specific or sensitive " +"information)." +msgstr "" + +#: ../../discuss/team_communication.rst:31 +msgid "Configuring a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:33 +msgid "" +"You can configure a channel's name, description, access rights, automatic " +"subscription, and emailing from :menuselection:`#channel-name --> Settings`." +" Changing channel access rights allows you to control which groups can view " +"each channel. You can make a channel visible by all users, invited users, or" +" users within a selected user group. Note that allowing \"Everyone\" to " +"follow a private channel will let other users view and join it as they would" +" a public channel." +msgstr "" + +#: ../../discuss/team_communication.rst:47 +msgid "How to set up a mailing list" +msgstr "" + +#: ../../discuss/team_communication.rst:49 +msgid "" +"A channel can be configured to behave as a mailing list. From within " +":menuselection:`#channel-name --> Settings`, define the email you would like" +" to use. Users can then post to the channel and choose to receive " +"notifications using the defined email address. An envelope icon will appear " +"next to the channel name in the list to indicate that a channel will send " +"messages by email." +msgstr "" + +#: ../../discuss/team_communication.rst:57 +msgid "Locating a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:59 +msgid "" +"If you do not see a channel on your dashboard, you can search the list of " +"**public channels** to locate the correct channel or create a new channel by" +" clicking the plus icon." +msgstr "" + +#: ../../discuss/team_communication.rst:66 +msgid "" +"You can also click the **CHANNELS** heading to browse a list of all public " +"channels. This allows the user to manually **join** and **leave** public " +"channels from a single screen." +msgstr "" + +#: ../../discuss/team_communication.rst:71 +msgid "" +"It is always wise to search for a channel before creating a new one to " +"ensure that duplicate entries are not created for the same topic." +msgstr "" + +#: ../../discuss/team_communication.rst:76 +msgid "Using filters to navigate within Discuss" +msgstr "" + +#: ../../discuss/team_communication.rst:78 +msgid "" +"The topbar search provides access to the same comprehensive search function " +"present in the rest of Odoo. You can apply multiple **filter criteria** and " +"**save filters** for later use. The search function accepts wildcards by " +"using the underscore character \"\\ **\\_**\\ \" to represent a **single " +"character wildcard.**" +msgstr "" + +#: ../../discuss/tracking.rst:3 +msgid "How to follow a discussion thread and define what I want to hear about" +msgstr "" + +#: ../../discuss/tracking.rst:6 +msgid "How to follow a discussion thread" +msgstr "" + +#: ../../discuss/tracking.rst:7 +msgid "" +"You can keep track of virtually any business object in Odoo (an opportunity," +" a quotation, a task, etc.), by **following** it." +msgstr "" + +#: ../../discuss/tracking.rst:14 +msgid "How to choose the events to follow" +msgstr "" + +#: ../../discuss/tracking.rst:15 +msgid "" +"You can choose which types of events you want to be notified about. The " +"example below shows the options available when following a **task** in the " +"**Project** app." +msgstr "" + +#: ../../discuss/tracking.rst:23 +msgid "How to add other followers" +msgstr "" + +#: ../../discuss/tracking.rst:24 +msgid "" +"You can invite other users and add channels as followers. Adding a channel " +"as a follower will send messages posted in the chatter to the channel with a" +" link back to the original document." +msgstr "" + +#: ../../discuss/tracking.rst:34 +msgid "How to be a default follower" +msgstr "" + +#: ../../discuss/tracking.rst:35 +msgid "" +"You are automatically set as a default follower of any item you create. In " +"some applications like CRM and Project, you can be a default follower of any" +" new record created to get notified of specific events (e.g. a new task " +"created, an opportunity won)." +msgstr "" + +#: ../../discuss/tracking.rst:40 +msgid "" +"To do so, start following the parent business object (e.g. the sales channel" +" in CRM, the project in Project). Then, choose the events you want to hear " +"about." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/ecommerce.po b/locale/ru/LC_MESSAGES/ecommerce.po new file mode 100644 index 000000000..472bc9ec3 --- /dev/null +++ b/locale/ru/LC_MESSAGES/ecommerce.po @@ -0,0 +1,1240 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../ecommerce.rst:5 +msgid "eCommerce" +msgstr "" + +#: ../../ecommerce/getting_started.rst:3 +msgid "Get started" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:3 +msgid "How to customize my catalog page" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:6 +msgid "Product Catalog" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:8 +msgid "" +"All your published items show up in your catalog page (or *Shop* page)." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:13 +msgid "" +"Most options are available in the *Customize* menu: display attributes, " +"website categories, etc." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:20 +msgid "Highlight a product" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:22 +msgid "" +"Boost the visibility of your star/promoted products: push them to top, make " +"them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop" +" page, switch to Edit mode and click any item to start customizing the grid." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:26 +msgid "" +"See how to do it: " +"https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:29 +msgid "Quick add to cart" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:31 +msgid "" +"If your customers buy a lot of items at once, make their process shorter by " +"enabling purchases from the catalog page. To do so, add product description " +"and add to cart button. Turn on the following options in *Customize* menu: " +"Product Description, Add to Cart, List View (to display product description " +"better)." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:3 +msgid "How to build a product page" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:5 +msgid "On the website click *New Page* in the top-right corner." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:7 +msgid "Then click *New Product* and follow the blinking tips." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:12 +msgid "Here are the main elements of the Product page:" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:17 +msgid "Many elements can be made visible from the *Customize* menu." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:22 +msgid "See how to configure your products from links here below." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:26 +msgid ":doc:`../managing_products/variants`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:27 +msgid ":doc:`../../sales/products_prices/taxes`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:28 +msgid ":doc:`../managing_products/stock`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:29 +msgid ":doc:`../maximizing_revenue/cross_selling`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:30 +msgid ":doc:`../maximizing_revenue/reviews`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:31 +msgid ":doc:`../maximizing_revenue/pricing`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:32 +msgid ":doc:`../../website/optimize/seo`" +msgstr "" + +#: ../../ecommerce/managing_products.rst:3 +msgid "Manage my products" +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:3 +msgid "How to display several images per product" +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:5 +msgid "" +"By default your product web page displays the main image of your product " +"only. If you like to show your products under several angles, you can turn " +"the image into a carrousel." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:11 +msgid "" +"Check *Several images per product* in :menuselection:`Website Admin --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:13 +msgid "" +"Open a product detail form and upload images from *Images* tab. Hit *Create*" +" in Edit mode to get the upload wizard." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:19 +msgid "Such extra image are common to all the product variants (if any)." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:3 +msgid "How to show product availability" +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:5 +msgid "" +"The availability of your products can be shown on the website to reassure " +"your customers." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:10 +msgid "" +"To display this, open the *Sales* tab in the product detail form and select " +"an option in *Availability*." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:16 +msgid "" +"A custom warning message can be anything related to a stock out, delivery " +"delay, etc." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:22 +msgid "This tool does not require the Inventory app to be installed." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:25 +msgid "" +"If one item is no longer sellable, unpublish it from your website. If it " +"comes to one particular product variant, deactivate the variant in the " +"backend (see :doc:`../maximizing_revenue/pricing`)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:3 +msgid "How to manage product variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:5 +msgid "" +"Product variants are used to offer variations of the same product to your " +"customers on the products page. For example, the customer chooses a T-shirt " +"and then selects its size and color." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:13 +msgid "How to create attributes & variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:15 +msgid "" +"Turn on *Products can have several attributes, defining variants (Example: " +"size, color,...)* in :menuselection:`Sales --> Settings`." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:18 +msgid "Select a product from the Products list, go to the *Variants* tab." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:20 +msgid "" +"Add as many attributes as you need from 3 different types: radio buttons, " +"drop-down menu or color buttons. You get several variants as soon as there " +"are 2 values for 1 attribute." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:28 +msgid "How to edit variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:30 +msgid "See all the variants from the product template detail form." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:38 +msgid "You can edit following data:" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:40 +msgid "Picture (will update in real time on the website)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:41 +msgid "Barcode," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:42 +msgid "Internal Reference (SKU #)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:43 +msgid "Volume," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:44 +msgid "Weight," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:45 +msgid "Active (available in quotes & website)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:48 +msgid "" +"Both the Barcode and the Internal Reference are variant-specific. You need " +"to populate them once the variants generated." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:52 +msgid "" +"See and edit all the variants from :menuselection:`Sales --> Sales --> " +"Product Variants` as well. This might be quicker if you manage lots of " +"variants." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:56 +msgid "How to set specific prices per variant" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:58 +msgid "" +"You can also set a specific public price per variant by clicking *Variant " +"Prices* in the product detail form (action in top-left corner)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:64 +msgid "" +"The Price Extra is added to the product price whenever the corresponding " +"attribute value is selected." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:74 +msgid "" +"Pricelist formulas let you set advanced price computation methods for " +"product variants. See :doc:`../maximizing_revenue/pricing`." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:78 +msgid "How to disable/archive variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:80 +msgid "" +"You can disable/archive specific variants so that they are no longer " +"available in quotes & website (not existing in your stock, deprecated, " +"etc.). Simply uncheck *Active* in their detail form." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:86 +msgid "" +"To retrieve such archived items, hit *Archived* on searching the variants " +"list. You can reactivate them the same way." +msgstr "" + +#: ../../ecommerce/maximizing_revenue.rst:3 +msgid "Maximize my revenue" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:3 +msgid "How to sell accessories and optional products (cross-selling)" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:5 +msgid "" +"You sell computers. Why not stimulating your customers to buy a top-notch " +"screen or an extra-warranty? That's the goal of cross-selling " +"functionalities:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:8 +msgid "Accessory products on checkout page," +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:9 +msgid "" +"Optional products on a new *Add to Cart* screen (not installed by default)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:12 +msgid "Accessory products when checking out" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:14 +msgid "" +"Accessories (e.g. for computers: mouse, keyboard) show up when the customer " +"reviews the cart before paying." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:20 +msgid "Select accessories in the *Sales* tab of the product detail page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:26 +msgid "" +"There is an algorithm to figure out the best accessories to display in case " +"several items are added to cart. If any item is the accessory of several " +"products added to cart, it is most likely that it will be atop the list of " +"suggested accessories." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:31 +msgid "Optional products when adding to cart" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:33 +msgid "" +"Optional products are directly related to the item added to cart (e.g. for " +"computers: warranty, OS software, extra components). Whenever the main " +"product is added to cart, such a new screen pops up as an extra step." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:40 +msgid "To publish optional products:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:42 +msgid "" +"Install *eCommerce Optional Products* addon in *Apps* menu. Remove the " +"default filter to search on addons as well, otherwise only main apps show " +"up." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:48 +msgid "Select optional items from the *Sales* tab of the product detail form." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:54 +msgid "" +"The quantity of optional items added to cart is the same than the main item." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:3 +msgid "How to adapt the prices to my website visitors" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:5 +msgid "This section sheds some light on pricing features of eCommerce app:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:7 +msgid "force a price by geo-localization," +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:9 +msgid "let the customer choose the currency." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:11 +msgid "" +"As a pre-requisite, check out how to managing produt pricing: " +":doc:`../../sales/products_prices/prices/pricing`)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:15 +msgid "Geo-IP to automatically apply the right price" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:17 +msgid "" +"Assign country groups to your pricelists. That way, your visitors not yet " +"logged in will get their own currency when landing on your website." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:20 +msgid "Once logged in, they get the pricelist matching their country." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:23 +msgid "Currency selector" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:25 +msgid "" +"In case you sell in several currencies, you can let your customers choose " +"their own currency. Check *Selectable* to add the pricelist to the website " +"drop-down menu." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:34 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:35 +msgid ":doc:`../../sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:36 +msgid ":doc:`promo_code`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:3 +msgid "How to create & share promotional codes" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:5 +msgid "" +"Want to boost your sales for Xmas? Share promocodes through your marketing " +"campaigns and apply any kind of discounts." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:9 +#: ../../ecommerce/maximizing_revenue/reviews.rst:13 +msgid "Setup" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:11 +msgid "" +"Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based" +" on formula* for *Sale Price*." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:14 +msgid "" +"Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a" +" new pricelist with the discount rule (see :doc:`pricing`). Then enter a " +"code." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:21 +msgid "" +"Make the promocode field available on your *Shopping Cart* page (option in " +"*Customize* menu). Add a product to cart to reach it." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:27 +msgid "" +"Once turned on you see a new section on the right side. On clicking *Apply* " +"prices get automatically updated in the cart." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:33 +msgid "" +"The promocode used by the customer is stored in the system so you can " +"analyze the performance of your marketing campaigns." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:39 +msgid "Show sales per pricelists..." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:43 +msgid ":doc:`pricing`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:3 +msgid "How to enable comments & rating" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:5 +msgid "" +"Publishing and monitoring customer experience will help you gain the trust " +"of new customers and better engage with your community. In 2 clicks, allow " +"your customer to share their feedback!" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:15 +msgid "" +"Activate comments & rating from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:21 +msgid "" +"Visitors must log in to share their comments. Make sure they are able to do " +"so (see Portal documentation)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:25 +msgid "Review the posts in real time" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:27 +msgid "" +"Whenever a post is published, the product manager and all the product " +"followers get notified in their Inbox (*Discuss* menu)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:34 +msgid "" +"By default the user who created the product is automatically set as " +"follower." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:36 +msgid "" +"Click the product name to open the detail form and review the comment (in " +"the product discussion thread)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:43 +msgid "Moderate & unpublish" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:45 +msgid "" +"You can easily moderate by using the chatter, either in the product detail " +"form or on the web page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:48 +msgid "" +"To unpublish the post, open the product web page and click the *Published* " +"button to turn it red (*Unpublished*)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:56 +msgid "..tip::" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:55 +msgid "" +"You can access the web page from the detail form by clicking the *Published*" +" smart button (and vice versa)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:3 +msgid "How to sell pricier product alternatives (upselling)" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:5 +msgid "" +"In order to maximize your revenue, suggesting pricier alternative products " +"is strongly advised for basic items. That way, your customer will spend more" +" time browsing your catalog." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:12 +msgid "To do so:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:14 +msgid "" +"Select such *Alternative Products* in the *Sales* tab of the product detail " +"form. 3 alternatives are fine! Don't publish too many otherwise your " +"customers will be confused." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:20 +msgid "" +"Turn on *Alternative Products* from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../ecommerce/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:3 +msgid "Introduction to Odoo eCommerce" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your eCommerce website in no " +"time. The topics follow the buying process:" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:13 +msgid "Product Page" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:14 +msgid "Shop Page" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:15 +msgid "Pricing" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:16 +msgid "Taxes" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:17 +msgid "Checkout process" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:18 +msgid "Upselling & cross-selling" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:19 +msgid "Payment" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:20 +msgid "Shipping & Tracking" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:24 +msgid ":doc:`../../website/publish/domain_name`" +msgstr "" + +#: ../../ecommerce/publish.rst:3 +msgid "Launch my website" +msgstr "" + +#: ../../ecommerce/shopper_experience.rst:3 +msgid "Get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:3 +msgid "How to get paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:5 +msgid "" +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:10 +msgid "What are the payment methods available" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:13 +msgid "Wire transfer" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:15 +msgid "" +"Wire Transfer is the default payment method available. The aim is providing " +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:21 +msgid "Payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:27 +msgid "`Paypal `__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:33 +msgid "Sips" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:38 +msgid "How to go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:40 +msgid "" +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 +msgid "" +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:61 +msgid "How to debit credit cards to pay subscriptions" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:62 +msgid "" +"`Odoo Subscription `__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 +msgid "" +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 +msgid "" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:85 +msgid "How to:" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:87 +msgid "Switch to developer mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:89 +msgid "Take the **Custom** payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:91 +msgid "" +"Set up the payment form (S2S Form Template) as instructed by your payment " +"acquirer. You can start from *default_acquirer_button* that you can " +"duplicate." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:98 +msgid "" +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:102 +msgid "" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. `__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:109 +msgid ":doc:`paypal`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:3 +msgid "How to get paid with Paypal" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:5 +msgid "" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:11 +msgid "Set up your Paypal account" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:13 +msgid "" +"Create a `Paypal Business Account `__ or upgrade " +"your account to *Business account* if you have a basic account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "" +"Log in to `Paypal `__ and open the settings of your " +"**Profile**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:22 +msgid "Now enter the menu **My selling tools**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:29 +msgid "" +"Turn on **Auto Return** and enter the **Return URL**: " +"/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:36 +msgid "" +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:43 +msgid "" +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: /payment/paypal/ipn" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 +msgid "Transaction fees" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:114 +msgid "" +"You can charge an extra to the customer to cover the transaction fees Paypal" +" charges you. Once redirected to Paypal, your customer sees an extra applied" +" to the order amount." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:117 +msgid "" +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site `__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox `__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:3 +msgid "How customers can access their customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:5 +msgid "" +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:14 +msgid "Sign up" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:16 +msgid "" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 +msgid "" +"Once logged in the customer will access the account by clicking *My Account*" +" in the login dropdown menu." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:31 +msgid "" +"THere they find all their history. The main address (billing) can also be " +"modified." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:37 +msgid "" +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." +msgstr "" + +#: ../../ecommerce/taxes.rst:3 +msgid "Collect taxes" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/expenses.po b/locale/ru/LC_MESSAGES/expenses.po new file mode 100644 index 000000000..a82aae070 --- /dev/null +++ b/locale/ru/LC_MESSAGES/expenses.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2016-11-22 13:16+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../expenses.rst:5 +msgid "Expenses" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/general.po b/locale/ru/LC_MESSAGES/general.po new file mode 100644 index 000000000..3064b9f9e --- /dev/null +++ b/locale/ru/LC_MESSAGES/general.po @@ -0,0 +1,831 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../general.rst:5 +msgid "General" +msgstr "" + +#: ../../general/auth.rst:3 +msgid "Authentication" +msgstr "" + +#: ../../general/auth/google.rst:3 +msgid "How to allow users to sign in with their Google account" +msgstr "" + +#: ../../general/auth/google.rst:5 +msgid "" +"Connect to your Google account and go to " +"`https://console.developers.google.com/ " +"`_." +msgstr "" + +#: ../../general/auth/google.rst:7 +msgid "" +"Click on **Create Project** and enter the project name and other details." +msgstr "" + +#: ../../general/auth/google.rst:15 +msgid "Click on **Use Google APIs**" +msgstr "" + +#: ../../general/auth/google.rst:20 +msgid "" +"On the left side menu, select the sub menu **Credentials** (from **API " +"Manager**) then select **OAuth consent screen**." +msgstr "" + +#: ../../general/auth/google.rst:25 +msgid "" +"Fill in your address, email and the product name (for example odoo) and then" +" save." +msgstr "" + +#: ../../general/auth/google.rst:30 +msgid "" +"Then click on **Add Credentials** and select the second option (OAuth 2.0 " +"Client ID)." +msgstr "" + +#: ../../general/auth/google.rst:38 +msgid "" +"Check that the application type is set on **Web Application**. Now configure" +" the allowed pages on which you will be redirected." +msgstr "" + +#: ../../general/auth/google.rst:40 +msgid "" +"To achieve this, complete the field **Authorized redirect URIs**. Copy paste" +" the following link in the box: http://mydomain.odoo.com/auth_oauth/signin. " +"Then click on **Create**" +msgstr "" + +#: ../../general/auth/google.rst:48 +msgid "" +"Once done, you receive two information (your Client ID and Client Secret). " +"You have to insert your Client ID in the **General Settings**." +msgstr "" + +#: ../../general/base_import.rst:3 +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" + +#: ../../general/base_import/import_faq.rst:3 +msgid "How to import data into Odoo" +msgstr "" + +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "" + +#: ../../general/base_import/import_faq.rst:7 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." +msgstr "" + +#: ../../general/base_import/import_faq.rst:16 +msgid "" +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." +msgstr "" + +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" +msgstr "" + +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../general/base_import/import_faq.rst:25 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:31 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:81 +msgid "" +"Odoo can automatically detect if a column is a date and it will try to guess" +" the date format from a set of most used date format. While this process can" +" work for a lot of simple date format, some exotic date format will not be " +"recognize and it is also possible to have some confusion (day and month " +"inverted as example) as it is difficult to guess correctly which part is the" +" day and which one is the month in a date like '01-03-2016'." +msgstr "" + +#: ../../general/base_import/import_faq.rst:83 +msgid "" +"To view which date format Odoo has found from your file you can check the " +"**Date Format** that is shown when clicking on **Options** under the file " +"selector. If this format is incorrect you can change it to your liking using" +" the *ISO 8601* to define the format." +msgstr "" + +#: ../../general/base_import/import_faq.rst:86 +msgid "" +"If you are importing an excel (.xls, .xlsx) file, you can use date cells to " +"store dates as the display of dates in excel is different from the way it is" +" stored. That way you will be sure that the date format is correct in Odoo " +"whatever your locale date format is." +msgstr "" + +#: ../../general/base_import/import_faq.rst:91 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:93 +msgid "" +"Yes, we fully support numbers with parenthesis to represent negative sign as" +" well as numbers with currency sign attached to them. Odoo also " +"automatically detect which thousand/decimal separator you use (you can " +"change those under **options**). If you use a currency symbol that is not " +"known to Odoo, it might not be recognized as a number though and it will " +"crash." +msgstr "" + +#: ../../general/base_import/import_faq.rst:95 +msgid "" +"Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../general/base_import/import_faq.rst:97 +msgid "32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:98 +msgid "32000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:99 +msgid "32,000.00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:100 +msgid "-32000.00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:101 +msgid "(32000.00)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:102 +msgid "$ 32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:103 +msgid "(32000.00 €)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:105 +msgid "Example that will not work:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:107 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:108 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:113 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:115 +msgid "" +"By default the Import preview is set on commas as field separators and " +"quotation marks as text delimiters. If your csv file does not have these " +"settings, you can modify the File Format Options (displayed under the Browse" +" CSV file bar after you select your file)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:117 +msgid "" +"Note that if your CSV file has a tabulation as separator, Odoo will not " +"detect the separations. You will need to change the file format options in " +"your spreadsheet application. See the following question." +msgstr "" + +#: ../../general/base_import/import_faq.rst:122 +msgid "" +"How can I change the CSV file format options when saving in my spreadsheet " +"application?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:124 +msgid "" +"If you edit and save CSV files in speadsheet applications, your computer's " +"regional settings will be applied for the separator and delimiter. We " +"suggest you use OpenOffice or LibreOffice Calc as they will allow you to " +"modify all three options (in 'Save As' dialog box > Check the box 'Edit " +"filter settings' > Save)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:126 +msgid "" +"Microsoft Excel will allow you to modify only the encoding when saving (in " +"'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:131 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:133 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When you" +" want to import such fields, Odoo will have to recreate links between the " +"different records. To help you import such fields, Odoo provides 3 " +"mechanisms. You must use one and only one mechanism per field you want to " +"import." +msgstr "" + +#: ../../general/base_import/import_faq.rst:135 +msgid "" +"For example, to reference the country of a contact, Odoo proposes you 3 " +"different fields to import:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:137 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../general/base_import/import_faq.rst:138 +msgid "" +"Country/Database ID: the unique Odoo ID for a record, defined by the ID " +"postgresql column" +msgstr "" + +#: ../../general/base_import/import_faq.rst:139 +msgid "" +"Country/External ID: the ID of this record referenced in another application" +" (or the .XML file that imported it)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:141 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:143 +msgid "Country: Belgium" +msgstr "" + +#: ../../general/base_import/import_faq.rst:144 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../general/base_import/import_faq.rst:145 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../general/base_import/import_faq.rst:147 +msgid "" +"According to your need, you should use one of these 3 ways to reference " +"records in relations. Here is when you should use one or the other, " +"according to your need:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:149 +msgid "" +"Use Country: This is the easiest way when your data come from CSV files that" +" have been created manually." +msgstr "" + +#: ../../general/base_import/import_faq.rst:150 +msgid "" +"Use Country/Database ID: You should rarely use this notation. It's mostly " +"used by developers as it's main advantage is to never have conflicts (you " +"may have several records with the same name, but they always have a unique " +"Database ID)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:151 +msgid "" +"Use Country/External ID: Use External ID when you import data from a third " +"party application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:153 +msgid "" +"When you use External IDs, you can import CSV files with the \"External ID\"" +" column to define the External ID of each record you import. Then, you will " +"be able to make a reference to that record with columns like " +"\"Field/External ID\". The following two CSV files give you an example for " +"Products and their Categories." +msgstr "" + +#: ../../general/base_import/import_faq.rst:155 +msgid "" +"`CSV file for categories " +"<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:157 +msgid "" +"`CSV file for Products " +"<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:161 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:163 +msgid "" +"If for example you have two product categories with the child name " +"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " +"Products/Sellable\"), your validation is halted but you may still import " +"your data. However, we recommend you do not import the data because they " +"will all be linked to the first 'Sellable' category found in the Product " +"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of " +"the duplicates' values or your product category hierarchy." +msgstr "" + +#: ../../general/base_import/import_faq.rst:165 +msgid "" +"However if you do not wish to change your configuration of product " +"categories, we recommend you use make use of the external ID for this field " +"'Category'." +msgstr "" + +#: ../../general/base_import/import_faq.rst:170 +msgid "" +"How can I import a many2many relationship field (e.g. a customer that has " +"multiple tags)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:172 +msgid "" +"The tags should be separated by a comma without any spacing. For example, if" +" you want your customer to be linked to both tags 'Manufacturer' and " +"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column" +" of your CSV file." +msgstr "" + +#: ../../general/base_import/import_faq.rst:174 +msgid "" +"`CSV file for Manufacturer, Retailer " +"<../../_static/example_files/m2m_customers_tags.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:179 +msgid "" +"How can I import a one2many relationship (e.g. several Order Lines of a " +"Sales Order)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:181 +msgid "" +"If you want to import sales order having several order lines; for each order" +" line, you need to reserve a specific row in the CSV file. The first order " +"line will be imported on the same row as the information relative to order. " +"Any additional lines will need an addtional row that does not have any " +"information in the fields relative to the order. As an example, here is " +"purchase.order_functional_error_line_cant_adpat.CSV file of some quotations " +"you can import, based on demo data." +msgstr "" + +#: ../../general/base_import/import_faq.rst:184 +msgid "" +"`File for some Quotations " +"<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:186 +msgid "" +"The following CSV file shows how to import purchase orders with their " +"respective purchase order lines:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:188 +msgid "" +"`Purchase orders with their respective purchase order lines " +"<../../_static/example_files/o2m_purchase_order_lines.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:190 +msgid "" +"The following CSV file shows how to import customers and their respective " +"contacts:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:192 +msgid "" +"`Customers and their respective contacts " +"<../../_static/example_files/o2m_customers_contacts.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:197 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:199 +msgid "" +"If you import a file that contains one of the column \"External ID\" or " +"\"Database ID\", records that have already been imported will be modified " +"instead of being created. This is very usefull as it allows you to import " +"several times the same CSV file while having made some changes in between " +"two imports. Odoo will take care of creating or modifying each record " +"depending if it's new or not." +msgstr "" + +#: ../../general/base_import/import_faq.rst:201 +msgid "" +"This feature allows you to use the Import/Export tool of Odoo to modify a " +"batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:206 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:208 +msgid "" +"If you do not set all fields in your CSV file, Odoo will assign the default " +"value for every non defined fields. But if you set fields with empty values " +"in your CSV file, Odoo will set the EMPTY value in the field, instead of " +"assigning the default value." +msgstr "" + +#: ../../general/base_import/import_faq.rst:213 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:215 +msgid "" +"If you need to import data from different tables, you will have to recreate " +"relations between records belonging to different tables. (e.g. if you import" +" companies and persons, you will have to recreate the link between each " +"person and the company they work for)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:217 +msgid "" +"To manage relations between tables, you can use the \"External ID\" " +"facilities of Odoo. The \"External ID\" of a record is the unique identifier" +" of this record in another application. This \"External ID\" must be unique " +"accoss all the records of all objects, so it's a good practice to prefix " +"this \"External ID\" with the name of the application or table. (like " +"'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../general/base_import/import_faq.rst:219 +msgid "" +"As an example, suppose you have a SQL database with two tables you want to " +"import: companies and persons. Each person belong to one company, so you " +"will have to recreate the link between a person and the company he work for." +" (If you want to test this example, here is a dump of such a " +"PostgreSQL database)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:221 +msgid "" +"We will first export all companies and their \"External ID\". In PSQL, write" +" the following command:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:227 +msgid "This SQL command will create the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:234 +msgid "" +"To create the CSV file for persons, linked to companies, we will use the " +"following SQL command in PSQL:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:240 +msgid "It will produce the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:248 +msgid "" +"As you can see in this file, Fabien and Laurence are working for the Bigees " +"company (company_1) and Eric is working for the Organi company. The relation" +" between persons and companies is done using the External ID of the " +"companies. We had to prefix the \"External ID\" by the name of the table to " +"avoid a conflict of ID between persons and companies (person_1 and company_1" +" who shared the same ID 1 in the orignial database)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:250 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two CSV files, you will have 4 " +"contacts and 3 companies. (the firsts two contacts are linked to the first " +"company). You must first import the companies and then the persons." +msgstr "" + +#: ../../general/odoo_basics.rst:3 +msgid "BASICS" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:3 +msgid "How to add a user" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:5 +msgid "" +"Odoo provides you with the option to add additional users at any given " +"point." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:9 +msgid "Add individual users" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:11 +msgid "" +"From the Settings module, go to the submenu :menuselection:`Users --> Users`" +" and click on **CREATE.** First add the name of your new user and the " +"professional email address - the one he will use to log into Odoo instance -" +" and a picture." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:19 +msgid "" +"Under Access Rights, you can choose which applications your user can access " +"and use. Different levels of rights are available depending on the app." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:23 +msgid "" +"When you’re done editing the page and have clicked on **SAVE**, an " +"invitation email will automatically be sent to the user. The user must click" +" on it to accept the invitation to your instance and create a log-in." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:32 +msgid "" +"Remember that each additional user will increase your subscription fees. " +"Refer to our `*Pricing page* `__ for more " +"information." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:39 +msgid "" +"You can also add a new user on the fly from your dashboard. From the above " +"screenshot, enter the email address of the user you would like to add and " +"click on **INVITE**. The user will receive an email invite containing a link" +" to set his password. You will then be able to define his accesses rights " +"under the :menuselection:`Settings --> Users menu`." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:45 +msgid "" +"`Deactivating Users <../../db_management/documentation.html#deactivating-" +"users>`_" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:46 +msgid ":doc:`../../crm/salesteam/setup/create_team`" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:3 +msgid "Manage Odoo in your own language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:5 +msgid "" +"Odoo provides you with the option to manage Odoo in different languages, and" +" each user can use Odoo in his own language ." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:9 +msgid "Load your desired language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:11 +msgid "" +"The first thing to do is to load your desired language on your Odoo " +"instance." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:14 +msgid "" +"From the general dashboard click on the **Settings** app; on the top left of" +" the page select :menuselection:`Translations --> Load a Translation`, " +"select a language to install and click on **LOAD.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:23 +msgid "" +"If you check the \"Websites to translate\" checkbox you will have the option" +" to change the navigation language on your website." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:27 +msgid "Change your language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:29 +msgid "" +"You can change the language to the installed language by going to the drop-" +"down menu at the top right side of the screen, choose **Preferences**." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:36 +msgid "" +"Then change the Language setting to your installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:42 +msgid "Open a new menu to view the changes." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:45 +msgid "Change another user's language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:47 +msgid "" +"Odoo also gives you the possibility for each user to choose his preferred " +"language." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:50 +msgid "" +"To change the language for a different user, choose :menuselection:`Users " +"--> Users` from the Settings app. Here you have a list of all users and you " +"can choose the user who you'd like to change the language for. Select the " +"user and click on **Edit** in the top left corner. Under Preferences you can" +" change the Language to any previously installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:61 +msgid ":doc:`../../website/publish/translate`" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/getting_started.po b/locale/ru/LC_MESSAGES/getting_started.po new file mode 100644 index 000000000..39c75eafc --- /dev/null +++ b/locale/ru/LC_MESSAGES/getting_started.po @@ -0,0 +1,635 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../getting_started/documentation.rst:5 +msgid "Odoo Online Implementation" +msgstr "" + +#: ../../getting_started/documentation.rst:7 +msgid "" +"This document summarizes **Odoo's Online services**, our Success Pack " +"**implementation methodology**, and *best practices* to **get started** with" +" our product." +msgstr "" + +#: ../../getting_started/documentation.rst:11 +msgid "" +"*We recommend that new Odoo Online customers read this document before the " +"kick-off call with our project manager. This way, we save time and don't " +"have to use your hours from the success pack discussing the basics.*" +msgstr "" + +#: ../../getting_started/documentation.rst:16 +msgid "" +"*If you have not read this document, our project manager will review this " +"with you at the time of the kick-off call.*" +msgstr "" + +#: ../../getting_started/documentation.rst:20 +msgid "Getting Started" +msgstr "" + +#: ../../getting_started/documentation.rst:22 +msgid "" +"Do not wait for the kick-off meeting to begin playing with the software. The" +" more exposure you have with Odoo, the more time you will save later during " +"the implementation." +msgstr "" + +#: ../../getting_started/documentation.rst:26 +msgid "" +"Once you purchase an Odoo Online subscription, you will receive instructions" +" by e-mail on how to activate or create your database. From this email, you " +"can activate your existing Odoo database or create a new one from scratch." +msgstr "" + +#: ../../getting_started/documentation.rst:31 +msgid "" +"If you did not receive this email, e.g. because the payment was made by " +"someone else in your company, contact our support using our `online support " +"form `__." +msgstr "" + +#: ../../getting_started/documentation.rst:38 +msgid "" +"Fill in the sign-in or sign-up screens and you will get your first Odoo " +"database ready to be used." +msgstr "" + +#: ../../getting_started/documentation.rst:41 +msgid "" +"In order to familiarize yourself with the user interface, take a few minutes" +" to create records: *products, customers, opportunities or projects / " +"tasks*. Follow the blinking dots, they give you tips about the user " +"interface as shown in the picture below." +msgstr "" + +#: ../../getting_started/documentation.rst:47 +msgid "|left_pic|" +msgstr "" + +#: ../../getting_started/documentation.rst:47 +msgid "|right_pic|" +msgstr "" + +#: ../../getting_started/documentation.rst:50 +msgid "" +"Once you get used to the user interface, have a look at the implementation " +"planners. These are accessible from the Settings app, or from the top " +"progress bar on the right hand side of the main applications." +msgstr "" + +#: ../../getting_started/documentation.rst:58 +msgid "These implementation planners will:" +msgstr "" + +#: ../../getting_started/documentation.rst:60 +msgid "help you define your goals and KPIs for each application," +msgstr "" + +#: ../../getting_started/documentation.rst:62 +msgid "guide you through the different configuration steps," +msgstr "" + +#: ../../getting_started/documentation.rst:64 +msgid "and provide you with tips and tricks to getting the most out of Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:66 +msgid "" +"Fill in the first steps of the implementation planner (goals, expectations " +"and KPIs). Our project manager will review them with you during the " +"implementation process." +msgstr "" + +#: ../../getting_started/documentation.rst:73 +msgid "" +"If you have questions or need support, our project manager will guide you " +"through all the steps. But you can also:" +msgstr "" + +#: ../../getting_started/documentation.rst:76 +msgid "" +"Read the documentation on our website: " +"`https://www.odoo.com/documentation/user " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:79 +msgid "" +"Watch the videos on our eLearning platform (Free with your first Success " +"Pack): `https://odoo.thinkific.com/courses/odoo-functional " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:82 +msgid "" +"Watch the webinars on our `Youtube channel " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:85 +msgid "" +"Or send your questions to our online support through our `online support " +"form `__." +msgstr "" + +#: ../../getting_started/documentation.rst:89 +msgid "What do we expect from you?" +msgstr "" + +#: ../../getting_started/documentation.rst:91 +msgid "" +"We are used to deploying fully featured projects within 25 to 250 hours of " +"services, which is much faster than any other ERP vendor on the market. Most" +" projects are completed between 1 to 9 calendar months." +msgstr "" + +#: ../../getting_started/documentation.rst:95 +msgid "" +"But what really **differentiates between a successful implementation and a " +"slow one, is you, the customer!** From our experience, when our customer is " +"engaged and proactive the implementation is smooth." +msgstr "" + +#: ../../getting_started/documentation.rst:100 +msgid "Your internal implementation manager" +msgstr "" + +#: ../../getting_started/documentation.rst:102 +msgid "" +"We ask that you maintain a single point of contact within your company to " +"work with our project manager on your Odoo Implementation. This is to ensure" +" efficiency and a single knowledge base in your company. Additionally, this " +"person must:" +msgstr "" + +#: ../../getting_started/documentation.rst:107 +msgid "" +"**be available at least 2 full days a week** for the project, otherwise you " +"risk slowing down your implementation. More is better with the fastest " +"implementations having a full time project manager." +msgstr "" + +#: ../../getting_started/documentation.rst:111 +msgid "" +"**have authority to take decisions** on their own. Odoo usually transforms " +"all departments within a company for the better. There can be many small " +"details that need quick turn arounds for answers and if there is too much " +"back and forth between several internal decision makers within your company " +"it could potentially seriously slow everything down." +msgstr "" + +#: ../../getting_started/documentation.rst:117 +msgid "" +"**have the leadership** to train and enforce policies internally with full " +"support from all departments and top management, or be part of top " +"management." +msgstr "" + +#: ../../getting_started/documentation.rst:121 +msgid "Integrate 90% of your business, not 100%" +msgstr "" + +#: ../../getting_started/documentation.rst:123 +msgid "" +"You probably chose Odoo because no other software allows for such a high " +"level of automation, feature coverage, and integration. But **don't be an " +"extremist.**" +msgstr "" + +#: ../../getting_started/documentation.rst:127 +msgid "" +"Customizations cost you time, money, are more complex to maintain, add risks" +" to the implementation, and can cause issues with upgrades." +msgstr "" + +#: ../../getting_started/documentation.rst:130 +msgid "" +"Standard Odoo can probably cover 90% of your business processes and " +"requirements. Be flexible on the remaining 10%, otherwise that 10% will cost" +" you twice the original project price. One always underestimates the hidden " +"costs of customization." +msgstr "" + +#: ../../getting_started/documentation.rst:134 +msgid "" +"**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was " +"designed. Learn how it works and don't try to replicate the way your old " +"system(s) works." +msgstr "" + +#: ../../getting_started/documentation.rst:138 +msgid "" +"**The project first, customizations second.** If you really want to " +"customize Odoo, phase it towards the end of the project, ideally after " +"having been in production for several months. Once a customer starts using " +"Odoo, they usually drop about 60% of their customization requests as they " +"learn to perform their work flows out of the box, or the Odoo way. It is " +"more important to have all your business processes working than customizing " +"a screen to add a few fields here and there or automating a few e-mails." +msgstr "" + +#: ../../getting_started/documentation.rst:147 +msgid "" +"Our project managers are trained to help you make the right decisions and " +"measure the tradeoffs involved but it is much easier if you are aligned with" +" them on the objectives. Some processes may take more time than your " +"previous system(s), however you need to weigh that increase in time with " +"other decreases in time for other processes. If the net time spent is " +"decreased with your move to Odoo than you are already ahead." +msgstr "" + +#: ../../getting_started/documentation.rst:155 +msgid "Invest time in learning Odoo" +msgstr "" + +#: ../../getting_started/documentation.rst:157 +msgid "" +"Start your free trial and play with the system. The more comfortable you are" +" with navigating Odoo, the better your decisions will be and the quicker and" +" easier your training phases will be." +msgstr "" + +#: ../../getting_started/documentation.rst:161 +msgid "" +"Nothing replaces playing with the software, but here are some extra " +"resources:" +msgstr "" + +#: ../../getting_started/documentation.rst:164 +msgid "" +"Documentation: `https://www.odoo.com/documentation/user " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:167 +msgid "" +"Introduction Videos: `https://www.odoo.com/r/videos " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:170 +msgid "" +"Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:174 +msgid "Get things done" +msgstr "" + +#: ../../getting_started/documentation.rst:176 +msgid "" +"Want an easy way to start using Odoo? Install Odoo Notes to manage your to-" +"do list for the implementation: `https://www.odoo.com/page/notes " +"`__. From your Odoo home, go to Apps and " +"install the Notes application." +msgstr "" + +#: ../../getting_started/documentation.rst:184 +msgid "This module allows you to:" +msgstr "" + +#: ../../getting_started/documentation.rst:186 +msgid "Manage to-do lists for better interactions with your consultant;" +msgstr "" + +#: ../../getting_started/documentation.rst:188 +msgid "Share Odoo knowledge & good practices with your employees;" +msgstr "" + +#: ../../getting_started/documentation.rst:190 +msgid "" +"Get acquainted with all the generic tools of Odoo: Messaging, Discussion " +"Groups, Kanban Dashboard, etc." +msgstr "" + +#: ../../getting_started/documentation.rst:197 +msgid "" +"This application is even compatible with the Etherpad platform " +"(http://etherpad.org). To use these collaborative pads rather than standard " +"Odoo Notes, install the following add-on: Memos Pad." +msgstr "" + +#: ../../getting_started/documentation.rst:202 +msgid "What should you expect from us?" +msgstr "" + +#: ../../getting_started/documentation.rst:205 +msgid "Subscription Services" +msgstr "" + +#: ../../getting_started/documentation.rst:208 +msgid "Cloud Hosting" +msgstr "" + +#: ../../getting_started/documentation.rst:210 +msgid "" +"Odoo provides a top notch cloud infrastructure including backups in three " +"different data centers, database replication, the ability to duplicate your " +"instance in 10 minutes, and more!" +msgstr "" + +#: ../../getting_started/documentation.rst:214 +msgid "" +"Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla " +"`__\\" +msgstr "" + +#: ../../getting_started/documentation.rst:217 +msgid "" +"Odoo Online Security: `https://www.odoo.com/page/security " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:220 +msgid "" +"Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy " +"`__" +msgstr "" + +#: ../../getting_started/documentation.rst:224 +msgid "Support" +msgstr "" + +#: ../../getting_started/documentation.rst:226 +msgid "" +"Your Odoo Online subscription includes an **unlimited support service at no " +"extra cost, 24/5, Monday to Friday**. To cover 24 hours, our teams are in " +"San Francisco, Belgium and India. Questions could be about anything and " +"everything from: how to use or configure, bugfix requests, payments or " +"subscription issues." +msgstr "" + +#: ../../getting_started/documentation.rst:232 +msgid "" +"Our support can be contacted through our `online support form " +"`__." +msgstr "" + +#: ../../getting_started/documentation.rst:235 +msgid "" +"Note: The support team cannot develop new features, customize, import data " +"or train your users. These services are provided by your dedicated project " +"manager, as part of the Success Pack." +msgstr "" + +#: ../../getting_started/documentation.rst:240 +msgid "Upgrades" +msgstr "" + +#: ../../getting_started/documentation.rst:242 +msgid "" +"Once every two months, Odoo releases a new version. You will get an upgrade " +"button within the **Manage Your Databases** screen. Upgrading your database " +"is at your own discretion, but allows you to benefit from new features." +msgstr "" + +#: ../../getting_started/documentation.rst:247 +msgid "" +"We provide the option to upgrade in a test environment so that you can " +"evaluate a new version or train your team before the roll out. Simply fill " +"our `online support form `__ to make this " +"request." +msgstr "" + +#: ../../getting_started/documentation.rst:252 +msgid "Success Pack Services" +msgstr "" + +#: ../../getting_started/documentation.rst:254 +msgid "" +"The Success Pack is a package of premium hour-based services performed by a " +"dedicated project manager and business analyst. The list of services " +"according to your success pack is detailed online: `https://www.odoo.com" +"/pricing-packs `__" +msgstr "" + +#: ../../getting_started/documentation.rst:259 +msgid "" +"The goal of the project manager is to help you get to production within the " +"defined time frame and budget, i.e. the initial number of hours defined in " +"your success pack." +msgstr "" + +#: ../../getting_started/documentation.rst:263 +msgid "His/her role includes:" +msgstr "" + +#: ../../getting_started/documentation.rst:265 +msgid "" +"**Project Management:** review of your objectives & expectations, phasing of" +" the implementation (road map), mapping of your business needs and the Odoo " +"features." +msgstr "" + +#: ../../getting_started/documentation.rst:269 +msgid "**Customized Support:** by phone, e-mail or webinar." +msgstr "" + +#: ../../getting_started/documentation.rst:271 +msgid "" +"**Training, Coaching, and Onsite Consulting:** remote trainings via screen " +"sharing or training on premises. For on premise training sessions, you will " +"be expected to pay extra for travel expenses and accommodations for your " +"consultant." +msgstr "" + +#: ../../getting_started/documentation.rst:276 +msgid "" +"**Configuration:** decisions about how to implement specific needs in Odoo " +"and advanced configuration. (e.g. logistic routes, advanced pricing " +"structures, etc.)" +msgstr "" + +#: ../../getting_started/documentation.rst:280 +msgid "" +"**Data Import**: we can do it or assist you on how to do it with a template " +"prepared by the project manager." +msgstr "" + +#: ../../getting_started/documentation.rst:283 +msgid "" +"If you have subscribed to a **Custom App**, you benefit from following extra" +" services:" +msgstr "" + +#: ../../getting_started/documentation.rst:286 +msgid "**Customization of screens**" +msgstr "" + +#: ../../getting_started/documentation.rst:288 +msgid "" +"**Customization of reports (PDF):** our project managers have access to " +"developers for advanced customizations." +msgstr "" + +#: ../../getting_started/documentation.rst:291 +msgid "" +"**Website Design:** standard themes are provided to get started at no extra " +"cost. However, our project manager can coach you on how to utilize the " +"building blocks of the website designer. The time spent will consume hours " +"of your success pack." +msgstr "" + +#: ../../getting_started/documentation.rst:296 +msgid "" +"**Workflow automations:** e.g. setting values in fields based on triggers, " +"sending reminders by emails, automating actions, etc. For very advanced " +"automations, our project managers have access to Odoo developers." +msgstr "" + +#: ../../getting_started/documentation.rst:302 +msgid "Implementation Methodology" +msgstr "" + +#: ../../getting_started/documentation.rst:304 +msgid "" +"We follow a **lean and hands-on methodology**, that is used to put customers" +" in production in a short period of time and at a low cost." +msgstr "" + +#: ../../getting_started/documentation.rst:307 +msgid "" +"After the kick-off meeting, we define a phasing plan to deploy Odoo " +"progressively, by groups of apps." +msgstr "" + +#: ../../getting_started/documentation.rst:313 +msgid "" +"The goal of the **Kick-off call** is for our project manager to come to an " +"understanding of your business in order to propose an implementation plan " +"(phasing). Each phase is the deployment of a set applications that you will " +"fully use in production at the end of the phase." +msgstr "" + +#: ../../getting_started/documentation.rst:319 +msgid "For every phase, the steps are the following:" +msgstr "" + +#: ../../getting_started/documentation.rst:321 +msgid "" +"**On Boarding:** Odoo's project manager will review Odoo's business flows " +"with you, according to your business. The goal is to train you, validate the" +" business process and configure according to your specific needs." +msgstr "" + +#: ../../getting_started/documentation.rst:326 +msgid "" +"**Data:** created manually or imported from your existing system. You are " +"responsible to export the data from your existing system and Odoo's project " +"manager will import them in Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:330 +msgid "" +"**Training:** once your applications are set up, your data imported, and the" +" system is working smoothly, you will train your users. There will be some " +"back and forth with your Odoo project manager to answer questions and " +"process your feedback." +msgstr "" + +#: ../../getting_started/documentation.rst:335 +msgid "**Production**: Once everyone is trained, your users start using Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:338 +msgid "" +"Once you are comfortable using Odoo, we will fine-tune the process and " +"**automate** some tasks and do the remaining customizations (**extra screens" +" and reports**)." +msgstr "" + +#: ../../getting_started/documentation.rst:342 +msgid "" +"Once all applications are deployed and users are comfortable on Odoo, our " +"project manager will not work on your project anymore (unless you have new " +"needs) and you will use the support service if you have further questions." +msgstr "" + +#: ../../getting_started/documentation.rst:348 +msgid "Managing your databases" +msgstr "" + +#: ../../getting_started/documentation.rst:350 +msgid "" +"To access your databases, go to Odoo.com, sign in and click **My Databases**" +" in the drop-down menu at the top right corner." +msgstr "" + +#: ../../getting_started/documentation.rst:356 +msgid "" +"Odoo gives you the opportunity to test the system before going live or " +"before upgrading to a newer version. Do not mess up your working environment" +" with test data!" +msgstr "" + +#: ../../getting_started/documentation.rst:360 +msgid "" +"In that purpose, you can create as many free trials as you want (available " +"for 15 days). Those instances can be instant copies of your working " +"environment. To do so, go to the Odoo.com account in **My Organizations** " +"page and click **Duplicate**." +msgstr "" + +#: ../../getting_started/documentation.rst:371 +msgid "" +"You can find more information on how to manage your databases :ref:`here " +"`." +msgstr "" + +#: ../../getting_started/documentation.rst:375 +msgid "Customer Success" +msgstr "" + +#: ../../getting_started/documentation.rst:377 +msgid "" +"Odoo is passionate about delighting our customers and ensuring that they " +"have all the resources needed to complete their project." +msgstr "" + +#: ../../getting_started/documentation.rst:380 +msgid "" +"During the implementation phase, your point of contact is the project " +"manager and eventually the support team." +msgstr "" + +#: ../../getting_started/documentation.rst:383 +msgid "" +"Once you are in production, you will probably have less interaction with " +"your project manager. At that time, we will assign a member of our Client " +"Success Team to you. They are specialized in the long-term relationship with" +" our customers. They will contact you to showcase new versions, improve the " +"way you work with Odoo, assess your new needs, etc..." +msgstr "" + +#: ../../getting_started/documentation.rst:390 +msgid "" +"Our internal goal is to keep customers for at least 10 years and offer them " +"a solution that grows with their needs!" +msgstr "" + +#: ../../getting_started/documentation.rst:393 +msgid "Welcome aboard and enjoy your Odoo experience!" +msgstr "" + +#: ../../getting_started/documentation.rst:396 +msgid ":doc:`../../db_management/documentation`" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/index.po b/locale/ru/LC_MESSAGES/index.po new file mode 100644 index 000000000..67da72a33 --- /dev/null +++ b/locale/ru/LC_MESSAGES/index.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../index.rst:3 +msgid "Odoo User Documentation" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/inventory.po b/locale/ru/LC_MESSAGES/inventory.po new file mode 100644 index 000000000..347e04917 --- /dev/null +++ b/locale/ru/LC_MESSAGES/inventory.po @@ -0,0 +1,7665 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../inventory.rst:5 ../../inventory/overview/concepts/double-entry.rst:64 +msgid "Inventory" +msgstr "" + +#: ../../inventory/barcode.rst:3 +msgid "Barcodes" +msgstr "" + +#: ../../inventory/barcode/operations.rst:3 +msgid "Daily Operations" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:3 +msgid "How to do an inventory adjustment with barcodes?" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:5 +msgid "From the Barcode application:" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:7 +msgid "Click on **Inventory**" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:12 +msgid "" +"Scan all the products (if you have 5 identical articles, scan it 5 times, or" +" use the keyboard to set the quantity)." +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:16 +msgid "" +"If you manage multiple locations, scan the location before scanning the " +"products. Eg. scan a shelf's barcode ; scan each product on the shelf ; " +"repeat for each shelf in the wharehouse." +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:20 +msgid "" +"When you've scanned all the items of the location, validate the inventory " +"manually or by scanning the **Validate** barcode." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:3 +msgid "How to process delivery orders?" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:5 +msgid "" +"There are two approaches to process delivery orders: you can either work on " +"printed documents (and scan lines on the documents), or on a screen (and " +"scan products directly)." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:10 +msgid "Process printed delivery orders:" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:12 +msgid "" +"Print delivery orders of the day by selecting all documents from the **To " +"Do** list and print **Picking Operations** from the top menu." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:15 +msgid "" +"Once you start processing your delivery orders, **scan the barcode** on the " +"top-right corner of the document to load the right record on the screen." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:19 +msgid "" +"Then, **scan the barcode** of every product, or scan the barcode of the " +"product on the picking line if the barcode on the product is not easily " +"accessible, visible or is missing." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:23 +#: ../../inventory/barcode/operations/receipts.rst:24 +msgid "" +"Once you scanned all products, scan the **Validate** barcode action to " +"finish the operation." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:30 +msgid "Process delivery orders from a computer or mobile device:" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:32 +msgid "" +"Load all the delivery orders marked as **To Do**, and open the first one." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:35 +#: ../../inventory/barcode/operations/receipts.rst:33 +msgid "Pick up and scan each listed product." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:37 +msgid "" +"When you've picked all the items, click the **Validate** button or scan the " +"**Validate barcode** action to finish the Operation." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:40 +msgid "" +"Move to the next delivery order to process by clicking on the top-right " +"right **arrow** or scanning the **Pager-Next** barcode action." +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:3 +msgid "How to do an internal transfer?" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:5 +msgid "In Odoo, there are two types of internal transfers:" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:7 +msgid "" +"Those initiated automatically by the system (for example, a quality control)" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:10 +msgid "" +"Those created by a worker (for example, through the internal transfer area " +"of the dashboard)." +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:13 +msgid "To make an Internal Transfer:" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:15 +msgid "From the home of the barcode application, scan the **source location**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:17 +msgid "Pick up and **scan the products**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:19 +msgid "Scan the **destination location**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:21 +msgid "**Validate** the transfer to finish it" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:3 +msgid "How to handle lots and serial numbers with barcodes?" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:5 +msgid "" +"Lots Numbers can be encoded from incoming shipments, internal moves and " +"outgoing deliveries:" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:8 +msgid "" +"In the barcode interface, **scan** the products you want create a lot from" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:10 +msgid "" +"If this product should be manage by lots, a window opens to help you scan " +"the lots/serial numbers" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:13 +msgid "" +"**Scan** a lot barcode, **type** one manually or **leave empty** to generate" +" one automatically" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:16 +msgid "Click or scan **Validate** once you are done" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:18 +msgid "What is the difference between **Lots** and **Serial Numbers**?" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:20 +msgid "" +"**Lot** numbers are attributed to several identical products, so each time " +"you scan a lot number, Odoo will add one on the product count." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:24 +msgid "" +"On the opposite, a **serial number** is unique, and represented by only one " +"barcode, sticked on only one item. This means that Odoo won't accept " +"scanning the same serial number more than once per operation." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:32 +msgid "Here, we configured **Lu - Petit Beukelaer** tracking by lots." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:37 +msgid "" +"Scan a product from this incoming shipment, then scan the lot number of each" +" product (you can also use the keyboard)." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:43 +msgid "Click save/scan **Validate** and you are done." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:3 +msgid "How to process incoming receipts?" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:5 +msgid "" +"There are two approaches to process incoming receipts: you can either work " +"on printed documents (and scan lines on the documents), or on a screen (and " +"scan products directly)." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:10 +msgid "Process printed incoming receipts:" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:12 +msgid "" +"Print incoming receipts of the day by selecting all documents from the **To " +"Receive** list and print **Picking Operations** from the top menu." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:16 +msgid "" +"Once you start processing your incoming receipts, scan the barcode on the " +"top-right corner of the document to load the right record on the screen." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:20 +msgid "" +"Then, scan the barcode of every product, or scan the barcode of the product " +"on the picking line if the barcode on the product is not easily accessible, " +"visible or is missing." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:28 +msgid "Process incoming receipts from a computer or mobile device:" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:30 +msgid "" +"Load all the incoming receipts marked as **To Receive**, and open the first " +"one." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:35 +msgid "" +"When you've picked all the items, click the **Validate** button or scan the " +"**Validate** barcode action to finish the Operation." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:38 +msgid "" +"Move to the next incoming receipt to process by clicking on the top-right " +"right **arrow** or scanning the **Pager-Next** barcode action." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:42 +#: ../../inventory/management/delivery/scheduled_dates.rst:137 +msgid "Example" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:44 +msgid "Open operation interface." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:49 +msgid "Scan." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:54 +msgid "" +"The picking appears. Scan items and/or fill in informations using the mouse " +"and keyboard." +msgstr "" + +#: ../../inventory/barcode/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:3 +msgid "Set up your barcode scanner" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:5 +msgid "" +"Getting started with barcode scanning in Odoo is fairly easy. Yet, a good " +"user experience relies on an appropriate hardware setup. This guide will " +"help you through the task of choosing and configuring the barcode scanner." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:11 +msgid "Find the barcode scanner that suits your needs" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:13 +msgid "" +"The 3 recommended type of barcode scanners to work with the Odoo " +"**Inventory** and **Barcode Scanning** apps are the **USB scanner**, **the " +"bluetooth scanner** and the **mobile computer scanner**." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:20 +msgid "" +"If you scan products at a computer location, the **USB scanner** is the way " +"to go. Simply plug it in the computer to start scanning. Just make sure when" +" you buy it that the scanner is compatible with your keyboard layout or can " +"be configured to be so." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:25 +msgid "" +"The **bluetooth scanner** can be paired with a smartphone or a tablet and is" +" a good choice if you want to be mobile but don't need a big investment. An " +"approach is to log in Odoo on you smartphone, pair the bluetooth scanner " +"with the smartphone and work in the warehouse with always the possibility to" +" check your smartphone from time to time and use the software 'manually'." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:32 +msgid "" +"For heavy use, the **mobile computer scanner** is the handiest solution. It " +"consists in a small computer with a built-in barcode scanner. This one can " +"turn out to be a very productive solution, however you need to make sure " +"that is is capable of running Odoo smoothy. The most recent models using " +"Android + Google Chrome or Windows + Internet Explorer Mobile should do the " +"job. However, due to the variety of models and configurations on the market," +" it is essential to test it first." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:42 +msgid "Configure your barcode scanner" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:45 +msgid "Keyboard layout" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:50 +msgid "" +"An USB barcode scanner needs to be configured to use the same keyboard " +"layout as your operating system. Otherwise, your scanner won't translate " +"characters correctly (replacing a 'A' with a 'Q' for example). Most scanners" +" are configured by scanning the appropriate barcode in the user manual." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:57 +msgid "Automatic carriage return" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:59 +msgid "" +"By default, Odoo has a 50 milliseconds delay between each successive scan " +"(it helps avoid accidental double scanning). If you want to suppress this " +"delay, you can configure your scanner to insert a carriage return at the end" +" of each barcode. This is usually the default configuration and can be " +"explicitly configured by scanning a specific barcode in the user manual ('CR" +" suffix ON', 'Apply Enter for suffix', etc.)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:3 +msgid "How to activate the barcodes in Odoo?" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:5 +msgid "" +"The barcode scanning features can save you a lot of the time usually lost " +"switching between the keyboard, the mouse and the scanner. Properly " +"attributing barcodes to products, pickings locations, etc. allows you to " +"work more efficiently by controlling the software almost exclusively with " +"the barcode scanner." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:17 +msgid "" +"Print this document to be able to use your barcode scanner to perform more " +"actions." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:19 +msgid ":ref:`Document:` |download_barcode|" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:23 +msgid "Set products barcodes" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:28 +msgid "" +"In order to fill a picking or to perform an inventory, you need to make sure" +" that your products are encoded in Odoo along with their barcodes. If this " +"is not already done, you can fill in the products barcodes through a handy " +"interface. Go to :menuselection:`Inventory --> Configuration --> Settings` " +"and click the **Configure Product Barcodes** button. This interface can also" +" be accessed via the planner." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:37 +msgid "" +"Product variants: be careful to add barcodes directly on the variant, and " +"not the template product (otherwise you won't be able to differentiate " +"them)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:42 +msgid "Set locations barcodes" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:47 +msgid "" +"If you manage multiple locations, you will find useful to attribute a " +"barcode to each location and stick it on the location. You can configure the" +" locations barcodes in :menuselection:`Inventory --> Configuration --> " +"Warehouse Management --> Locations`. There is button in the **Print** menu " +"that you can use to print the locations names and barcodes. There are 4 " +"barcodes per page, arranged in a way that is convenient to print on sticker " +"paper." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:56 +msgid "" +"Example of location naming: **warehouse short name** - **location short " +"name** - (**Corridor X** - **Shelf Y** - **Height Z**) Example: A032-025-133" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:63 +msgid "Barcode formats" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:65 +msgid "" +"Most retail products use EAN-13 barcodes. They cannot be made up without " +"proper authorization: you must pay the International Article Numbering " +"Association a fee in exchange for an EAN code sequence (that's why no two " +"products in a store will ever have the same EAN code)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:70 +msgid "" +"Still, as Odoo supports any string as a barcode, so you can always define " +"your own barcode format for internal use." +msgstr "" + +#: ../../inventory/management.rst:3 +msgid "Warehouse Management" +msgstr "" + +#: ../../inventory/management/adjustment.rst:3 +msgid "Inventory Adjustment" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:3 +msgid "How to make the initial inventory?" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:5 +msgid "" +"One of the most important feature in an warehouse management software is to " +"keep the inventory right." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:8 +msgid "" +"Once your products have been defined, it is time to make your initial " +"inventory. You will reflect reality by inventorying the right quantities in " +"the right locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:13 +#: ../../inventory/management/lots_serial_numbers/lots.rst:55 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:34 +msgid "Product Configuration" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:15 +msgid "" +"In the Inventory module, open the :menuselection:`Inventory Control --> " +"Products`, then click on **Create** to create a new product. Configure the " +"product type so that it is **Stockable** and not a consumable." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:23 +msgid "Start the initial inventory" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:26 +msgid "Update the product quantity for one product" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:28 +msgid "" +"In the product you just created, you can see in the upper tiles that we have" +" 0 product On Hand. Click on the **Update qty on Hand** button." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:31 +msgid "" +"A new window opens. In the **New Quantity on Hand** field, type the quantity" +" of product you currently hold in stock, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:39 +msgid "" +"if you are using multiple locations for your warehouse, you will be able to " +"set the location of your product from this screen." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:42 +msgid "" +"You can now see from the On Hand tab that the quantity has been updated." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:47 +msgid "" +"Now, if you check the **Inventory Adjustments** in the **Inventory Control**" +" menu, you will see that a new line named \"INV: (name of your product)\" " +"has automatically been created and validated by the system." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:55 +msgid "Multiple products at once" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:57 +msgid "" +"Create all the products for which you want to follow the stock (as stockable" +" products). Once the required products in stock have been defined, use an " +"initial inventory operation to put the current quantities into the system by" +" location. Go to :menuselection:`Inventory Control --> Inventory " +"Adjustments` to start your initial inventory." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:63 +msgid "" +"Give it a name (for example Initial Inventory) and select the stock location" +" of your inventory. Note that when you select a parent location (such as " +"Stock, which might be split into sub locations), you can also select the sub" +" (or child) locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:71 +msgid "" +"You can choose between making an inventory for all products, for a few or " +"only for one. In this case, we choose the **All products** option." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:79 +msgid "" +"If you need your stock valuation to be done in a different period than the " +"one that will be selected by default according to the inventory end date, " +"enter the corresponding accounting period in the Force Valuation Period " +"field. The accounting module needs to be installed." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:84 +msgid "" +"Click the **Start Inventory** button. Depending on the type of inventory you" +" have chosen (all products or selected ones) you might have to add products " +"manually by clicking on **Add an item**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:88 +msgid "" +"Add the **Real Quantity** that you have in your stock for each product." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:92 +msgid "" +"additional information will be available according to the options you " +"activated (multi-locations, serial number, consignee stocks)." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:98 +msgid "" +"Click the **Validate Inventory** button to confirm the inventory and post " +"it." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:102 +msgid "Reporting" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:104 +msgid "" +"To check the current stock, go to :menuselection:`Inventory Control --> " +"Products`, and click on the **list button**:" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:3 +msgid "How to choose between minimum stock rule and make to order?" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:5 +msgid "" +"**Minimum Stock rules** and **Make to Order** have similar consequences but " +"different rules. They should be used depending on your manufacturing and " +"delivery strategies." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:15 +msgid "" +"**Minimum Stock** rules are used to ensure that you always have the minimum " +"amount of a product in stock in order to manufacture your products and/or " +"answer to your customer needs. When the stock level of a product reaches its" +" minimum the system will automatically generate a procurement with the " +"quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:22 +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:56 +msgid "Make to Order" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:24 +msgid "" +"The **Make to Order** function will trigger a **Purchase Order** of the " +"amount of the **Sales Order** related to the product. The system will " +"**not** check the current stock valuation. This means that a draft purchase " +"order will be generated regardless of the quantity on hand of the product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:30 +#: ../../inventory/management/delivery/delivery_countries.rst:12 +#: ../../inventory/management/delivery/inventory_flow.rst:37 +#: ../../inventory/management/delivery/label_type.rst:13 +#: ../../inventory/management/delivery/one_step.rst:13 +#: ../../inventory/management/delivery/packaging_type.rst:13 +#: ../../inventory/management/delivery/three_steps.rst:34 +#: ../../inventory/management/delivery/two_steps.rst:29 +#: ../../inventory/management/incoming/handle_receipts.rst:50 +#: ../../inventory/management/incoming/three_steps.rst:28 +#: ../../inventory/management/incoming/two_steps.rst:21 +#: ../../inventory/management/misc/owned_stock.rst:22 +#: ../../inventory/management/misc/scrap.rst:25 +#: ../../inventory/overview/concepts/double-entry.rst:159 +#: ../../inventory/overview/concepts/double-entry.rst:164 +#: ../../inventory/routes/concepts/cross_dock.rst:21 +#: ../../inventory/routes/concepts/inter_warehouse.rst:10 +#: ../../inventory/routes/concepts/procurement_rule.rst:25 +#: ../../inventory/routes/concepts/push_rule.rst:29 +#: ../../inventory/routes/concepts/use_routes.rst:22 +#: ../../inventory/routes/costing/landed_costs.rst:18 +#: ../../inventory/routes/strategies/putaway.rst:23 +#: ../../inventory/routes/strategies/removal.rst:18 +#: ../../inventory/settings/products/packages.rst:17 +#: ../../inventory/settings/products/packages.rst:66 +#: ../../inventory/settings/products/uom.rst:17 +#: ../../inventory/settings/products/variants.rst:114 +#: ../../inventory/settings/warehouses/location_creation.rst:6 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:6 +#: ../../inventory/shipping/operation/invoicing.rst:16 +#: ../../inventory/shipping/operation/labels.rst:15 +#: ../../inventory/shipping/operation/multipack.rst:13 +#: ../../inventory/shipping/setup/delivery_method.rst:17 +#: ../../inventory/shipping/setup/third_party_shipper.rst:14 +msgid "Configuration" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:35 +msgid "" +"The Minimum Stock Rules configuration is available through the menu " +":menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the " +"drop down menu. There, click on **Create** to set minimum and maximum stock " +"values for a given product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"If the active field is set to False, it will allow you to hide the " +"orderpoint without removing it." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Default Unit of Measure used for all stock operation." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"Moves created through this orderpoint will be put in this procurement group." +" If none is given, the moves generated by procurement rules will be grouped " +"into one big picking." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"When the virtual stock goes below the Min Quantity specified for this field," +" Odoo generates a procurement to bring the forecasted quantity to the Max " +"Quantity." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"When the virtual stock goes below the Min Quantity, Odoo generates a " +"procurement to bring the forecasted quantity to the Quantity specified as " +"Max Quantity." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"The procurement quantity will be rounded up to this multiple. If it is 0, " +"the exact quantity will be used." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"Number of days after the orderpoint is triggered to receive the products or " +"to order to the vendor" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:45 +msgid "" +"Then, click on your product to access the related product form and, on the " +"**Inventory submenu**, do not forget to select a supplier." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:52 +msgid "" +"Don't forget to select the right product type in the product form. A " +"consumable can not be stocked and will thus not be accounted for in the " +"stock valuation." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:58 +msgid "" +"The Make to Order configuration is available on your product form through " +"your :menuselection:`Inventory module --> Inventory control --> Products` " +"(or any other module where products are available)." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:62 +msgid "On the product form, under **Inventory**, click on **Make To Order**." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:68 +msgid "Choice between the two options" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:70 +msgid "" +"The choice between the two options is thus dependent of your inventory " +"strategy. If you prefer to have a buffer and always have at least a minimum " +"amount, the minimum stock rule should be used. If you want to reorder your " +"stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../inventory/management/delivery.rst:3 +msgid "Delivery Orders" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:3 +msgid "How do I cancel a delivery order?" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:6 +#: ../../inventory/management/delivery/delivery_countries.rst:6 +#: ../../inventory/management/delivery/label_type.rst:6 +#: ../../inventory/management/delivery/one_step.rst:6 +#: ../../inventory/management/delivery/packaging_type.rst:6 +#: ../../inventory/management/delivery/three_steps.rst:6 +#: ../../inventory/management/delivery/two_steps.rst:6 +#: ../../inventory/management/incoming/handle_receipts.rst:6 +#: ../../inventory/management/incoming/three_steps.rst:6 +#: ../../inventory/management/incoming/two_steps.rst:6 +#: ../../inventory/management/lots_serial_numbers/lots.rst:6 +#: ../../inventory/management/misc/scrap.rst:6 ../../inventory/overview.rst:3 +#: ../../inventory/overview/process/sale_to_delivery.rst:6 +#: ../../inventory/routes/concepts/procurement_rule.rst:6 +#: ../../inventory/routes/concepts/push_rule.rst:6 +#: ../../inventory/routes/concepts/use_routes.rst:6 +#: ../../inventory/routes/costing/landed_costs.rst:6 +#: ../../inventory/routes/strategies/putaway.rst:6 +#: ../../inventory/routes/strategies/removal.rst:6 +#: ../../inventory/settings/products/packages.rst:6 +#: ../../inventory/settings/products/uom.rst:6 +#: ../../inventory/shipping/operation/cancel.rst:6 +#: ../../inventory/shipping/operation/invoicing.rst:6 +#: ../../inventory/shipping/operation/labels.rst:6 +#: ../../inventory/shipping/operation/multipack.rst:6 +#: ../../inventory/shipping/setup/delivery_method.rst:6 +#: ../../inventory/shipping/setup/third_party_shipper.rst:6 +msgid "Overview" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:8 +msgid "" +"Odoo gives you the possibility to cancel a delivery method whether it has " +"been validated to fast, it needs to be modified or for any other reason." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:12 +msgid "" +"Some carriers are more flexible than others, so make sure to cancel your " +"delivery order as fast as possible if it needs to be done so you don't have " +"any bad surprise." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:17 +#: ../../inventory/shipping/operation/multipack.rst:26 +#: ../../inventory/shipping/setup/third_party_shipper.rst:107 +msgid "Sale process" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:19 +msgid "" +"Go to the **Sales** module, click on **Sales** and then on **Sales Order**. " +"Then click on the sale order you want to cancel." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:25 +msgid "" +"Click on the **Delivery** button, in the upper right corner of the sale " +"order." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:31 +msgid "" +"Now, click on the **Additional info** tab and you will see that next to the " +"**Carrier Tracking Reference**, there is a **Cancel** button. Click on it to" +" cancel the delivery." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:38 +msgid "" +"To make sure that your delivery is cancelled, check in the history, you will" +" receive the confirmation of the cancellation." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:3 +msgid "How can I limit a delivery method to a certain number of countries?" +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:8 +msgid "" +"With Odoo, you can have different types of delivery methods, and you can " +"limit them to a certain number of countries." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:14 +msgid "" +"Go to the **Inventory** module, click on **Configuration** and then on " +"**Delivery Methods**." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:20 +msgid "" +"Select the delivery method that you want to change, or create a new one." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:25 +msgid "" +"In the **Destination** tab, choose the countries to which you want to apply " +"this delivery method." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:28 +msgid "Now, that this is done, Let's see the result." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:30 +msgid "" +"If you go to the website, and you try to buy something, once you've entered " +"your details and you proceed to the payment, the website will propose you " +"only the delivery methods that apply to your shipping address." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:39 +msgid "" +"This process doesn't work in backend. We assume that when you create a Sale " +"Order, you know which delivery method you can use since you created them." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:3 +msgid "" +"How to send products to customers directly from suppliers (drop-shipping)?" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:6 +msgid "What is drop-shipping?" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:8 +msgid "" +"Drop-Shipping is a system that allows orders taken from your store to be " +"shipped straight from your supplier to your customer. On a usual delivery " +"system, products are sent from your supplier to your warehouse to be put in " +"stock, and then shipped to your customers after ordering. With drop-" +"shipping, no item is stocked. When a customer places an order in your shop, " +"the item is delivered straight from the supplier to the customer. Therefore," +" the product doesn't need to get through your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:18 +msgid "Points to be considered while implementing drop-shipping" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:20 +msgid "" +"Use drop-shipping only for the products you can't or don't want to keep in " +"stock. One reason is that you'll always make smaller margins on items that " +"are drop-shipped, so you should keep it only for items that take up a lot of" +" space in your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:25 +msgid "" +"Drop-shipping is best for niche products. Chances are that products that are" +" in high demand are being offered by large suppliers at a fraction of the " +"price you'll be able to charge, so using a more costly shipping method won't" +" be financially rewarding. But if your product is unique, then it makes " +"sense!" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:31 +msgid "" +"To protect your customers from bad experiences, test drop-shipping companies" +" for yourself beforehand and list the best ones." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:34 +msgid "" +"Make sure time is not against you. Drop-shipping should take a reasonable " +"amount of time and surely not more than it would have taken you to handle it" +" all by yourself. It's also nice to be able to provide your customers with a" +" tracking number." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:39 +msgid "" +"Items have to be available from your supplier. It's good to know if the " +"product you're selling is available upstream. If you don't have that " +"information, inform your customers that you don't hold the item in stock and" +" that it's subject to availability from a third party." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:46 +msgid "" +"For more information and insights on Drop-shipping, read our blog on `What " +"is drop-shipping and how to use it `__." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:50 +msgid "Configuring drop-shipping" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:52 +msgid "" +"Open the menu :menuselection:`Inventory --> Configuration --> Settings`. Go " +"to **Location & Warehouse**, locate the **Dropshipping** option and tick the" +" box **Allow suppliers to deliver directly to your customers**. Then, click " +"on **Apply**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:60 +msgid "" +"Then go to the menu :menuselection:`Sales --> Configuration --> Settings`. " +"Locate **Order Routing** and tick the box **Choose specific routes on sales " +"order lines (advanced)**. Click on **Apply**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:67 +msgid "" +"Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a " +"supplier to the products you want to dropship." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:74 +msgid "How to send products from the customers directly to the suppliers" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:76 +msgid "" +"Create a **Sales Order** and specify on a sales order line for your products" +" that the route is **Dropshipping**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:82 +msgid "" +"Open the menu :menuselection:`Purchases --> Purchases --> Requests for " +"Quotation`. The draft purchase order is automatically created from the " +"procurement with the drop-shipping route. Once the order is confirmed, you " +"will see that one shipment has been created." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:90 +msgid "" +"To confirm the sending from the vendor to the customer, go back to " +"**Inventory** app. On the dashboard, click on **# TO RECEIVE** on the " +"dropship card." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:97 +msgid "" +"It will open the list of drop-shipping transfers. Validate the transfer once" +" it has been done. The items will be directly delivered from the partner to " +"the customer without transiting to your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:103 +msgid ":doc:`inventory_flow`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:3 +msgid "How to choose the right inventory flow to handle delivery orders?" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:5 +msgid "" +"Depending on factors such as the type of items you sell, the size of your " +"warehouse, the number of orders you register everyday... the way you handle " +"deliveries to your customers can vary a lot." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:9 +msgid "" +"Odoo allows you to handle shipping from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:12 +msgid "**One step (shipping)**: Ship directly from stock" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:14 +msgid "" +"**Two steps (pick + ship)**: Bring goods to output location before shipping" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:17 +msgid "" +"**Three steps (pick + pack + ship)**: Make packages into a dedicated " +"location, then bring them to the output location for shipping" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:20 +msgid "" +"For companies having a rather small warehouse and that do not require high " +"stock of items or don't sell perishable items, a one step shipping is the " +"simplest solution, as it does not require a lot of configuration and allows " +"to handle orders very quickly." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:25 +msgid "" +"Using inventory methods such as FIFO, LIFO and FEFO require to have at least" +" two steps to handle a shipment. The picking method will be determined by " +"the removal strategy, and the items removed will then be shipped to the " +"customer. This method is also interesting if you hold larger stocks and " +"especially when the items you stock are big in size." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:31 +msgid "" +"The three steps system becomes useful in more specific situations, the main " +"one being for handling very large stocks. The items are transferred to a " +"packing area, where they will be assembled by area of destination, and then " +"set to outbound trucks for final delivery to the customers." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:40 +#: ../../inventory/management/incoming/handle_receipts.rst:53 +msgid "One step flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:42 +msgid "Please read documentation on :doc:`one_step`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:45 +#: ../../inventory/management/incoming/handle_receipts.rst:58 +msgid "Two steps flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:47 +#: ../../inventory/management/incoming/handle_receipts.rst:60 +msgid "Please read documentation on :doc:`two_steps`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:50 +#: ../../inventory/management/incoming/handle_receipts.rst:63 +msgid "Three steps flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:52 +#: ../../inventory/management/incoming/handle_receipts.rst:65 +msgid "Please read documentation on :doc:`three_steps`" +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:3 +msgid "How can I change the label type?" +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:8 +msgid "" +"With Odoo, you can choose among different types of labels for your delivery " +"orders. Follow the steps below and give an appropriate label type to your " +"delivery." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:15 +msgid "" +"In the **Inventory** module, Go to **Configuration** and click on **Delivery" +" methods**." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:18 +msgid "Choose a delivery method and then click on **Edit**." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:23 +msgid "" +"In the **Pricing** tab, under **Fedex label stock type**, you can choose one" +" of the label types available. The availability will vary depending on the " +"carrier." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:30 +msgid "" +"Once this is done, you can see the result if you go to the Sales module and " +"you create a new sale order." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:33 +msgid "" +"As you confirm the sale and validate the delivery with the carrier for which" +" you have modified the label type, The label will appear in your history." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:46 +msgid "" +"The default label type is paper letter, and if you choose the label type " +"bottom half for example, here is the difference :" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:3 +msgid "How to process delivery orders in one step (shipping)?" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default to utilize a one-step operation: once all goods are " +"available, they are able to be shipped in a single delivery order." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:15 +msgid "" +"There is no configuration needed. The default outgoing shipments are " +"configured to be directly delivered from the stock." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:18 +msgid "" +"However, if **advance routes** is activated and you set another shipping " +"configuration on your warehouse, you can set it back to the one-step " +"delivery configuration. Go to :menuselection:`Configuration --> Warehouses` " +"and edit the concerned warehouse." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:23 +msgid "" +"Set the outgoing shippings the option to **Ship directly from stock (Ship " +"Only)**" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:30 +#: ../../inventory/management/delivery/two_steps.rst:68 +msgid "Create a Sales Order" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:32 +msgid "" +"Create a sales order (From quotation to sales order) with some products to " +"deliver." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:35 +msgid "" +"Notice that we now see ``1`` delivery associated with this sales order in " +"the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:41 +msgid "" +"If you click on the **1 Delivery** stat button, you should now see your " +"picking." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:45 +#: ../../inventory/management/delivery/three_steps.rst:99 +#: ../../inventory/management/delivery/two_steps.rst:88 +msgid "Process a Delivery" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:47 +#: ../../inventory/management/delivery/three_steps.rst:143 +#: ../../inventory/management/delivery/two_steps.rst:113 +msgid "" +"Go to **Inventory** and click on the **# TO DO** link under the **Delivery " +"Orders** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:53 +#: ../../inventory/management/delivery/three_steps.rst:110 +#: ../../inventory/management/delivery/three_steps.rst:130 +#: ../../inventory/management/delivery/three_steps.rst:149 +#: ../../inventory/management/delivery/two_steps.rst:99 +#: ../../inventory/management/delivery/two_steps.rst:119 +#: ../../inventory/management/incoming/three_steps.rst:99 +msgid "Click on the picking that you want to process." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:55 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"**customer**." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:58 +msgid "" +"This has completed the **Shipping Step** and the WH/OUT should now show " +"**Done** in the status column at the top of the page, which means the " +"product has been shipped to the customer." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:3 +msgid "How can you change the packaging type for your sale order?" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:8 +msgid "" +"Odoo gives you the possibility to change the default packaging type and " +"adapt the packaging the way you want it, depending on the weight of the " +"order." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:15 +msgid "" +"In the **Inventory** module, Go to **Configuration** and then click on " +"**Settings**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:18 +msgid "" +"In :menuselection:`Traceability --> Packages`, flag **Record packages used " +"on packing : pallets, boxes,...**" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:24 +msgid "*Sale process*" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:26 +msgid "In the **Sales** module, go to **Sales** and click on **Sale Order**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:28 +msgid "Create your new Sale Order, and **Confirm the Sale**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:33 +msgid "" +"Once you've confirmed the Sale, you need to click on **Delivery**, to be " +"redirected to the Delivery order." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:36 +msgid "Click on **Edit**, and you can now change the packaging." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:41 +msgid "" +"In the **Operations** tab, in the last column, change the **0** and put the " +"number of products that you want to pack together. Then click on **Put in " +"Pack**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:48 +msgid "" +"Choose the type of packaging that you want. You can also see that the weight" +" has been adapted to your package, and you can change it manually if you " +"want it to be more precise. Then click on **Save**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:52 +msgid "Repeat the operation until all the products are put in pack." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:54 +msgid "Finally, click on **Validate** to confirm the delivery." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:3 +msgid "How is the scheduled delivery date computed?" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:5 +msgid "" +"Scheduled dates are computed in order to be able to plan deliveries, " +"receptions and so on. Depending on the habits of your company Odoo " +"automatically generates scheduled dates via the scheduler. The Odoo " +"scheduler computes everything per line, whether it's a manufacturing order, " +"a delivery order, a sale order, etc. The dates that are computed are " +"dependent on the different leads times configured in Odoo." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:13 +msgid "Configuring lead times" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:15 +msgid "" +"Configuring **lead times** is a first essentiel move in order to compute " +"scheduled dates. Lead times are the delays (in term of delivery, " +"manufacturing, ...) promised to your different partners and/or clients." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:19 +msgid "Configuration of the different lead times are made as follows:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:22 +msgid "At a product level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:24 +msgid "**Supplier lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:26 +msgid "" +"Is the time needed for the supplier to deliver your purchased product. To " +"configure the supplier lead time select a product, and go in the " +"**Inventory** tab. You will have to add a vendor to your product in order to" +" select a supplier lead time." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:35 +msgid "" +"Do not forget that it is possible to add different vendors and thus " +"different delivery lead times depending on the vendor." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:38 +msgid "" +"Once a vendor is selected, just open its form and fill its **Delivery lead " +"time**. In this case security days have no influence, the scheduled delivery" +" days will be equal to: **Date** of the purchase order + **Delivery Lead " +"Time**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:46 +msgid "**Customer lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:48 +msgid "" +"Customer lead time is the time needed to get your product from your store / " +"warehouse to your customer. It can be configured for any product. Simply " +"select a product, go into the sales tab and indicate your **Customer lead " +"time**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:56 +msgid "**Manufacturing lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:58 +msgid "" +"At the same page it is possible to configure the **Manufacturing Lead Time**" +" as well. Manufacturing lead time is the time needed to manufacture the " +"product." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:63 +msgid "" +"Don't forget to tick the manufacturing box in inventory if you want to " +"create manufacturing routes." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:67 +msgid "At the company level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:69 +msgid "" +"At company level, it is possible to configure **security days** in order to " +"cope with eventual delays and to be sure to meet your engagements. The idea " +"is to subtract **backup** days from the **computed scheduled date** in case " +"of delays." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:74 +msgid "**Sales Safety days**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:76 +msgid "" +"Sales safety days are **back-up** days to ensure you will be able to deliver" +" your clients engagements in times. They are margins of errors for delivery " +"lead times. Security days are the same logic as the early wristwatch, in " +"order to arrive on time. The idea is to subtract the numbers of security " +"days from the calculation and thus to compute a scheduled date earlier than " +"the one you promised to your client. In that way you are sure to be able to " +"keep your commitment." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:84 +msgid "" +"To set ut your security dates, go to :menuselection:`Settings --> General " +"settings` and click on **Configure your company data**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:90 +msgid "" +"Once the menu is open, go in the configuration tab and indicate the number " +"of safety days." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:93 +msgid "**Purchase Safety days**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:95 +msgid "Purchase days follow to the same logic than sales security days." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:97 +msgid "" +"They are margins of error for vendor lead times. When the system generates " +"purchase orders for procuring products, they will be scheduled that many " +"days earlier to cope with unexpected vendor delays. Purchase lead time can " +"be found in the same menu as the sales safety days" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:106 +msgid "" +"Note that you can also configure a default Manufacturing lead time from " +"here." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:110 +msgid "At route level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:112 +msgid "" +"The internal transfers that a product might do due to the movement of stocks" +" can also influence the computed date." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:115 +msgid "" +"The delays due to internal transfers can be specified in the **inventory** " +"app when creating a new push rule in a route." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:118 +msgid "Go to the push rules section on a route form to set a delay." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:124 +msgid "At sale order level:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:126 +msgid "**Requested date**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:128 +msgid "" +"Odoo offers the possibility to select a requested date by the client by " +"indicating the date in the other information tab of the sales order. If this" +" date is earlier than the theoreticaly computed date odoo will automatically" +" display a warning." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:139 +msgid "" +"As an example, you may sell a car today (January 1st), that is purchased on " +"order, and you promise to deliver your customer within 20 days (January 20)." +" In such a scenario, the scheduler may trigger the following events, based " +"on your configuration:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:144 +msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:146 +msgid "" +"January 18: receive the product from your supplier (1 day of Purchase days)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:149 +msgid "" +"January 10: deadline to order at your supplier (9 days of supplier delivery " +"lead time)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:152 +msgid "" +"January 8: trigger a purchase request to your purchase team, since the team " +"need on average 2 days to find the right supplier and order." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:3 +msgid "How to process delivery orders in three steps (pick + pack + ship)?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default on a **one-step** operation: once all goods are available," +" they can be shipped in bulk in a single delivery order. However, that " +"process may not reflect the reality and your company may require more steps " +"before shipping." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:14 +msgid "" +"With the **three steps** process (**Pick + Pack + Ship**), the items are " +"transferred to a packing area, where they will be assembled by area of " +"destination, and then set to outbound trucks for final delivery to the " +"customers." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:19 +msgid "" +"A few configuration steps are necessary in order to accomplish **Pick + Pack" +" + Ship** in Odoo. These steps create some additional locations, which by " +"default are called **Output** and **Packing Zone**. So, if your warehouse's " +"code is ``WH``, this configuration will create a location called " +"``WH/Output`` and another one called ``WH/Packing Zone``." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:25 +msgid "" +"Goods will move from **WH/Stock** to **WH/Packing Zone** in the first step. " +"Then move from **WH/Packing Zone** to **WH/Output**. Then finally it will be" +" delivered from **WH/Output** to its **final destination**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:30 +#: ../../inventory/management/delivery/two_steps.rst:25 +msgid "" +"Check out :doc:`inventory_flow` to determine if this inventory flow is the " +"correct method for your needs." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:37 +msgid "Install the Inventory module" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:39 +msgid "From the **App** menu, search and install the **Inventory** module." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:44 +msgid "" +"You will also need to install the **Sales** module to be able to issue sales" +" orders." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:48 +msgid "Allow managing routes" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:50 +msgid "" +"Odoo configures movement of delivery orders via **routes**. Routes provide a" +" mechanism to link different actions together. In this case, we will link " +"the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:54 +msgid "" +"To allow management of routes, go to :menuselection:`Configuration --> " +"Settings`" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:56 +msgid "" +"Under :menuselection:`Location & Warehouse --> Routes`, activate the radio " +"button **Advanced routing of products using rules**. Make sure that the " +"option **Manage several locations per warehouse** is activated as well." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:64 +msgid "Configure the warehouse for Pick + Pack + Ship" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:66 +msgid "" +"Go to :menuselection:`Configuration --> Warehouses` and edit the warehouse " +"that will be used." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:69 +msgid "" +"For outgoing shippings, set the option to **Make packages into a dedicated " +"location, bring them to the output location for shipping (Pick + Pack + " +"Ship).**" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:77 +msgid "Create a Sale Order" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:79 +msgid "" +"From the **Sale** module, create a sales order with some products to " +"deliver." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:81 +msgid "" +"Notice that we now see ``3`` transfers associated with this sales order in " +"the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:87 +msgid "If you click the button, you should now see three different pickings:" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:89 +msgid "The first with a reference **PICK** to designate the picking process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:91 +msgid "" +"The second one with the reference **PACK** that is the packing process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:93 +msgid "The last with a reference **OUT** to designate the shipping process." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:102 +#: ../../inventory/management/delivery/two_steps.rst:91 +msgid "How to Process the Picking Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:104 +msgid "" +"Ensure that you have enough product in stock and Go to **Inventory** and " +"click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:112 +#: ../../inventory/management/delivery/two_steps.rst:101 +msgid "Click on **Reserve** to reserve the products if they are available." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:114 +msgid "" +"Click on **Validate** to complete the move from **WH/Stock** to **WH/Packing" +" Zone**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:116 +msgid "" +"This has completed the picking Step and the **WH/PICK** should now show " +"**Done** in the status column at the top of the page. The product has been " +"moved from **WH/Stock** to **WH/Packing Zone** location, which makes the " +"product available for the next step (Packing)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:122 +msgid "How to Process the Packing Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:124 +msgid "" +"Go to **Inventory** and click on the **# TRANSFERS** link under the **Pack**" +" kanban card." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:132 +msgid "" +"Click on **Validate** to complete the move from **WH/Packing Zone** to " +"**WH/Output**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:135 +msgid "" +"This has completed the packing step and the **WH/PACK** should now show " +"**Done** in the status column at the top of the page. The product has been " +"moved from **WH/Packing Zone** to **WH/Output location**, which makes the " +"product available for the next step (Shipping)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:141 +#: ../../inventory/management/delivery/two_steps.rst:111 +msgid "How to Process the Shipping Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:151 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"**customer** (Click **Apply** to assign the quantities based on the " +"quantities listed in the **To Do** column)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:155 +msgid "" +"This has completed the shipping step and the **WH/OUT** should now show " +"**Done** in the status column at the top of the page. The product has been " +"shipped to the customer." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:3 +msgid "How to process delivery orders in two steps (pick + ship)?" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default to utilize a **one-step** operation: once all goods are " +"available, they are able to be shipped in a single delivery order. However, " +"your company's business process may have one or more steps that happen " +"before shipping. In the **two steps** process, the items in a delivery order" +" are **picked** in the warehouse and brought to an **output location** for " +"**shipping**. The goods are then shipped." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:16 +msgid "" +"In order to accomplish a **Pick + Ship** delivery in Odoo, there are a few " +"necessary configuration steps. These steps create an additional location, " +"which by default is called **Output**. So, if your warehouse's code is " +"``WH``, this configuration will create a location called ``WH/Output``. " +"Goods will move from ``WH/Stock`` to ``WH/Output`` in the first step " +"(picking). Then, they move from ``WH/Output`` to ``WH/Customers`` (in the " +"case of sales orders) in the second step (shipping)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:32 +msgid "Allow management of routes" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:34 +msgid "" +"Odoo configures movement of delivery orders via the **routes**. Routes " +"provide a mechanism to chain different actions together. In this case, we " +"will chain the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:38 +msgid "" +"To allow management of routes, go to :menuselection:`Configuration --> " +"Settings`." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:40 +msgid "" +"Ensure that the radio button **Advanced routing of products using rules** is" +" checked." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:46 +msgid "" +"Click on **Apply** at the top of the page to save changes (if you needed to " +"check the radio button above)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:50 +msgid "" +"If you checked option **Advanced routing of products using rules** you may " +"need to activate **Manage several locations per warehouse** if it wasn't " +"activated beforehand." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:55 +msgid "Configure warehouse for Pick + Ship" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:57 +msgid "" +"To configure a **Pick + Ship** move, go to :menuselection:`Configuration -->" +" Warehouses` and edit the warehouse that will be used." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:61 +msgid "" +"For outgoing shippings, set the option to **Bring goods to output location " +"before shipping (Pick + Ship)**" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:70 +msgid "" +"Install the **Sale** if it is not the case, and create a sales order with " +"some products to deliver." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:73 +msgid "" +"Notice that we now see ``2`` transfers associated with this sales order in " +"the **Delivery** stat button above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:79 +msgid "" +"If you click on the **2 Transfers** stat button, you should now see two " +"different pickings, one with a reference **PICK** to designate the picking " +"process and another with a reference **OUT** to designate the shipping " +"process." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:93 +msgid "" +"Ensure that you have enough product in stock, and go to **Inventory** and " +"click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:103 +msgid "" +"Click on **Validate** to complete the move from **WH/Stock** to " +"**WH/Output**." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:105 +msgid "" +"This has completed the picking step and the **WH/PICK** move should now show" +" **Done** in the status column at the top of the page. The product has been " +"moved from **WH/Stock** to **WH/Output** location, which makes the product " +"**available for the next step** (Shipping)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:121 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"customer (Click **Apply** to assign the quantities based on the quantities " +"listed in the **To Do** column)" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:125 +msgid "" +"This has completed the shipping step and the **WH/OUT** move should now show" +" **Done** in the status column at the top of the page. The product has been " +"shipped to the customer." +msgstr "" + +#: ../../inventory/management/incoming.rst:3 +msgid "Incoming Shipments" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:3 +msgid "How to choose the right flow to handle receipts?" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:8 +msgid "" +"Depending on factors such as the type of items you receive, the size of your" +" warehouse, the number of receipt you register everyday... the way you " +"handle receipts to your customers can vary a lot." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:12 +msgid "" +"Odoo allows you to handle receipts from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:15 +msgid "**One step**: Receive goods directly in stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:17 +msgid "**Two steps**: Unload in input location then go to stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:19 +msgid "" +"**Three steps**: Unload in input location, go through a quality control " +"before being admitted in stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:22 +msgid "" +"Odoo uses **routes** to define exactly how you will handle the different " +"receipt steps. The configuration is done at the level of the warehouse. In " +"standard, the reception is a one step process, but changing the " +"configuration can allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:27 +msgid "The principles are the following:" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:29 +msgid "**One step**: You receive the goods directly in your stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:31 +msgid "" +"**Two steps**: You receive the goods in an input area then transfer them " +"from input area to your stock. As long as the goods are not transferred in " +"your stock, they will not be available for further processing." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:36 +msgid "" +"**Three steps**: In many companies, it is necessary to assess the received " +"good. The goal is to check that the products correspond to the quality " +"requirements agreed with the suppliers. Adding a quality control step in the" +" goods receipt process can become essential." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:42 +msgid "" +"You receive the goods in an input area, then transfer them into quality area" +" for quality control. When your quality check process finishes then you can " +"move the goods from QC to stock. Of course, you may change the quantity and " +"only transfer to Stock the quantity that is valid and decide that you will " +"return the quantity that is not good." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:55 +msgid "This is the default configuration in Odoo." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:68 +#: ../../inventory/management/incoming/three_steps.rst:126 +#: ../../inventory/management/incoming/two_steps.rst:97 +msgid ":doc:`../delivery/inventory_flow`" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:3 +msgid "How to add a quality control step in goods receipt? (3 steps)" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:8 +msgid "" +"In many companies, it is necessary to assess the received good. The goal is " +"to check that the products correspond to the quality requirements agreed " +"with the suppliers. Therefore, adding a quality control step in the goods " +"receipt process can become essential." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:13 +#: ../../inventory/management/incoming/two_steps.rst:8 +msgid "" +"Odoo uses routes to define exactly how you will handle the different receipt" +" steps. The configuration is done at the level of the warehouse. By default," +" the reception is a one step process, but changing the configuration can " +"allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:18 +msgid "" +"The 3 steps flow is as follows: You receive the goods in an input area, then" +" transfer them into quality area for quality control. When the quality check" +" has been processed, you can move the goods from QC to stock. Of course, you" +" may change the quantity and only transfer to stock the quantity that is " +"valid and decide that you will return the quantity that is not good." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:25 +#: ../../inventory/management/incoming/two_steps.rst:18 +msgid "This is the case that will be explained in this document." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:31 +#: ../../inventory/management/incoming/two_steps.rst:24 +msgid "Use advanced routes" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:33 +msgid "" +"To allow management of routes, go to the menu :menuselection:`Inventory --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:39 +#: ../../inventory/management/incoming/two_steps.rst:32 +msgid "" +"Ensure that the routes option **Advance routing of product using rules** is " +"checked, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:42 +msgid "" +"Make sure that **Manage several locations per warehouse** is also ticked." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:46 +msgid "How to add a quality control step in goods receipt?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:48 +msgid "" +"Go to the menu :menuselection:`Inventory --> Configuration --> Warehouse` " +"and choose the warehouse where you want to change reception methods." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:51 +msgid "" +"By default, warehouses are configured with one step reception (**Receive " +"goods directly into stock**)." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:54 +msgid "" +"To add quality control before transfer goods into stock location, tick " +"**Unload in input location, go through a quality control before being " +"admitted in stock (3 steps)**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:62 +msgid "How to control a receipt?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:65 +msgid "How to process the receipt step ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:67 +msgid "" +"In the **Purchase** app, create a **Request for Quotation**. Click on the " +"**Confirm order** button. You can see that there is one **Shipment** related" +" to purchase order in the stat button above the purchase order form view. " +"This is the receipt step." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:75 +msgid "" +"Go to **Inventory** and click on the link **# TO RECEIVE** in the " +"**Receipts** card." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:80 +msgid "" +"Click on the receipt that you want to process. Click on **Validate** to " +"complete the move from the **Vendor** location to **WH/Input**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:83 +msgid "" +"This has completed the receipt step and the status column at the top of the " +"page for **WH/IN** should now show **Done**. The product has been moved from" +" the **Vendor** to the **WH/Input** location, which makes the product " +"available for the next step (Move to the quality control zone)" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:89 +msgid "" +"How to move your product from the receipt zone to the quality control zone ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:91 +msgid "" +"Go to the **Inventory** dashboard. You will see that there is one transfer " +"ready (the move to the quality control zone) and one waiting (the move to " +"the stock after the control). Click on the link **# TRANSFERS** in the " +"**Internal Transfers** to process the quality control." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:101 +msgid "" +"Click on **Validate** to complete the move from **WH/Input** to **WH/Quality" +" Control**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:104 +msgid "" +"This has completed the internal transfer step and the status column at the " +"top of the page for **WH/INT** should now show **Done**. The receipt is now " +"ready to be controlled." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:109 +msgid "How to to process the quality control ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:111 +msgid "" +"Go back to the **Inventory** dashboard. The waiting transfer is now ready. " +"Click on the link **# TRANSFERS** in the **Internal Transfers** card to " +"process the quality control." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:118 +msgid "" +"Click on the last picking to process. Click on **Validate** to complete the " +"move from **WH/Quality Control** to **WH/Stock**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:121 +msgid "" +"This has completed the quality control step and the status column at the top" +" of the page for **WH/INT** should now show **Done**. The receipt has been " +"controlled and has moved to your stock." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:127 +msgid ":doc:`two_steps`" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:3 +msgid "How to unload your shipment to an input location? (2 steps)" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:13 +msgid "" +"The 2 steps flow is the following : You receive the goods in an input area " +"then transfer them from input area to your stock. As long as the goods are " +"not transferred in your stock, they will not be available for further " +"processing." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:26 +msgid "" +"To allow management of routes, go to the menu :menuselection:`Inventory --> " +"Configuration --> Settings`" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:35 +msgid "" +"Make sure that **\"Manage several locations per warehouse\"** is also " +"ticked." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:39 +msgid "How to configure your warehouse ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:41 +msgid "" +"Go to the the menu :menuselection:`Inventory --> Configuration --> " +"Warehouse` and choose the warehouse where you want to change reception " +"methods." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:44 +msgid "" +"By default, warehouses are configured with one step reception (option " +"**Receive goods directly into stock**)." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:47 +msgid "" +"To add the control step, tick **Unload in input location then go to stock (2" +" steps)**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:54 +msgid "How to receipt a shipment in 2 steps?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:57 +msgid "How to process the Receipt step ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:59 +msgid "" +"In the purchase module, create a **Request for Quotation**, then click on " +"the **Confirm order** button. You can see that there is one **Shipment** " +"related to purchase order in the **stat button** above the purchase order " +"form view. This is the receipt step." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:67 +msgid "" +"Go to **Inventory** and click on the **# TO RECEIVE** link on the " +"**Receipts** card." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:73 +msgid "" +"Click on the receipt that you want to process, then click on **Validate** to" +" complete the move from the **Vendor** to **WH/Input**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:76 +msgid "" +"This has completed the Receipt Step and the move refered with **WH/IN**. The" +" product has been moved from the **Vendor** to the **WH/Input** location, " +"which makes the product available for the next step." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:81 +msgid "How to to transfer the receipt to your stock ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:83 +msgid "" +"Go back to the **Inventory** dashboard. The waiting transfer is now ready. " +"Click on the **# TRANSFERS** in the **Internal Transfers** to process the " +"quality control." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:90 +msgid "" +"Click on the picking you want to process. Click on **Validate** to complete " +"the move from **WH/Input** to **WH/Stock**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:93 +msgid "" +"This has completed the internal transfer step and the move refered with " +"**WH/INT**. The receipt has been moved to your stock." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:98 +msgid ":doc:`three_steps`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers.rst:3 +msgid "Lots and Serial Numbers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:3 +msgid "What's the difference between lots and serial numbers?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:6 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:6 +#: ../../inventory/management/misc/owned_stock.rst:6 +#: ../../inventory/settings/products/variants.rst:170 +msgid "Introduction" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:8 +msgid "" +"In Odoo, lots and serial numbers have similarities in their functional " +"system but are different in their behavior. They are both managed within the" +" **Inventory**, **Purchases** and **Sales** app." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:12 +msgid "" +"**Lots** correspond to a certain number of products you received and store " +"altogether in one single pack." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:15 +msgid "" +"**Serial numbers** are identification numbers given to one product in " +"particular, to allow to track the history of the item from reception to " +"delivery and after-sales." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:20 +msgid "When to use" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:22 +msgid "" +"**Lots** are interesting for products you receive in great quantity and for " +"which a lot number can help in reportings, quality controls, or any other " +"info. Lots will help identify a number of pieces having for instance a " +"production fault. It can be useful for a batch production of clothes or " +"food." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:28 +msgid "" +"**Serial numbers** are interesting for items that could require after-sales " +"service, such as smartphones, laptops, fridges, and any electronic devices. " +"You could use the manufacturer's serial number or your own, depending on the" +" way you manage these products" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:34 +msgid "When not to use" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:36 +msgid "" +"Storing consumable products such as kitchen roll, toilet paper, pens and " +"paper blocks in lots would make no sense at all, as there are very few " +"chances that you can return them for production fault." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:40 +msgid "" +"On the other hand, giving a serial number to every product is a time-" +"consuming task that will have a purpose only in the case of items that have " +"a warranty and/or after-sales services. Putting a serial number on bread, " +"for instance, makes no sense at all." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:46 +#: ../../inventory/management/lots_serial_numbers/lots.rst:135 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:47 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:129 +msgid ":doc:`lots`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:3 +msgid "How to manage lots of identical products?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:8 +msgid "" +"Lots are useful for products you receive in great quantity and for which a " +"lot number can help in reportings, quality controls, or any other info. Lots" +" will help identify a number of pieces having for instance a production " +"fault. It can be useful for a batch production of clothes or food." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:14 +msgid "" +"Odoo has the capacity to manage lots ensuring compliance with the " +"traceability requirements imposed by the majority of industries." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:17 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:15 +msgid "" +"The double-entry management in Odoo enables you to run very advanced " +"traceability." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:21 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:19 +msgid "Setting up" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:24 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:22 +msgid "Application configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:26 +msgid "" +"You need activate the tracking of lots in the settings. In the **Inventory**" +" application, go to :menuselection:`Configuration --> Settings`, select " +"**Track lots or serial numbers**" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:33 +msgid "" +"In order to have an advanced management of the lots, you should also select " +"**Manage several locations per warehouse**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:39 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:31 +#: ../../inventory/shipping/operation/labels.rst:27 +#: ../../inventory/shipping/setup/third_party_shipper.rst:26 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:42 +msgid "Operation types configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:44 +msgid "" +"You also need to set up how you will manage lots for each operations. In the" +" **Inventory** application, go to :menuselection:`Configuration --> " +"Operation Types`." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:48 +msgid "" +"For each type (receipts, internal transfers, deliveries,...), you can set if" +" you can create new lot numbers or only use existing lot numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:57 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:36 +msgid "" +"Finally, you have to configure which products you want to track in lots." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:59 +msgid "" +"Go into :menuselection:`Inventory Control --> Products`, and open the " +"product of your choice. Click on **Edit**, and in the **Inventory** tab, " +"select **Tracking by Lots**, then click on **Save**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:67 +msgid "Manage lots" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:70 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:49 +msgid "Transfers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:72 +msgid "" +"In order to process a transfer of a product tracked by lot, you have to " +"input the lot number(s)." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:75 +msgid "Click on the lot icon :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:80 +msgid "" +"A window will pop-up. Click on **Add an item** and fill in the lot number " +"and the quantity." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:86 +msgid "" +"Depending on your operation type configuration, you will be able to fill in " +"new lot numbers, or only use existing ones." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:90 +msgid "In the scanner interface, you just have to scan the lot numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:93 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:79 +msgid "Inventory adjustment" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:95 +msgid "Inventory of a product tracked by lot can be done in 2 ways:" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:97 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:83 +msgid "Classic inventory by products" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:99 +msgid "Inventory of a lot" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:101 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:87 +msgid "" +"When doing a classic inventory, there is a **Serial Number** column. If the " +"product has already been assigned with a number, it is already pre-filled." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:105 +msgid "" +"Click on **Add an item** if the product has not been inventoried yet. You " +"can easily create lots, just type in a new lot number in the column." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:111 +msgid "" +"You can also just do the inventory of a lot. In this case, you will have to " +"fill in the **Lot number**. You can also create a new lot from here. Just " +"type in the number, a window will pop out to link the number to a product." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:120 +msgid "Lots traceability" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:122 +msgid "" +"You can check the lot traceability from :menuselection:`Inventory --> " +"Inventory Control --> Serial Numbers/Lots`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:128 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:122 +msgid "You can have more details by clicking on the **Traceability** button :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:134 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:128 +msgid ":doc:`differences`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:3 +msgid "How to work with serial numbers?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:8 +msgid "" +"Serial Number Tracking is used to track products with serial numbers on " +"every transactions. You can track the current location of the product with " +"serial numbers. When the products are moved from one location to another " +"location, the system will automatically identify the current location of the" +" product based on last movement of the product. So you can get the last " +"location where the products are moved." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:24 +msgid "" +"You need activate the tracking of serial numbers in the settings. In the " +"**Inventory** application, go to :menuselection:`Configuration --> " +"Settings`, select **Track lots or serial numbers**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:38 +msgid "" +"Go into :menuselection:`Inventory Control --> Products`, and open the " +"product of your choice. Click on **Edit**, and in the **Inventory** tab, " +"select **By Unique Serial Number**, then click on **Save**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:46 +msgid "Manage Serial Numbers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:51 +msgid "" +"In order to process a transfer of a product tracked by serial number, you " +"have to input the number(s). In order to be able to assign serial numbers to" +" products with tracking features enabled you will first need to mark your " +"transfer as to do. Click on the **Mark as TODO** button to display the Lot " +"Split icon." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:57 +msgid "Click on the serial number icon :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:62 +msgid "" +"A window will pop-up. Click on **Add an item** and fill in the serial " +"numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:68 +msgid "" +"If you move products that already have serial numbers assigned, those will " +"appear in the list. Just click on the **+** icon to to confirm that you are " +"moving those serial numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:76 +msgid "In the scanner interface, you just have to scan the serial numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:81 +msgid "" +"Inventory of a product tracked by serial numbers can be done in 2 ways:" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:85 +msgid "Inventory of a serial number" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:91 +msgid "" +"Click on **Add an item** if the product has not been inventoried yet. You " +"can easily create serial numbers, just type in a new number in the column." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:98 +msgid "The quantity should be 1 for each line." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:100 +msgid "" +"You can also just do the inventory of a serial number. In this case, you " +"will have to fill in the serial number. You can also create a new one from " +"here. Just type in the number, a window will pop out to link it to a " +"product." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:109 +msgid "Serial Number traceability" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:111 +msgid "" +"The serial number given to these items allow you to keep track of where they" +" were received, put in stock, to whom they were sold and where they were " +"shipped to." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:115 +msgid "" +"To track an item, open the **Inventory** module, and in " +":menuselection:`Inventory Control --> Serial Numbers/lots`, click on the " +"serial number corresponding to your search." +msgstr "" + +#: ../../inventory/management/misc.rst:3 +msgid "Miscellaneous Operations" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:3 +msgid "How to manage stock that you don't own?" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:8 +msgid "" +"Some suppliers can sometimes offer you to store and sell products without " +"having to buy those items: this technique is called **consignee stock**." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:12 +msgid "" +"Consignee stock is a great way for manufacturers and suppliers to launch new" +" products. As resellers may be reluctant to buying a product that they are " +"not sure to be able to sell, consignee stock will allow them to propose an " +"item to check its market without having to pay for it in the first place." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:18 +msgid "" +"Odoo has the ability to manage consignee stocks through the advanced " +"settings." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:24 +msgid "" +"Open the menu :menuselection:`Inventory --> Configuration --> Settings`, and" +" in the **Product Owners** section, select **Manage consignee stocks " +"(advanced)**, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:32 +msgid "Reception of Consignee Stock" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:34 +msgid "" +"In the Inventory's Dashboard, open the **Receipts** and create a new " +"reception. You can see that in the right side of the page, a new **Owner** " +"line has appeared. You can specify the partner which owns the stock or leave" +" it blank if you are the owner." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:3 +msgid "How to configure and run schedulers?" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:6 +msgid "What is a scheduler" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:8 +msgid "" +"The scheduler is the calculation engine which plans and prioritises " +"production and purchasing automatically according to the rules defined on " +"products. By default, the scheduler is set to run once a day (Odoo " +"automatically creates a **Scheduled Action** for this)." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:14 +msgid "Calculating Requirements / Scheduling" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:16 +msgid "" +"Scheduling only validates procurements that are confirmed but not yet " +"started. These procurement reservations will themselves start production, " +"tasks or purchases depending on the configuration of the requested product." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:21 +msgid "" +"You take into account the priority of operations when starting reservations " +"and procurements. Urgent requests, those with a date in the past, or " +"requests with a date earlier than the others will be started first. In case " +"there are not enough products in stock to satisfy all the requests, you can " +"be sure that the most urgent requests will be produced first." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:29 +msgid "Configure and run the scheduler" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:32 +msgid "Run the scheduler manually" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:34 +msgid "" +"This feature is not visible by default. You have to enable **debug mode** to" +" see this. To enable debug mode, go to :menuselection:`Help --> About` and " +"click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:38 +msgid "" +"You can also start the scheduler manually from the menu " +":menuselection:`Inventory --> Schedulers --> Run Schedulers`. The scheduler " +"uses all the relevant parameters defined for products, suppliers and the " +"company to determine the priorities between the different production orders," +" deliveries and supplier purchases." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:48 +msgid "Configure and run the scheduler (only for advanced users)" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:50 +msgid "" +"This feature is not visible by default. You have to enable **debug mode** to" +" see this. To enable debug mode, go to :menuselection:`Help -> About` and " +"click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:54 +msgid "" +"You can set the starting time of the scheduler by modifying the " +"corresponding action in the menu :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`. Modify the Run mrp Scheduler " +"configuration." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:63 +msgid ":doc:`../delivery/scheduled_dates`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:3 +msgid "How to scrap products?" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:8 +msgid "" +"Scrap means waste that either has no economic value or only the value of its" +" basic material" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:11 +msgid "content recoverable through recycling." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:13 +msgid "" +"In your warehouse you sometimes find products that are damaged or that are " +"unusable due to expiry or for some other reason. You often notice this " +"during picking or physical inventory." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:17 +msgid "" +"Since you cannot normally sell or store these products, you have to scrap " +"product." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:20 +msgid "" +"When goods are scrapped they are not reflected in the system as a part of " +"the inventory. The scrapped material will be physically moved to scrap area." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:27 +msgid "" +"When you install inventory management, odoo automatically creates one " +"default scrap location, namely **Virtual location/Scrapped**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:30 +msgid "" +"To create an extra scrap location, Go to :menuselection:`Inventory --> " +"Configuration --> Setting` and check **Manage several locations per " +"warehouse**, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:38 +msgid "" +"After applying **Manage several location per warehouse**, you can create a " +"new scrap location in :menuselection:`Configuration --> Warehouse Management" +" --> Locations.`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:43 +msgid "" +"To define a scrap location, you have to check **Is a Scrap Location?** on " +"location form view." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:47 +msgid "Different ways to scrap product" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:49 +msgid "Odoo provides several ways to scrap products." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:52 +msgid "1) Scrap from Receipt (Initial Demand tab)." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:54 +msgid "" +"To scrap product from incoming shipment, Go to :menuselection:`Inventory -->" +" Dashboard --> Receipts`." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:60 +msgid "" +"Open the incoming shipment, and in the **Initial demand** tab, click on the " +"scrap products button." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:67 +msgid "2) Scrap from delivery order (Initial Demand tab) ." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:69 +msgid "" +"To scrap product from outgoing shipment, Go to :menuselection:`Inventory -->" +" Dashboard --> Delivery Orders`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:75 +msgid "" +"Open the outgoing shipment, and in the **Initial demand** tab, click on the " +"scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:82 +msgid "3) Scrap from internal transfer (Initial Demand tab)." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:84 +msgid "" +"To scrap product from internal transfer, Go to :menuselection:`Inventory -->" +" Dashboard --> Receipts`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:90 +msgid "" +"Open the internal transfer, and in the **Initial demand** tab, click on the " +"scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:96 +msgid "" +"When you click on scrap button, a popup will open. You can enter the " +"quantity of products, and specify the scrap location, then click on " +"**Scrap**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:104 +msgid "" +"To allow change scrap location on wizard, you have to select **Manage " +"several location per warehouse** in the settings at " +":menuselection:`Inventory --> Configuration --> Setting`" +msgstr "" + +#: ../../inventory/management/reporting.rst:3 +msgid "Valuation Methods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:5 +msgid "How to do an inventory valuation? (Anglo-Saxon Accounting)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:7 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:7 +msgid "" +"Every year your inventory valuation has to be recorded in your balance " +"sheet. This implies two main choices:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:10 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:10 +msgid "" +"the way you compute the cost of your stored items (Standard vs. Average vs. " +"Real Price);" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:13 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:13 +msgid "" +"the way you record the inventory value into your books (periodic vs. " +"Perpetual)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:17 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:17 +msgid "Costing Method" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:63 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:64 +msgid "Standard Price" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:28 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:73 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:128 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:181 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:29 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:74 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:129 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:182 +msgid "Operation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:29 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:74 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:129 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:182 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:30 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:75 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:130 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:183 +msgid "Unit Cost" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:30 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:75 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:130 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:183 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:31 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:76 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:131 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:184 +msgid "Qty On Hand" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:31 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:76 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:131 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:184 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:32 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:77 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:132 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:185 +msgid "Delta Value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:32 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:77 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:132 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:185 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:33 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:78 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:133 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:186 +msgid "Inventory Value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:34 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:39 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:44 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:49 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:55 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:84 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:139 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:192 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:202 +msgid "$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:35 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:80 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:135 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:188 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:36 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:81 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:136 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:189 +msgid "0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:37 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:79 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:82 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:134 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:137 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:187 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:190 +msgid "$0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:38 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:83 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:138 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:191 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:40 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:85 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:140 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:193 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:41 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:86 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:141 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:194 +msgid "8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:41 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:86 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:141 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:194 +msgid "+8*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:42 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:87 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:142 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:195 +msgid "$80" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:43 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:88 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:143 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:196 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:45 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:90 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:145 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:198 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:46 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:91 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:146 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:199 +msgid "12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:46 +msgid "+4*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:47 +msgid "$120" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:48 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:93 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:148 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:201 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:49 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:94 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:149 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:202 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:50 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:95 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:150 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:203 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:51 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:96 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:151 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:204 +msgid "2" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-10*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:53 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:206 +msgid "$20" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:54 +msgid "Receive 2 Products at $9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:56 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:101 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:156 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:209 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:57 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:102 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:157 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:210 +msgid "4" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:57 +msgid "+2*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:58 +msgid "$40" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:60 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:61 +msgid "" +"**Standard Price** means you estimate the cost price based on direct " +"materials, direct labor and manufacturing overhead at the end of a specific " +"period (usually once a year). You enter this cost price in the product form." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:118 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:119 +msgid "Average Price" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:89 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:94 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:144 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:197 +msgid "$12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:91 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:146 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:199 +msgid "+4*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:92 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:147 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:200 +msgid "$144" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-10*$12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:98 +msgid "$24" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:99 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:154 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:207 +msgid "Receive 2 Products at $6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:100 +msgid "$9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:102 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:157 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:210 +msgid "+2*$6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:103 +msgid "$36" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:105 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:106 +msgid "" +"The **Average Price** method recomputes the cost price as a receipt order " +"has been processed, based on prices defined in tied purchase orders: FORMULA" +" (see here attached)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:109 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:110 +msgid "The average cost does not change when products leave the warehouse." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:111 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:112 +msgid "" +"From an accounting point of view, this method is mainly justified in case of" +" huge purchase price variations and is quite unusual due to its operational " +"complexity. Your actually need a software like Odoo to easily keep this cost" +" up-to-date." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:116 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:117 +msgid "" +"This method is dedicated to advanced users. It requires well established " +"business processes because the order in which you process receipt orders " +"matters in the cost computation." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:171 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:172 +msgid "FIFO" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:149 +msgid "$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-8*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-2*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:153 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:211 +msgid "$32" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:155 +msgid "$11" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:158 +msgid "$44" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:160 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:213 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:161 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:214 +msgid "" +"For **Real Price** (FIFO, LIFO, FEFO, etc), the costing is further refined " +"by the removal strategy set on the warehouse location or product's internal " +"category. The default strategy is FIFO. With such method, your inventory " +"value is computed from the real cost of your stored products (cfr. " +"Quantitative Valuation) and not from the cost price shown in the product " +"form. Whenever you ship items, the cost price is reset to the cost of the " +"last item(s) shipped. This cost price is used to value any product not " +"received from a purchase order (e.g. inventory adjustments)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:170 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:171 +msgid "" +"FIFO is advised if you manage all your workflow into Odoo (Sales, Purchases," +" Inventory). It suits any kind of users." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 +msgid "LIFO (not accepted in IFRS)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-4*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-6*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:208 +msgid "$8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 +msgid "LIFO is not permitted outside the United States." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:225 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:226 +msgid "" +"Odoo allows any method. The default one is **Standard Price**. To change it," +" check **Use a 'Fixed', 'Real' or 'Average' price costing method** in " +"Purchase settings. Then set the costing method from products' internal " +"categories. Categories show up in the Inventory tab of the product form." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:231 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:232 +msgid "" +"Whatever the method is, Odoo provides a full inventory valuation in " +":menuselection:`Inventory --> Reports --> Inventory Valuation` (i.e. current" +" quantity in stock * cost price)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:236 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:237 +msgid "Periodic Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:238 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:239 +msgid "" +"In a periodic inventory valuation, goods reception and outgoing shipments " +"have no direct impact in the accounting. At the end of the month or year, " +"the accountant posts one journal entry representing the value of the " +"physical inventory." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:243 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:244 +msgid "" +"This is the default configuration in Odoo and it works out-of-the-box. Check" +" following operations and find out how Odoo is managing the accounting " +"postings." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +msgid "Vendor Bill" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "\\" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "Debit" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "Credit" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 +msgid "Assets: Inventory" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 +msgid "50" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 +msgid "Assets: Deferred Tax Assets" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 +msgid "4.68" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 +msgid "Liabilities: Accounts Payable" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 +msgid "54.68" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 +#: ../../inventory/overview/concepts/double-entry.rst:30 +#: ../../inventory/overview/concepts/double-entry.rst:45 +#: ../../inventory/overview/concepts/double-entry.rst:52 +#: ../../inventory/overview/concepts/double-entry.rst:57 +#: ../../inventory/overview/concepts/double-entry.rst:64 +#: ../../inventory/overview/concepts/double-entry.rst:72 +msgid "Configuration:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:261 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:262 +msgid "" +"Purchased Goods: defined on the product or on the internal category of " +"related product (Expense Account field)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +msgid "" +"Deferred Tax Assets: defined on the tax used on the purchase order line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:264 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:264 +msgid "Accounts Payable: defined on the vendor related to the bill" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:265 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:265 +msgid "Goods Receptions" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:266 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:287 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:266 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:286 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 +msgid "No Journal Entry" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 +msgid "Customer Invoice" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 +msgid "Revenues: Sold Goods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 +msgid "100" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 +msgid "Liabilities: Deferred Tax Liabilities" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 +msgid "9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 +msgid "Assets: Accounts Receivable" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 +msgid "109" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:279 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:279 +msgid "" +"Revenues: defined on the product or on the internal category of related " +"product (Income Account field)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:281 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:280 +msgid "Deferred Tax Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 +msgid "Accounts Receivable: defined on the customer (Receivable Account)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 +msgid "" +"The fiscal position used on the invoice may have a rule that replaces the " +"Income Account or the tax defined on the product by another one." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:286 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:285 +msgid "Customer Shipping" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 +msgid "Manufacturing Orders" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:295 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:294 +msgid "" +"At the end of the month/year, your company does a physical inventory or just" +" relies on the inventory in Odoo to value the stock into your books." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:298 +msgid "" +"Then you need to break down the purchase balance into both the inventory and" +" the cost of goods sold using the following formula:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:301 +msgid "" +"Cost of goods sold (COGS) = Starting inventory value + Purchases – Closing " +"inventory value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:303 +msgid "To update the stock valuation in your books, record such an entry:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 +msgid "Assets: Inventory (closing value)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 +msgid "X" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 +msgid "Expenses: Cost of Good Sold" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 +msgid "Expenses: Purchased Goods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 +msgid "Assets: Inventory (starting value)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:319 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:319 +msgid "Perpetual Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:321 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:321 +msgid "" +"In a perpetual inventory valuation, goods receptions and outgoing shipments " +"are posted in your books in real time. The books are therefore always up-to-" +"date. This mode is dedicated to expert accountants and advanced users only. " +"As opposed to periodic valuation, it requires some extra configuration & " +"testing." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:328 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:328 +msgid "Let's take the case of a reseller." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:340 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:340 +msgid "**Configuration:**" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:342 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:342 +msgid "Accounts Receivable/Payable: defined on the partner (Accounting tab)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:344 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:344 +msgid "" +"Deferred Tax Assets/Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:347 +msgid "" +"Revenues/Expenses: defined by default on product's internal category and can" +" be set in product form (Accounting tab) as a specific replacement value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:351 +msgid "" +"Goods Received Not Purchased: to set as Stock Input Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:354 +msgid "" +"Goods Issued Not Invoiced: to set as Stock Output Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:357 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:352 +msgid "" +"Inventory: to set as Stock Valuation Account in product's internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:359 +msgid "" +"Price Difference: to set in product's internal category or in product form " +"as a specific replacement value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:364 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:356 +msgid ":doc:`../../routes/strategies/removal`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:365 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:357 +msgid ":doc:`../../../accounting/others/inventory/avg_price_valuation`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:366 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:358 +msgid ":doc:`../../routes/costing/landed_costs`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:5 +msgid "How to do an inventory valuation? (Continental Accounting)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:35 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:40 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:45 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:50 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:56 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:85 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:140 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:193 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:203 +msgid "€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:38 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:80 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:83 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:135 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:138 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:188 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:191 +msgid "€0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:39 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:84 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:139 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:192 +msgid "Receive 8 Products at €10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:42 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:87 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:142 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:195 +msgid "+8*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:43 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:88 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:143 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:196 +msgid "€80" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:44 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:89 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:144 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:197 +msgid "Receive 4 Products at €16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:47 +msgid "+4*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:48 +msgid "€120" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-10*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:54 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:207 +msgid "€20" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:55 +msgid "Receive 2 Products at €9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:58 +msgid "+2*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:59 +msgid "€40" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:90 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:95 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:145 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:198 +msgid "€12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:92 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:147 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:200 +msgid "+4*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:93 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:148 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:201 +msgid "€144" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-10*€12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:99 +msgid "€24" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:100 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:155 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:208 +msgid "Receive 2 Products at €6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:101 +msgid "€9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:103 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:158 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:211 +msgid "+2*€6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:104 +msgid "€36" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:150 +msgid "€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-8*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-2*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:154 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:212 +msgid "€32" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:156 +msgid "€11" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:159 +msgid "€44" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-4*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-6*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:209 +msgid "€8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:297 +msgid "" +"Create a journal entry to move the stock variation value from your " +"Profit&Loss section to your assets." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 +msgid "Expenses: Inventory Variations" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:311 +msgid "" +"If the stock value decreased, the **Inventory** account is credited and te " +"**Inventory Variations** debited." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:346 +msgid "" +"Revenues/Expenses: defined by default on product's internal category; can be" +" also set in product form (Accounting tab) as a replacement value." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:349 +msgid "" +"Inventory Variations: to set as Stock Input/Output Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/overview/concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:5 +msgid "Double-Entry Inventory Management" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:7 +msgid "" +"A double-entry inventory has no stock input, output (disparition of " +"products) or transformation. Instead, all operations are stock moves between" +" locations (possibly virtual)." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:16 +msgid "Operations" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:18 +msgid "" +"Stock moves represent the transit of goods and materials between locations." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:30 +msgid "Production Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:24 +msgid "Consume:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "2 Wheels: Stock → Production" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bike Frame: Stock → Production" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:26 +msgid "Produce:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:27 +msgid "1 Bicycle: Production → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Stock: the location the Manufacturing Order is initiated from" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Production: on the product form, field \"Production Location\"" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:36 +msgid "Drop-shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:33 +msgid "1 Bicycle: Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:36 +msgid "Configurarion:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Supplier: on the product form" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Customer: on the sale order itself" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:45 +msgid "Client Delivery" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:39 +msgid "Pick" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:40 +msgid "1 Bicycle: Stock → Packing Zone" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:41 +msgid "Pack" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:42 +msgid "1 Bicycle: Packing Zone → Output" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:43 +#: ../../inventory/shipping.rst:3 +msgid "Shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:44 +msgid "1 Bicycle: Output → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "on the pick+pack+ship route for the warehouse" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:52 +msgid "Inter-Warehouse transfer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:49 +msgid "Transfer:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Warehouse 1 → Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Warehouse 2: the location the transfer is initiated from" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Warehouse 1: on the transit route" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:57 +msgid "Broken Product (scrapped)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:55 +msgid "1 Bicycle: Warehouse → Scrap" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:58 +msgid "Scrap: Scrap Location when creating the scrapping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:60 +msgid "Missing products in inventory" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:61 +msgid "1 Bicycle: Warehouse → Inventory Loss" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:62 +msgid "Extra products in inventory" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:63 +msgid "1 Bicycle: Inventory Loss → Warehouse" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:65 +msgid "Inventory Loss: \"Inventory Location\" field on the product" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:72 +msgid "Reception" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Supplier → Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Input → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Supplier: purchase order supplier" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Input: \"destination\" field on the purchase order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:75 +msgid "Analysis" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:77 +msgid "" +"Inventory analysis can use products count or products value (= number of " +"products * product cost)." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:80 +msgid "For each inventory location, multiple data points can be analysed:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:148 +msgid "Procurements & Procurement Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:150 +msgid "" +"A procurement is a request for a specific quantity of products to a specific" +" location. They can be created manually or automatically triggered by:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:159 +msgid "New sale orders" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:157 +#: ../../inventory/overview/concepts/double-entry.rst:162 +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "Effect" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:157 +msgid "" +"A procurement is created at the customer location for every product ordered " +"by the customer (you have to deliver the customer)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:160 +msgid "" +"Procurement Location: on the customer, field \"Customer Location\" " +"(property)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:164 +msgid "Minimum Stock Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:163 +msgid "A procurement is created at the rule's location." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:165 +msgid "Procurement location: on the rule, field \"Location\"" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "Procurement rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "A new procurement is created on the rule's source location" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:170 +msgid "" +"*Procurement rules* describe how procurements on specific locations should " +"be fulfilled e.g.:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:173 +msgid "where the product should come from (source location)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:174 +msgid "" +"whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made " +"To Stock)`" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:182 +msgid "Routes" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:184 +msgid "" +"Procurement rules are grouped in routes. Routes define paths the product " +"must follow. Routes may be applicable or not, depending on the products, " +"sales order lines, warehouse,..." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:188 +msgid "" +"To fulfill a procurement, the system will search for rules belonging to " +"routes that are defined in (by order of priority):" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:202 +#: ../../inventory/settings/warehouses.rst:3 +msgid "Warehouses" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:194 +msgid "Warehouse Route Example: Pick → Pack → Ship" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:196 +msgid "Picking List:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:197 +msgid "Pick Zone → Pack Zone" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:198 +msgid "Pack List:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:199 +msgid "Pack Zone → Gate A" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:201 +msgid "Delivery Order:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:201 +msgid "Gate A → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:203 +msgid "" +"Routes that describe how you organize your warehouse should be defined on " +"the warehouse." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "A Product" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:205 +msgid "Product Route Example: Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:207 +#: ../../inventory/overview/concepts/double-entry.rst:217 +msgid "Reception:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:208 +#: ../../inventory/overview/concepts/double-entry.rst:218 +msgid "Supplier → Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:209 +msgid "Confirmation:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:210 +msgid "Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "Storage:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:221 +msgid "Product Category" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:215 +msgid "Product Category Route Example: cross-dock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:219 +msgid "Cross-Docks:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:220 +msgid "Input → Output" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:221 +msgid "Delivery:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:222 +msgid "Output → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Sale Order Line" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:224 +msgid "Sale Order Line Example: Drop-shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Order:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:230 +msgid "Push Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:232 +msgid "" +"Push rules trigger when products enter a specific location. They " +"automatically move the product to a new location. Whether a push rule can be" +" used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:240 +#: ../../inventory/settings/products/uom.rst:88 +msgid "Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:239 +msgid "Product lands in Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:240 +msgid "Push 1: Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:241 +msgid "Push 2: Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:244 +msgid "Warehouse Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:243 +msgid "Product lands in Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:244 +msgid "Push: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:247 +msgid "Procurement Groups" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:249 +msgid "" +"Routes and rules define inventory moves. For every rule, a document type is " +"provided:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:252 +msgid "Picking" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:253 +msgid "Packing" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:254 +msgid "Delivery Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:255 +msgid "Purchase Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:256 +msgid "..." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:258 +msgid "" +"Moves are grouped within the same document type if their procurement group " +"and locations are the same." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:261 +msgid "" +"A sale order creates a procurement group so that pickings and delivery " +"orders of the same order are grouped. But you can define specific groups on " +"reordering rules too. (e.g. to group purchases of specific products " +"together)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:3 +msgid "Terminologies" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:5 +msgid "" +"**Warehouse**: A warehouse in Odoo is a location where you store products. " +"It is either a physical or a virtual warehouse. It could be a store or a " +"repository." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:9 +msgid "" +"**Location**: Locations are used to structure storage zones within a " +"warehouse. In addition to internal locations (your warehouse), Odoo has " +"locations for suppliers, customers, inventory loss counter-parts, etc." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:14 +msgid "" +"**Lots**: Lots are a batch of products identified with a unique barcode or " +"serial number. All items of a lot are from the same product. (e.g. a set of " +"24 bottle) Usually, lots come from manufacturing order batches or " +"procurements." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:19 +msgid "" +"**Serial Number**: A serial number is a unique identifier of a specific " +"product. Technically, serial numbers are similar to having a lot of 1 unique" +" item." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:23 +msgid "" +"**Unit of Measure**: Define how the quantity of products is expressed. " +"Meters, Pounds, Pack of 24, Kilograms,… Unit of measure of the same category" +" (ex: size) can be converted to each others (m, cm, mm) using a fixed ratio." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:28 +msgid "" +"**Consumable**: A product for which you do not want to manage the inventory " +"level (no quantity on hand or forecasted) but that you can receive and " +"deliver. When this product is needed Odoo suppose that you always have " +"enough stock." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:33 +msgid "" +"**Stockable**: A product for which you want to manage the inventory level." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:36 +msgid "" +"**Package:** A package contains several products (identified by their serial" +" number/lots or not). Example: a box containing knives and forks." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:40 +msgid "" +"**Procurement**: A procurement is a request for a specific quantity of " +"products to a specific location. Procurement are automatically triggered by " +"other documents: Sale orders, Minimum Stock Rules, and Procurement rules. " +"You can trigger the procurement manually. When procurements are triggered " +"automatically, you should always pay attention for the exceptions (e.g. a " +"product should be purchased from a vendor, but no supplier is defined)." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:48 +msgid "" +"**Routes**: Routes define paths the product must follow. Routes may be " +"applicable or not, depending on the products, sales order lines, warehouse,…" +" To fulfill a procurement, the system will search for rules belonging to " +"routes that are defined in the related product/sale order." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:54 +msgid "" +"**Push Rules**: Push rules trigger when products enter a specific location. " +"They automatically move the product to a new location. Whether a push rule " +"can be used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:58 +msgid "" +"**Procurement Rules** or **Pull Rules**: Procurement rules describe how " +"procurements on specific locations should be fulfilled e.g.: where the " +"product should come from (source location), whether the procurement is MTO " +"or MTS,..." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:63 +msgid "" +"**Procurement Group**: Routes and rules define inventory moves. For every " +"rule, a document type is provided: Picking, Packing, Delivery Order, " +"Purchase Order,… Moves are grouped within the same document type if their " +"procurement group and locations are the same." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:69 +msgid "" +"**Stock Moves**: Stock moves represent the transit of goods and materials " +"between locations." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:72 +msgid "" +"**Quantity On Hand**: The quantity of a specific product that is currently " +"in a warehouse or location." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:75 +msgid "" +"**Forecasted Quantity**: The quantity of products you can sell for a " +"specific warehouse or location. It is defined as the Quantity on Hand - " +"Future Delivery Orders + Future incoming shipments + Future manufactured " +"units." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:80 +msgid "" +"**Reordering Rules**: It defines the conditions for Odoo to automatically " +"trigger a request for procurement (buying at a supplier or launching a " +"manufacturing order). It is triggered when the forecasted quantity meets the" +" minimum stock rule." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:85 +msgid "" +"**Cross-Dock**: Cross-docking is a practice in the logistics of unloading " +"materials from an incoming semi-trailer truck or railroad car and loading " +"these materials directly into outbound trucks, trailers, or rail cars, with " +"no storage in between. (does not go to the stock, directly from incoming to " +"packing zone)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:91 +msgid "" +"**Drop-Shipping**: move products from the vendor/manufacturer directly to " +"the customer (could be retailer or consumer) without going through the usual" +" distribution channels. Products are sent directly from the vendor to the " +"customer, without passing through your own warehouse." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:97 +msgid "" +"**Removal Strategies**: the strategy to use to select which product to pick " +"for a specific operation. Example: FIFO, LIFO, FEFO." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:100 +msgid "" +"**Putaway Strategies**: the strategy to use to decide in which location a " +"specific product should be set when arriving somewhere. (example: cables " +"goes in rack 3, storage A)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:104 +msgid "" +"**Scrap**: A product that is broken or outdated. Scrapping a product removes" +" it from the stock." +msgstr "" + +#: ../../inventory/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:3 +msgid "From procurement to delivery" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:8 +msgid "" +"Inventory is the heart of your business. It can be really complicated, but " +"with Odoo, doing a receipt or a delivery has never been easier. We will show" +" you in this document how easy to do a full process, from the receipt to the" +" delivery." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:13 +msgid "" +"Odoo inventory is fully integrated with other applications, such as " +"**Purchase**, **Sales** or **Inventory**. But is not limited to those " +"processes, it is also fully integrated with our **e-Commerce**, " +"**Manufacturing** and **Repairs** applications." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:19 +msgid "How to process a receipt ?" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:22 +msgid "Install Purchase application" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:24 +msgid "" +"First, you will need to install the **Purchase Management** application. Go " +"to :menuselection:`Apps` and install it." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:31 +msgid "Make a purchase order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:33 +msgid "" +"Go to the **Purchases** applications. The first screen is the **Request for " +"Quotation** list. Click on the **Create** button." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:36 +msgid "" +"Fill in the **Vendor** information and click on **Add an Item** to add some " +"products to your request for quotation." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:42 +msgid "" +"Click on **Confirm order** when you are sure about the products, prices and " +"quantity." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:46 +msgid "Retrieve the Receipt" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:48 +msgid "You can retrieve the receipt order in 2 ways:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:51 +msgid "From the purchase order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:53 +msgid "" +"On the top right of your purchase order, you will see a button with the " +"related **Receipt**:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:59 +#: ../../inventory/overview/process/sale_to_delivery.rst:136 +msgid "Click on it to see the **Transfer order**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:62 +#: ../../inventory/overview/process/sale_to_delivery.rst:139 +msgid "From the Inventory Dashboard" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:64 +msgid "" +"When opening the **Inventory** application, click on **# to receive** to see" +" the list of your deliveries to process." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:70 +msgid "In the list, click on the one related to the purchase order:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:76 +msgid "Process the Receipt" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:81 +#: ../../inventory/overview/process/sale_to_delivery.rst:162 +msgid "" +"To process the stock transfer. Simply click on **Validate** to complete the " +"transfer. A message will appear asking if you want to process the whole " +"order, accept it by clicking on **Apply**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:86 +msgid "" +"Procurements can be automated. Please read our document " +":doc:`../../management/adjustment/min_stock_rule_vs_mto` for more " +"information." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:91 +msgid "How to process a delivery order ?" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:94 +msgid "Install Sales application" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:96 +msgid "" +"First, you will need to install the **Sales Management** application. Go to " +":menuselection:`Apps` and install it." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:103 +msgid "Place a sale order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:105 +msgid "" +"Go to the **Sales** applications. Click on the **Quotations** button of your" +" team." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:111 +msgid "" +"You will get the list of all your quotations. Click on the **Create** " +"button." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:114 +msgid "" +"Fill in the **Customer informations** and click on **Add an Item** to add " +"some products to your quotation." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:120 +msgid "Click on **Confirm sale** to place the order." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:123 +msgid "Retrieve the Delivery order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:125 +msgid "You can retrieve the delivery order in 2 ways:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:128 +msgid "From the sale order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:130 +msgid "" +"On the top right of your sale order, you will see a button with the related " +"**Delivery**:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:141 +msgid "" +"When opening the **Inventory** application, click on **# to do** to see the " +"list of your receipts to process." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:147 +msgid "In the list, click on the one related to the sale order:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:153 +msgid "" +"If the product is not in stock, the sale order will be listed as **Waiting**" +" on your dashboard." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:157 +msgid "Process the delivery" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:167 +msgid "E-Commerce orders are processed the same way." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:170 +msgid "" +"You can easily integrate your delivery orders with different delivery " +"methods. Please read the document " +":doc:`../../shipping/setup/delivery_method`." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:175 +msgid "Advanced flows" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:177 +msgid "" +"In this document, the flows that are explained are the most simple ones. " +"Odoo also suit for companies having advanced warehouse management." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:180 +msgid "" +"By default, only **receipts** and **deliveries** are configured but you can " +"activate the use of multi-locations and multi-warehouses to do **internal " +"transfers**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:184 +msgid "**Routes**: you can automate flows with push and pull rules" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:186 +msgid "" +"**Multi-step** receipts and deliveries can be easily configured for each " +"warehouse" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:189 +msgid "" +"Much more: **Barcode scanning**, **serial numbers**, **lots**, **cross-" +"docking**, **dropshipping**, integration with a **third-party** shipper, " +"**putaway** and **removal** strategies.... All of it is possible with Odoo." +msgstr "" + +#: ../../inventory/overview/start.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:3 +msgid "How to setup Odoo inventory?" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:5 +msgid "" +"The Odoo Inventory application has an implementation guide that you should " +"follow to configure it. It's a step-by-step manual with links to the " +"different screens you need." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:9 +msgid "" +"Once you have installed the **Inventory** application, click on the top-" +"right progress bar to get access to the implementation guide." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:15 +msgid "The implementation guide helps you through the following steps:" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:17 +msgid "Set up your warehouse" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:19 +msgid "Import your vendors" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:21 +msgid "Import your products" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:23 +msgid "Set up the initial inventory" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:25 +msgid "Configure your sales and purchase flows" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:27 +msgid "Set up replenishment mechanisms" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:29 +msgid "" +"Configure advanced features like package, traceability, routes and inventory" +" valuation." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:37 +msgid "" +"If you want to set up operations with barcode scanner in your warehouse, you" +" should install the **Barcode** application that adds features on top of the" +" inventory application. The barcode application will guide you to configure " +"and use your scanner optimally." +msgstr "" + +#: ../../inventory/routes.rst:3 +msgid "Advanced Routes" +msgstr "" + +#: ../../inventory/routes/concepts.rst:3 +msgid "Concepts" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:3 +msgid "How to organize a cross-dock in your warehouse?" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:5 +msgid "" +"Cross dock area is temporarily area where we are not storing any product " +"instead just managing place according to delivery for further customer. This" +" will save lot of time for inter warehouse transfer and storing process. We " +"are managing our products with docking area where product directly place " +"from supplier location and transfer this to gate pass for customer delivery." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:17 +msgid "" +"For more information on how to organise your warehouse, read `What is cross " +"docking and is it for me? `_" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:24 +msgid "Warehouse and routes" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:26 +msgid "" +"In the **Inventory** module, open :menuselection:`Configuration --> Settings" +" --> Location & Warehouse`, then in **Routes**, select **Advanced routing of" +" products using rules**, then click on **Apply**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:33 +msgid "" +"Open :menuselection:`Configuration --> Warehouse Management --> Warehouses`," +" then open the warehouse you want to cross-dock from and click on **Edit**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:36 +msgid "In the **Warehouse Configuration** tab, select:" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:38 +msgid "" +"**Incoming Shipments**: Unload in input location then go to stock (2 steps)" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:41 +msgid "**Outgoing Shipments**: Ship directly from stock (Ship only)" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:43 +msgid "then click on **Save**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:48 +msgid "" +"This steps has generated a cross-docking route that you can see in " +":menuselection:`Inventory --> Configurations --> Routes --> Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:52 +msgid "Cross Docking Route" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:54 +msgid "" +"We will use the route **Buy** for first part of the flow and create a route " +"for the remaining part:" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:60 +msgid "" +"Each of the procurement rule will now be configured. Cross Dock location is " +"created as an internal physical location." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:67 +msgid ":menuselection:`Input --> Cross Dock`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:73 +msgid ":menuselection:`Cross Dock --> Output`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:79 +msgid ":menuselection:`Output --> Customer`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:82 +msgid "Product with cross dock" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:84 +msgid "" +"We have created the Vegetable Fennel product and assigned the routes created" +" above as well as the **Buy** route." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:87 +msgid "" +"We have also specified a supplier and a minimum order rule which is needed " +"for replenishment of a stockable product." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:95 +msgid ":doc:`use_routes`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:96 +msgid ":doc:`../../management/incoming/two_steps`" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:3 +msgid "How to do inter-warehouses transfers?" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:5 +msgid "" +"If you own different warehouses you might want to transfer goods from one " +"warehouse to the other. This is very easy thanks to the inventory " +"application in Odoo." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:12 +msgid "" +"First of all you have to select the multi locations option. Go to " +":menuselection:`Configuration --> Settings` in the **Inventory " +"application**. Then tick the **Manage several locations per warehouse** " +"option. Please don't forget to **apply** your changes." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:22 +msgid "" +"This option should also be ticked if you wish to manage different locations " +"and routes in your warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:26 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:9 +msgid "Creating a new warehouse" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:28 +msgid "" +"The next step is to create your new warehouse. In the Inventory application " +"click on :menuselection:`Configuration --> Warehouse Management --> " +"Warehouses`. You are now able to create your warehouse by clicking on " +"**Create**." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:33 +msgid "" +"Fill in a **Warehouse Name** and a **Short Name**. The short name is 5 " +"characters maximum." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:41 +msgid "" +"please note that the **Short Name** is very important as it will appear on " +"your transfer orders and other warehouse documents. It might be smart to use" +" an understandable one (e.g.: WH/[first letters of location])." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:46 +msgid "" +"If you go back to your dashboard, new operations will automatically have " +"been generated for your new warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:53 +msgid "Creating a new inventory" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:55 +msgid "" +"If you create a new warehouse you might already have an existing physical " +"inventory in it. In that case you should create an inventory in Odoo, if not" +" you can skip this step." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:59 +msgid "" +"Go into the inventory application, select :menuselection:`Inventory Control " +"--> Inventory Adjustment`. You can then create a new inventory by clicking " +"on **Create**. Fill in the **Inventory Reference**, **Date** and be sure to " +"select the right warehouse and location." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:67 +msgid "" +"Next, click on **Start Inventory**. A new window will open where you will be" +" able to input your existing products. Select add an item and indicate the " +"**Real Quantity** available in the warehouse. The theoretical quantity can " +"not be changed as it represents a computed quantity from purchase and sales " +"orders." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:76 +msgid "" +"Don't forget to validate your inventory once you have recorder the state of " +"all yours product." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:80 +msgid "Create an internal transfer" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:82 +msgid "" +"The final step is to create your internal transfer. If you want to tranfer 2" +" units of a product from your first warehouse to another one in Brussels, " +"proceed as follows:" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:86 +msgid "" +"From your dashboard, select a internal movement of one of the two " +"warehouses. To do so, click on :menuselection:`More --> Transfer`." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:92 +msgid "" +"A new window will open where you will be able to select the source location " +"zone (in this case our \"old warehouse\") and the destination location zone " +"(in this case our \"new\" warehouse located in Brussels)." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:96 +msgid "" +"Add the products you want to transfer by clicking on **Add an Item** and " +"don't forget to **Validate** or **Mark as TODO** once you are done." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:102 +msgid "" +"If you select **Validate**, Odoo will process all quantities to transfer." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:104 +msgid "" +"If you select **Mark as TODO**, Odoo will put the transfer in **Waiting " +"Availability** status. Click on **Reserve** to reserve the amount of " +"products in your source warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:108 +msgid "It is also possible to manually transfer each product:" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:110 +msgid "Via your dashboard, select the transfer order in the source location." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:115 +msgid "Select the right transfer order" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:120 +msgid "" +"3. Click on the little pencil logo in the lower right corner in order to " +"open the operation details window. In this new window you can manually " +"indicate how much products you process" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:129 +msgid "" +"If you decide to partially process the transfer order (e.g. a part of the " +"products can't be shipped yet due to an unexpected event), Odoo will " +"automatically ask if you wish to create a **backorder**. Create a backorder " +"if you expect to process the remaining products later, do not create a " +"backorder if you will not supply/receive the remaining products." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:3 +msgid "What is a procurement rule?" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:8 +msgid "" +"The procurement inventory control system begins with a customer's order. " +"With this strategy, companies only make enough product to fulfill customer's" +" orders. One advantage to the system is that there will be no excess of " +"inventory that needs to be stored, thus reducing inventory levels and the " +"cost of carrying and storing goods. However, one major disadvantage to the " +"pull system is that it is highly possible to run into ordering dilemmas, " +"such as a supplier not being able to get a shipment out on time. This leaves" +" the company unable to fulfill the order and contributes to customer " +"dissatisfaction." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:18 +msgid "" +"An example of a pull inventory control system is the make-to-order. The goal" +" is to keep inventory levels to a minimum by only having enough inventory, " +"not more or less, to meet customer demand. The MTO system eliminates waste " +"by reducing the amount of storage space needed for inventory and the costs " +"of storing goods." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:27 +msgid "" +"Procurement rules are part of the routes. Go to the Inventory " +"application>Configuration>Settings and tick \"Advance routing of products " +"using rules\"." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:35 +msgid "Procurement rules settings" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:37 +msgid "" +"The procurement rules are set on the routes. In the inventory application, " +"go to Configuration > Routes." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:40 +msgid "In the Procurement rules section, click on Add an item." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:45 +msgid "" +"Here you can set the conditions of your rule. There are 3 types of action " +"possibles :" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:48 +msgid "Move from another location rules" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:50 +msgid "" +"Manufacturing rules that will trigger the creation of manufacturing orders." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:53 +msgid "Buy rules that will trigger the creation of purchase orders." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:56 +msgid "" +"The Manufacturing application has to be installed in order to trigger " +"manufacturing rules." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:60 +msgid "" +"The Purchase application has to be installed in order to trigger **buy** " +"rules." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:68 +msgid "Try to create a procurement rule in our demo instance." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:71 +msgid "" +"Some Warehouse Configuration creates routes with procurement rules already " +"defined." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:75 +#: ../../inventory/routes/concepts/use_routes.rst:130 +#: ../../inventory/routes/concepts/use_routes.rst:152 +msgid ":doc:`push_rule`" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:76 +#: ../../inventory/routes/concepts/push_rule.rst:84 +#: ../../inventory/routes/concepts/use_routes.rst:153 +msgid ":doc:`inter_warehouse`" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:77 +#: ../../inventory/routes/concepts/push_rule.rst:85 +#: ../../inventory/routes/concepts/use_routes.rst:154 +msgid ":doc:`cross_dock`" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:3 +msgid "What is a push rule?" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:8 +msgid "" +"The push system of inventory control involves forecasting inventory needs to" +" meet customer demand. Companies must predict which products customers will " +"purchase along with determining what quantity of goods will be purchased. " +"The company will in turn produce enough product to meet the forecast demand " +"and sell, or push, the goods to the consumer. Disadvantages of the push " +"inventory control system are that forecasts are often inaccurate as sales " +"can be unpredictable and vary from one year to the next. Another problem " +"with push inventory control systems is that if too much product is left in " +"inventory. This increases the company's costs for storing these goods. An " +"advantage to the push system is that the company is fairly assured it will " +"have enough product on hand to complete customer orders, preventing the " +"inability to meet customer demand for the product." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:22 +msgid "" +"A push flow indicates how locations are chained with the other ones. As soon" +" as a given quantity of products is moved in the source location, a chained " +"move is automatically foreseen according to the parameters set on the flow " +"specification (destination location, delay, type of move, journal). It can " +"be triggered automatically or manually." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:31 +msgid "" +"Push rules are part of the routes. Go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings` and tick **Advance routing of products using" +" rules**." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:39 +msgid "Push rules settings" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:41 +msgid "" +"The push rules are set on the routes. Go to :menuselection:`Configuration " +"--> Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:44 +msgid "In the push rule section, click on **Add an item**." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:49 +msgid "" +"Here you can set the conditions of your rule. In this example, when a good " +"is in **Input location**, it needs to be moved to the quality control. In " +"the 3 steps receipts, another push rule will make the goods that are in the " +"quality control location move to the stock." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:59 +msgid "Try to create a push rule in our demo instance." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:62 +msgid "" +"Some warehouse configuration creates routes with push rules already defined." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:66 +msgid "Stock transfers" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:68 +msgid "" +"The push rule will trigger stock transfer. According to the rule set on your" +" route, you will see that some transfers might be ready and other are " +"waiting." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:72 +msgid "" +"The push rule that was set above will create moves from **WH/Input** " +"location to the **WH/Quality Control** location." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:78 +msgid "" +"In this example, another move is waiting according to the second push rule, " +"it defines that when the quality control is done, the goods will be moved to" +" the main stock." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:83 +#: ../../inventory/routes/concepts/use_routes.rst:128 +msgid ":doc:`procurement_rule`" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:3 +msgid "How to use routes?" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:8 +msgid "" +"A route is a collection of procurement rules and push rules. Odoo can manage" +" advanced push/pull routes configuration, for example:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:11 +msgid "Manage product manufacturing chains" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:13 +msgid "Manage default locations per product" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:15 +msgid "" +"Define routes within your warehouse according to business needs, such as " +"quality control, after sales services or supplier returns" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:18 +msgid "" +"Help rental management, by generating automated return moves for rented " +"products" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:24 +msgid "" +"Procurement rules are part of the routes. Go to the **Inventory** " +"application, :menuselection:`Configuration --> Settings` and tick **Advance " +"routing of products using rules**." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:32 +msgid "Pre-configured routes" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:34 +msgid "Odoo has some pre-configured routes for your warehouses." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:36 +msgid "" +"In the Inventory application, go to :menuselection:`Configuration --> " +"Warehouses`." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:39 +msgid "" +"In the **Warehouse Configuration** tab, **Incoming Shipments** and " +"**Outgoing Shippings** options set some routes according to your choices." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:46 +msgid "Custom Routes" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:48 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:54 +msgid "" +"First, you have to select the places where this route can be selected. You " +"can combine several choices." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:58 +msgid "Routes applied on warehouses" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:60 +msgid "" +"If you tick **Warehouses**, you have to choose on which warehouse it will be" +" applied. The route will be set for all transfer in that warehouse that " +"would meet the conditions of the procurement and push rules." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:68 +msgid "Routes applied on products" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:70 +msgid "" +"If you tick **Products**, you have to manually set on which product it will " +"be applied." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:76 +msgid "" +"Open the product on which you want to apply the routes " +"(:menuselection:`Inventory --> Control --> Products`). In the Inventory Tab," +" select the route(s):" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:84 +msgid "Routes applied on Product Category" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:86 +msgid "" +"If you tick **Product Categories**, you have to manually set on which " +"categories it will be applied." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:92 +msgid "" +"Open the product on which you want to apply the routes " +"(:menuselection:`Configuration --> Product Categories`). Select the route(s)" +" under the **Logistics** section :" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:100 +msgid "Routes applied on Sales Order lines" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:102 +msgid "" +"If you tick **Sales order lines**, you have to manually set the route every " +"time you make a sale order." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:108 +msgid "" +"In order to make it work, you also have to activate the use of the routes on" +" the sales order." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:111 +msgid "" +"In the Sales application, go to :menuselection:`Configuration --> Settings` " +"and tick **Choose specific routes on sales order lines (advanced)**." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:118 +msgid "You can now choose the routes for each lines of your sales orders:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:124 +msgid "Procurement and push rules" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:126 +msgid "Please refer to the documents:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:133 +msgid "Procurement configuration" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:135 +msgid "" +"When doing a procurement request, you can force the route you want to use. " +"On the product (:menuselection:`Inventory Control --> Products`), click on " +"**Procurement Request**. Choose the route you want to use next to " +"**Preferred Routes**:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:144 +msgid "Make-to-Order Route" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:146 +msgid "" +"If you work with no stock, or with minimum stock rules, it is better to use " +"the **Make To Order** route. Combine it with the route **Buy** or " +"**Manufacture** and it will trigger automatically the purchase order or the " +"Manufacturing Order when your products are out-of-stock." +msgstr "" + +#: ../../inventory/routes/costing.rst:3 +msgid "Product Costing" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:3 +msgid "How to integrate landed costs in the cost of the product?" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:8 +msgid "Landed costs include all charges associated to a good transfer." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:10 +msgid "Landed cost includes = Cost of product + Shipping + Customs + Risk" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:12 +msgid "" +"All of these components might not be applicable in every shipment, but " +"relevant components must be considered as a part of the landed cost. We have" +" to identify landed cost to decide sale price of product because it will " +"impact on company profits." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:21 +msgid "Applications configuration" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:23 +msgid "" +"First, you need to activate the use of the landed costs. Go to " +":menuselection:`Inventory application --> Configuration --> Setting`. Check " +"accounting option **Include landed costs in product costing computation** & " +"**Perpetual inventory valuation**, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:32 +msgid "" +"Then go to the :menuselection:`Purchase application --> Configuration --> " +"Setting`. Choose costing method **Use a 'Fixed', 'Real' or 'Average' price " +"costing method**, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:40 +msgid "Landed Cost Types" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:42 +msgid "" +"Start by creating specific products to indicate your various **Landed " +"Costs**, such as freight, insurance or custom duties. Go to " +":menuselection:`Inventory --> Configuration --> Landed Cost types`." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:52 +msgid "" +"Landed costs are only possible for products configured in real time " +"valuation with real price costing method. The costing method is configured " +"on the product category." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:57 +msgid "Link landed costs to a transfer" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:59 +msgid "" +"To calculate landed costs, go to :menuselection:`Inventory --> Inventory " +"Control --> Landed Costs`." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:62 +msgid "" +"Click on the **Create** button and select the picking(s) you want to " +"attribute landed costs." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:68 +msgid "" +"Select the account journal in which to post the landed costs. We recommend " +"you to create a specific journal for landed costs. Therefore it will be " +"easier to keep track of your postings." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:75 +msgid "" +"Click the **Compute** button to see how the landed costs will be split " +"across the picking lines." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:81 +msgid "" +"To confirm the landed costs attribution, click on the **Validate** button." +msgstr "" + +#: ../../inventory/routes/strategies.rst:3 +msgid "Putaway & Removal Strategies" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:3 +msgid "What is a putaway strategy?" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:8 +msgid "" +"A good warehouse implementation takes care that products automatically move " +"to their appropriate destination location. Putaway is the process of taking " +"products off the receiving shipment and putting them into the most " +"appropriate location." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:13 +msgid "" +"If for instance a warehouse contains volatile substances, it is important to" +" make sure that certain products are not stored close to each other because " +"of a potential chemical reaction." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:17 +msgid "" +"A putaway strategy follows the same principle as removal strategies but " +"affects the destination location. Putaway strategies are defined at the " +"location level (unlike removal strategies which are defined at the product " +"level)." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:25 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Settings` and check " +"option **Manage several location per warehouse & Advance routing of products" +" using rules**, then click on **Apply**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:33 +msgid "Setting up a strategy" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:35 +msgid "" +"Let's take as an example a retail shop where we store vegetables and fruits." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:38 +msgid "" +"We have to store this type of product in different locations to maintain " +"product quality." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:41 +msgid "" +"Suppose there is one warehouse location **WH/Stock** and there is sub " +"location **WH/Stock/Vegetables** & **WH/Stock/Fruits**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:44 +msgid "" +"You can create a putaway strategy from :menuselection:`Inventory --> " +"Configuration --> Locations`. Open any location where you want to set a " +"putaway strategy, click on **Edit** and locate the option **Put Away " +"Strategy**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:52 +msgid "" +"Open the roll-down menu and click on **Create and Edit**. This will open a " +"form view of put away strategy on which you have to set a name for the " +"strategy, and set the method and fixed location for each category." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:59 +msgid "" +"When you have entered all the necessary information, click on **Save**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:61 +msgid "" +"Now, when you purchase products with those categories, they will " +"automatically be transferred to the correct location." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:64 +msgid "" +"To check current inventory, Go to :menuselection:`Inventory --> Inventory " +"Control --> Current Inventory`" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:67 +msgid "There you can see current inventory by location." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:3 +msgid "What is a removal strategy (FIFO, LIFO, and FEFO)?" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:8 +msgid "" +"Removal strategies are usually in picking operations to select the best " +"products in order to optimize the distance for the worker, for quality " +"control purpose or due to reason of product expiration." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:12 +msgid "" +"When a product movement needs to be done, Odoo will find available products " +"that can be assigned to shipping. The way Odoo assign these products depend " +"on the **removal strategy** that is defined on the **product category** or " +"on the **location**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:20 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Settings`:" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:29 +msgid "" +"Check **Track lots or serial numbers**, **Manage several location per " +"warehouse** and **Advanced routing of products using rules**, then click on " +"**Apply**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:33 +msgid "" +"Then, open :menuselection:`Configuration --> Locations` and open the " +"location on which you want to apply a removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:40 +msgid "Types of removal strategy" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:43 +msgid "FIFO ( First In First Out )" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:45 +msgid "" +"A **First In First Out** strategy implies that the products that were " +"stocked first will move out first. Companies should use FIFO method if they " +"are selling perishable goods. Companies selling products with relatively " +"short demand cycles, such as clothes, also may have to pick FIFO to ensure " +"they are not stuck with outdated styles in inventory." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:51 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Locations`, open the " +"stock location and set **FIFO** removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:54 +msgid "Let's take one example of FIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:56 +msgid "" +"In your warehouse stock (``WH/Stock``) location, there are ``3`` lots of " +"``iPod 32 Gb`` available." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:59 +msgid "" +"You can find details of available inventory in inventory valuation report." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:65 +msgid "Create one sales order ``25`` unit of ``iPod 32 GB`` and confirm it." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:67 +msgid "" +"You can see in the outgoing shipment product that the ``Ipod 32 Gb`` are " +"assigned with the **oldest** lots, using the FIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:75 +msgid "LIFO (Last In First Out)" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:77 +msgid "" +"In this warehouse management, the products which are brought in the last, " +"moves out the first. LIFO is used in case of products which do not have a " +"shelf life." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:81 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Locations`, open the " +"stock location and set **LIFO** removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:84 +msgid "" +"In our example, let's check the current available stock of ``Ipod 32 Gb`` on" +" ``WH/Stock`` location." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:90 +msgid "Create a sale order with ``10`` units of ``Ipod 32 Gb``." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:92 +msgid "" +"You can see in the outgoing shipment product that the ``Ipod 32 Gb`` are " +"assigned with the **newest** lots, using the LIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:100 +msgid "FEFO ( First Expiry First Out )" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:102 +msgid "" +"In FEFO warehouse management, the products are dispatched from the warehouse" +" according to their expiration date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:105 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Setting`. Check the " +"option **Define Expiration date on serial numbers**. Then click on **Apply**" +" to save changes." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:112 +msgid "" +"This will allow you to set four expiration fields for each lot or serial " +"number: **best before date**, **end of life date**, **alert date** and " +"**removal date**. These dates can be set from :menuselection:`Inventory " +"Control --> Serial Numbers/Lots`." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:119 +msgid "" +"**Best Before Date**: This is the date on which the goods with this " +"serial/lot number start deteriorating, without being dangerous yet." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:122 +msgid "" +"**End of Life Date:** This is the date on which the goods with this " +"serial/lot number may become dangerous and must not be consumed." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:125 +msgid "" +"**Removal Date:** This is the date on which the goods with this serial/lot " +"number should be removed from the stock. Using the FEFO removal strategym " +"goods are picked for delivery orders using this date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:129 +msgid "" +"**Alert Date:** This is the date on which an alert should be sent about the " +"goods with this serial/lot number." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:132 +msgid "" +"Lots will be picked based on their **removal date**, from earliest to " +"latest. Lots without a removal date defined will be picked after lots with " +"removal dates." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:136 +msgid "" +"All dates except **removal date** are for informational and reporting " +"purposes only. Lots that are past any or all of the above expiration dates " +"may still be picked for delivery orders, and no alerts will be sent when " +"lots pass their **alert date**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:140 +msgid "" +"Expiration dates on lots can also be set automatically when goods are " +"received into stock. After enabling expiration dates on serial numbers, four" +" new fields will become available in the inventory tab of the product form: " +"**product life time**, **product use time**, **product removal time**, and " +"**product alert time**. When an integer is entered into one of these fields," +" the expiration date of a lot/serial of the product in question will be set " +"to the creation date of the lot/serial number plus the number of days " +"entered in the time increment field. If the time increment field is set to " +"zero, then the expiration date of a lot/serial must be defined manually " +"after the lot has been created." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:149 +msgid "" +"Each of these time increment fields is used to generate one of the lot " +"expiration date fields as follows:" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:151 +msgid "Product Use Time --> Best Before Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:153 +msgid "Product Removal Time --> Removal Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:155 +msgid "Product Life Time --> End of Life Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:157 +msgid "Product Alert Time --> Alert Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:159 +msgid "" +"To set the removal strategy on location, go to :menuselection:`Configuration" +" --> Locations` and choose FEFO." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:165 +msgid "" +"Let's take an example, there are ``3`` lots of ``ice cream`` available in " +"``WH/Stock`` location: ``LOT0001``, ``LOT0002``, ``LOT0003`` with different " +"expiration date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Lot / Serial No**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Product**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Expiration Date**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +msgid "LOT0001" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +#: ../../inventory/routes/strategies/removal.rst:174 +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "Ice Cream" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +msgid "08/20/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:174 +msgid "LOT0002" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:174 +msgid "08/10/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "LOT0003" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "08/15/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:179 +msgid "" +"We will create a sale order with ``15kg`` of ``ice cream`` and confirm it." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:181 +msgid "" +"The outgoing shipment related to sale order will make the move based on " +"removal strategy **FEFO**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:184 +msgid "" +"It will take ``10kg`` from ``LOT0002`` and ``5kg`` from ``LOT0003`` based on" +" the removal dates." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:192 +msgid ":doc:`../../management/reporting/valuation_methods_continental`" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:193 +msgid ":doc:`../../management/reporting/valuation_methods_anglo_saxon`" +msgstr "" + +#: ../../inventory/settings.rst:3 +msgid "Settings" +msgstr "" + +#: ../../inventory/settings/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:3 +msgid "How to use packages?" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:8 +#: ../../inventory/settings/products/usage.rst:31 +msgid "" +"The package is the physical container in which you put one or several " +"product." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:11 +msgid "By default, Odoo does not take into account the use of it." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:13 +msgid "" +"Once you activate the option, you will be able to manage one or several " +"packages when doing your transfers." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:19 +msgid "" +"To configure the use of packages, go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings`. µ Locate the **Packages** section and tick " +"**Record packages used on packing: pallets, boxes,...**" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:27 +#: ../../inventory/shipping/operation/multipack.rst:23 +msgid "Click on **Apply** when you are done." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:30 +msgid "Pack products" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:32 +msgid "" +"Putting products in packs is usually done when processing warehouses " +"transfers (receipt, internals or deliveries)." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:35 +msgid "" +"To be able to put products in pack, the status of your transfer has to be " +"**Available**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:41 +msgid "" +"In the operation tab, you can put your products into one or multiple " +"packages." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:44 +#: ../../inventory/shipping/operation/multipack.rst:50 +msgid "" +"Choose the quantity you want to put in the first pack in the **Done** " +"column, then click on the link **Put in Pack**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:50 +#: ../../inventory/shipping/operation/multipack.rst:56 +msgid "It will automatically create a pack with the requested quantity." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:52 +#: ../../inventory/shipping/operation/multipack.rst:58 +msgid "Do the same steps for the other pieces you want to pack in." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:57 +#: ../../inventory/shipping/operation/multipack.rst:63 +msgid "Click on **Validate** when you are done." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:60 +msgid "Whole packages transfers" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:62 +msgid "" +"If you are using several locations and/or warehouses, it is possible to " +"transfer packages with its contents." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:68 +msgid "" +"You need to configure the **Operation Type** to allow moving packages. Go to" +" :menuselection:`Configuration --> Operations Types`. Tick **Allow moving " +"packs**:" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:75 +msgid "Transfer packages" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:77 +msgid "" +"Create a transfer order. Choose the source and the destination locations, " +"then click on **Mark as todo**. Do not put anything under the **Initial " +"Demand** tab." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:84 +msgid "" +"In the Operation tab, click on **Add an item** under the **Package To Move**" +" section." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:87 +msgid "Tick the **Done** checkbox to confirm the move of the package :" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:92 +msgid "When it is finished, click on **Validate**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:95 +msgid "Packages traceability" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:97 +msgid "" +"To trace a package or check its content, go to :menuselection:`Inventory " +"Control --> Packages`." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:103 +msgid "Click on **Package Transfers** to see all its moves." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:106 +#: ../../inventory/settings/products/usage.rst:70 +msgid ":doc:`../../overview/start/setup`" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:107 +msgid ":doc:`usage`" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:108 +#: ../../inventory/settings/products/usage.rst:71 +msgid ":doc:`uom`" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:3 +msgid "How to use different units of measure?" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:8 +msgid "" +"In some cases, handling products in different unit of measures is necessary." +" For example, if you buy products in a country where the metric system is of" +" application and sell the in a country where the imperial system is used, " +"you will need to convert the units." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:13 +msgid "" +"You can set up Odoo to work with different units of measure for one product." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:19 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Settings`. In the **Products** section, select **Some products may be " +"sold/purchased in different units of measure (advanced)**, then click on " +"**Apply**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:27 +msgid "Setting up units on your products" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:29 +msgid "" +"In :menuselection:`Inventory Control --> Products`, open the product which " +"you would like to change the purchase/sale unit of measure, and click on " +"**Edit**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:32 +msgid "" +"In the **Unit of Measure** section, select the unit in which the product " +"will be sold and in which internal transfers will be done." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:35 +msgid "" +"In the **Purchase Unit of Measure** section, select the unit in which you " +"purchase the product. When you're done, click on **Save**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:42 +msgid "Click on the edit button |edit| to create new unit of measures." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:46 +msgid "Transfer from one unit to another" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:48 +msgid "" +"When doing inter-unit transfers, the rounding is automatically done by Odoo." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:51 +msgid "" +"The unit of measure can be changed throughout the whole process. The only " +"condition is that the unit of measure is part of the same category." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:54 +msgid "In this example, we are in the egg business :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:56 +msgid "We buy eggs by trays (30 eggs)" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:58 +msgid "We check all eggs individually when receiving it (quality control)" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:60 +msgid "We sell eggs by the dozen to the customers" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:66 +msgid "" +"The **Sale price** is expressed in the **Product unit of measure**. The " +"**Cost price** is expressed in the **Purchase Unit of Measure**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:70 +msgid "" +"All internal transfers are expressed in the **Product Unit of Measure**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:74 +msgid "Procurement" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:76 +msgid "" +"When doing your procurement request, you can still change the unit of " +"measure." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:82 +msgid "The unit of measure can also be changed in the purchase order :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:90 +msgid "The quality control is done by unit." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:92 +msgid "" +"The basic unit of measure of our product is **Unit**. Therefore the quality " +"check is done by unit." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:99 +msgid "" +"The unit of measure can only be changed when the transfer status is " +"**Draft**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:103 +#: ../../inventory/shipping/setup/delivery_method.rst:74 +msgid "Delivery process" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:105 +msgid "" +"The eggs are sold by the dozen. You can choose the unit of measure on the " +"sale order document. When doing it, the price is automatically computed from" +" the unit to the dozen." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:112 +msgid "" +"In the delivery order, the initial demand is done in the sales order unit of" +" measure :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:118 +msgid "" +"But the transfer is done in the product unit of measure. Everything is " +"converted automatically :" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:3 +msgid "When should you use packages, units of measure or kits?" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:6 +msgid "Unit of measures" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:8 +msgid "" +"Units of measures are an indication about the unit used to handle a product." +" Products can be expressed in multiple units of measure at once." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:11 +msgid "" +"Activate this option if you are working with several ones in your warehouse." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:14 +msgid "" +"The purchase unit of measure might be different that the one you use in your" +" warehouse." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:17 +msgid "" +"The selling unit of measure is set on the sale order and can be different." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:24 +msgid "" +"The conversion between the different units of measures is done " +"automatically. The only condition is that all the units have to be in the " +"same category (Unit, Weight, Volume, Length,...)" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:29 +msgid "Packages" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:38 +msgid "Packaging" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:40 +msgid "Packaging is the physical container that protects your product." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:42 +msgid "" +"If you are selling computers, the packaging contains the computer with the " +"notice and the power plug." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:45 +msgid "In Odoo, packagings are just used for indicative purpose." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:51 +msgid "" +"You can define on the **Packages** which **Packaging** it uses. But it is " +"only for indicative purpose." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:55 +msgid "When to use packages, packagings or unit of measures ?" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:57 +msgid "" +"For example, you are sellings eggs. In your warehouse, you manage the eggs " +"individually. Lots of eggs are scrapped and you do it egg by egg. The **unit" +" of measure** is ``Unit(s)``." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:61 +msgid "" +"If you are selling eggs by the dozen, the selling **unit of measure** is the" +" ``Dozen``. You will set it on your sale order." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:64 +msgid "" +"The ``cardboard trays`` that contains the dozen of eggs is the " +"**packaging**." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:66 +msgid "" +"When you are selling several trays, you might wrap all the trays into a " +"``box`` or in a ``plastic`` wrapping. It is the **package**." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:72 +msgid ":doc:`packages`" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:3 +msgid "Using product variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:10 +msgid "" +"As an example, a company selling t-shirts may have the following product:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:13 +msgid "B&C T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:15 +msgid "Sizes: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:16 +msgid "Colors: Blue, Red, White, Black" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:26 +msgid "Impact of variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:50 +msgid "Should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:53 +msgid "When should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:55 +msgid "Using variants has the following impacts:" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:77 +msgid "When should you avoid using variants?" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:91 +msgid "Quality: T-Shirts, Polos, Shirts" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:93 +#: ../../inventory/settings/products/variants.rst:105 +#: ../../inventory/settings/products/variants.rst:110 +msgid "Color: Red, Blue" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:95 +#: ../../inventory/settings/products/variants.rst:106 +#: ../../inventory/settings/products/variants.rst:111 +msgid "Size: S, M, L, XL" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:103 +msgid "Product Template: T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:108 +msgid "Product Template: Polos" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:117 +msgid "Activate the variant feature" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:129 +msgid "Creating products with variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:135 +msgid "Now, click on the product you wish to add variants to." +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:160 +msgid "" +"You can also add a different barcode and internal reference to the variant." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:163 +msgid "" +"When you have entered all the specifications of the variant, click on " +"**Save**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:167 +msgid "Managing Product Variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:172 +msgid "" +"The examples below are all based on this product template that has two " +"variant attributes :" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:175 +msgid "T-Shirt B&C" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:177 +msgid "Color: Red, Blue, White" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:179 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:182 +msgid "Managing combination possibilities" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:197 +msgid "" +"That deactivating a product is different than having an inventory of 0." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:200 +msgid "Setting a price per variant" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:202 +msgid "" +"You can add a cost over the main price for some of the variants of a " +"product." +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:220 +msgid "When you have entered all the extra values, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3 +msgid "What is the difference between warehouses and locations?" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:5 +msgid "" +"In Odoo, a **Warehouse** is the actual building/place in which your items " +"are stocked. You can setup multiple warehouses and create moves between " +"warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:9 +msgid "" +"A **Location**, is a specific space within your warehouse. It can be " +"considered as a sublocation of your warehouse, as a shelf, a floor, an " +"aisle, etc. Therefore, a location is part of one warehouse only and it is " +"not possible to link one location to multiple warehouses. You can configure " +"as much locations as you need under one warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:15 +msgid "There are 3 types of locations:" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:17 +msgid "" +"The **Physical Locations** are internal locations that are part of the " +"warehouses for which you are the owner. They can be the loading and " +"unloading area of your warehouse, a shelf or a department, etc." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:21 +msgid "" +"The **Partner Locations** are spaces within a customer and/or vendor's " +"warehouse. They work the same way as Physical Locations with the only " +"difference being that you are not the owner of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:25 +msgid "" +"The **Virtual Locations** are places that do not exist, but in which " +"products can be placed when they are not physically in an inventory yet (or " +"anymore). They come in handy when you want to place lost products out of " +"your stock (in the **Inventory loss**), or when you want to take into " +"account products that are on their way to your warehouse (**Procurements**)." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:31 +msgid "" +"In Odoo, locations are structured hierarchically. You can structure your " +"locations as a tree, dependent on a parent-child relationship. This gives " +"you more detailed levels of analysis of your stock operations and the " +"organization of your warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:37 +#: ../../inventory/settings/warehouses/location_creation.rst:44 +msgid ":doc:`warehouse_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:38 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:48 +msgid ":doc:`location_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:3 +msgid "How to create a new location?" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:9 +msgid "Creating a new location" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:11 +msgid "" +"In order to be able to create new locations, you must allow the system to " +"manage multiple locations. In the **Inventory** module, open the menu " +":menuselection:`Configuration --> Settings`. In the **Location & Warehouse**" +" section, tick the **Manage several locations per warehouse** box, then " +"click on **Apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:20 +msgid "" +"In the **Inventory** module, open :menuselection:`Configuration --> " +"Warehouse Management --> Locations` In the Locations window, click on " +"**Create**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:24 +msgid "" +"Type the name of the location in the **Location Name** field, and select the" +" **Parent Location** in the list. The parent location can be a physical, " +"partner or virtual location, and you can add as many sub-locations as needed" +" to a location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:29 +msgid "" +"You can also fill in the **Additional Information** fields and add a note to" +" describe your location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:35 +msgid "When you are finished, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:38 +msgid "" +"A warehouse also corresponds to a location. As the locations are " +"hierarchical, Odoo will create the parent location of the warehouse, " +"containing all the sublocations in it." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:43 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:47 +msgid ":doc:`difference_warehouse_location`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:3 +msgid "How to create a new warehouse?" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:11 +msgid "" +"In order to be able to create a new warehouse, you must allow the system to " +"manage multiple locations. In the **Inventory** module, open the menu " +":menuselection:`Settings --> Configuration`. In the **Location & Warehouse**" +" section, tick the **Manage several locations per warehouse** box, then " +"click on **apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:20 +msgid "" +"Open the menu :menuselection:`Configuration --> Warehouse Management --> " +"Warehouses`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:22 +msgid "" +"In the warehouses screen, click on **Create**. A new screen appears, with 3 " +"fields :" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:25 +msgid "In **Warehouse Name**, insert the full name of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:27 +msgid "" +"In the **Short Name** field, insert a 5-characters code for your warehouse. " +"Keep in mind that this code is the one that will appear in the lists, so " +"make sure you choose a name that is easy to understand and easy to enter." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:32 +msgid "" +"In the **Address** field, you can select an existing company or create one " +"on-the-go. Therefore, the address of your warehouse will be the same as the " +"one of the company you selected. You can also leave this field empty and " +"edit it afterwards." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:40 +msgid "Click on **Save** to finish configuring your new warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:43 +msgid "" +"When you create a warehouse, the system will create the necessary picking " +"types and main child locations for this main location in the background." +msgstr "" + +#: ../../inventory/shipping/operation.rst:3 +msgid "Shipping Operations" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:12 +msgid "" +"It will allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:20 +msgid "" +"If the delivery order is not **Validated**, then the request hasn't been " +"made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:24 +msgid "" +"If you have clicked on **Validate**, the request has been made and you " +"should have received the tracking number and the label. You can still cancel" +" the request. Simply click on the **Cancel** button next to the **Carrier " +"Tracking Ref**:" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:42 +msgid "" +"After cancelling the shipping request, you can change the carrier you want " +"to use. Confirm it by clicking on the **Send to shipper** button. You will " +"get a new tracking number and a new label." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:50 +#: ../../inventory/shipping/operation/labels.rst:115 +#: ../../inventory/shipping/operation/multipack.rst:83 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:51 +#: ../../inventory/shipping/operation/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:8 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:10 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:13 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:18 +msgid "" +"To configure the price of your delivery methods, go to the **Inventory** " +"app, click on :menuselection:`Configuration --> Delivery --> Delivery " +"Methods`." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:21 +msgid "" +"You can manually set a price for the shipping: It can be fixed or based on " +"rules." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:24 +msgid "" +"Or you can use the transportation company computation system. Read the " +"document :doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:28 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:31 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:33 +#: ../../inventory/shipping/operation/invoicing.rst:55 +msgid "" +"On your sale order, choose the carrier that will be used. Click on " +"**Delivery Method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:39 +#: ../../inventory/shipping/operation/multipack.rst:36 +msgid "" +"The price is computed when you **save** the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:42 +msgid "" +"To invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product. It may vary from the real price." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:46 +msgid "" +"When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:53 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:61 +msgid "" +"The price is computed when you **save** the sale order. Confirm the sale " +"order and proceed to deliver the product." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:64 +msgid "" +"The real shipping cost are computed when the delivery order is validated." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:70 +msgid "" +"Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:76 +msgid "" +"When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:83 +msgid "" +"If you split the delivery and make several ones, each delivery order will " +"add a line to the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:87 +msgid ":doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:88 +#: ../../inventory/shipping/operation/multipack.rst:84 +msgid ":doc:`labels`" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:3 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers " +"linked with the transportation company tracking system. It allows you to " +"manage the transport company, the real prices and the destination. And " +"finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:18 +#: ../../inventory/shipping/setup/third_party_shipper.rst:17 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:20 +msgid "" +"In the **Inventory** module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:30 +#: ../../inventory/shipping/setup/delivery_method.rst:34 +#: ../../inventory/shipping/setup/third_party_shipper.rst:33 +msgid "Configure the delivery method" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:32 +#: ../../inventory/shipping/setup/delivery_method.rst:36 +#: ../../inventory/shipping/setup/third_party_shipper.rst:35 +msgid "" +"To configure your delivery methods, go to the **Inventory** module, click on" +" :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:35 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:41 +msgid "" +"In the **Pricing** tab, the name of the provider means that the delivery " +"will be handled and computed by the shipper system." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:46 +msgid "" +"The first one is linked to **your account** (develop key, password,...). For" +" more information, please refer to the provider website." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:49 +#: ../../inventory/shipping/setup/third_party_shipper.rst:62 +msgid "" +"The second column varies according to the **provider**. You can choose the " +"packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:52 +#: ../../inventory/shipping/setup/third_party_shipper.rst:65 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:55 +#: ../../inventory/shipping/setup/third_party_shipper.rst:77 +msgid "Company configuration" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:57 +#: ../../inventory/shipping/setup/third_party_shipper.rst:79 +msgid "" +"In order to compute the right price, the provider needs your company " +"information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:64 +#: ../../inventory/shipping/setup/third_party_shipper.rst:86 +msgid "" +"To check your information, go to the **Settings** application and click on " +"**General Settings**. Click on the first link **Configure your company " +"data**." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:68 +#: ../../inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:70 +#: ../../inventory/shipping/setup/third_party_shipper.rst:92 +msgid "" +"The shipper companies need the weight of your product, otherwise the price " +"computation cannot be done." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:73 +msgid "" +"Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open " +"the products you want to ship and set a weight on it." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:80 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to do" +" the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:85 +msgid "How to print shipping labels ?" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:87 +msgid "" +"The delivery order created from the sale order will take the shipping " +"information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:90 +#: ../../inventory/shipping/setup/third_party_shipper.rst:135 +msgid "" +"If you create a delivery transfer from the inventory module, you can add the" +" third party shipper in the additional info tab." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:96 +msgid "" +"Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:98 +#: ../../inventory/shipping/setup/third_party_shipper.rst:151 +msgid "" +"The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:110 +msgid "" +"If you are doing multi-packages shippings, most of the time, there will be " +"one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:3 +msgid "How to manage multiple packs for the same delivery order?" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:8 +msgid "" +"By default, Odoo considers that your delivery is composed of one package. " +"But you can easily ship your deliveries with more than one package. It is " +"fully integrated with the third-party shippers." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:15 +msgid "" +"To configure the use of packages, go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings`. Locate the **Packages** section and tick " +"**Record packages used on packing: pallets, boxes,...**" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:29 +#: ../../inventory/shipping/setup/delivery_method.rst:77 +#: ../../inventory/shipping/setup/third_party_shipper.rst:110 +msgid "Sale order" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:34 +msgid "Click on a **Delivery Method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:40 +msgid "Multi-packages Delivery" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:42 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:48 +msgid "From here, you can split your delivery into multiple packages." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:66 +msgid "Multi-packages with a 3rd party-shipper" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:68 +msgid "" +"Once the delivery order is validated, you will receive the tracking number. " +"The **carrier Tracking ref** field will automatically be filled. Click on " +"the **Tracking** button to check your delivery on the provider website." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:76 +msgid "" +"The **labels** to stick on your packages are available in the history " +"underneath:" +msgstr "" + +#: ../../inventory/shipping/setup.rst:3 +msgid "Shipping Setup" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:3 +msgid "How to setup a delivery method?" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:8 +msgid "" +"Odoo can handle various delivery methods, but it is not activated by " +"default. Delivery methods can be used for your sale orders, your deliveries " +"but also on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:12 +msgid "" +"Delivery methods allow you to manage the transport company, the price and " +"the destination. You can even integrate Odoo with external shippers to " +"compute the real price and the packagings." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:20 +msgid "Install the inventory module" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:22 +msgid "" +"Delivery methods are handled by the **Delivery costs** module. Go to " +"**Apps** and search for the module. You should remove the **Apps** filter in" +" order to see it :" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:30 +#: ../../inventory/shipping/setup/third_party_shipper.rst:29 +msgid "" +"If you want to integrate delivery methods in your e-commerce, you'll have to" +" install the **eCommerce Delivery** module." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:39 +msgid "First set a name and a transporter company." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:44 +msgid "" +"Then you'll have to set the pricing. It can be fixed or based on rules." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:46 +msgid "" +"If the price is fixed, tick **Fixed price**. You'll just have to define the " +"price. If you want the delivery to be free above a certain amount, tick the " +"option **Free if Order total is more than** and set a price." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:54 +msgid "" +"If the price varies according to rules, tick **Based on Rules**. Click on " +"**add an item to a pricing rule**. Choose a condition based on either the " +"weight, the volume, the price or the quantity." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:61 +msgid "" +"Finally you can limit the delivery method to a few destinations. The limit " +"can be applied to some countries, states or even zip codes. This feature " +"limits the list of countries on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:69 +msgid "" +"You can integrate Odoo with external shippers in order to compute the real " +"price and packagings, and handle the printing the shipping labels. See " +":doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:82 +msgid "" +"You can now choose the **Delivery Method** on your sale order. If you want " +"to invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:88 +#: ../../inventory/shipping/setup/third_party_shipper.rst:130 +msgid "Delivery" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:90 +msgid "You can add or change the delivery method on the delivery itself." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:95 +msgid "" +"On the delivery, check the **Carrier Information**. The carrier is the " +"chosen delivery method." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:99 +msgid ":doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:100 +#: ../../inventory/shipping/setup/third_party_shipper.rst:158 +msgid ":doc:`../operation/invoicing`" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:9 +msgid "A DHL Password" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:11 +msgid "A DHL Account Number" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:15 +msgid "" +"Getting SiteID and password for countries other than United States (UK and " +"Rest of the world)" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:17 +msgid "" +"You should contact DHL account manager and request integration for XML " +"Express API. The presales should provide you live credentials." +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:22 +msgid "" +"You need to write to xmlrequests@dhl.com along with your full Account " +"details like account number, region, address, etc. to get API Access." +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:24 +msgid "" +"In meantime, for testing the solution, you can use the tests credentials as " +"given in the demo data:" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:26 +msgid "**SiteID**: CustomerTest" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:28 +msgid "**Password**: alkd89nBV" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:30 +msgid "**DHL Account Number**: 803921577" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo can be linked with the transportation company tracking system. It will " +"allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:19 +msgid "" +"In the inventory module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:38 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created. Most of the time, there will be **2** delivery methods for the same" +" provider: one for **international** shipping and the other for **domestic**" +" shipping." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:43 +msgid "" +"You can create other methods with the same provider with other " +"configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:46 +msgid "" +"You can change the **Name** of the delivery method. This is the name that " +"will appear on your ecommerce." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:49 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:54 +msgid "" +"In the pricing tab, the name of the provider chosen under the **Price " +"computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:57 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:59 +msgid "" +"The first one is linked to **your account** (developer key, password,...). " +"For more information, please refer to the provider website." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:67 +msgid "" +"Finally you can limit the delivery method to a few destinations. You can " +"limit it to some countries, states or even zip codes. This feature limits " +"the list of countries on your e-commerce. It is useful for the domestic " +"providers. For example, USPS US only delivers from the United States to the " +"United States." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:95 +msgid "" +"Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products" +" you want to ship and set a weight on it." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:102 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to " +"make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:115 +msgid "" +"You can now choose the carrier on your sale order. Click on **Delivery " +"method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:118 +msgid "" +"The price is computed when you save the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:121 +msgid "" +"If you want to invoice the price of the delivery charge on the sale order, " +"click on **Set price**, it will add a line with the name of the delivery " +"method as a product. It may vary from the real price." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:125 +msgid "" +"Otherwise, the real price (computed when the delivery is validated) will " +"automatically be added to the invoice. For more information, please read the" +" document :doc:`../operation/invoicing`" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:132 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it. You can change the carrier if you want to." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:141 +msgid "" +"The weight is computed based on the products weights. The shipping cost will" +" be computed once the transfer is validated." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:144 +msgid "" +"Click on **Validate** to receive the tracking number. The **Carrier Tracking" +" ref** field will automatically be filled. Click on the **Tracking** button " +"to check your delivery on the provider website." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:159 +msgid ":doc:`../operation/labels`" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:13 +msgid "" +"An Access Key is a 16 character alpha-numeric code that allows access to the" +" UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:19 +msgid "" +"Note that only customers located in the US can open a UPS account online. If" +" you are located outside the US, you will need to contact UPS Customer " +"Service in order to to open an account." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:23 +msgid "" +"You can read additional information about opening a UPS account on the their" +" website, on the page, `How to Open a UPS Account Online " +"`_" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:27 +msgid "" +"If you don't already have a UPS account, you can create one along with your " +"online profile by following these steps:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:30 +msgid "" +"1. Access the UPS.com web site at `www.ups.com `__, and" +" click the **New User** link at the top of the page." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:34 +msgid "" +"2. Click the **Register for MyUPS** button, and follow the prompts to " +"complete the registration process." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:37 +msgid "" +"If you already have a UPS account, you can add it to your online profile as " +"follows:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:39 +msgid "" +"1. Log in to the UPS.com site (`http://www.ups.com `__)" +" using your UPS.com User ID and Password." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:43 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:45 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:47 +msgid "" +"4. Click the **Add an Existing UPS Account** link in the **UPS Account " +"Details** section of the page." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:50 +msgid "" +"5. In the **Add New Account** screen, enter the **UPS Account Number**, " +"**Account Name**, and **Postal Code** fields. The country defaults to United" +" States.q" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:54 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:57 +msgid "Get an Access Key" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:59 +msgid "" +"After you have added your UPS account number to your user profile you can " +"request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:62 +msgid "" +"1. Go to the **UPS Developer Kit** web page " +"`https://www.ups.com/upsdeveloperkit?loc=en\\_US " +"`__" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:65 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:67 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:69 +msgid "Verify your contact information" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:71 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:73 +msgid "" +"The **Access Key** will be provided to you on the web page, and an email " +"with the Access Key will be sent to the email address of the primary " +"contact." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/manufacturing.po b/locale/ru/LC_MESSAGES/manufacturing.po new file mode 100644 index 000000000..726b2831f --- /dev/null +++ b/locale/ru/LC_MESSAGES/manufacturing.po @@ -0,0 +1,728 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../manufacturing.rst:5 +msgid "Manufacturing" +msgstr "" + +#: ../../manufacturing/operations.rst:3 +msgid "Manufacturing Operations" +msgstr "" + +#: ../../manufacturing/operations/replenishment.rst:3 +msgid "Replenishment Strategies" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:3 +msgid "How to select the right replenishment strategy" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:5 +msgid "" +"Minimum Stock rules and Make to Order have similar consequences but " +"different rules. They should be used depending on your manufacturing and " +"delivery strategies." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:15 +msgid "" +"Minimum Stock rules are used to ensure that you always have the minimum " +"amount of a product in stock in order to manufacture your products and/or " +"answer to your customer needs. When the stock level of a product reaches its" +" minimum the system will automatically generate a procurement order with the" +" quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:22 +#: ../../manufacturing/operations/replenishment/strategies.rst:58 +msgid "Make to Order" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:24 +msgid "" +"The Make to Order function will trigger a Purchase Order of the amount of " +"the Sales Order related to the product. The system will **not** check the " +"current stock. This means that a draft purchase order will be generated " +"regardless of the quantity on hand of the product." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:30 +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:27 +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:62 +msgid "Configuration" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:35 +msgid "" +"The Minimum Stock Rules configuration is available through your Inventory " +"module. In the Inventory Control menu select \"Reordering Rule\" in the drop" +" down menu. There, click on \"Create\" to set minimum and maximum stock " +"values for a given product." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:44 +msgid "" +"Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity " +"multiple\" fields" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:47 +msgid "" +"Then, click on your product to access the related product form and, on the " +"\"Inventory submenu\", do not forget to select a supplier." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:54 +msgid "" +"Don't forget to select the right product type. A consumable can not be " +"stocked and will thus not be accounted for in the stock valuation." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:60 +msgid "" +"The Make to Order configuration is available on your product form through " +"your :menuselection:`Inventory --> Inventory control --> Products` (or any " +"other module where products are available)." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:64 +msgid "On the product form, under Inventory, click on \"Make To Order\"." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:70 +msgid "Choice between the two options" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:72 +msgid "" +"The choice between the two options is thus dependent of your inventory " +"strategy. If you prefer to have a buffer and always have at least a minimum " +"amount, the minimum stock rule should be used. If you want to reorder your " +"stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../manufacturing/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials.rst:3 +#: ../../manufacturing/overview/main_concepts/terminologies.rst:6 +msgid "Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:3 +msgid "How to Sell a Set of Products as a Kit" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:5 +msgid "" +"A *kit* is a set of components that are delivered without first being " +"assembled or mixed. Kits are described in Odoo using *bills of materials*. " +"There are two basic ways to configure kits, depending on how stock of the " +"kit product is to be managed. In either case, both the Inventory and " +"Manufacturing apps must be installed." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:12 +msgid "Manage Stock of Component Products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:14 +msgid "" +"If you would like to assemble kits as they are ordered, managing stock of " +"the kit *components* only, you will use a Kit BoM without a manufacturing " +"step." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:18 +msgid "" +"A product using a Kit BoM will appear as a single line item on a quotation " +"and sales order, but will generate a delivery order with one line item for " +"each of the components of the kit. In the examples below, the image at left " +"shows a sales order for the kit \"Custom Computer Kit\", while the image at " +"right shows the corresponding delivery order." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:24 +msgid "|image0|\\ |image1|" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:29 +msgid "" +"From the **Products** menu in either the Inventory or Manufacturing app, " +"create each component product as you would any other product, then create " +"the top-level, or kit product. The kit product should have only the route " +"**Manufacture** set. Because you cannot track the stock of kit products, the" +" Product Type should be set to **Consumable**. Because a kit product cannot " +"be purchased, **Can be Purchased** should be unchecked." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:37 +msgid "" +"All other parameters on the kit product may be modified according to your " +"preference. The component products require no special configuration." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:44 +msgid "" +"Once the products are configured, create a bill of materials for the kit " +"product. Add each component and its quantity. Select the BoM Type **Ship " +"this product as a set of components**. All other options may be left with " +"their default values." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:53 +msgid "Manage Stock of Kit Product and Component Products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:55 +msgid "" +"If you would like to manage stock of the top-level kit product, you will use" +" a standard BoM with a manufacturing step instead of a Kit BoM. When using a" +" standard BoM to assemble kits, a manufacturing order will be created. The " +"manufacturing order must be registered as completed before the kit product " +"will appear in your stock." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:64 +msgid "" +"On the kit product, select the route **Manufacture**. You may also select " +"**Make to Order**, which will create a manufacturing order whenever a sales " +"order is confirmed. Select the product type **Stockable Product** to enable " +"stock management." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:72 +msgid "" +"When you create the bill of materials, select the BoM Type **Manufacture " +"this product**. The assembly of the kit will be described by a manufacturing" +" order rather than a packing operation." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:3 +msgid "How to manage BoMs for product variants" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:5 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:125 +msgid "" +"Odoo allows you to use one bill of materials for multiple variants of the " +"same product. Simply enable variants from :menuselection:`Configuration --> " +"Settings`." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:12 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:132 +msgid "" +"You will then be able to specify which component lines are to be used in the" +" manufacture of each product variant. You may specify multiple variants for " +"each line. If no variant is specified, the line will be used for all " +"variants." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:17 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:137 +msgid "" +"When defining variant BoMs on a line-item-basis, the **Product Variant** " +"field in the main section of the BoM should be left blank. This field is " +"used when creating a BoM for one variant of a product only." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:3 +msgid "How to manage semi-finished products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:5 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:83 +msgid "" +"A subassembly is a manufactured product which is intended to be used as a " +"component of another manufactured product. You may wish to employ sub-" +"assemblies to simplify a complex BoM, to more accurately represent your " +"manufacturing flow, or to use the same subassembly in multiple BoMs. A BoM " +"that employs subassemblies is often referred to as a multi-level BoM." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:12 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:90 +msgid "" +"Multi-level bills of materials in Odoo are accomplished by creating a top-" +"level BoM and subassembly BoMs. Next, the procurement route of the " +"subassembly product is defined. This ensures that every time a manufacturing" +" order for the top-level product is created, a manufacturing order for each " +"subassembly is created as well." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:19 +msgid "Configure the Top -Level Product BoM" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:21 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:99 +msgid "" +"To configure a multi-level BoM, create the top-level product and its BoM. " +"Include any subassemblies in the list of components. Create a BoM for each " +"subassembly as you would for any product." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:29 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:107 +msgid "Configure the Subassembly Product Data" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:31 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:109 +msgid "" +"On the product form of the subassembly, you must select the routes " +"**Manufacture** and **Make To Order**. The **Manufacture** route takes " +"precedence over the **Buy** route, so selecting the latter will have no " +"effect." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:39 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:117 +msgid "" +"If you would like to be able to purchase the subassembly in addition to " +"manufacturing it, select **Can be Purchased**. All other fields on the " +"subassembly product form may be configured according to your preference." +msgstr "" + +#: ../../manufacturing/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../manufacturing/overview/getting_started.rst:5 +msgid "How to consume composents to make a finished product" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:3 +msgid "How to create a Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:5 +msgid "" +"A bill of materials (BoM) is a document that describes the component " +"products, the quantity of each component, and the process required to " +"manufacture a product, including a routing and individual steps." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:9 +msgid "" +"In Odoo, each product may have multiple BoMs associated with it, but a BoM " +"can only be associated with a single product. A single BoM can, however, " +"describe multiple variants of the same product." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:14 +msgid "Setting up a Basic BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:16 +msgid "" +"If you choose to manage your manufacturing operations using manufacturing " +"orders only, you will define basic bills of materials without routings. For " +"more information about which method of management to use, review the " +"**Getting Started** section of the *Manufacturing* chapter of the " +"documentation." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:22 +msgid "" +"Before creating your first bill of materials, you will need to create a " +"product and at least one component (components are considered products in " +"Odoo). You can do so from :menuselection:`Master Data --> Products`, or on " +"the fly from the relevant fields on the BoM form. Review the Inventory " +"chapter for more information about configuring products. Once you have " +"created a product and at least one component, select them from the relevant " +"dropdown menus to add them to your bill of materials. A new bill of " +"materials can be created from :menuselection:`Master Data --> Bills of " +"Materials`, or using the button on the top of the product form." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:32 +msgid "" +"Under the **Miscellaneous** tab, you can fill additional fields. " +"**Sequence** defines the order in which your BoMs will be selected for " +"production orders, with lower numbers having higher priority. **Version** " +"allows you to track changes to your BoM over time." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:38 +msgid "Adding a Routing to a BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:40 +msgid "" +"A routing defines a series of operations required to manufacture a product " +"and the work center at which each operation is performed. A routing may be " +"added to multiple BoMs, though a BoM may only have one routing. For more " +"information about configuring routings, review the chapter on routings." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:46 +msgid "" +"After enabling routings from :menuselection:`Configuration --> Settings`, " +"you will be able to add a routing to a bill of materials by selecting a " +"routing from the dropdown list or creating one on the fly." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:50 +msgid "" +"You may define the work operation or step in which each component is " +"consumed using the field, **Consumed in Operation** under the **Components**" +" tab. Similarly, you can define the operation at which the product will be " +"produced under the **Miscellaneous** tab using the field **Produced at " +"Operation**. If this field is left blank, the products will be " +"consumed/produced at the final operation in the routing." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:61 +msgid "Adding Byproducts to a BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:63 +msgid "" +"In Odoo, a byproduct is any product produced by a BoM in addition to the " +"primary product." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:66 +msgid "" +"To add byproducts to a BoM, you will first need to enable them from " +":menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:72 +msgid "" +"Once byproducts are enabled, you can add them to your bills of materials " +"under the **Byproducts** tab of the bill of materials. You can add any " +"product or products as byproducts. Byproducts are produced in the same step " +"of the routing as the primary product of the BoM." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:81 +msgid "Setting up a BoM for a Product With Sub-Assemblies" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:97 +msgid "Configure the Top-Level Product BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:123 +msgid "Using a Single BoM to Describe Several Variants of a Single Product" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:3 +msgid "How to process a manufacturing order" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:8 +msgid "" +"There are two basic ways to manage manufacturing in Odoo. The first way " +"manages work with one document only. This document is the **manufacturing " +"order**. The second way uses additional documents to give you more precise " +"control over the manufacturing process. In this way, **Manufacturing " +"orders** are divided into one or more steps defined by **work orders**, " +"performed in an order defined by **routings**." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:17 +msgid "How to manage manufacturing without routings" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:19 +msgid "" +"You will most likely use manufacturing orders without routings if all the " +"work to produce your product is performed in one place, by one person, in " +"one step, and/or you do not need the level of granular control afforded by " +"work orders and routings." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:24 +msgid "" +"Managing your operations in this way is the default behavior in Odoo. There " +"are two basic phases from planning to production:" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:27 +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:52 +msgid "Create manufacturing orders" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:29 +msgid "Record Production" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:32 +msgid "How to manage manufacturing with routings and work orders" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:34 +msgid "" +"To use work orders and routings, you will need to enable the option **Manage" +" production by work orders** From :menuselection:`Configuration --> " +"Settings`. You will then be able to add routings to bills of materials, and " +"configure some additional related fields. You will also be able to create " +"**work centers**, the locations at which work orders are performed." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:41 +msgid "" +"When manufacturing with routings and work orders, each work order is " +"scheduled individually. You will also have access to time and capacity " +"planning, and reports on costing and efficiency on a work center level." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:45 +msgid "" +"Manufacturing using routings can be broken down into several steps. When " +"configuring your BoM, you will need to add a routing defining the component " +"work orders. After planning the manufacturing order, you will have the added" +" step of scheduling work orders." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:50 +msgid "The workflow is thus divided into three basic phases, as follows:" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:54 +msgid "Schedule the associated work orders." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:56 +msgid "Perform the scheduled work and record production." +msgstr "" + +#: ../../manufacturing/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:3 +msgid "Introduction to Odoo Manufacturing" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:13 +msgid "Work in progress." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:3 +msgid "Manufacturing Terminologies" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:9 +msgid "" +"A bill of materials (BoM) is a document that describes the materials, the " +"quantity of each material, and the steps required to manufacture a product. " +"Depending on the industry and the nature of the finished product, a " +"different name may be used to describe the same document. For example, in " +"the pharmaceutical industry, the term “recipe” may be used." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:14 +msgid "Cycle" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:17 +msgid "" +"A production cycle is a frame of time during which an entire manufacturing " +"process can be fulfilled." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:19 +msgid "Downtime or Leave" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:22 +msgid "" +"Time during which a resource is unavailable. If the resource is a machine, " +"the unavailability is downtime, while if the resource is human, unavailable " +"time is called a Leave." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:25 +msgid "Finished products" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:28 +msgid "" +"Finished products are the final output of a manufacturing process. They are " +"normally not intended to be used as input into another manufacturing order " +"of the company." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:31 +msgid "Kit" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:34 +msgid "" +"A kit is a set of components that are described by a bill of materials, but " +"which are delivered separately rather than assembled or mixed." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:36 +msgid "Multi-level Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:39 +msgid "" +"A bill of material can quickly grow very complex. To keep it manageable, it " +"can be broken down into several smaller manufactured parts, each having its " +"own BOM. These parts are typically referred to as sub-assembly of " +"intermediate products." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:44 +msgid "" +"Defining a BOM in multiple levels reduces the complexity of the top-level " +"document and allows components to be reused in other BoMs." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:46 +msgid "Phantom Bill of Material" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:49 +msgid "" +"A phantom bill of material is always used in the context of multi-level " +"BOMs. It allows to add a sub-assembly as part of a bigger end-product while " +"avoiding to trigger a separate manufacturing order for the sub-assembly." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:54 +msgid "" +"As such, when a manufacturing order for the final product is launched, the " +"components of the sub-assembly are reflected in the parent BOM as if they " +"were direct components of the parent BOM." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:58 +msgid "" +"Phantom BOM are thus used for grouping a set of components with the aim of " +"reusing them in many other BOM without the need to launch separate " +"manufacturing orders for the sub-assemblies." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:61 +msgid "Raw Materials" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:64 +msgid "" +"Raw materials and components constitute the input that are transformed to " +"produce semi-finished or finished goods." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:67 +msgid "" +"The transformation here can take many aspects according to the industry. It " +"can be simple assembly, welding, mixing, etc." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:69 +msgid "Routing" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:72 +msgid "" +"A routing is a document that describes a series of Work Orders and the Work " +"Centers at which they will be carried out" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:74 +msgid "Semi-finished products and sub-assemblies" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:77 +msgid "" +"These are products which are manufactured with the purpose to be consumed in" +" another manufacturing order." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:79 +msgid "Work Order Operations" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:82 +msgid "" +"Work Order Operations specify the set of activities necessary to fully " +"process a manufacturing order. Each activity or operation takes some time to" +" be completed and is performed into a determined production unit (also " +"called work center)." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:86 +msgid "Work Order" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:89 +msgid "" +"A work order is a single manufacturing operation that is scheduled for " +"execution on a given date and a given duration." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:91 +msgid "Work Center" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:94 +msgid "" +"Work centers identify production units and their resources. They are used to" +" represent the plant capacity as well as costing information. The capacity " +"is a combination of resources and their availability time." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:97 +msgid "Resources" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:100 +msgid "" +"In manufacturing a resource can be a human being (employee) or machine " +"available in a work center." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:102 +msgid "Working Time" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:105 +msgid "" +"Each resource has its normal working time. For instance, machines can be set" +" up to operate 7 days a week 20 hours out of 24." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/point_of_sale.po b/locale/ru/LC_MESSAGES/point_of_sale.po new file mode 100644 index 000000000..a4ccca6ad --- /dev/null +++ b/locale/ru/LC_MESSAGES/point_of_sale.po @@ -0,0 +1,2947 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../point_of_sale.rst:5 +msgid "Point of Sale" +msgstr "" + +#: ../../point_of_sale/advanced.rst:3 +msgid "Advanced topics" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:3 +msgid "How to use discount tags on products?" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:5 +msgid "This tutorial will describe how to use discount tags on products." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:8 +msgid "Barcode Nomenclature" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:10 +msgid "" +"To start using discounts tags, let's first have a look at the **barcode " +"nomenclature** in order to print our correct discounts tags." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:13 +msgid "I want to have a discount for the product with the following barcode." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:18 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Barcode " +"Nomenclatures`. In the default nomenclature, you can see that to set a " +"discount, you have to start you barcode with ``22`` and the add the " +"percentage you want to set for the product." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:26 +msgid "" +"For instance if you want ``50%`` discount on a product you have to start you" +" barcode with ``2250`` and then add the product barcode. In our example, the" +" barcode will be:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:34 +msgid "Scanning your products" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:36 +msgid "If you go back to the **dashboard** and start a **new session**" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:41 +msgid "You have to scan:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:43 +msgid "the product" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:45 +msgid "the discount tag" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:47 +msgid "When the product is scanned, it appears on the ticket" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:52 +msgid "" +"Then when you scan the discount tag, ``50%`` discount is applied on the " +"product." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:58 +msgid "That's it, this how you can use discount tag on products with Odoo." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:61 +#: ../../point_of_sale/advanced/loyalty.rst:114 +#: ../../point_of_sale/advanced/manual_discount.rst:83 +#: ../../point_of_sale/advanced/mercury.rst:94 +#: ../../point_of_sale/advanced/multi_cashiers.rst:171 +#: ../../point_of_sale/advanced/register.rst:57 +#: ../../point_of_sale/advanced/reprint.rst:35 +#: ../../point_of_sale/overview/start.rst:155 +#: ../../point_of_sale/restaurant/print.rst:69 +#: ../../point_of_sale/restaurant/split.rst:81 +#: ../../point_of_sale/restaurant/tips.rst:43 +#: ../../point_of_sale/restaurant/transfer.rst:35 +msgid ":doc:`../shop/cash_control`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:62 +#: ../../point_of_sale/advanced/loyalty.rst:115 +#: ../../point_of_sale/advanced/manual_discount.rst:84 +#: ../../point_of_sale/advanced/mercury.rst:95 +#: ../../point_of_sale/advanced/multi_cashiers.rst:172 +#: ../../point_of_sale/advanced/register.rst:58 +#: ../../point_of_sale/advanced/reprint.rst:36 +#: ../../point_of_sale/overview/start.rst:156 +#: ../../point_of_sale/restaurant/print.rst:70 +#: ../../point_of_sale/restaurant/split.rst:82 +#: ../../point_of_sale/restaurant/tips.rst:44 +#: ../../point_of_sale/restaurant/transfer.rst:36 +msgid ":doc:`../shop/invoice`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:63 +#: ../../point_of_sale/advanced/loyalty.rst:116 +#: ../../point_of_sale/advanced/manual_discount.rst:85 +#: ../../point_of_sale/advanced/mercury.rst:96 +#: ../../point_of_sale/advanced/multi_cashiers.rst:173 +#: ../../point_of_sale/advanced/register.rst:59 +#: ../../point_of_sale/advanced/reprint.rst:37 +#: ../../point_of_sale/overview/start.rst:157 +#: ../../point_of_sale/restaurant/print.rst:71 +#: ../../point_of_sale/restaurant/split.rst:83 +#: ../../point_of_sale/restaurant/tips.rst:45 +#: ../../point_of_sale/restaurant/transfer.rst:37 +msgid ":doc:`../shop/refund`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:64 +#: ../../point_of_sale/advanced/loyalty.rst:117 +#: ../../point_of_sale/advanced/manual_discount.rst:86 +#: ../../point_of_sale/advanced/mercury.rst:97 +#: ../../point_of_sale/advanced/multi_cashiers.rst:174 +#: ../../point_of_sale/advanced/register.rst:60 +#: ../../point_of_sale/advanced/reprint.rst:38 +#: ../../point_of_sale/overview/start.rst:158 +#: ../../point_of_sale/restaurant/print.rst:72 +#: ../../point_of_sale/restaurant/split.rst:84 +#: ../../point_of_sale/restaurant/tips.rst:46 +#: ../../point_of_sale/restaurant/transfer.rst:38 +msgid ":doc:`../shop/seasonal_discount`" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:3 +msgid "How to create & run a loyalty & reward system" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:6 +#: ../../point_of_sale/advanced/manual_discount.rst:41 +#: ../../point_of_sale/advanced/multi_cashiers.rst:37 +#: ../../point_of_sale/advanced/multi_cashiers.rst:88 +#: ../../point_of_sale/advanced/reprint.rst:6 +#: ../../point_of_sale/overview/start.rst:22 +#: ../../point_of_sale/restaurant/print.rst:6 +#: ../../point_of_sale/restaurant/split.rst:6 +#: ../../point_of_sale/restaurant/tips.rst:6 +#: ../../point_of_sale/shop/seasonal_discount.rst:6 +msgid "Configuration" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:8 +msgid "" +"In the **Point of Sale** application, go to :menuselection:`Configuration " +"--> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:14 +msgid "" +"You can tick **Manage loyalty program with point and reward for customers**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:21 +msgid "Create a loyalty program" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:23 +msgid "" +"After you apply, go to :menuselection:`Configuration --> Loyalty Programs` " +"and click on **Create**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:29 +msgid "" +"Set a **name** and an **amount** of points given **by currency**, **by " +"order** or **by product**. Extra rules can also be added such as **extra " +"points** on a product." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:33 +msgid "To do this click on **Add an item** under **Rules**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:38 +msgid "You can configure any rule by setting some configuration values." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:40 +msgid "**Name**: An internal identification for this loyalty program rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:41 +msgid "**Type**: Does this rule affects products, or a category of products?" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:42 +msgid "**Target Product**: The product affected by the rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:43 +msgid "**Target Category**: The category affected by the rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:44 +msgid "" +"**Cumulative**: The points won from this rule will be won in addition to " +"other rules" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:45 +msgid "" +"**Points per product**: How many points the product will earn per product " +"ordered" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:46 +msgid "" +"**Points per currency**: How many points the product will earn per value " +"sold" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:51 +msgid "" +"Your new rule is now created and rewards can be added by clicking on **Add " +"an Item** under **Rewards**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:57 +msgid "Three types of reward can be given:" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:59 +msgid "" +"**Resale**: convert your points into money. Set a product that represents " +"the value of 1 point." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:64 +msgid "" +"**Discount**: give a discount for an amount of points. Set a product with a " +"price of ``0 €`` and without any taxes." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:69 +msgid "**Gift**: give a gift for an amount of points" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:77 +msgid "Applying your loyalty program to a point of sale" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:79 +msgid "On the **Dashboard**, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:84 +msgid "Next to loyalty program, set the program you want to set." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:90 +msgid "Gathering and consuming points" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:92 +msgid "To start gathering points you need to set a customer on the order." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:94 +msgid "Click on **Customer** and select the right one." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:96 +msgid "Loyalty points will appear on screen." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:101 +msgid "" +"The next time the customer comes to your shop and has enough points to get a" +" reward, the **Rewards** button is highlighted and gifts can be given." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:108 +msgid "" +"The reward is added and of course points are subtracted from the total." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:3 +msgid "How to apply manual discounts?" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:6 +#: ../../point_of_sale/advanced/mercury.rst:6 +#: ../../point_of_sale/overview.rst:3 ../../point_of_sale/overview/start.rst:6 +msgid "Overview" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:8 +msgid "" +"You can apply manual discounts in two different ways. You can directly set a" +" discount on the product or you can set a global discount on the whole cart." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:13 +msgid "Discount on the product" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:15 +#: ../../point_of_sale/advanced/register.rst:8 +msgid "On the dashboard, click on **New Session**:" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:20 +msgid "You will get into the main point of sale interface :" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:25 +#: ../../point_of_sale/advanced/mercury.rst:76 +#: ../../point_of_sale/shop/cash_control.rst:53 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. If you click on a product, it will be added in the cart. You can " +"directly set the correct quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:30 +msgid "" +"The same way you insert a quantity, Click on **Disc** and then type the " +"discount (in percent). This is how you insert a manual discount on a " +"specific product." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:38 +msgid "Global discount" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:43 +msgid "" +"If you want to set a global discount, you need to go to " +":menuselection:`Configuration --> Settings` and tick **Allow global " +"discounts**" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:50 +msgid "Then from the dashboard, click on :menuselection:`More --> Settings`" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:55 +msgid "" +"You have to activate **Order Discounts** and create a product that will be " +"added as a product with a negative price to deduct the discount." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:61 +msgid "" +"On the product used to create the discount, set the price to ``0`` and do " +"not forget to remove all the **taxes**, that can make the calculation wrong." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:68 +msgid "Set a global discount" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:70 +msgid "" +"Now when you come back to the **dashboard** and start a **new session**, a " +"**Discount** button appears and by clicking on it you can set a " +"**discount**." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:76 +msgid "" +"When it's validated, the discount line appears on the order and you can now " +"process to the payment." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:3 +msgid "How to accept credit card payments in Odoo POS using Mercury?" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:8 +msgid "" +"A **MercuryPay** account (see `MercuryPay website " +"`__.) is required to accept credit card payments" +" in Odoo 9 POS with an integrated card reader. MercuryPay only operates with" +" US and Canadian banks making this procedure only suitable for North " +"American businesses. An alternative to an integrated card reader is to work " +"with a standalone card reader, copy the transaction total from the Odoo POS " +"screen into the card reader, and record the transaction in Odoo POS." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:18 +msgid "Module installation" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:20 +msgid "" +"Go to **Apps** and install the **Mercury Payment Services** application." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:26 +msgid "Mercury Configuration" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:28 +msgid "" +"In the **Point of Sale** application, click on :menuselection:`Configuration" +" --> Mercury Configurations` and then on **Create**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:35 +msgid "Introduce your **credentials** and then save them." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:40 +msgid "" +"Then go to :menuselection:`Configuration --> Payment methods` and click on " +"**Create**. Under the **Point of Sale** tab you can set a **Mercury " +"configuration** to the **Payment method**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:47 +msgid "" +"Finally, go to :menuselection:`Configuration --> Point of Sale` and add a " +"new payment method on the point of sale by editing it." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:54 +msgid "" +"Then select the payment method corresponding to your mercury configuration." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:60 +msgid "Save the modifications." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:63 +#: ../../point_of_sale/shop/cash_control.rst:48 +msgid "Register a sale" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:65 +msgid "" +"On the dashboard, you can see your point(s) of sales, click on **New " +"Session**:" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:71 +#: ../../point_of_sale/overview/start.rst:114 +msgid "You will get the main point of sale interface:" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:82 +msgid "Payment with credit cards" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:84 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the credit" +" card **Payment Method**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:90 +msgid "" +"Type in the **Amount** to be paid with the credit card. Now you can swipe " +"the card and validate the payment." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:3 +msgid "How to manage multiple cashiers?" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:5 +msgid "" +"This tutorial will describe how to manage multiple cashiers. There are four " +"differents ways to manage several cashiers." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:9 +msgid "Switch cashier without any security" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:11 +msgid "" +"As prerequisite, you just need to have a second user with the **Point of " +"Sale User** rights (Under the :menuselection:`General Settings --> Users` " +"menu). On the **Dashboard** click on **New Session** as the main user." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:18 +#: ../../point_of_sale/advanced/multi_cashiers.rst:64 +#: ../../point_of_sale/advanced/multi_cashiers.rst:123 +msgid "On the top of the screen click on the **user name**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:23 +msgid "And switch to another cashier." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:28 +msgid "" +"The name on the top has changed which means you have changed the cashier." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:34 +msgid "Switch cashier with pin code" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:39 +msgid "" +"If you want your cashiers to need a pin code to be able to use it, you can " +"set it up in by clicking on **Settings**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:45 +msgid "Then click on **Manage access rights**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:50 +msgid "" +"**Edit** the cashier and add a security pin code on the **Point of Sale** " +"tab." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:57 +msgid "Change cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:59 +#: ../../point_of_sale/advanced/multi_cashiers.rst:118 +msgid "On the **Dashboard** click on **New Session**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:69 +msgid "Choose your **cashier**:" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:74 +msgid "" +"You will have to insert the user's **pin code** to be able to continue." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:79 +msgid "Now you can see that the cashier has changed." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:85 +msgid "Switch cashier with cashier barcode badge" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:90 +msgid "" +"If you want your cashiers to scan its badge, you can set it up in by " +"clicking on **Settings**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:96 +msgid "Then click on **Manage access rights**" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:101 +msgid "" +"**Edit** the cashier and add a **security pin code** on the **Point of " +"Sale** tab." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:108 +msgid "" +"Be careful of the barcode nomenclature, the default one forced you to use a " +"barcode starting with ``041`` for cashier barcodes. To change that go to " +":menuselection:`Point of Sale --> Configuration --> Barcode Nomenclatures`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:116 +msgid "Change Cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:128 +msgid "" +"When the cashier scans his own badge, you can see on the top that the " +"cashier has changed." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:132 +msgid "Assign session to a user" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:134 +msgid "" +"Click on the menu :menuselection:`Point of Sale --> Orders --> Sessions`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:139 +msgid "" +"Then, click on **New** and assign as **Responsible** the correct cashier to " +"the point of sale." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:145 +msgid "When the cashier logs in he is able to open the session" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:151 +msgid "Assign a default point of sale to a cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:153 +msgid "" +"If you want your cashiers to be assigned to a point of sale, go to " +":menuselection:`Point of Sales --> Configuration --> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:159 +msgid "Then click on **Manage Access Rights**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:164 +msgid "" +"**Edit** the cashier and add a **Default Point of Sale** under the **Point " +"of Sale** tab." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:3 +msgid "How to register customers?" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:6 +#: ../../point_of_sale/restaurant/split.rst:21 +#: ../../point_of_sale/shop/invoice.rst:6 +#: ../../point_of_sale/shop/seasonal_discount.rst:78 +msgid "Register an order" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:13 +msgid "You arrive now on the main view :" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:18 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. If you click on a product, it will be added in the cart. You can " +"directly set the quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:23 +msgid "Record a customer" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:25 +msgid "On the main view, click on **Customer**:" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:30 +msgid "Register a new customer by clicking on the button." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:35 +msgid "The following form appear. Fill in the relevant information:" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:40 +msgid "When it's done click on the **floppy disk** icon" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:45 +msgid "" +"You just registered a new customer. To set this customer to the current " +"order, just tap on **Set Customer**." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:51 +msgid "The customer is now set on the order." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:3 +msgid "How to reprint receipts?" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:8 +msgid "This feature requires a POSBox and a receipt printer." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:10 +msgid "" +"If you want to allow a cashier to reprint a ticket, go to " +":menuselection:`Configuration --> Settings` and tick the option **Allow " +"cashier to reprint receipts**." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:17 +msgid "" +"You also need to allow the reprinting on the point of sale. Go to " +":menuselection:`Configuration --> Point of Sale`, open the one you want to " +"configure and and tick the option **Reprinting**." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:25 +msgid "How to reprint a receipt?" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:27 +msgid "" +"In the Point of Sale interface click on the **Reprint Receipt** button." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:32 +msgid "The last printed receipt will be printed again." +msgstr "" + +#: ../../point_of_sale/analyze.rst:3 +msgid "Analyze sales" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:3 +msgid "Getting daily sales statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:7 +msgid "Point of Sale statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:9 +msgid "" +"On your dashboard, click on the **More** button on the point of sale you " +"want to analyse. Then click on **Orders**." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:15 +msgid "You will get the figures for this particular point of sale." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:21 +msgid "Global statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:23 +msgid "Go to :menuselection:`Reports --> Orders`." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:25 +msgid "You will get the figures of all orders for all point of sales." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:31 +msgid "Cashier statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:33 +msgid "Go to :menuselection:`Reports --> Sales Details`." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:35 +msgid "" +"Choose the dates. Select the cashiers by clicking on **Add an item**. Then " +"click on **Print Report**." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:41 +msgid "You will get a full report in a PDF file. Here is an example :" +msgstr "" + +#: ../../point_of_sale/belgian_fdm.rst:3 +msgid "Belgian Fiscal Data Module" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:3 +msgid "Setting up the Fiscal Data Module with the Odoo POS" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:8 +msgid "" +"The Belgian government requires certain businesses to use a government-" +"certified device called a **Fiscal Data Module** (also known as a " +"**blackbox**). This device works together with the POS application and logs " +"certain transactions. On top of that, the used POS application must also be " +"certified by the government and must adhere to strict standards specified by" +" them. `Odoo 9 (Enterprise Edition) is a certified application " +"`_. More " +"information concerning the Fiscal Data Module can be found on `the official " +"website `_." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:20 +msgid "Required hardware" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:22 +msgid "" +"A government certified `Fiscal Data Module " +"`_ per POS, all of them should work, but the " +"Cleancash SC-B is recommended, you will also need:" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:27 +msgid "" +"Serial null modem cable per FDM (`example `__)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:29 +msgid "" +"Serial-to-USB adapter per FDM (`example " +"`__)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:32 +msgid "A registered POSBox per POS configuration" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:35 +msgid "Setup" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:38 +msgid "POSBox" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:40 +msgid "" +"In order to use a Fiscal Data Module, you will need a registered POSBox. " +"These POSBoxes are similar to the regular POSBoxes we sell, but they are " +"registered with the Belgian government. This is required by law. Attempting " +"to use a Fiscal Data Module on a non-registered POSBox will not work. You " +"can verify that the Fiscal Data Module is recognized by the POSBox by going " +"to the *Hardware status page* via the POSBox homepage." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:52 +msgid "Odoo" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:54 +msgid "" +"An Odoo POS app can be given certified POS capabilities by installing the " +"**Belgian Registered Cash Register** app (technical name: " +"``pos_blackbox_be``). Because of government restrictions imposed on us, this" +" installation cannot be undone. After this, you will have to ensure that " +"each POS configuration has a unique registered POSBox associated with it " +"(:menuselection:`Point of Sale --> Configuration --> Point of Sale` and " +"ensure Hardware Proxy / POSBox and the serial number of your POSBox is set)." +" The first time you open the Point of Sale and attempt to do a transaction, " +"you will be asked to input the PIN that you received with your VAT signing " +"card." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:69 +msgid "Certification & On-premise" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:71 +msgid "" +"The certification granted by the government is restricted to the use on " +"odoo.com SaaS instance. The usage of the module from the source or a " +"modified version will **not** be certified. For on-premise users, we also " +"support the Fiscal Data Module in such installations. The main restriction " +"is that this requires an obfuscated version of the ``pos_blackbox_be`` " +"module we will provide on request for Enterprise customers." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:79 +msgid "Restrictions" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:81 +msgid "" +"As mentioned before, in order to get certified the POS application must " +"adhere to strict government guidelines. Because of this, a certified Odoo " +"POS has some limitations not present in the non-certified Odoo POS." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:86 +msgid "Refunding is disabled" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:87 +msgid "Modifying orderline prices" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:88 +msgid "Creating/modifying/deleting POS orders" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:89 +msgid "Selling products without a valid tax" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:90 +msgid "Multiple Odoo POS configurations per POSBox are not allowed" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:91 +msgid "Using the POS without a connection to the POSBox (and thus FDM)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:92 +msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:3 +msgid "Point of Sale Hardware Setup" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:6 +msgid "POSBox Setup Guide" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:11 +#: ../../point_of_sale/overview/setup.rst:206 +msgid "Prerequisites" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:13 +msgid "" +"Before you start setting up your POSBox make sure you have everything. You " +"will need :" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:16 +msgid "The POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:17 +msgid "A 2A Power adapter" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:18 +msgid "A computer or tablet with an up-to-date web browser" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:19 +msgid "A running SaaS or Odoo instance with the Point of Sale installed" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:20 +msgid "A local network set up with DHCP (this is the default setting)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:21 +msgid "An RJ45 Ethernet Cable or a Linux compatible USB Wi-Fi adapter" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:22 +msgid "" +"An Epson USB TM-T20 Printer or another ESC/POS compatible printer " +"(officially supported printers are listed at the `POS Hardware page " +"`_)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:25 +msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:26 +msgid "An Epson compatible cash drawer" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:29 +#: ../../point_of_sale/overview/setup.rst:214 +msgid "Step By Step Setup Guide" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:32 +msgid "Current version of the POSBox (since 2015)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:36 +msgid "Connect peripheral devices" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:38 +msgid "" +"Officially supported hardware is listed on `the POS Hardware page " +"`_, but other hardware " +"might work as well." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:42 +msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:45 +msgid "" +"**Cash drawer**: The cash drawer should be connected to the printer with an " +"RJ25 cable." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:48 +msgid "" +"**Barcode scanner**: Connect your barcode scanner. In order for your barcode" +" scanner to be compatible it must behave as a keyboard and must be " +"configured in **US QWERTY**. It also must end barcodes with an Enter " +"character (keycode 28). This is most likely the default configuration of " +"your barcode scanner." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:54 +msgid "**Scale**: Connect your scale and power it on." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:56 +msgid "" +"**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. " +"Make sure this will connect the POSBox to the same network as your POS " +"device." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:60 +msgid "" +"**Wi-Fi**: If you do not wish to use Ethernet, plug in a Linux compatible " +"USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux " +"compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 " +"chipset. Make sure not to plug in an Ethernet cable, because all Wi-Fi " +"functionality will be bypassed when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:68 +msgid "Power the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:70 +msgid "" +"Plug the power adapter into the POSBox, a bright red status led should light" +" up." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:74 +msgid "Make sure the POSBox is ready" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:76 +msgid "" +"Once powered, The POSBox needs a while to boot. Once the POSBox is ready, it" +" should print a status receipt with its IP address. Also the status LED, " +"just next to the red power LED, should be permanently lit green." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:82 +#: ../../point_of_sale/overview/setup.rst:293 +msgid "Setup the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:84 +msgid "" +"To setup the POSBox in the Point of Sale go to :menuselection:`Point of Sale" +" --> Configuration --> Settings` and select your Point of Sale. Scroll down " +"to the ``Hardware Proxy / POSBox`` section and activate the options for the " +"hardware you want to use through the POSBox. Specifying the IP of the POSBox" +" is recommended (it is printed on the receipt that gets printed after " +"booting up the POSBox). When the IP is not specified the Point of Sale will " +"attempt to find it on the local network." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:93 +msgid "" +"If you are running multiple Point of Sales on the same POSBox, make sure " +"that only one of them has Remote Scanning/Barcode Scanner activated." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:96 +msgid "" +"It might be a good idea to make sure the POSBox IP never changes in your " +"network. Refer to your router documentation on how to achieve this." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:101 +msgid "Launch the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:103 +msgid "" +"If you didn't specify the POSBox's IP address in the configuration, the POS " +"will need some time to perform a network scan to find the POSBox. This is " +"only done once." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:107 +msgid "" +"The Point of Sale is now connected to the POSBox and your hardware should be" +" ready to use." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:111 +msgid "Wi-Fi configuration" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:113 +msgid "" +"The POSBox is Wi-Fi-capable. In order to use it you'll need a Linux " +"compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are" +" Linux compatible. Officially supported are Wi-Fi adapters with a Ralink " +"5370 chipset." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:118 +msgid "" +"Make sure not to plug in an Ethernet cable, as all Wi-Fi related " +"functionality will be disabled when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:122 +msgid "" +"When the POSBox boots with a Wi-Fi adapter it will start its own Wi-Fi " +"Access Point called \"Posbox\" you can connect to. The receipt that gets " +"printed when the POSBox starts will reflect this. In order to make the " +"POSBox connect to an already existing Wi-Fi network, go to the homepage of " +"the POSBox (indicated on the receipt) and go to the Wi-Fi configuration " +"page. On there you can choose a network to connect to. Note that we only " +"support open and WPA(2)-PSK networks. When connecting to a WPA-secured " +"network, fill in the password field. The POSBox will attempt to connect to " +"the specified network and will print a new POSBox status receipt after it " +"has connected." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:133 +msgid "" +"If you plan on permanently setting up the POSBox with Wi-Fi, you can use the" +" \"persistent\" checkbox on the Wi-Fi configuration page when connecting to " +"a network. This will make the network choice persist across reboots. This " +"means that instead of starting up its own \"Posbox\" network it will always " +"attempt to connect to the specified network after it boots." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:140 +msgid "" +"When the POSBox fails to connect to a network it will fall back to starting " +"it's own \"Posbox\" Access Point. If connection is lost with a Wi-Fi network" +" after connecting to it, the POSBox will attempt to re-establish connection " +"automatically." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:146 +msgid "Multi-POS Configuration" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:148 +msgid "" +"The advised way to setup a multi Point of Sale shop is to have one POSBox " +"per Point of Sale. In this case it is mandatory to manually specify the IP " +"address of each POSBox in each Point of Sale. You must also configure your " +"network to make sure the POSBox's IP addresses don't change. Please refer to" +" your router documentation." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:155 +msgid "POSBoxless Guide (advanced)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:159 +msgid "" +"If you are running your Point of Sale on a Debian-based Linux distribution, " +"you do not need the POSBox as you can run its software locally. However the " +"installation process is not foolproof. You'll need at least to know how to " +"install and run Odoo. You may also run into issues specific to your " +"distribution or to your particular setup and hardware configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:166 +msgid "" +"Drivers for the various types of supported hardware are provided as Odoo " +"modules. In fact, the POSBox runs an instance of Odoo that the Point of Sale" +" communicates with. The instance of Odoo running on the POSBox is very " +"different from a 'real' Odoo instance however. It does not handle *any* " +"business data (eg. POS orders), but only serves as a gateway between the " +"Point of Sale and the hardware." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:173 +msgid "" +"The goal of this section will be to set up a local Odoo instance that " +"behaves like the Odoo instance running on the POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:177 +msgid "Image building process" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:179 +msgid "" +"We generate the official POSBox images using the scripts in " +"https://github.com/odoo/odoo/tree/8.0/addons/point_of_sale/tools/posbox. " +"More specifically, we run `posbox_create_image.sh " +"`_." +" This builds an image called ``posbox.img``, which we zip and upload to " +"`nightly.odoo.com `_ for users to download." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:187 +msgid "" +"The scripts in this directory might be useful as a reference if you get " +"stuck or want more detail about something." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:191 +msgid "Summary of the image creation process" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:193 +msgid "" +"The image creation process starts by downloading the latest `Raspbian " +"`_ image. It then locally mounts this Raspbian " +"image and copies over some files and scripts that will make the Raspbian " +"image turn itself into a POSBox when it boots. These scripts will update " +"Raspbian, remove non-essential packages and install required packages. In " +"order to boot Raspbian we use qemu, which is capable of providing ARM " +"emulation. After this, the emulated Raspbian OS will shut itself down. We " +"then once again locally mount the image, remove the scripts that were used " +"to initialize the image at boot and we copy over some extra configuration " +"files. The resulting image is then ready to be tested and used." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:208 +msgid "A Debian-based Linux distribution (Debian, Ubuntu, Mint, etc.)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:209 +msgid "A running Odoo instance you connect to to load the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:210 +msgid "" +"You must uninstall any ESC/POS printer driver as it will conflict with " +"Odoo's built-in driver" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:217 +msgid "Extra dependencies" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:219 +msgid "" +"Because Odoo runs on Python 2, you need to check which version of pip you " +"need to use." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:222 +msgid "``# pip --version``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:224 +#: ../../point_of_sale/overview/setup.rst:230 +msgid "If it returns something like::" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:228 +msgid "You need to try pip2 instead." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:234 +msgid "You can use pip." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:236 +msgid "The driver modules requires the installation of new python modules:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:238 +msgid "``# pip install pyserial``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:240 +msgid "``# pip install pyusb==1.0.0b1``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:242 +msgid "``# pip install qrcode``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:245 +msgid "Access Rights" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:247 +msgid "" +"The drivers need raw access to the printer and barcode scanner devices. " +"Doing so requires a bit system administration. First we are going to create " +"a group that has access to USB devices" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:251 +msgid "``# groupadd usbusers``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:253 +msgid "Then we add the user who will run the OpenERP server to ``usbusers``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:255 +msgid "``# usermod -a -G usbusers USERNAME``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:257 +msgid "" +"Then we need to create a udev rule that will automatically allow members of " +"``usbusers`` to access raw USB devices. To do so create a file called " +"``99-usbusers.rules`` in the ``/etc/udev/rules.d/`` directory with the " +"following content::" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:265 +msgid "Then you need to reboot your machine." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:268 +msgid "Start the local Odoo instance" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:270 +msgid "We must launch the Odoo server with the correct settings" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:272 +msgid "" +"``$ ./odoo.py " +"--load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale,hw_scanner,hw_escpos``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:275 +msgid "Test the instance" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:277 +msgid "" +"Plug all your hardware to your machine's USB ports, and go to " +"``http://localhost:8069/hw_proxy/status`` refresh the page a few times and " +"see if all your devices are indicated as *Connected*. Possible source of " +"errors are: The paths on the distribution differ from the paths expected by " +"the drivers, another process has grabbed exclusive access to the devices, " +"the udev rules do not apply or a superseded by others." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:285 +msgid "Automatically start Odoo" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:287 +msgid "" +"You must now make sure that this Odoo install is automatically started after" +" boot. There are various ways to do so, and how to do it depends on your " +"particular setup. Using the init system provided by your distribution is " +"probably the easiest way to accomplish this." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:295 +msgid "" +"The IP address field in the POS configuration must be either ``127.0.0.1`` " +"or ``localhost`` if you're running the created Odoo server on the machine " +"that you'll use as the Point of Sale device. You can also leave it empty." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:301 +msgid "POSBox Technical Documentation" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:304 +msgid "Technical Overview" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:307 +msgid "The POSBox Hardware" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:309 +msgid "" +"The POSBox's Hardware is based on a `Raspberry Pi 2 " +"`_, a popular " +"single-board computer. The Raspberry Pi 2 is powered with a 2A micro-usb " +"power adapter. 2A is needed to give enough power to the barcode scanners. " +"The Software is installed on a 8Gb Class 10 or Higher SD Card. All this " +"hardware is easily available worldwide from independent vendors." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:318 +msgid "Compatible Peripherals" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:320 +msgid "" +"Officially supported hardware is listed on the `POS Hardware page " +"`_." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:324 +msgid "The POSBox Software" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:326 +msgid "" +"The POSBox runs a heavily modified Raspbian Linux installation, a Debian " +"derivative for the Raspberry Pi. It also runs a barebones installation of " +"Odoo which provides the webserver and the drivers. The hardware drivers are " +"implemented as Odoo modules. Those modules are all prefixed with ``hw_*`` " +"and they are the only modules that are running on the POSBox. Odoo is only " +"used for the framework it provides. No business data is processed or stored " +"on the POSBox. The Odoo instance is a shallow git clone of the ``8.0`` " +"branch." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:335 +msgid "" +"The root partition on the POSBox is mounted read-only, ensuring that we " +"don't wear out the SD card by writing to it too much. It also ensures that " +"the filesystem cannot be corrupted by cutting the power to the POSBox. Linux" +" applications expect to be able to write to certain directories though. So " +"we provide a ramdisk for /etc and /var (Raspbian automatically provides one " +"for /tmp). These ramdisks are setup by ``setup_ramdisks.sh``, which we run " +"before all other init scripts by running it in ``/etc/init.d/rcS``. The " +"ramdisks are named /etc_ram and /var_ram respectively. Most data from /etc " +"and /var is copied to these tmpfs ramdisks. In order to restrict the size of" +" the ramdisks, we do not copy over certain things to them (eg. apt related " +"data). We then bind mount them over the original directories. So when an " +"application writes to /etc/foo/bar it's actually writing to " +"/etc_ram/foo/bar. We also bind mount / to /root_bypass_ramdisks to be able " +"to get to the real /etc and /var during development." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:351 +msgid "Logs of the running Odoo server can be found at:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:353 +msgid "``/var/log/odoo/odoo.log``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:355 +msgid "" +"Various POSBox related scripts (eg. wifi-related scripts) running on the " +"POSBox will log to /var/log/syslog and those messages are tagged with " +"``posbox_*``." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:360 +msgid "Accessing the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:363 +msgid "Local Access" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:365 +msgid "" +"If you plug a QWERTY USB keyboard into one of the POSBox's USB ports, and if" +" you connect a computer monitor to the *HDMI* port of the POSBox, you can " +"use it as a small GNU/Linux computer and perform various administration " +"tasks, like viewing some logs." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:370 +msgid "The POSBox will automatically log in as root on the default tty." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:373 +msgid "Remote Access" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:375 +msgid "" +"If you have the POSBox's IP address and an SSH client you can access the " +"POSBox's system remotely. The login credentials are ``pi``/``raspberry``." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:380 +msgid "Updating The POSBox Software" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:382 +msgid "" +"Only upgrade the POSBox if you experience problems or want to use newly " +"implemented features." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:385 +msgid "" +"The best way to update the POSBox software is to download a new version of " +"the image and flash the SD-Card with it. This operation is described in " +"detail in `this tutorial `_, just " +"replace the standard Raspberry Pi image with the latest one found at `the " +"official POSBox image page `_. This " +"method of upgrading will ensure that you're running the latest version of " +"the POSBox software." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:394 +msgid "" +"The second way of upgrading is through the built in upgrade interface that " +"can be reached through the POSBox homepage. The nice thing about upgrading " +"like this is that you don't have to flash a new image. This upgrade method " +"is limited to what it can do however. It can not eg. update installed " +"configuration files (like eg. /etc/hostapd.conf). It can only upgrade:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:401 +msgid "The internal Odoo application" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:402 +msgid "" +"Scripts in the folder " +"``odoo/addons/point_of_sale/tools/posbox/configuration/``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:404 +msgid "When in doubt, always use the first method of upgrading." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:407 +msgid "Troubleshoot" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:410 +msgid "The POS cannot connect to the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:412 +msgid "" +"The easiest way to make sure the POSBox is properly set-up is to turn it on " +"with the printer plugged in as it will print a receipt indicating any error " +"if encountered or the POSBox's IP address in case of success. If no receipt " +"is printed, check the following steps:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:416 +msgid "" +"Make sure the POSBox is powered on, indicated by a brightly lit red status " +"LED." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:418 +msgid "" +"Make sure the POSBox is ready, this is indicated by a brightly lit green " +"status LED just next to the red power status LED. The POSBox should be ready" +" ~2 minutes after it is started." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:421 +msgid "" +"Make sure the POSBox is connected to the same network as your POS device. " +"Both the device and the POSBox should be visible in the list of connected " +"devices on your network router." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:424 +msgid "" +"Make sure that your LAN is set up with DHCP, and gives IP addresses in the " +"range 192.168.0.X, 192.168.1.X, 10.0.0.X. If you cannot setup your LAN that " +"way, you must manually set up your POSBox's IP address." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:428 +msgid "" +"If you have specified the POSBox's IP address in the configuration, make " +"sure it correspond to the printed on the POSBox's status receipt." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:431 +msgid "Make sure that the POS is not loaded over HTTPS." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:432 +msgid "" +"A bug in Firefox's HTTP implementation prevents the autodiscovery from " +"working reliably. When using Firefox you should manually set up the POSBox's" +" IP address in the POS configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:437 +msgid "The Barcode Scanner is not working" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:439 +msgid "" +"The barcode scanner must be configured in US QWERTY and emit an Enter after " +"each barcode. This is the default configuration of most barcode readers. " +"Refer to the barcode reader documentation for more information." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:443 +msgid "" +"The POSBox needs a 2A power supply to work with some barcode scanners. If " +"you are not using the provided power supply, make sure the one you use has " +"enough power." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:446 +msgid "" +"Some barcode scanners will need more than 2A and will not work, or will work" +" unreliably, even with the provided power supply. In those case you can plug" +" the barcode scanner in a self-powered USB hub." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:449 +msgid "" +"Some poorly built barcode scanners do not advertise themselves as barcode " +"scanners but as a usb keyboard instead, and will not be recognized by the " +"POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:454 +msgid "The Barcode Scanner is not working reliably" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:456 +msgid "" +"Make sure that no more than one device with 'Scan via Proxy'/'Barcode " +"Scanner' enabled are connected to the POSBox at the same time." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:461 +msgid "Printing the receipt takes too much time" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:463 +msgid "" +"A small delay before the first print is expected, as the POSBox will do some" +" preprocessing to speed up the next printings. If you suffer delays " +"afterwards it is most likely due to poor network connection between the POS " +"and the POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:469 +msgid "Some characters are not correctly printed on the receipt" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:471 +msgid "" +"The POSBox does not support all languages and characters. It currently " +"supports Latin and Cyrillic based scripts, with basic Japanese support." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:476 +msgid "The printer is offline" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:478 +msgid "" +"Make sure the printer is connected, powered, has enough paper and has its " +"lid closed, and is not reporting an error. If the error persists, please " +"contact support." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:483 +msgid "The cashdrawer does not open" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:485 +msgid "" +"The cashdrawer should be connected to the printer and should be activated in" +" the POS configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:489 +msgid "Credits" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:490 +msgid "" +"The POSBox project was developed by Frédéric van der Essen with the kind " +"help of Gary Malherbe, Fabien Meghazi, Nicolas Wisniewsky, Dimitri Del " +"Marmol, Joren Van Onder and Antony Lesuisse." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:494 +msgid "" +"This development would not have been possible without the Indiegogo campaign" +" and those who contributed to it. Special thanks goes to the partners who " +"backed the campaign with founding partner bundles:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:498 +msgid "Camptocamp" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:499 +msgid "BHC" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:500 +msgid "openBig" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:501 +msgid "Eeezee-IT" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:502 +msgid "Solarsis LDA" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:503 +msgid "ACSONE" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:504 +msgid "Vauxoo" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:505 +msgid "Ekomurz" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:506 +msgid "Datalp" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:507 +msgid "Dao Systems" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:508 +msgid "Eggs Solutions" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:509 +msgid "OpusVL" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:511 +msgid "" +"And also the partners who've backed the development with the Founding POSBox" +" Bundle:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:514 +msgid "Willow IT" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:515 +msgid "E\\. Akhalwaya & Sons" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:516 +msgid "Multibase" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:517 +msgid "Mindesa" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:518 +msgid "bpso.biz" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:519 +msgid "Shine IT." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:3 +msgid "Getting started with Odoo Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:8 +msgid "" +"Odoo's online **Point of Sale** application is based on a simple, user " +"friendly interface. The **Point of Sale** application can be used online or " +"offline on iPads, Android tablets or laptops." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:12 +msgid "" +"Odoo **Point of Sale** is fully integrated with the **Inventory** and the " +"**Accounting** applications. Any transaction with your point of sale will " +"automatically be registered in your inventory management and accounting and," +" even in your **CRM** as the customer can be identified from the app." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:17 +msgid "" +"You will be able to run real time statistics and consolidations across all " +"your shops without the hassle of integrating several external applications." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:25 +msgid "Install the Point of Sale Application" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:27 +msgid "" +"Start by installing the **Point of Sale** application. Go to " +":menuselection:`Apps` and install the **Point of Sale** application." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:33 +msgid "" +"Do not forget to install an accounting **chart of account**. If it is not " +"done, go to the **Invoicing/Accounting** application and click on **Browse " +"available countries**:" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:40 +msgid "Then choose the one you want to install." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:42 +msgid "When it is done, you are all set to use the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:45 +msgid "Adding Products" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:47 +msgid "" +"To add products from the point of sale **Dashboard** go to " +":menuselection:`Orders --> Products` and click on **Create**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:50 +msgid "" +"The first example will be oranges with a price of ``3€/kg``. In the " +"**Sales** tab, you can see the point of sale configuration. There, you can " +"set a product category, specify that the product has to be weighted or not " +"and ensure that it will be available in the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:58 +msgid "" +"In same the way, you can add lemons, pumpkins, red onions, bananas... in the" +" database." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:62 +msgid "How to easily manage categories?" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:64 +msgid "" +"If you already have a database with your products, you can easily set a " +"**Point of Sale Category** by using the Kanban view and by grouping the " +"products by **Point of Sale Category**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:72 +msgid "Configuring a payment method" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:74 +msgid "" +"To configure a new payment method go to :menuselection:`Configuration --> " +"Payment methods` and click on **Create**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:81 +msgid "" +"After you set up a name and the type of payment method, you can go to the " +"point of sale tab and ensure that this payment method has been activated for" +" the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:86 +msgid "Configuring your points of sales" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:88 +msgid "" +"Go to :menuselection:`Configuration --> Point of Sale`, click on the " +"``main`` point of sale. Edit the point of sale and add your custom payment " +"method into the available payment methods." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:95 +msgid "" +"You can configure each point of sale according to your hardware, " +"location,..." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "An internal identification of the point of sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Accounting journal used to post sales entries." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Accounting journal used to create invoices." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"Check this if you want to group the Journal Items by Product while closing a" +" Session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"Defines what kind of barcodes are available and how they are assigned to " +"products, customers and cashiers" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"This sequence is automatically created by Odoo but you can change it to " +"customize the reference numbers of your orders." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "This Point of sale's sales will be related to this Sales Channel." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables an integrated Virtual Keyboard" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables invoice generation from the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The payment input will behave similarily to bank payment input, and will be " +"prefilled with the exact due amount" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The point of sale will display this product category by default. If no " +"category is specified, all available products will be shown" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The product used to encode the customer tip. Leave empty if you do not " +"accept tips." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The displayed prices will always include all taxes, even if the taxes have " +"been setup differently" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "For imprecise industrial touchscreens" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The product categories will be displayed with pictures." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The hostname or ip address of the hardware proxy, Will be autodetected if " +"left empty" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enable barcode scanning with a remotely connected barcode scanner" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables Electronic Scale integration" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatically open the cashdrawer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bypass browser printing and prints via the hardware proxy" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The receipt will automatically be printed at the end of each order" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The receipt screen will be skipped if the receipt can be printed " +"automatically." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "A short text that will be inserted as a header in the printed receipt" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "A short text that will be inserted as a footer in the printed receipt" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Check the amount of the cashbox at opening and closing." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables Bill Splitting in the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Allows to print the Bill before payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Allow custom notes on Orderlines" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The restaurant floors served by this point of sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:100 +msgid "Now you are ready to make your first steps with your point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:103 +msgid "First Steps in the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:106 +msgid "Your first order" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:108 +msgid "" +"On the dashboard, you can see your points of sales, click on **New " +"session**:" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:119 +msgid "" +"On the right you can see the products list with the categories on the top. " +"If you click on a product, it will be added in the cart. You can directly " +"set the correct quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:125 +#: ../../point_of_sale/shop/cash_control.rst:59 +msgid "Payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:127 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84 €`` " +"and pays with a ``20 €`` note. When it's done, click on **Validate**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:134 +#: ../../point_of_sale/shop/cash_control.rst:68 +msgid "" +"Your ticket is printed and you are now ready to make your second order." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:137 +#: ../../point_of_sale/shop/cash_control.rst:71 +msgid "Closing a session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:139 +msgid "" +"At the end of the day, to close the session, click on the **Close** button " +"on the top right. Click again on the close button of the point of sale. On " +"this page, you will see a summary of the transactions" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:146 +msgid "" +"If you click on a payment method line, the journal of this method appears " +"containing all the transactions performed." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:152 +msgid "Now, you only have to validate and close the session." +msgstr "" + +#: ../../point_of_sale/restaurant.rst:3 +msgid "Advanced Restaurant Features" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:3 +msgid "How to register multiple orders simultaneously?" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:6 +msgid "Register simultaneous orders" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:8 +msgid "" +"On the main screen, just tap on the **+** on the top of the screen to " +"register another order. The current orders remain opened until the payment " +"is done or the order is cancelled." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:16 +msgid "Switch from one order to another" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:18 +msgid "Simply click on the number of the order." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:24 +msgid "Cancel an order" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:26 +msgid "" +"If you made a mistake or if the order is cancelled, just click on the **-** " +"button. A message will appear to confirm the order deletion." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:34 +#: ../../point_of_sale/shop/invoice.rst:115 +msgid ":doc:`../advanced/register`" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:35 +msgid ":doc:`../advanced/reprint`" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:36 +msgid ":doc:`transfer`" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:3 +msgid "How to handle kitchen & bar order printing?" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:8 +#: ../../point_of_sale/restaurant/split.rst:10 +msgid "From the dashboard click on :menuselection:`More --> Settings`:" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:13 +msgid "Under the **Bar & Restaurant** section, tick **Bill Printing**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:18 +msgid "In order printers, click on **add an item** and then **Create**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:23 +msgid "" +"Set a printer **Name**, its **IP address** and the **Category** of product " +"you want to print on this printer. The category of product is useful to " +"print the order for the kitchen." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:30 +msgid "Several printers can be added this way" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:35 +msgid "" +"Now when you register an order, products will be automatically printed on " +"the correct printer." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:39 +msgid "Print a bill before the payment" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:41 +msgid "On the main screen, click on the **Bill** button." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:46 +msgid "Finally click on **Print**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:51 +msgid "Click on **Ok** once it is done." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:54 +msgid "Print the order (kitchen printing)" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:56 +msgid "" +"This is different than printing the bill. It only prints the list of the " +"items." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:59 +msgid "Click on **Order**, it will automatically be printed." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:65 +msgid "" +"The printer is automatically chosen according to the products categories set" +" on it." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:3 +msgid "How to setup Point of Sale Restaurant?" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:5 +msgid "" +"Go to the **Point of Sale** application, :menuselection:`Configuration --> " +"Settings`" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:11 +msgid "" +"Enable the option **Restaurant: activate table management** and click on " +"**Apply**." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:17 +msgid "" +"Then go back to the **Dashboard**, on the point of sale you want to use in " +"restaurant mode, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:23 +msgid "" +"Under the **Restaurant Floors** section, click on **add an item** to insert " +"a floor and to set your PoS in restaurant mode." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:29 +msgid "Insert a floor name and assign the floor to your point of sale." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:34 +msgid "" +"Click on **Save & Close** and then on **Save**. Congratulations, your point " +"of sale is now in Restaurant mode. The first time you start a session, you " +"will arrive on an empty map." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:40 +msgid ":doc:`table`" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:3 +msgid "How to handle split bills?" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:8 +msgid "" +"Split bills only work for point of sales that are in **restaurant** mode." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:15 +msgid "In the settings tick the option **Bill Splitting**." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:23 +#: ../../point_of_sale/restaurant/transfer.rst:8 +msgid "From the dashboard, click on **New Session**." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:28 +msgid "Choose a table and start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:33 +msgid "" +"When customers want to pay and split the bill, there are two ways to achieve" +" this:" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:36 +msgid "based on the total" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:38 +msgid "based on products" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:44 +msgid "Splitting based on the total" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:46 +msgid "" +"Just click on **Payment**. You only have to insert the money tendered by " +"each customer." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:49 +msgid "" +"Click on the payment method (cash, credit card,...) and enter the amount. " +"Repeat it for each customer." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:55 +msgid "" +"When it's done, click on validate. This is how to split the bill based on " +"the total amount." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:59 +msgid "Split the bill based on products" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:61 +msgid "On the main view, click on **Split**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:66 +msgid "" +"Select the products the first customer wants to pay and click on **Payment**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:71 +msgid "You get the total, process the payment and click on **Validate**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:76 +msgid "Follow the same procedure for the next customer of the same table." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:78 +msgid "When all the products have been paid you go back to the table map." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:3 +msgid "How to configure your table map?" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:6 +msgid "Make your table map" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:8 +msgid "" +"Once your point of sale has been configured for restaurant usage, click on " +"**New Session**:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:14 +msgid "" +"This is your main floor, it is empty for now. Click on the **+** icon to add" +" a table." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:20 +msgid "" +"Drag and drop the table to change its position. Once you click on it, you " +"can edit it." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:23 +msgid "Click on the corners to change the size." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:28 +msgid "The number of seats can be set by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:33 +msgid "The table name can be edited by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:38 +msgid "You can switch from round to square table by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:43 +msgid "The color of the table can modify by clicking on this icon :" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:48 +msgid "This icon allows you to duplicate the table:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:53 +msgid "To drop a table click on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:58 +msgid "" +"Once your plan is done click on the pencil to leave the edit mode. The plan " +"is automatically saved." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:65 +msgid "Register your orders" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:67 +msgid "" +"Now you are ready to make your first order. You just have to click on a " +"table to start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:70 +msgid "" +"You can come back at any time to the map by clicking on the floor name :" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:76 +msgid "Edit a table map" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:78 +msgid "On your map, click on the pencil icon to go in edit mode :" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:3 +msgid "How to handle tips?" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:8 +#: ../../point_of_sale/shop/seasonal_discount.rst:63 +msgid "From the dashboard, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:13 +msgid "Add a product for the tip." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:18 +msgid "" +"In the tip product page, be sure to set a sale price of ``0€`` and to remove" +" all the taxes in the accounting tab." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:25 +msgid "Adding a tip" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:27 +msgid "On the payment page, tap on **Tip**" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:32 +msgid "Tap down the amount of the tip:" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:37 +msgid "" +"The total amount has been updated and you can now register the payment." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:3 +msgid "How to transfer a customer from table?" +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:5 +msgid "" +"This only work for Point of Sales that are configured in restaurant mode." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:13 +msgid "" +"Choose a table, for example table ``T1`` and start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:18 +msgid "" +"Register an order. For some reason, customers want to move to table ``T9``. " +"Click on **Transfer**." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:24 +msgid "Select to which table you want to transfer customers." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:29 +msgid "You see that the order has been added to the table ``T9``" +msgstr "" + +#: ../../point_of_sale/shop.rst:3 +msgid "Advanced Shop Features" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:3 +msgid "How to set up cash control?" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:5 +msgid "" +"Cash control permits you to check the amount of the cashbox at the opening " +"and closing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:9 +msgid "Configuring cash control" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:11 +msgid "" +"On the **Point of Sale** dashboard, click on :menuselection:`More --> " +"Settings`." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:17 +msgid "On this page, scroll and tick the the option **Cash Control**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:23 +msgid "Starting a session" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:25 +msgid "On your point of sale dashboard click on **new session**:" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:30 +msgid "" +"Before launching the point of sale interface, you get the open control view." +" Click on set an opening balance to introduce the amount in the cashbox." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:37 +msgid "" +"Here you can insert the value of the coin or bill, and the amount present in" +" the cashbox. The system sums up the total, in this example we have " +"``86,85€`` in the cashbox. Click on **confirm**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:44 +msgid "" +"You can see that the opening balance has changed and when you click on " +"**Open Session** you will get the main point of sale interface." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:61 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84€`` " +"and pays with a ``20€`` note. When it's done, click on **Validate**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:73 +msgid "" +"At the time of closing the session, click on the **Close** button on the top" +" right. Click again on the **Close** button to exit the point of sale " +"interface. On this page, you will see a summary of the transactions. At this" +" moment you can take the money out." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:81 +msgid "" +"For instance you want to take your daily transactions out of your cashbox." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:87 +msgid "" +"Now you can see that the theoretical closing balance has been updated and it" +" only remains you to count your cashbox to set a closing balance." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:93 +msgid "You can now validate the closing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:96 +#: ../../point_of_sale/shop/refund.rst:20 +#: ../../point_of_sale/shop/seasonal_discount.rst:92 +msgid ":doc:`invoice`" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:97 +#: ../../point_of_sale/shop/invoice.rst:116 +#: ../../point_of_sale/shop/seasonal_discount.rst:93 +msgid ":doc:`refund`" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:98 +#: ../../point_of_sale/shop/invoice.rst:117 +#: ../../point_of_sale/shop/refund.rst:21 +msgid ":doc:`seasonal_discount`" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:3 +msgid "How to invoice from the POS interface?" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:8 +msgid "" +"On the **Dashboard**, you can see your points of sales, click on **New " +"session**:" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:14 +msgid "You are on the ``main`` point of sales view :" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:19 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. Switch categories by clicking on it." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:22 +msgid "" +"If you click on a product, it will be added in your cart. You can directly " +"set the correct **Quantity/Weight** by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:26 +msgid "Add a customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:29 +msgid "By selecting in the customer list" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:31 +#: ../../point_of_sale/shop/invoice.rst:54 +msgid "On the main view, click on **Customer** (above **Payment**):" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:36 +msgid "You must set a customer in order to be able to issue an invoice." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:41 +msgid "" +"You can search in the list of your customers or create new ones by clicking " +"on the icon." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:48 +msgid "" +"For more explanation about adding a new customer. Please read the document " +":doc:`../advanced/register`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:52 +msgid "By using a barcode for customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:59 +msgid "Select a customer and click on the pencil to edit." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:64 +msgid "Set a the barcode for customer by scanning it." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:69 +msgid "" +"Save modifications and now when you scan the customer's barcode, he is " +"assigned to the order" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:73 +msgid "" +"Be careful with the **Barcode Nomenclature**. By default, customers' " +"barcodes have to begin with 042. To check the default barcode nomenclature, " +"go to :menuselection:`Point of Sale --> Configuration --> Barcode " +"Nomenclatures`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:82 +msgid "Payment and invoicing" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:84 +msgid "" +"Once the cart is processed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84 €`` " +"and pays with by a ``VISA``." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:88 +msgid "" +"Before clicking on **Validate**, you have to click on **Invoice** in order " +"to create an invoice from this order." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:94 +msgid "Your invoice is printed and you can continue to make orders." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:97 +msgid "Retrieve invoices of a specific customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:99 +msgid "" +"To retrieve the customer's invoices, go to the **Sale** application, click " +"on :menuselection:`Sales --> Customers`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:102 +msgid "On the customer information view, click on the **Invoiced** button :" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:107 +msgid "" +"You will get the list all his invoices. Click on the invoice to get the " +"details." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:114 +#: ../../point_of_sale/shop/refund.rst:19 +#: ../../point_of_sale/shop/seasonal_discount.rst:91 +msgid ":doc:`cash_control`" +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:3 +msgid "How to return and refund products?" +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:5 +msgid "" +"To refund a customer, from the PoS main view, you have to insert negative " +"values. For instance in the last order you count too many ``pumpkins`` and " +"you have to pay back one." +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:12 +msgid "" +"You can see that the total is negative, to end the refund, you only have to " +"process the payment." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:3 +msgid "How to apply Time-limited or seasonal discounts?" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:8 +msgid "To apply time-limited or seasonal discount, use the pricelists." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:10 +msgid "You have to create it and to apply it on the point of sale." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:13 +msgid "Sales application configuration" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:15 +msgid "" +"In the **Sales** application, go to :menuselection:`Configuration --> " +"Settings`. Tick **Advanced pricing based on formula**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:23 +msgid "Creating a pricelist" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:25 +msgid "" +"Once the setting has been applied, a **Pricelists** section appears under " +"the configuration menu on the sales application." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:31 +msgid "Click on it, and then on **Create**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:36 +msgid "" +"Create a **Pricelist** for your point of sale. Each pricelist can contain " +"several items with different prices and different dates. It can be done on " +"all products or only on specific ones. Click on **Add an item**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "" +"If unchecked, it will allow you to hide the pricelist without removing it." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Allow the end user to choose this price list" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:45 +msgid "" +"For example, the price of the oranges costs ``3€`` but for two days, we want" +" to give a ``10%`` discount to our PoS customers." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:51 +msgid "" +"You can do it by adding the product or its category and applying a " +"percentage discount. Other price computation can be done for the pricelist." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:55 +msgid "After you save and close, your pricelist is ready to be used." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:61 +msgid "Applying your pricelist to the Point of Sale" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:68 +msgid "On the right, you will be able to assign a pricelist." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:74 +msgid "" +"You just have to update the pricelist to apply the time-limited discount(s)." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:80 +msgid "" +"When you start a new session, you can see that the price have automatically " +"been updated." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:87 +msgid "When you update a pricelist, you have to close and open the session." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/practical.po b/locale/ru/LC_MESSAGES/practical.po new file mode 100644 index 000000000..2a9edcd16 --- /dev/null +++ b/locale/ru/LC_MESSAGES/practical.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../practical.rst:3 +msgid "Practical Information" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/project.po b/locale/ru/LC_MESSAGES/project.po new file mode 100644 index 000000000..0300f4e53 --- /dev/null +++ b/locale/ru/LC_MESSAGES/project.po @@ -0,0 +1,1696 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../project.rst:5 +msgid "Project" +msgstr "" + +#: ../../project/advanced.rst:3 +msgid "Advanced" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:3 +msgid "How to use projects to handle claims/issues?" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:5 +msgid "" +"A company selling support services often has to deal with problems occurring" +" during the implementation of the project. These issues have to be solved " +"and followed up as fast as possible in order to ensure the deliverability of" +" the project and a positive customer satisfaction." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:10 +msgid "" +"For example, as an IT company offering the implementation of your software, " +"you might have to deal with customers emails experiencing technical " +"problems. Odoo offers the opportunity to create dedicated support projects " +"which automatically generate tasks upon receiving an customer support email." +" This way, the issue can then be assigned directly to an employee and can be" +" closed more quickly." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:18 +#: ../../project/advanced/so_to_task.rst:24 +#: ../../project/configuration/time_record.rst:12 +#: ../../project/configuration/visualization.rst:15 +#: ../../project/planning/assignments.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:20 +msgid "" +"The following configuration are needed to be able to use projects for " +"support and issues. You need to install the **Project management** and the " +"**Issue Tracking** modules." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:31 +msgid "Create a project" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:33 +msgid "" +"The first step in order to set up a claim/issue management system is to " +"create a project related to those claims. Let's start by simply creating a " +"**support project**. Enter the Project application dashboard, click on " +"create and name your project **Support**. Tick the **Issues** box and rename" +" the field if you want to customize the Issues label (e.g. **Bugs** or " +"**Cases**). As issues are customer-oriented tasks, you might want to set the" +" Privacy/Visibility settings to **Customer project** (therefore your client " +"will be able to follow his claim in his portal)." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:43 +msgid "" +"You can link the project to a customer if the project has been created to " +"handle a specific client issues, otherwise you can leave the field empty." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:51 +msgid "Invite followers" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:53 +msgid "" +"You can decide to notify your employees as soon as a new issue will be " +"created. On the **Chatter** (bottom of the screen), you will notice two " +"buttons on the right : **Follow** (green) and **No follower** (white). Click" +" on the first to receive personally notifications and on the second to add " +"others employees as follower of the project (see screenshot below)." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:63 +msgid "Set up your workflow" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:65 +msgid "" +"You can easily personalize your project stages to suit your workflow by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column** (see image below). If you want to " +"rearrange the order of your stages, you can easily do so by dragging and " +"dropping the column you want to move to the desired location. You can also " +"edit, fold or unfold anytime your stages by using the **setting** icon on " +"your desired stage." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:77 +msgid "Generate issues from emails" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:79 +msgid "" +"When your project is correctly set up and saved, you will see it appearing " +"in your dashboard. Note that an email address for that project is " +"automatically generated, with the name of the project as alias." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:87 +msgid "" +"If you cannot see the email address on your project, go to the menu " +":menuselection:`Settings --> General Settings` and configure your alias " +"domain. Hit **Apply** and go back to your **Projects** dashboard where you " +"will now see the email address under the name of your project." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:92 +msgid "" +"Every time one of your client will send an email to that email address, a " +"new issue will be created." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:96 +#: ../../project/advanced/so_to_task.rst:113 +#: ../../project/planning/assignments.rst:137 +msgid ":doc:`../configuration/setup`" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:97 +msgid ":doc:`../configuration/collaboration`" +msgstr "" + +#: ../../project/advanced/feedback.rst:3 +msgid "How to gather feedback from customers?" +msgstr "" + +#: ../../project/advanced/feedback.rst:6 +#: ../../project/configuration/setup.rst:6 +#: ../../project/configuration/time_record.rst:6 ../../project/overview.rst:3 +#: ../../project/overview/main_concepts.rst:3 +msgid "Overview" +msgstr "" + +#: ../../project/advanced/feedback.rst:8 +msgid "" +"As a manager, it's not always simple to follow everything your teams do. " +"Having a simple customer feedback can be very interesting to evaluate the " +"performances of your teams. You can very easily gather feedbacks from your " +"customers using Odoo." +msgstr "" + +#: ../../project/advanced/feedback.rst:13 +msgid "" +"An e-mail can be sent during the project to get the customer feedbacks. He " +"just has to choose between 3 smileys to assess your work (Smile, Neutral or " +"Sad)." +msgstr "" + +#: ../../project/advanced/feedback.rst:18 +msgid "How to gather feedbacks from customers" +msgstr "" + +#: ../../project/advanced/feedback.rst:20 +msgid "" +"Before getting started some configuration is necessary. First of all it's " +"necessary to install the **Project** application. To do so simply go to the " +"apps module and install it." +msgstr "" + +#: ../../project/advanced/feedback.rst:27 +msgid "" +"Moreover, in the same menu, you have to install the **Project Rating** " +"module." +msgstr "" + +#: ../../project/advanced/feedback.rst:33 +msgid "" +"Next, go back into the back-end and enter the project module. Select the " +"**Configuration** button and click on **Settings** in the dropdown menu. " +"Next select **Allow activating customer rating on projects, at issue " +"completion**. Don't forget to apply your changes." +msgstr "" + +#: ../../project/advanced/feedback.rst:42 +msgid "How to get a Customer feedback?" +msgstr "" + +#: ../../project/advanced/feedback.rst:44 +msgid "" +"A e-mail can be sent to the customers at each stage of the ongoing projects." +msgstr "" + +#: ../../project/advanced/feedback.rst:47 +msgid "" +"First, you need to choose for which projects you want to get a feedback." +msgstr "" + +#: ../../project/advanced/feedback.rst:50 +msgid "Project configuration" +msgstr "" + +#: ../../project/advanced/feedback.rst:52 +msgid "" +"Go to the **Project** application, in the project settings select the " +"**Customer satisfaction** option." +msgstr "" + +#: ../../project/advanced/feedback.rst:59 +msgid "Email Template" +msgstr "" + +#: ../../project/advanced/feedback.rst:61 +msgid "" +"Go to the stage settings (click on the gear icon on the top of the stage " +"column, then select **Edit**). Choose the e-mail template that will be used." +" You can directly edit it from there." +msgstr "" + +#: ../../project/advanced/feedback.rst:68 +msgid "Here is an email example that a customer can receive :" +msgstr "" + +#: ../../project/advanced/feedback.rst:74 +msgid "" +"The customer just has to click on a smiley (Smile, Neutral or Sad) to assess" +" your work. The customer can reply to the email to add more information. It " +"will be added to the chatter of the task." +msgstr "" + +#: ../../project/advanced/feedback.rst:79 +msgid "Reporting" +msgstr "" + +#: ../../project/advanced/feedback.rst:81 +msgid "" +"You have a brief summary on the satisfaction in the upper right corner of " +"the project." +msgstr "" + +#: ../../project/advanced/feedback.rst:88 +msgid "How to display the ratings on your website?" +msgstr "" + +#: ../../project/advanced/feedback.rst:90 +msgid "" +"First of all it's necessary to install the **Website Builder** application. " +"To do so simply go to the apps module and search for the website builder." +msgstr "" + +#: ../../project/advanced/feedback.rst:97 +msgid "" +"Moreover, in the same menu, you have to install the **Website Rating Project" +" Issue** module." +msgstr "" + +#: ../../project/advanced/feedback.rst:103 +msgid "" +"Then, you will be able to publish your result on your website by clicking on" +" the website button in the upper right corner and confirming it in the front" +" end of the website." +msgstr "" + +#: ../../project/advanced/feedback.rst:111 +msgid ":doc:`claim_issue`" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:3 +msgid "How to create tasks from sales orders?" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:5 +msgid "" +"In this section, we will see the integration between Odoo's **Project " +"management** and **Sales** modules and more precisely how to generate tasks " +"from sales order lines." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:9 +msgid "" +"In project management, a task is an activity that needs to be accomplished " +"within a defined period of time. For a company selling services, the task " +"typically represents the service that has been sold to the customer and that" +" needs to be delivered. This is why it is useful to be able to generate a " +"task from a sale order in order to streamline the process between the Sales " +"and Services departments." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:16 +msgid "" +"As an example, you may sell a pack of ``50 Hours`` of support at " +"``$25,000``. The price is fixed and charged initially. But you want to keep " +"track of the support service you did for the customer. On the sale order, " +"the service will trigger the creation of a task from which the consultant " +"will record timesheets and, if needed, reinvoice the client according to the" +" overtime spent on the project." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:27 +msgid "Install the required applications" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:29 +msgid "" +"In order to be able to generate a task from a sale order you will need to " +"install the **Sales Management** and **Project** application. Simply go into" +" the application module and install the following:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:39 +msgid "" +"Moreover if you wish to be able to invoice your customers based on time " +"spent on the task, it is also necessary to install the **Timesheet** module." +" Simply go into the application module and install the following:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:47 +msgid "Create and set up a product" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:49 +msgid "" +"You need to configure your service on the product form itself in order to " +"generate a task every time it will be sold. From the **Sales** module, use " +"the menu :menuselection:`Sales --> Products` and create a new product with " +"the`following setup:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:54 +msgid "**Name**: Technical Support" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:56 +msgid "**Product Type**: Service" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:58 +msgid "" +"**Unit of Measure**: Hours (go to :menuselection:`Configuration --> " +"Settings` and, under **Unit of measures**, check the **Some products may be " +"sold/purchased in different unit of measures (advanced)** radio button)" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:63 +msgid "" +"**Invoicing policy**: You can set up your invoice policy either on ordered " +"quantity or on delivered quantity. You can easily follow the amount of hours" +" that were delivered and/or invoiced to your client." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:68 +msgid "" +"**Track Service**: Create a task and track hours, as your product is a " +"service invoiceable by hours you have to set the units of measures of the " +"product to hours as well." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:76 +msgid "" +"Link your task to an existing project or create a new one on the fly if the " +"product is specific to one project. Otherwise, you can leave it blank, odoo " +"will then create a project per SO." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:81 +msgid "Create the Sales Order" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:83 +msgid "" +"Once the product is set up, you can create a quotation or a sale order with " +"the related product. Once the quotation is confirmed and transformed into a " +"sale order, the task will be created." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:91 +msgid "Access the task generated from the sale order" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:93 +msgid "On the Project module, your new task will appear :" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:95 +msgid "" +"either on a related project if you have selected one in the product form" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:98 +msgid "" +"either on a new project with the name of related the sale order as title " +"(you can easily change the name of the project by clicking on " +":menuselection:`More --> Settings`)" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:105 +msgid "" +"On the task itself, you will now be able to record timesheets and to invoice" +" your customers based on your invoicing policy." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:109 +msgid "" +"On Odoo, the central document is the sales order, which means that the " +"source document of the task is the related sales order." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:114 +msgid ":doc:`../../sales/invoicing/services/reinvoice`" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:115 +msgid ":doc:`../../sales/invoicing/services/support`" +msgstr "" + +#: ../../project/application.rst:3 +msgid "Awesome Timesheet App" +msgstr "" + +#: ../../project/application/intro.rst:3 +msgid "Demonstration Video" +msgstr "" + +#: ../../project/application/intro.rst:11 +#: ../../project/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../project/application/intro.rst:13 +msgid "" +"Awesome Timesheet is a mobile app that helps me to instantly record any time" +" spent on projects in just a click. It's so effortless." +msgstr "" + +#: ../../project/application/intro.rst:16 +msgid "" +"Regardless of the device, the timesheet app is just one click away. Look at " +"the chrome plugin. No need to sign in, just click and start. It's smooth. It" +" works offline too and is automatically synchronized with my Odoo account." +msgstr "" + +#: ../../project/application/intro.rst:21 +msgid "" +"Plus, I get individual statistics via the mobile and chrome plugin. I can go" +" further in the analysis in my Odoo account. I receive reports of timesheets" +" per user, drill-down per project, and much more." +msgstr "" + +#: ../../project/application/intro.rst:25 +msgid "" +"Awesome Timesheet is fully integrated with Odoo invoicing, the customer " +"billing is done automatically. But also with Odoo projects. It's time-" +"saving!" +msgstr "" + +#: ../../project/application/intro.rst:28 +msgid "Download awesome timesheet now and gain in productivity." +msgstr "" + +#: ../../project/configuration.rst:3 +msgid "Configuration and basic usage" +msgstr "" + +#: ../../project/configuration/collaboration.rst:3 +msgid "How to manage & collaborate on tasks?" +msgstr "" + +#: ../../project/configuration/collaboration.rst:6 +msgid "Responsibilities" +msgstr "" + +#: ../../project/configuration/collaboration.rst:8 +msgid "In Odoo, you can assign the person who is in charge of the task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:10 +msgid "" +"When creating a task, by default you are responsible for it. You can change " +"this by simply typing the username of someone else and choosing it from the " +"suggestions in the drop down menu." +msgstr "" + +#: ../../project/configuration/collaboration.rst:15 +msgid "" +"If you add someone new, you can \"Create & Edit\" a new user on the fly. In " +"order to do so, you need the administrator rights." +msgstr "" + +#: ../../project/configuration/collaboration.rst:19 +msgid "Followers" +msgstr "" + +#: ../../project/configuration/collaboration.rst:21 +msgid "" +"In a task, you can add other users as **Followers**. Adding a follower means" +" that this person will be notified of any changes that might happen in the " +"task. The goal is to allow outside contribution from the chatter. This can " +"be invaluable when you need the advice of colleagues from other departments." +" You could also invite customers to take part in the task. They'll be " +"notified by email of the conversation in the chatter, and will be able to " +"take part in it simply by replying to the mail. The followers can see the " +"whole task like you, with the description and the chatter." +msgstr "" + +#: ../../project/configuration/collaboration.rst:32 +msgid "Project: follow a project to follow the pipe" +msgstr "" + +#: ../../project/configuration/collaboration.rst:34 +msgid "" +"You can decide to follow a Project. In this situation, you'll be notified of" +" any changes from the project: tasks sliding from one stage to " +"another,conversation taking place,, etc. You'll receive all the information " +"in your inbox. This feature is perfect for a Project Manager who wants to " +"see the big picture all the time." +msgstr "" + +#: ../../project/configuration/collaboration.rst:41 +msgid "Task: follow a specific task" +msgstr "" + +#: ../../project/configuration/collaboration.rst:43 +msgid "" +"Following a task is the same idea as following a project, except you are " +"focused on a specific part of the project. All notifications or changes in " +"that task also appear in your inbox." +msgstr "" + +#: ../../project/configuration/collaboration.rst:48 +msgid "Choose which action to follow" +msgstr "" + +#: ../../project/configuration/collaboration.rst:50 +msgid "" +"You can choose what you want to follow by clicking on the down arrow in the " +"Following button." +msgstr "" + +#: ../../project/configuration/collaboration.rst:53 +msgid "" +"By default, you follow the discussions but you can also choose to be " +"notified when a note is logged in, when a task is created, blocked or ready " +"to go, and when the stage of the task has changed." +msgstr "" + +#: ../../project/configuration/collaboration.rst:61 +msgid "Time management: analytic accounts" +msgstr "" + +#: ../../project/configuration/collaboration.rst:63 +msgid "" +"Whether it helps you for estimation of future projects or data for billing " +"or invoicing, time tracking in Project Management is a real plus." +msgstr "" + +#: ../../project/configuration/collaboration.rst:67 +msgid "" +"The Odoo Timesheet app is perfectly integrated with Odoo Project and can " +"help you track time easily." +msgstr "" + +#: ../../project/configuration/collaboration.rst:70 +msgid "" +"Once Odoo Timesheet is installed, the timesheet option is automatically " +"available in projects and on tasks." +msgstr "" + +#: ../../project/configuration/collaboration.rst:73 +msgid "" +"To avoid any confusion, Odoo works with analytic accounts. An analytic " +"account is the name that will always be the reference for a specific project" +" or contract. Each time a project is created, an analytic account is " +"automatically created under the same name." +msgstr "" + +#: ../../project/configuration/collaboration.rst:79 +msgid "Record a timesheet on a project:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:81 +msgid "Click on the settings of a project." +msgstr "" + +#: ../../project/configuration/collaboration.rst:86 +msgid "Click on the Timesheet button in the top grey menu." +msgstr "" + +#: ../../project/configuration/collaboration.rst:91 +msgid "" +"You get the Odoo Timesheet. Click on Create and a line will appear with " +"today's date and time. Your project name is automatically selected as the " +"Analytic Account. No task is set, you can choose to add a specific task for " +"it, or not." +msgstr "" + +#: ../../project/configuration/collaboration.rst:99 +msgid "" +"If you go now to Odoo Timesheet, your line will be recorded among your other" +" timesheets." +msgstr "" + +#: ../../project/configuration/collaboration.rst:103 +msgid "Record a timesheet on a task:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:105 +msgid "Within a task, the timesheet option is also available." +msgstr "" + +#: ../../project/configuration/collaboration.rst:107 +msgid "" +"In the task, click on the Edit button. Go on the Timesheet tab and click on " +"Add an item." +msgstr "" + +#: ../../project/configuration/collaboration.rst:110 +msgid "" +"A line will appear with the name of the project already selected in the " +"Analytic account." +msgstr "" + +#: ../../project/configuration/collaboration.rst:113 +msgid "" +"Again, you'll find back these timesheet lines in the Odoo Timesheet " +"application." +msgstr "" + +#: ../../project/configuration/collaboration.rst:119 +msgid "" +"At the end of your project, you can get a real idea of the time you spent on" +" it by searching based on the Analytic Account name of your project." +msgstr "" + +#: ../../project/configuration/collaboration.rst:124 +msgid "Document Management in tasks" +msgstr "" + +#: ../../project/configuration/collaboration.rst:126 +msgid "" +"You can manage documents related to tasks whether they're plans, pictures of" +" the formatting, etc. An image is sometimes more informative than a thousand" +" words! You have two ways to add a document to a task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:130 +msgid "" +"1. You can add an image/document to your task by clicking on the Attachment " +"tab on the top of the form." +msgstr "" + +#: ../../project/configuration/collaboration.rst:136 +msgid "" +"2. You can add an image/document to your task through the Chatter. You can " +"log a note/send a message and attach a file to it. Or if someone sends an " +"email with an attachment, the document will be automatically saved in the " +"task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:145 +msgid "" +"If you have an important image that helps to understand the tasks you can " +"set it up as Cover Image. It'll show up in the Kanban view directly." +msgstr "" + +#: ../../project/configuration/collaboration.rst:152 +msgid "Collaborate on tasks" +msgstr "" + +#: ../../project/configuration/collaboration.rst:154 +msgid "" +"Tasks in Odoo Project are made to help you to work easily together with your" +" colleagues. This helps you save time and energy." +msgstr "" + +#: ../../project/configuration/collaboration.rst:157 +msgid "" +"The idea is to stay up to date with what interests you. You can collaborate " +"with your colleagues by writing on the same task at the same time, with task" +" delegation and the Chatter." +msgstr "" + +#: ../../project/configuration/collaboration.rst:162 +msgid "Create a task from an email" +msgstr "" + +#: ../../project/configuration/collaboration.rst:164 +msgid "" +"You can configure an email address linked to your project. When an email is " +"sent to that address, it automatically creates a task in the first step of " +"the project, with all the recipients (To/Cc/Bcc) as followers." +msgstr "" + +#: ../../project/configuration/collaboration.rst:168 +msgid "" +"With Odoo Online, the mail gateway is already configured and so every " +"project gets an automatic email address." +msgstr "" + +#: ../../project/configuration/collaboration.rst:171 +msgid "" +"The email is always the name of the project (with \"-\" instead of the " +"space), you'll see it under the name of your project in the Project " +"Dashboard." +msgstr "" + +#: ../../project/configuration/collaboration.rst:178 +msgid "" +"This email address create by default following the project name can be " +"changed." +msgstr "" + +#: ../../project/configuration/collaboration.rst:181 +msgid "The alias of the email address can be changed by the project manager." +msgstr "" + +#: ../../project/configuration/collaboration.rst:183 +msgid "To do so, go to the Project Settings and click on the Email Tab." +msgstr "" + +#: ../../project/configuration/collaboration.rst:185 +msgid "You can directly edit your project email address." +msgstr "" + +#: ../../project/configuration/collaboration.rst:191 +msgid "The Chatter, status and follow-up." +msgstr "" + +#: ../../project/configuration/collaboration.rst:193 +msgid "" +"The Chatter is a very useful tool. It is a communication tool and shows the " +"history of the task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:196 +msgid "" +"In the Chatter, you can see when the task has been created, when it has " +"passed from one stage to another, etc. Any changes made to that task are " +"logged into the Chatter automatically by the system. It also includes the " +"history of the interaction between you and your customer or colleagues. All " +"interactions are logged on the chatter, making it easy for the task leader " +"to remember past interactions." +msgstr "" + +#: ../../project/configuration/collaboration.rst:203 +msgid "" +"You can interact with followers whether there are internal (your colleagues)" +" or external (the client for example) by logging a note or important " +"information. Also, if you want to send an email to all the followers of that" +" specific task, you can choose to add a message to notify all of them. For " +"both of these options, the date and time is saved on the entry." +msgstr "" + +#: ../../project/configuration/collaboration.rst:214 +msgid "The description of the task, the Pad" +msgstr "" + +#: ../../project/configuration/collaboration.rst:216 +msgid "" +"Odoo allows you to replace the task description field by an Etherpad " +"collaborative note (http://etherpad.org). This means that you can " +"collaborate on tasks in real time with several users contributing to the " +"same content. Every user has their own color and you can replay the whole " +"creation of the content." +msgstr "" + +#: ../../project/configuration/collaboration.rst:222 +msgid "" +"To activate this option, go to :menuselection:`Project Settings --> Pads`, " +"tick \"Collaborative rich text on task description\"." +msgstr "" + +#: ../../project/configuration/collaboration.rst:229 +msgid "" +"If you just need the pad and not the whole task page, you can click on the " +"icon on the top right to get to the pad directly in a full screen view. " +"Click on the ```` icon to get the direct URL of the task description: " +"useful if you want to send it to someone without adding this person as a " +"follower." +msgstr "" + +#: ../../project/configuration/collaboration.rst:239 +msgid "Tasks states" +msgstr "" + +#: ../../project/configuration/collaboration.rst:242 +msgid "Set the state of a task" +msgstr "" + +#: ../../project/configuration/collaboration.rst:244 +msgid "" +"The status of the task is the easiest way to inform your colleagues when you" +" are working on a task, if the task is ready or if it is blocked. It is a " +"visual indicator that is seen in a glance." +msgstr "" + +#: ../../project/configuration/collaboration.rst:248 +msgid "" +"You can change the status of the task from the kanban view or directly from " +"the task. Just click on the status ball to get the choices:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:258 +msgid "Custom states" +msgstr "" + +#: ../../project/configuration/collaboration.rst:260 +msgid "" +"You can decide what the different status mean for each stage of your " +"project. On the kanban view, click on the gear icon on the top of the stage," +" then click on edit:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:267 +msgid "Next to the color ball, write the explanation of the state." +msgstr "" + +#: ../../project/configuration/collaboration.rst:272 +msgid "Now, the explanation will be displayed instead of the generic text:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:278 +msgid "Color Tags" +msgstr "" + +#: ../../project/configuration/collaboration.rst:280 +msgid "" +"In every task, you can add a tag. Tags are very useful to categorize the " +"tasks. It helps you to highlight a task from the Kanban view or better find " +"them thanks to the filters." +msgstr "" + +#: ../../project/configuration/collaboration.rst:284 +msgid "" +"If you are always working with a specific type of tag, you can highlight the" +" tasks containing the tag with the colors. Each tag can get a specific " +"color, it's very visual on the Kanban view." +msgstr "" + +#: ../../project/configuration/collaboration.rst:291 +msgid "" +"In order to make it appear on the kanban view, you have to set a color on " +"the tag, directly from the task:" +msgstr "" + +#: ../../project/configuration/setup.rst:3 +msgid "How to set up & configure a project?" +msgstr "" + +#: ../../project/configuration/setup.rst:8 +msgid "" +"Odoo Project allows you to manage a project together with your whole team, " +"and to communicate with any member for each project and task." +msgstr "" + +#: ../../project/configuration/setup.rst:11 +msgid "" +"It works with projects containing tasks following customizable stages. A " +"project can be internal or customer-oriented. A task is something to perform" +" as part of a project. You will be able to give different tasks to several " +"employees working on this project." +msgstr "" + +#: ../../project/configuration/setup.rst:17 +msgid "Installing the Project module" +msgstr "" + +#: ../../project/configuration/setup.rst:19 +msgid "" +"Open the **Apps** module, search for **Project Management**, and click on " +"**Install**." +msgstr "" + +#: ../../project/configuration/setup.rst:26 +msgid "Creating a new project" +msgstr "" + +#: ../../project/configuration/setup.rst:28 +msgid "" +"Open the **Project** application, and click on **Create**. From this window," +" you can specify the name of the project and set up the privacy of the " +"project." +msgstr "" + +#: ../../project/configuration/setup.rst:32 +msgid "The privacy setting works as:" +msgstr "" + +#: ../../project/configuration/setup.rst:34 +msgid "**Customer Project**: visible in portal if the customer is a follower." +msgstr "" + +#: ../../project/configuration/setup.rst:37 +msgid "**All Employees**: employees see all tasks or issues." +msgstr "" + +#: ../../project/configuration/setup.rst:39 +msgid "" +"**Private Project**: followers can see only the followed tasks or issues" +msgstr "" + +#: ../../project/configuration/setup.rst:42 +msgid "" +"You can also specify if the project is destined to a customer, or leave the " +"**Customer** field empty if not." +msgstr "" + +#: ../../project/configuration/setup.rst:48 +msgid "When you have entered all the required details, click on **Save**." +msgstr "" + +#: ../../project/configuration/setup.rst:51 +msgid "Manage your project's stages" +msgstr "" + +#: ../../project/configuration/setup.rst:54 +msgid "Add your project's stages" +msgstr "" + +#: ../../project/configuration/setup.rst:56 +msgid "On your project's dashboard. Click on **# Tasks**." +msgstr "" + +#: ../../project/configuration/setup.rst:61 +msgid "" +"In the new window, add a new column and name it according to the first stage" +" of your project, then add as many columns as there are stages in your " +"project." +msgstr "" + +#: ../../project/configuration/setup.rst:68 +msgid "" +"For each stage, there are markers for the status of tasks within a stage, " +"that you can personalize to fit your needs." +msgstr "" + +#: ../../project/configuration/setup.rst:71 +msgid "" +"Drag your mouse pointer over a stage name, and click on the appearing " +"bearing, and on the opening menu, click on **Edit**." +msgstr "" + +#: ../../project/configuration/setup.rst:77 +msgid "" +"A new window will open. The color dots and star icon correspond to " +"customizable markers applied on tasks, making it easier to know what task " +"requires attention. You can give them any signification you like." +msgstr "" + +#: ../../project/configuration/setup.rst:84 +msgid "Click on **Save** when you are done." +msgstr "" + +#: ../../project/configuration/setup.rst:87 +msgid "Rearrange stages" +msgstr "" + +#: ../../project/configuration/setup.rst:89 +msgid "" +"You can easily personalize this view to better suit your business needs by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column**. If you want to rearrange the order" +" of your stages, you can easily do so by dragging and dropping the column " +"you want to move to the desired location. You can also fold or unfold your " +"stages by using the **Setting** icon on your desired stage." +msgstr "" + +#: ../../project/configuration/setup.rst:100 +msgid ":doc:`visualization`" +msgstr "" + +#: ../../project/configuration/setup.rst:101 +msgid ":doc:`collaboration`" +msgstr "" + +#: ../../project/configuration/setup.rst:102 +msgid ":doc:`time_record`" +msgstr "" + +#: ../../project/configuration/time_record.rst:3 +msgid "How to record time spent?" +msgstr "" + +#: ../../project/configuration/time_record.rst:8 +msgid "" +"Odoo allows you to record the time spent per employee and per project, for " +"simple reports as well as for direct invoicing to the customer." +msgstr "" + +#: ../../project/configuration/time_record.rst:14 +msgid "" +"In order to record the time spent on projects, you must first activate the " +"invoicing of timesheets. Into the **Project** application, open " +":menuselection:`Configuration --> Settings`. In the **Timesheets** section " +"of the page, tick **Activate timesheets on issues**." +msgstr "" + +#: ../../project/configuration/time_record.rst:23 +msgid "" +"Activating the option will install the Sales, Invoicing, Issue Tracking, " +"Employee and Timesheet apps." +msgstr "" + +#: ../../project/configuration/time_record.rst:27 +msgid "Recording timesheets" +msgstr "" + +#: ../../project/configuration/time_record.rst:29 +msgid "" +"You can record the time spent in projects straight from the projects " +"application. You can either record timesheets in a project, or in a task." +msgstr "" + +#: ../../project/configuration/time_record.rst:34 +msgid "Recording in a project" +msgstr "" + +#: ../../project/configuration/time_record.rst:36 +msgid "" +"In the **Project** application dashboard, open the **More** menu of the " +"project you want to record timesheets for, and click on **Timesheets**." +msgstr "" + +#: ../../project/configuration/time_record.rst:42 +msgid "" +"In the new window, click on **Create** and insert the required details, then" +" click on **Save**." +msgstr "" + +#: ../../project/configuration/time_record.rst:49 +msgid "Recording in a task" +msgstr "" + +#: ../../project/configuration/time_record.rst:51 +msgid "" +"In the **Project** app, open the project you want to record timesheets for, " +"and open the task on which you have been working." +msgstr "" + +#: ../../project/configuration/time_record.rst:54 +msgid "" +"In the task, click on **Edit**, open the **Timesheets** tab and click on " +"**Add an item**. Insert the required details, then click on **Save**." +msgstr "" + +#: ../../project/configuration/visualization.rst:3 +msgid "How to visualize a project's tasks?" +msgstr "" + +#: ../../project/configuration/visualization.rst:5 +msgid "How to visualize a project's tasks" +msgstr "" + +#: ../../project/configuration/visualization.rst:7 +msgid "" +"Tasks are assignments that members of your organisations have to fulfill as " +"part of a project. In day to day business, your company might struggle due " +"to the important amount of tasks to fulfill. Those task are already complex " +"enough. Having to remember them all and follow up on them can be a real " +"burden. Luckily, Odoo enables you to efficiently visualize and organize the " +"different tasks you have to cope with." +msgstr "" + +#: ../../project/configuration/visualization.rst:17 +msgid "" +"The only configuration needed is to install the project module in the module" +" application." +msgstr "" + +#: ../../project/configuration/visualization.rst:24 +msgid "Creating Tasks" +msgstr "" + +#: ../../project/configuration/visualization.rst:26 +msgid "" +"Once you created a project, you can easily generate tasks for it. Simply " +"open the project and click on create a task." +msgstr "" + +#: ../../project/configuration/visualization.rst:32 +msgid "" +"You then first give a name to your task, the related project will " +"automatically be filled in, assign the project to someone, and select a " +"deadline if there is one." +msgstr "" + +#: ../../project/configuration/visualization.rst:40 +#: ../../project/planning/assignments.rst:47 +msgid "Get an overview of activities with the kanban view" +msgstr "" + +#: ../../project/configuration/visualization.rst:42 +msgid "" +"Once you created several tasks, they can be managed and followed up thanks " +"to the Kanban view." +msgstr "" + +#: ../../project/configuration/visualization.rst:45 +msgid "" +"The Kanban view is a post-it like view, divided in different stages. It " +"enables you to have a clear view on the stages your tasks are in and which " +"one have the higher priorities." +msgstr "" + +#: ../../project/configuration/visualization.rst:49 +#: ../../project/planning/assignments.rst:53 +msgid "" +"The Kanban view is the default view when accessing a project, but if you are" +" on another view, you can go back to it any time by clicking the kanban view" +" logo in the upper right corner" +msgstr "" + +#: ../../project/configuration/visualization.rst:57 +msgid "How to nototify your collegues about the status of a task?" +msgstr "" + +#: ../../project/configuration/visualization.rst:63 +#: ../../project/planning/assignments.rst:80 +msgid "Sort tasks by priority" +msgstr "" + +#: ../../project/configuration/visualization.rst:65 +msgid "" +"On each one of your columns, you have the ability to sort your tasks by " +"priority. Tasks with a higher priority will be automatically moved to the " +"top of the column. From the Kanban view, click on the star in the bottom " +"left of a task to tag it as **high priority**. For the tasks that are not " +"tagged, Odoo will automatically classify them according to their deadlines." +msgstr "" + +#: ../../project/configuration/visualization.rst:72 +msgid "" +"Note that dates that passed their deadlines will appear in red (in the list " +"view too) so you can easily follow up the progression of different tasks." +msgstr "" + +#: ../../project/configuration/visualization.rst:80 +#: ../../project/planning/assignments.rst:119 +msgid "Keep an eye on deadlines with the Calendar view" +msgstr "" + +#: ../../project/configuration/visualization.rst:82 +msgid "" +"If you add a deadline in your task, they will appear in the calendar view. " +"As a manager, this view enables you to keep an eye on all deadline in a " +"single window." +msgstr "" + +#: ../../project/configuration/visualization.rst:89 +#: ../../project/planning/assignments.rst:128 +msgid "" +"All the tasks are tagged with a color corresponding to the employee assigned" +" to them. You can easily filter the deadlines by employees by ticking the " +"related boxes on the right of the calendar view." +msgstr "" + +#: ../../project/configuration/visualization.rst:94 +#: ../../project/planning/assignments.rst:133 +msgid "" +"You can easily change the deadline from the Calendar view by dragging and " +"dropping the task to another case." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo Project" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:13 +msgid "" +"As a business manager, I have a varied job involving multiple stakeholders. " +"To manage every task seamlessly, Odoo Projects is of great help." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:17 +msgid "" +"With Odoo Projects, our project team members can easily plan and execute the" +" launching of a new product line in Canada. I organized this project by " +"creating different stages. It allows us to clearly identify the status of " +"any task at any time, and for any user. It is convenient for any other " +"project manager too." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:24 +msgid "" +"These well-structured project stages are fully customizable. Here I identify" +" one missing stage, I can easily add it in just a click. In our project " +"management process, I proceed to a final review, so I add this stage. Odoo " +"projects is designed to work for any kind of business." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:30 +msgid "" +"Once a task is done, each colleague can highlight it by changing its status." +" That will help the project manager to review the task before changing the " +"stage with a simple drag and drop. Easy, right?" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:35 +msgid "" +"We can also organize the different tasks by adapting the view. Here, I " +"select the list view, which shows other information such as the working time" +" progress. If I click on my task, I land on the form view where I can edit " +"the planned hours and enter my timesheets. This is a great tool for any " +"project manager. Controlling the working time progress and the time spent " +"for each team member is essential. I set the time for the sales team " +"training to 24 hours. Today, I prepared the material, so I will log 4 hours " +"in the timesheet. The working time progress updates automatically. Thanks to" +" this timesheet integration, the project manager has a thorough follow-up on" +" the progress of each task." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:49 +msgid "" +"Another great feature in Odoo projects is the forecast tool. When it is " +"activated, I can plan resources per project and the workload. Therefore, the" +" time allocation for other projects is much easier. For this project, I have" +" to train members of the sales team. It will require 50% of my time until " +"the end of the week. As project manager, I can do this resource allocation " +"for any user and adapt it according to their other projects. This will " +"prevent any form of time overlap. I can reassign a task or adapt the " +"deadline. Odoo projects is the perfect app for strategic and executive " +"planning." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:61 +msgid "" +"Plus, every aspect of any project can be analyzed, thanks to the reports. " +"For example, We can have a report of effective hours spent in comparison " +"with the planned hours. I can assess the profitability of any project, any " +"task, or any team member. I can also look at the number of hours assigned to" +" each team member." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:68 +msgid "" +"Another element of an excellent project management is communication. This is" +" a key factor for the success of any project. While dealing with multiple " +"stakeholders, being able to share documents directly in the task is very " +"helpful. With Odoo projects, I can discuss through the chat feature that is " +"always one-click away. I can also start a new conversation with anyone in my" +" team." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:76 +msgid "" +"In addition to being a powerful app for managing projects seamlessy, Odoo " +"projects is also an effective customer service or after-sales app. With it, " +"I can follow any customer issue, even create a dedicated support project. " +"The app also automatically creates an invoice of time spent on tasks or " +"issues." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:83 +msgid "" +"Odoo projects is a powerful, yet easy-to-use app. At first, I used the " +"planner to clearly state my objectives and set up the project app. Get this " +"app, it will help you get started quickly too." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:88 +msgid "Start your free trial now and better manage your projects with Odoo!" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:91 +msgid "Start your free trial now with the CRM sales people love" +msgstr "" + +#: ../../project/planning.rst:3 +msgid "Planning your project" +msgstr "" + +#: ../../project/planning/assignments.rst:3 +msgid "How to plan and track employees' assignments?" +msgstr "" + +#: ../../project/planning/assignments.rst:5 +msgid "" +"Following and planning your employees' assignments can be a heavy challenge " +"especially when you manage several people. Luckily, using Odoo Project, you " +"can handle it in only a couple of clicks." +msgstr "" + +#: ../../project/planning/assignments.rst:12 +msgid "" +"The only necessary configuration is to install the **Project Management** " +"module. To do so, go in the application module, search for project and " +"install the application." +msgstr "" + +#: ../../project/planning/assignments.rst:19 +msgid "" +"If you wish to manage time estimation, you will need to enable timesheets on" +" tasks. From the **Project** application, go to " +":menuselection:`Configuration --> Settings` in the dropdown menu. Then, " +"under **Time Work Estimation**, select the **manage time estimation on " +"tasks** option. Do not forget to apply your changes." +msgstr "" + +#: ../../project/planning/assignments.rst:28 +msgid "" +"This feature will create a progress bar in the form view of your tasks. " +"Every time your salesperson will add working time in his timesheet, the bar " +"will be updated accordingly, based on the initially planned hours." +msgstr "" + +#: ../../project/planning/assignments.rst:36 +msgid "Manage tasks with views" +msgstr "" + +#: ../../project/planning/assignments.rst:38 +msgid "" +"You can have an overview of your different task thanks to the multiple views" +" available with Odoo. Three main views will help you to plan and follow up " +"on your employees' tasks: the kanban view, the list view (using timesheets) " +"and the calendar view." +msgstr "" + +#: ../../project/planning/assignments.rst:43 +msgid "" +"Create and edit tasks in order to fill up your pipeline. Don't forget to " +"fill in a responsible person and an estimated time if you have one." +msgstr "" + +#: ../../project/planning/assignments.rst:49 +msgid "" +"The Kanban view is a post-it like view, divided in different stages. It " +"enables you to have a clear view on the stages your tasks are in and the " +"ones having the higher priorities." +msgstr "" + +#: ../../project/planning/assignments.rst:61 +msgid "Add/rearrange stages" +msgstr "" + +#: ../../project/planning/assignments.rst:63 +msgid "" +"You can easily personalize your project to suit your business needs by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column** (see image below). If you want to " +"rearrange the order of your stages, you can easily do so by dragging and " +"dropping the column you want to move to the desired location. You can also " +"fold or unfold your stages by using the **setting** icon on your desired " +"stage." +msgstr "" + +#: ../../project/planning/assignments.rst:75 +msgid "" +"Create one column per stage in your working process. For example, in a " +"development project, stages might be: Specifications, Development, Test, " +"Done." +msgstr "" + +#: ../../project/planning/assignments.rst:82 +msgid "" +"On each one of your columns, you have the ability to sort your tasks by " +"priority. Tasks with a higher priority will automatically be moved to the " +"top of the column. From the Kanban view, click on the star in the bottom " +"left of a task to tag it as **high priority**. For the tasks that are not " +"tagged, Odoo will automatically classify them according to their deadlines." +msgstr "" + +#: ../../project/planning/assignments.rst:89 +msgid "" +"Note that dates that passed their deadlines will appear in red( in the list " +"view too) so you can easily follow up the progression of different tasks." +msgstr "" + +#: ../../project/planning/assignments.rst:97 +msgid "Don't forget you can filter your tasks with the filter menu." +msgstr "" + +#: ../../project/planning/assignments.rst:100 +msgid "Track the progress of each task with the list view" +msgstr "" + +#: ../../project/planning/assignments.rst:102 +msgid "" +"If you enabled the **Manage Time Estimation on Tasks**, your employees will " +"be able to log their activities on tasks under the **Timesheets** sub-menu " +"along with their duration. The **Working Time Progress** bar will be updated" +" each time the employee will add an activity." +msgstr "" + +#: ../../project/planning/assignments.rst:110 +msgid "" +"As a manager, you can easily overview the time spent on tasks for all " +"employees by using the list view. To do so, access the project of your " +"choice and click on the List view icon (see below). The last column will " +"show you the progression of each task." +msgstr "" + +#: ../../project/planning/assignments.rst:121 +msgid "" +"If you add a deadline in your task, they will appear in the calendar view. " +"As a manager, this view enables you to keep an eye on all deadlines in a " +"single window." +msgstr "" + +#: ../../project/planning/assignments.rst:138 +msgid ":doc:`forecast`" +msgstr "" + +#: ../../project/planning/forecast.rst:3 +msgid "How to forecast tasks?" +msgstr "" + +#: ../../project/planning/forecast.rst:6 +msgid "Introduction to forecast" +msgstr "" + +#: ../../project/planning/forecast.rst:8 +msgid "" +"Scheduling and forecasting tasks is another way to manage projects. In Odoo," +" the Forecast option gives you access to the Gantt chart." +msgstr "" + +#: ../../project/planning/forecast.rst:11 +msgid "" +"So far, you've been working with the Kanban view, which shows you the " +"progress of a project and its related tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:14 +msgid "" +"Now, with the Forecast option, the Gantt view gives you the big picture. " +"It's highly visual which is a real plus for complex projects, and it helps " +"team members to collaborate better." +msgstr "" + +#: ../../project/planning/forecast.rst:18 +msgid "" +"This option is a real benefit in terms of planning and organizing the " +"workload and human resources." +msgstr "" + +#: ../../project/planning/forecast.rst:22 +msgid "How to configure the projects?" +msgstr "" + +#: ../../project/planning/forecast.rst:25 +msgid "Configure the project application" +msgstr "" + +#: ../../project/planning/forecast.rst:27 +msgid "" +"The **Forecast** option helps you to organize your projects. This is perfect" +" when you need to set up a project with a specific deadline. Therefore, each" +" task is assigned a specific timeframe (amount of hours) in which your " +"employee should complete it!" +msgstr "" + +#: ../../project/planning/forecast.rst:32 +msgid "" +"First you need to activate the **Forecast** option for the whole project " +"application:" +msgstr "" + +#: ../../project/planning/forecast.rst:35 +msgid "" +"Go to :menuselection:`Project --> Configuration --> Settings`. Select the " +"Forecast option and click **Apply**." +msgstr "" + +#: ../../project/planning/forecast.rst:41 +msgid "" +"Once this is done, you still need to activate the **Forecast** option " +"specifically for your **Project** (maybe you don't need the Gantt chart for " +"all the projects that you manage)." +msgstr "" + +#: ../../project/planning/forecast.rst:46 +msgid "Configure a specific project." +msgstr "" + +#: ../../project/planning/forecast.rst:48 +msgid "" +"When creating a new project, make sure to select the option \"Allow " +"Forecast\" in your project settings." +msgstr "" + +#: ../../project/planning/forecast.rst:51 +msgid "You'll see the **Forecast** option appearing in the top menu." +msgstr "" + +#: ../../project/planning/forecast.rst:56 +msgid "" +"If you add the Forecasting option to an existing project, whether there are " +"task deadlines or not scheduled, the task won't be displayed." +msgstr "" + +#: ../../project/planning/forecast.rst:59 +msgid "The tasks of a project are not related to a forecast." +msgstr "" + +#: ../../project/planning/forecast.rst:62 +msgid "How to create a forecast?" +msgstr "" + +#: ../../project/planning/forecast.rst:64 +msgid "" +"Before creating a project with forecast, list all the tasks with the " +"projected time they should take. It will help you to coordinate the work." +msgstr "" + +#: ../../project/planning/forecast.rst:68 +msgid "" +"In order to display the projects in the Gantt chart, you need to create the " +"forecast from the task page. To create a forecast, click on the top left " +"corner of the task, **Create a Forecast**." +msgstr "" + +#: ../../project/planning/forecast.rst:76 +msgid "" +"You can also create a new Forecast easily by directly clicking on an empty " +"space in the Gantt chart calendar." +msgstr "" + +#: ../../project/planning/forecast.rst:79 +msgid "" +"The Forecast interface will fill in the name of the Project and the task " +"automatically. You just need to add the dates and the time the task should " +"take." +msgstr "" + +#: ../../project/planning/forecast.rst:87 +msgid "" +"The \"Effective hours\" field appears only if you have the **Timesheet** app" +" installed on your database. This option helps you to see the progress of a " +"task thanks to the integration with Timesheet." +msgstr "" + +#: ../../project/planning/forecast.rst:91 +msgid "" +"For example: When a user fills in a Timesheet with your Project name " +"(Analytic account), with 10 hours spent, the forecast will display 10 hours " +"in the Effective hours field." +msgstr "" + +#: ../../project/planning/forecast.rst:96 +msgid "What are the difference between the views?" +msgstr "" + +#: ../../project/planning/forecast.rst:98 +msgid "" +"In the **Project** app menu you have a **Forecast** menu. This sub-menu " +"helps you to see the Gantt chart from different points of view: by users or " +"by projects." +msgstr "" + +#: ../../project/planning/forecast.rst:103 +msgid "By users : people management" +msgstr "" + +#: ../../project/planning/forecast.rst:105 +msgid "" +"This option displays the Gantt chart with the people assigned. Odoo's Gantt " +"chart shows you who's involved; it gives you the big picture of the project." +" It's very useful to allocate your resources effectively." +msgstr "" + +#: ../../project/planning/forecast.rst:109 +msgid "" +"On the left side, first level, you can see which users are involved. Then, " +"on the second level you see which projects they are assigned to. On the " +"third, you see which tasks they're on." +msgstr "" + +#: ../../project/planning/forecast.rst:113 +msgid "" +"Each task is represented by a coloured rectangle. This rectangle reflects " +"the duration of the task in the calendar." +msgstr "" + +#: ../../project/planning/forecast.rst:116 +msgid "" +"The top rectangle on the first level is the sum of all the tasks compiled " +"from the third level. If it's green, it means that the total time allocated " +"to that user is less than 100%. When it's red, it means that this user is " +"assigned to multiple tasks which total more than 100% of his/her time." +msgstr "" + +#: ../../project/planning/forecast.rst:126 +msgid "Plan the workload" +msgstr "" + +#: ../../project/planning/forecast.rst:128 +msgid "" +"When creating a forecast, you have to select the time the user should spend " +"on it. 100% means that your user should work on it full time during those " +"days. He/She has no other tasks to work on. So you can decide from 1 to 100%" +" how your users should organize their time between different tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:134 +msgid "" +"The power of integration helps you to avoid double booking an employee. For " +"example, if your expert is already at 40% on another task in another " +"project, you can book him/her for only 60% for that period." +msgstr "" + +#: ../../project/planning/forecast.rst:138 +msgid "" +"In the example below, the user \"Administrator\" is working on 2 projects " +"(\"IT1367 Delivery Phases\" and \"Implementation Process56\"). The user is " +"assigned to both projects with a total of 110% of their time. This is too " +"much so the Project Manager should change the users assigned to the task. " +"Otherwise, the PM can change the dedicated time or the dates, to make sure " +"that this is feasible." +msgstr "" + +#: ../../project/planning/forecast.rst:149 +#: ../../project/planning/forecast.rst:191 +msgid "Gantt view advantages" +msgstr "" + +#: ../../project/planning/forecast.rst:151 +msgid "" +"This Gantt view ‘by user' helps you to better plan your human resources. You" +" avoid confusion about the the tasks and the assignations of the users. The " +"Gantt Chart is highly visual and helps to comprehend all the different " +"elements at once. Also, you immediately know what has to be done next. This " +"method helps you to better understand the relations between the tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:158 +#: ../../project/planning/forecast.rst:193 +msgid "The dynamic view of the Gantt in Odoo allows you to:" +msgstr "" + +#: ../../project/planning/forecast.rst:160 +#: ../../project/planning/forecast.rst:195 +msgid "" +"change the time and date of a forecast by clicking and sliding the tasks in " +"the future or in the past" +msgstr "" + +#: ../../project/planning/forecast.rst:163 +#: ../../project/planning/forecast.rst:198 +msgid "create a new forecast into the Gantt chart immediately" +msgstr "" + +#: ../../project/planning/forecast.rst:165 +#: ../../project/planning/forecast.rst:200 +msgid "modify an existing forecast" +msgstr "" + +#: ../../project/planning/forecast.rst:167 +#: ../../project/planning/forecast.rst:202 +msgid "change the length of a task by extending or shortening the rectangle." +msgstr "" + +#: ../../project/planning/forecast.rst:170 +msgid "By projects: project management" +msgstr "" + +#: ../../project/planning/forecast.rst:172 +msgid "" +"The Gantt Chart is the perfect view of a project to better understand the " +"interactions between the tasks. You can avoid overlapping tasks or starting " +"one too early if another one isn't finished. Odoo Gantt chart is clear and " +"helps you to coordinate tasks efficiently." +msgstr "" + +#: ../../project/planning/forecast.rst:177 +msgid "" +"This option displays the Gantt chart by showing the projects on the first " +"level of hierarchy." +msgstr "" + +#: ../../project/planning/forecast.rst:180 +msgid "" +"On the left side, first level, you can see the projects. Then, on the second" +" level you see which users are assigned. On the third, you see which tasks " +"they're on." +msgstr "" + +#: ../../project/planning/forecast.rst:184 +msgid "" +"This view won't show your HR time. The colours don't apply. (see **By " +"Users** section)" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/purchase.po b/locale/ru/LC_MESSAGES/purchase.po new file mode 100644 index 000000000..2096665bf --- /dev/null +++ b/locale/ru/LC_MESSAGES/purchase.po @@ -0,0 +1,2922 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../purchase.rst:5 +msgid "Purchase" +msgstr "" + +#: ../../purchase/overview.rst:3 +#: ../../purchase/replenishment/flows/dropshipping.rst:6 +#: ../../purchase/replenishment/flows/purchase_triggering.rst:6 +#: ../../purchase/replenishment/flows/warning_triggering.rst:6 +#: ../../purchase/replenishment/multicompany/setup.rst:6 +msgid "Overview" +msgstr "" + +#: ../../purchase/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:3 +msgid "Request for Quotation, Purchase Tender or Purchase Order?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:5 +msgid "" +"Although they are intimately related, Requests for Quotation, Purchase " +"Tenders and Purchase Orders are not the same." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:8 +msgid "" +"A **Request for Quotation** (RfQ) is used when you plan to purchase some " +"products and you would like to receive a quote for those products. In Odoo, " +"the Request for Quotation is used to send your list of desired products to " +"your supplier. Once your supplier has answered your request, you can choose " +"to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:15 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:5 +msgid "" +"A **Purchase Tender** (PT), also known as Call for Bids, is used to drive " +"competition between several suppliers in order to get the best offer for a " +"list of products. In comparison to the RfQ, a Purchase Tender is sent to " +"multiple suppliers, stating each are competing with one another, and that " +"the best offer will win. The main interest is that it usually leads to " +"better offers." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:22 +msgid "" +"The **Purchase Order** (PO) is the actual order that you place to the " +"supplier that you chose, either through a RfQ, a Purchase Tender, or simply " +"when you already know which supplier to order from." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:27 +msgid "When to use?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:29 +msgid "" +"A **RfQ** is interesting when you have never purchased the products with " +"that supplier before and therefore don't know their price. It is also useful" +" if you want to challenge your suppliers once you have a well-established " +"relationship with them. You can also use it to assess the cost of a project " +"and see if it makes it feasible." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:35 +msgid "" +"A **Purchase Tender** is used for public offers that require an open " +"offering from several suppliers. It is also useful when you need to make a " +"one-off order for a product and you would like to get the best offer, no " +"matter which supplier it is. It may be used when your supplier has not been " +"up to your standards and you would like to either push them to deliver a " +"better service, or find a replacement in their competitors." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:43 +msgid "When not to use?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:45 +msgid "" +"**RfQ**\\ s become unnecessary once you have established your favorite " +"supplier for each item, and will only increase the delay in the delivery of " +"your items. In that case, the process will be simpler by starting straight " +"from a Purchase Order." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:50 +msgid "" +"**Purchase Tenders** are a long and tedious process that will likely take " +"more than several weeks in the best cases. If you need a quick delivery, " +"this is not the way to go. Also, if you have a well-established relationship" +" with one supplier, think twice before you initiate a PT with them as it " +"might tear the relationship and finally lead to less interesting deals." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:58 +#: ../../purchase/replenishment/flows/compute_date.rst:139 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:39 +msgid "Example" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:60 +msgid "" +"My company builds wooden furniture. For the new series of table we are " +"designing, we need some screws, metal frames and rubber protections." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:63 +msgid "" +"I create a Request for Quotation in Odoo with those products to my usual " +"supplier, and send it by email. He answers back with an offer. However, I am" +" not convinced by the offer, and I want to see if anyone can give a better " +"one." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:68 +msgid "" +"I decide to push competition a bit and set up a Purchase Tender, that Odoo " +"will send to a list of suppliers I specified. Out of the 8 offers I receive," +" one gets my attention and I decide to go ahead with that one." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:72 +msgid "" +"I confirm the order to the supplier by creating a Purchase Order from the " +"PT, and Odoo automatically asks delivery of the items to the supplier." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:77 +#: ../../purchase/purchases/master/suppliers.rst:16 +#: ../../purchase/purchases/master/uom.rst:22 +#: ../../purchase/purchases/rfq/analyze.rst:24 +#: ../../purchase/purchases/rfq/bills.rst:31 +#: ../../purchase/purchases/rfq/create.rst:16 +#: ../../purchase/purchases/rfq/reception.rst:14 +#: ../../purchase/purchases/tender/partial_purchase.rst:14 +#: ../../purchase/replenishment/flows/dropshipping.rst:13 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:58 +#: ../../purchase/replenishment/flows/warning_triggering.rst:21 +msgid "Configuration" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:79 +msgid "" +"If you want to know how to create a **Purchase Order**, read the " +"documentation on :doc:`from_po_to_invoice`" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:82 +msgid "" +"If you want to know how to create a **RfQ**, read the documentation on " +":doc:`../../purchases/rfq/create`" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:85 +msgid "" +"If you want to know how to create a **Purchase Tender**, read the " +"documentation on :doc:`../../purchases/tender/manage_multiple_offers`" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:3 +msgid "From purchase order to invoice and receptions" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:5 +msgid "" +"For most of your everyday purchases, chances are you already know where to " +"purchase and at what price. For these cases, a simple Purchase Order (PO) " +"will allow you to handle the whole process." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:9 +msgid "" +"In Odoo, a purchase order can be created as is, but can also be the result " +"of a Request for Quotation or of a Purchase Tender. Therefore, every " +"purchase made in Odoo has a PO." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:13 +msgid "" +"The PO will generate an invoice, and depending on the contract with your " +"supplier, you will be required to pay the invoice before or after delivery." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:18 +msgid "Install the Purchase Management application" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:20 +msgid "" +"From the **Apps** application, search and install the **Purchase " +"Management** application." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:27 +msgid "Creating a Purchase Order" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:29 +msgid "" +"In the **Purchases** app, open the **Purchase** menu and click on **Purchase" +" Orders**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:32 +msgid "In the **Purchase Orders** window, click on **Create**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:37 +msgid "" +"From the new window, insert the **Vendor** and type in the **Order Date**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:40 +msgid "In the **Products** section, click on **Add an item**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:45 +msgid "Select your product from the list and add a description if necessary." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:47 +msgid "The **Scheduled Date** menu corresponds to the expected delivery date." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:49 +msgid "" +"Type in the quantity which you wish to purchase, then click on **Save** and " +"on **Confirm Order**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:53 +msgid "" +"If you wish to go through the complete flow and create a **Request for " +"Quotation** for this order, refer to the document on " +":doc:`../../purchases/rfq/create`" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:57 +msgid "" +"As you can see, the status of the PO has switched to ``Purchase Order``." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:63 +msgid "Registering invoice, payments and receiving products" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:65 +msgid "" +"Depending on the contract you have with your supplier, you can either pay " +"for the purchase upon delivery of the goods, or get the goods delivered " +"after payment." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:70 +msgid "Payment upon or after reception" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:72 +msgid "Still from your purchase order, click on **Receive Products**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:74 +msgid "" +"In the next page, check that the number of products received corresponds to " +"the number ordered, then manually enter the delivered quantity and click on " +"**Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:81 +msgid "" +"Go back to the PO. In the PO, a **Shipment** and an **Invoice** button have " +"appeared." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:87 +msgid "" +"Click on the **Invoices** button, then click on **Validate**. The invoice is" +" now registered in the system. Click on **Register Payment**, insert the " +"detail of the payment, and click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:94 +#: ../../purchase/overview/process/from_po_to_invoice.rst:124 +msgid "" +"Your products are now ready for picking and storage, and the invoice is " +"marked as paid." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:98 +msgid "Upfront payment" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:100 +msgid "" +"From the **Purchase Order** page, open the **Invoices** tab, then click on " +"**Create**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:103 +msgid "" +"In the next page, click on **Validate**. The invoice is now registered in " +"the system. Click on **Register Payment**, insert the detail of the payment," +" and click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:110 +msgid "" +"Go back to the PO. In the PO, a **Shipment** tab and an **Invoice** tab have" +" appeared." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:116 +msgid "" +"Click on **Receive Products**, then in the new page, click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:121 +msgid "" +"A window will appear, asking if you wish to process every item at once. " +"Click on **Apply**." +msgstr "" + +#: ../../purchase/purchases.rst:3 +msgid "Purchases" +msgstr "" + +#: ../../purchase/purchases/master.rst:3 +msgid "Master Data" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:3 +msgid "How to import supplier pricelists?" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:8 +msgid "" +"Big companies use to import supplier pricelists day to day. Indeed, prices " +"are always changing and you need to get price up to date to deal with a high" +" number of products." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:12 +msgid "" +"To manage supplier prices on product form, read this document " +"(:doc:`suppliers`). Here we will show you how to import customer prices." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:16 +msgid "Required configuration" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:18 +msgid "In purchase settings, you have 2 options:" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:20 +msgid "Manage vendor price on the product form" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:22 +msgid "Allow using and importing vendor pricelists" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:24 +msgid "Here we are selecting: **Allow using and importing vendor pricelists**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:30 +msgid "Import vendor pricelists" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:32 +msgid "" +"There are 2 scenarios: import the vendor pricelist for the first time, or " +"update an existing vendor pricelist. In both scenarios, we assume your " +"product list and vendor list is updated and you want to import the price " +"list of vendors for a given product." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:40 +msgid "" +"To import a list from a document, the best pratice is to export first to get" +" an example of data formating and a proper header to reimport." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:50 +msgid "Import the list for the first time" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:53 +msgid "Prepare the document" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:55 +msgid "" +"In :menuselection:`Purchase --> Purchase --> Supplier Pricelists`, export a " +"template of document to get import/export compatible and get the right " +"format to import in mass. Create manually a data and export it " +"(:menuselection:`select --> Action --> Export`)" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:63 +msgid "Here is the list of fields you can import:" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Header of the document to import (csv, xls)**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Meaning and how to get it**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Example**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "name_id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "Vendor ID -> export supplier list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "\\_\\_export\\_\\_.res\\_partner\\_12" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "product_code" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "Vendor product Code -> free text" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "569874" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "price" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "Vendor Price -> free text" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "1500" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "product_tmpl_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "Product Template ID -> export you product list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "\\_\\_export\\_\\_.product_template_13" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:76 +msgid "currency_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:76 +msgid "Currency -> to get it export the currency list" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "date_end" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "End date of the price validity" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "2015-10-22" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "min_qty" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "Minimal quantity to purchase from this vendor" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "2" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "product_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "Product Variante name -> export your variant list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "\\_\\_export\\_\\_.product\\_13" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "date_start" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "Start date of price validity" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "2015-12-31" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:87 +msgid "You obtain a document which can be imported, fill in your vendor pices" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:92 +msgid "" +"Import this document in Odoo. Click on **Import** in the list view and " +"upload your document. You can validate and check error. Once the system " +"tells you everything is ok, you can import the list." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:102 +msgid "" +"After the import, the **Vendors** section in **Inventory** tab of the " +"product form is filled in." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:106 +msgid "Update the vendor pricelist" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:108 +msgid "" +"When the pricelist of your suppliers change, it is necessary to update " +"existing prices." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:111 +msgid "" +"Follow the procedure of the first scenario in order to export existing data " +"from :menuselection:`Purchases --> Purchase --> Vendor Pricelist`. Select " +"everything, and export from the **Action** menu." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:115 +msgid "" +"Change price, end date, add a line, change a supplier, ... and then reimport" +" in Odoo. Thanks to the ID, the list will be updated. Either the id is " +"recognized and the line is updated or the ID is not known by Odoo and it " +"will create a new pricelist line." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:120 +msgid "" +"After the import, the **Vendors** section in **Inventory** tab of the " +"product form is updated." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:3 +msgid "How to set several suppliers on a product?" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:5 +msgid "" +"Keeping track of your vendors can be a real burden in day-to-day business " +"life. Prices can change and you might have several suppliers for one " +"product. With Odoo you have the possibility to directly link vendors with " +"the corresponding product and specify prices automatically the first time " +"you purchase them." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:11 +msgid "" +"We will take the following example: We need to buy ``5 t-shirts``. We found " +"a **Vendor**; called ``Bob&Jerry's`` and we want to issue a request for " +"quotation." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:19 +msgid "Install the purchase module" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:21 +msgid "" +"The first step to set your suppliers on your products is to install the " +"purchase module. Go into your **App** module and install the **Purchase** " +"module." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:29 +msgid "" +"By installing the purchase module, the inventory and invoicing module will " +"be installed as well." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:33 +msgid "Create a Vendor" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:35 +msgid "" +"The second step is to create a vendor. In this case we'll create the vendor " +"``Bob&Jerry's``. Enter the purchase module, select :menuselection:`Purchase " +"--> Vendors` and create a new vendor." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:39 +msgid "" +"You can choose if the contact is a company or a person, fill in basic " +"information such as address, phone, email,..." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:42 +msgid "" +"If you did not create the contact from the purchase module you will need to " +"go in the **Sales and Purchases** tab as well and indicate that the contact " +"is a **Vendor** (see picture below). If the contact is created from the " +"purchase module this box will be ticked automatically." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:51 +msgid "Create a product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:53 +msgid "" +"Next we can create the product we want to buy. We don't know the price of " +"the t-shirt yet because we still need to issue our **Request for " +"Quotation**." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:57 +msgid "" +"To create a product enter your purchase module select " +":menuselection:`Purchase --> Products` and create a new product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:60 +msgid "" +"We will call our product ``T-shirt`` and specify that the product can be " +"sold and purchased." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:67 +msgid "Add Vendors to the product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:69 +msgid "" +"The next action is to add vendors to the product. There are two ways to " +"handle this. If you issue a purchase order for the first time Odoo will " +"automatically link the vendor and its price to the product. You can also add" +" vendors manually" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:75 +msgid "By issuing a first Purchase Order to new vendor" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:77 +msgid "" +"When issuing a purchase order for the first time to a vendor, he will " +"automatically be linked to the product by Odoo. For our example let's say " +"that we issue a first purchase order to ``Bob&Jerry's`` for ``5 t-shirts`` " +"at ``12.35 euros / piece``." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:82 +msgid "" +"First create your purchase order with the correct product and supplier (see " +"picture below, or the documentation page :doc:`../rfq/create` for more " +"information)" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:89 +msgid "" +"When we save and validate the purchase order the vendor will automatically " +"be added to the product's vendors list. To check this enter the purchase " +"module, select :menuselection:`Purchase --> Products` and select our T-shirt" +" product. By opening the **Inventory** tab we notice that our vendor and its" +" price has automatically been added." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:98 +msgid "" +"Note that every first time the product is purchased from a new vendor, Odoo " +"will automatically link the contact and price with the product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:103 +msgid "By adding manually" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:105 +msgid "" +"We can of course also add vendors and vendors information manually. On the " +"same page than previously, simply click on **Edit** and click the **Add an " +"item** button." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:112 +msgid "" +"When adding a new **Vendor** you are also able to add extra information such" +" as the vendor product name or code, the validity of the price and the " +"eventual minimum quantity required. These informations can be added and " +"modified for existing vendors by simply clicking on the vendors line." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:3 +msgid "How to purchase in different unit of measures than sales?" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:5 +msgid "" +"In day-to-day business, it may happen that your supplier uses a different " +"unit of measure than you do in sales. This can cause confusion between sales" +" and purchase representative and even make you lose a lot of time converting" +" measures. Luckily in Odoo, you can handle different units of measures " +"between sales and purchase very easily." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:11 +msgid "Let's take the following examples:" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:13 +msgid "" +"You buy water from a supplier. The supplier is american and sells his water " +"in **Gallons**. Your customers however are European. You would thus like to " +"see your purchases quantities expressed in **Gallons** and the sold " +"quantities in **Liters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:18 +msgid "" +"You buy curtains from a supplier. The supplier sells you the curtains in the" +" unit **roll** and you sell the curtains in **square meters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:25 +msgid "Install purchase and sales modules" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:27 +msgid "" +"The first step is to make sure that the apps **Sales** and **Purchase** are " +"correctly installed." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:31 +msgid "|uom01|" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:31 +msgid "|uom02|" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:36 +msgid "Enable the Unit of Measures option" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:38 +msgid "" +"Enter the purchase module, select :menuselection:`Configuration --> " +"Settings` and tick the **Some products may be sold/purchased in different " +"unit of measures (advanced)** box." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:46 +msgid "Specify sales and purchase unit of measures" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:49 +msgid "Standard units of measures" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:51 +msgid "" +"Let's take the classic units of measures existing in Odoo as first example. " +"Please remember that differents units of measures between sales and purchase" +" necessarily need to share the same category. Categories include: **Unit**, " +"**weight**, **working time**, **volume**, etc." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:57 +msgid "" +"It is possible to create your own category and unit of measure if it is not " +"standard in Odoo (see next chapter)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:60 +msgid "" +"Let's assume we buy water from our vendors in **Gallons** and sell to our " +"customers in **Liters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:63 +msgid "" +"We go into the purchase module select :menuselection:`Purchase --> " +"Products`." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:65 +msgid "" +"Create your own product or select an existing one. In the products general " +"information you have the possibility to select the **Unit of measure** (will" +" be used in sales, inventory,...) and the **Purchase Unit of Measure** (for " +"purchase)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:70 +msgid "" +"In this case select **Liters** for **Unit of Measure** and **Gallons** for " +"**Purchase Unit of Measure**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:77 +msgid "Create your own unit of measure and unit of measure category" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:79 +msgid "" +"Let's take now our second example (you buy curtains from a supplier, the " +"supplier sells you the curtains in the unit **roll** and you sell the " +"curtains in **square meters**)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:83 +msgid "" +"The two measures are part of two different categories. Remember, you cannot " +"relate an existing measure from one category with an existing measure of " +"another category. We thus first have to create a shared **Measure Category**" +" where both units have a conversion relationship." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:88 +msgid "" +"To do so, go into your sales module select :menuselection:`Configuration -->" +" Products --> Unit of Measure`. Create a new unit of **Measure Category** by" +" selecting the dropdown list and clicking on create and edit (see picture " +"below)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:96 +msgid "" +"Create a new unit of measure. In this case our category will be called " +"**Inter-Category-Computation**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:102 +msgid "" +"The next step is to create the **Rolls** and **Square meter** units of " +"measure and to link them to the new category. To do so, go into your " +"purchase module select :menuselection:`Configuration --> Products --> Units " +"of Measure`." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:106 +msgid "Create two new units:" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:108 +msgid "" +"The **Roll** unit who is part of the Inter-Category-Computation category and" +" is the **Reference Unit type** (see picture below). The Reference Unit type" +" is the measure set as a reference within the category. Meaning that other " +"measures will be converted depending on this measure (ex: 1 roll = 10 square" +" meters, 2 rolls = 20 square meters, etc.)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:118 +msgid "" +"For the **Square Meter**, we will specify that ``1 Roll = 10 square meters``" +" of curtain. It will thus be necessary to specify that as type, the square " +"meter is bigger than the reference unit. The **Bigger Ratio** is ``10`` as " +"``one Roll = 10 square meters``." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:126 +msgid "" +"It is now possible to input **square meters** as Unit of measure and a " +"**Roll** as Purchase Unit of Measure in the product form." +msgstr "" + +#: ../../purchase/purchases/rfq.rst:3 +msgid "Request for Quotations" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:3 +msgid "How to analyze the performance of my vendors?" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:5 +msgid "" +"If your company regularly buys products from several suppliers, it would be " +"useful to get statistics on your purchases. There are several reasons to " +"track and analyze your vendor's performance :" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:9 +msgid "You can see how dependant from a supplier your company is;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:11 +msgid "you can negotiate discounts on prices;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:13 +msgid "You can check the average delivery time per supplier;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:15 +msgid "Etc." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:17 +msgid "" +"For example, an IT products reseller that issues dozens of purchase orders " +"to several suppliers each week may want to measure for each product the " +"total price paid for each vendor and the delivery delay. The insights " +"gathered by the company will help it to better analyze, forecast and plan " +"their future orders." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:27 +#: ../../purchase/purchases/tender/partial_purchase.rst:17 +msgid "Install the Purchase Management module" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:29 +msgid "" +"From the **Apps** menu, search and install the **Purchase Management** " +"module." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:36 +msgid "Issue some purchase orders" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:38 +msgid "" +"Of course, in order to analyze your vendors' performance, you need to issue " +"some **Request For Quotations** (RfQ) and confirm some **Purchase Orders**. " +"If you want to know how to generate a purchase order, please read the " +"documentation :doc:`../../overview/process/from_po_to_invoice`." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:44 +msgid "Analyzing your vendors" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:47 +msgid "Generate flexible reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:49 +msgid "" +"You have access to your vendors' performances on the Reports menu. By " +"default, the report groups all your purchase orders on a pivot table by " +"**total price**, **product quantity** and **average price** for the **each " +"month** and for **each supplier**. Simply by accessing this basic report, " +"you can get a quick overview of your actual performance. You can add a lot " +"of extra data to your report by clicking on the **Measures** icon." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:60 +msgid "" +"By clicking on the **+** and **-** icons, you can drill up and down your " +"report in order to change the way your information is displayed. For " +"example, if I want to see all the products bought for the current month, I " +"need to click on the **+** icon on the vertical axis and then on " +"\"Products\"." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:67 +msgid "" +"Depending on the data you want to highlight, you may need to display your " +"reports in a more visual view. You can transform your report in just a click" +" in 3 graph views : a **Pie Chart**, a **Bar Chart** and a **Line Chart**: " +"These views are accessible through the icons highlighted on the screenshot " +"below." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:77 +msgid "" +"On the contrary to the pivot table, a graph can only be computed with one " +"dependent and one independent measure." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:81 +msgid "Customize reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:83 +msgid "" +"You can easily customize your purchase reports depending on your needs. To " +"do so, use the **Advanced search view** located in the right hand side of " +"your screen, by clicking on the magnifying glass icon at the end of the " +"search bar button. This function allows you to highlight only selected data " +"on your report. The **filters** option is very useful in order to display " +"some categories of datas, while the **Group by** option improves the " +"readability of your reports. Note that you can filter and group by any " +"existing field, making your customization very flexible and powerful." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:97 +msgid "" +"You can save and reuse any customized filter by clicking on **Favorites** " +"from the **Advanced search view** and then on **Save current search**. The " +"saved filter will then be accessible from the **Favorites** menu." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:103 +#: ../../purchase/purchases/rfq/create.rst:76 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:75 +#: ../../purchase/purchases/tender/partial_purchase.rst:77 +msgid ":doc:`../../overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:3 +msgid "How to setup two levels of approval for purchase orders?" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:6 +msgid "Two level approval setup" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:8 +msgid "" +"Double validation on purchases forces a validation when the purchased amount" +" exceeds a certain limit." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:11 +msgid "" +"Install **Purchase Management** module and then go to **General Settings** " +"to configure the company data." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:17 +msgid "" +"Set here the amount limit for second approval and set approval from manager " +"side." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:21 +#: ../../purchase/replenishment/flows/purchase_triggering.rst:47 +msgid "Process" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:23 +msgid "" +"Logged as a purchase user, create a purchase order for more than the amount " +"set above, and confirm it. The purchase order is set in a state **To " +"Approve**" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:29 +msgid "The manager gets the order to approve and validates the final order." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:34 +msgid "Once approved, the purchase order follows the normal process." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:3 +msgid "How to control supplier bills?" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:5 +msgid "" +"The **Purchase** application allows you to manage your purchase orders, " +"incoming products, and vendor bills all seamlessly in one place." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:8 +msgid "" +"If you want to set up a vendor bill control process, the first thing you " +"need to do is to have purchase data in Odoo. Knowing what has been purchased" +" and received is the first step towards understanding your purchase " +"management processes." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:13 +msgid "Here is the standard work flow in Odoo:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:15 +msgid "" +"You begin with a **Request for Quotation (RFQ)** to send out to your " +"vendor(s)." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:18 +msgid "" +"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase " +"Order (PO)**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:21 +msgid "" +"Confirming the PO generates an **Incoming Shipment** if you purchased any " +"stockable products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:24 +msgid "" +"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with " +"products received in the previous step to ensure accuracy." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:27 +msgid "" +"This process may be done by three different people within the company, or " +"only one." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:34 +msgid "Installing the Purchase and Inventory applications" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:36 +msgid "" +"From the **Apps** application, search for the **Purchase** module and " +"install it. Due to certain dependencies, installing purchase will " +"automatically install the **Inventory** and **Accounting** applications." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:41 +msgid "Creating products" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:43 +msgid "" +"Creating products in Odoo is essential for quick and efficient purchasing " +"within Odoo. Simply navigate to the **Products** submenu under **Purchase**," +" and click **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:50 +msgid "" +"When creating the product, Pay attention to the **Product Type** field, as " +"it is important:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:53 +msgid "" +"Products that are set as **Stockable** or **Consumable** will allow you to " +"keep track of their inventory levels. These options imply stock management " +"and will allow for receiving these kinds of products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:58 +msgid "" +"Conversely, products that are set as a **Service** or **Digital Product** " +"will not imply stock management, simply due to the fact that there is no " +"inventory to manage. You will not be able to receive products under either " +"of these designations." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:64 +msgid "" +"It is recommended that you create a **Miscellaneous** product for all " +"purchases that occur infrequently and do not require inventory valuation or " +"management. If you create such a product, it is recommend to set the product" +" type to **Service**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:70 +msgid "Managing your Vendor Bills" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:73 +msgid "Purchasing products or services" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:75 +msgid "" +"From the purchase application, you can create a purchase order with as many " +"products as you need. If the vendor sends you a confirmation or quotation " +"for an order, you may record the order reference number in the **Vendor " +"Reference** field. This will enable you to easily match the PO with the the " +"vendor bill later (as the vendor bill will probably include the Vendor " +"Reference)" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:85 +msgid "" +"Validate the purchase order and receive the products from the **Inventory** " +"application." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:89 +msgid "Receiving Products" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:91 +msgid "" +"If you purchased any stockable products that you manage the inventory of, " +"you will need to receive the products from the **Inventory** application " +"after you confirm a purchase order. From the **Inventory** dashboard, you " +"should see a button linking you directly to the transfer of products. This " +"button is outlined in red below:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:100 +msgid "" +"Navigating this route will take you to a list of all orders awaiting to be " +"received." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:106 +msgid "" +"If you have a lot of awaiting orders, apply a filter using the search bar in" +" the upper right. With this search bar, you may filter based on the " +"**Vendor** (or **Partner**), the product, or the source document, also known" +" as the reference of your purchase order. You also have the capability to " +"group the orders by different criteria under **Group By**. Selecting an item" +" from this list will open the following screen where you then will receive " +"the products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:117 +msgid "Purchasing **Service** products does not trigger a delivery order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:120 +msgid "Managing Vendor Bills" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:122 +msgid "" +"When you receive a **Vendor Bill** for a previous purchase, be sure to " +"record it in the **Purchases** application under the **Control Menu**. You " +"need to create a new vendor bill even if you already registered a purchase " +"order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:130 +msgid "" +"The first thing you will need to do upon creating a **Vendor Bill** is to " +"select the appropriate **Vendor** as this will also pull up any associated " +"accounting or pricelist information. From there, you can choose to specify " +"any one or multiple purchase orders to populate the vendor bill with. When " +"you select a purchase order from the list, Odoo will pull any uninvoiced " +"products associated to that purchase order and automatically populate that " +"information below. If you are having a hard time finding the appropriate " +"vendor bill, you may search through the list by inputting the vendor " +"reference number or your internal purchase order number." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:144 +msgid "" +"While the invoice is in draft state, you can make any modifications you need" +" (i.e. remove or add product lines, modify quantities, and change prices)." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:149 +msgid "Your vendor may send you several bills for the same purchase order if:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:151 +msgid "" +"Your vendor is in back-order and is sending you invoices as they ship the " +"products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:154 +msgid "Your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:156 +msgid "" +"Every time you record a new vendor bill, Odoo will automatically populate " +"the product quantities based on what has been received from the vendor. If " +"this value is showing a zero, this means that you have not yet received this" +" product and simply serves as a reminder that the product is not in hand and" +" you may need to inquire further into this. At any point in time, before you" +" validate the vendor bill, you may override this zero quantity." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:165 +msgid "Vendor Bill Matching" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:168 +msgid "What to do if your vendor bill does not match what you received" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:170 +msgid "" +"If the bill you receive from the vendor has different quantities than what " +"Odoo automatically populates as quantities, this could be due to several " +"reasons:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:174 +msgid "" +"The vendor is incorrectly charging you for products and/or services that you" +" have not ordered." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:177 +msgid "" +"The vendor is billing you for products that you might not have received yet," +" as the invoicing control may be based on ordered or received quantities." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:181 +msgid "Or the vendor did not bill you for previously purchased products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:183 +msgid "" +"In these instances it is recommended that you verify that the bill, and any " +"associated purchase order to the vendor, are accurate and that you " +"understand what you have ordered and what you have already received." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:187 +msgid "" +"If you are unable to find a purchase order related to a vendor bill, this " +"could be due to one of a few reasons:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:190 +msgid "" +"The vendor has already invoiced you for this purchase order, therefore it is" +" not going to appear anywhere in the selection." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:193 +msgid "" +"Someone in the company forgot to record a purchase order for this vendor." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:196 +msgid "Or the vendor is charging you for something you did not order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:199 +msgid "How product quantities are managed" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:201 +msgid "" +"By default, services are managed based on ordered quantities, while " +"stockables and consumables are managed based on received quantities." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:204 +msgid "" +"If you need to manage products based on ordered quantities over received " +"quantities, you will need to enable **Debug Mode** from the **About Odoo** " +"information. Once debug mode is activated, select the product(s) you wish to" +" modify, and you should see a new field appear, labeled **Control Purchase " +"Bills**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:213 +msgid "" +"You can then change the default management method for the selected product " +"to be based on either:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:216 +msgid "Ordered quantities" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:218 +msgid "Received quantities" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:221 +msgid "Batch Billing" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:223 +msgid "" +"When creating a vendor bill and selecting the appropriate purchase order, " +"you may continue to select additional purchase orders and Odoo will add the " +"additional line items from that purchase order. If you have not deleted the " +"previous line items from the first purchase order the bill will be linked to" +" all the appropriate purchase orders." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:3 +msgid "How to cancel a purchase order?" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:5 +msgid "" +"Due to misunderstandings, human errors or change of plans, it is sometimes " +"necessary to cancel purchase orders sent to suppliers. Odoo allows you to do" +" it, even if some or even all of the ordered goods already arrived in your " +"warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:10 +msgid "" +"We will first take as example the case where you order **3 iPad mini** that " +"haven't arrived in your transfers yet. As the installation of the inventory " +"application is required when using the **Purchase** module, it is also " +"interesting to see the case of partially delivered goods that you want to " +"cancel." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:17 +msgid "Create a Purchase Order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:19 +msgid "" +"The first step to create a **Purchase Order** is to create a **Request for " +"Quotation (RFQ)** from the menu :menuselection:`Purchases --> Purchase --> " +"Requests for quotation`. Confirm your RFQ to have a confirmed purchase order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:25 +msgid "" +"To learn more about the purchase order process, read the documentation page " +":doc:`../../overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:30 +msgid "Cancel your Purchase Order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:33 +msgid "Use case 1 : you didn't receive your goods yet" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:35 +msgid "" +"If you confirmed your purchase order and did not received your goods yet, " +"you can simply cancel the PO it by clicking the cancel button." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:41 +msgid "" +"Odoo will automatically cancel the outstanding shipments related to this PO " +"and the status bar will switch from **Purchase order** to **Cancelled**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:48 +msgid "Use case 2 : partially delivered goods" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:50 +msgid "" +"In this case, **2** of the **3 iPad Mini** arrived before you needed to " +"cancel the PO." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:54 +msgid "Register good received and cancel backorder" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:56 +msgid "" +"The first thing to do will be to register the goods received and to cancel " +"the arrival of the **third iPad Mini** that is still supposed to be shipped." +" From the PO, click on **Receive products** and, on the **iPad Mini order " +"line**, manually change the received quantities under the Column **Done**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:66 +msgid "To learn more, see :doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:68 +msgid "" +"When clicking on **Validate**, Odoo will warn you that you have processed " +"less products than the initial demand (2 instead of 3 in our case) and will " +"ask you the permission to create a backorder." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:75 +msgid "" +"Click on **No backorder** to cancel the supply of the remaining product. You" +" will notice than the quantity to receive has been changed accordingly and, " +"therefore, the delivery status has switched to **Done**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:83 +msgid "Create reverse transfer" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:85 +msgid "" +"Now, you need to return the iPad Minis that you have received to your vendor" +" location. To do so, click on the **Reverse** button from the same document." +" A reverse transfer window will pop up. Enter the quantity to return and the" +" corresponding location and click on **Return**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:93 +msgid "" +"Process the return shipment and control that the stock move is from your " +"stock to your vendor location." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:99 +msgid "" +"When the reverse transfer is done, the status of your purchase order will be" +" automatically set to done, meaning that your PO has been completely " +"cancelled." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:104 +#: ../../purchase/purchases/rfq/reception.rst:120 +msgid ":doc:`bills`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:105 +msgid ":doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:3 +msgid "How to create a Request for Quotation?" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:5 +msgid "" +"A Request for Quotation (RfQ) is used when you plan to purchase some " +"products and you would like to receive a quote for those products. In Odoo, " +"the Request for Quotation is used to send your list of desired products to " +"your supplier. Once your supplier has answered your request, you can choose " +"to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:12 +msgid "" +"For more information on best uses, please read the chapter " +":doc:`../../overview/process/difference`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:19 +msgid "Creating a Request for Quotation" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:21 +msgid "" +"In the Purchases module, open :menuselection:`Purchase --> Requests for " +"Quotation` and click on **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:27 +msgid "" +"Select your supplier in the **Vendor** menu, or create it on-the-fly by " +"clicking on **Create and Edit**. In the **Order Date** field, select the " +"date to which you wish to proceed to the actual order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoming Shipments" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Reference of the sales order or bid sent by the vendor. It's used to do the " +"matching when you receive the products as this reference is usually written " +"on the delivery order sent by your vendor." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Depicts the date where the Quotation should be validated and converted into " +"a purchase order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Reference of the document that generated this purchase order request (e.g. a" +" sales order or an internal procurement request)" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "This will determine picking type of incoming shipment" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Put an address if you want to deliver directly from the vendor to the " +"customer. Otherwise, keep empty to deliver to your own company." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Technical field used to display the Drop Ship Address" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"International Commercial Terms are a series of predefined commercial terms " +"used in international transactions." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:35 +msgid "View *Request for Quotation* in our Online Demonstration" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:37 +msgid "" +"In **Products**, click on Add an item. Select the product you wish to order " +"in the **Product** menu. Specify the **Quantity** by inserting the number " +"and selecting the unit of measure. In the **Unit Price** field, specify the " +"price you would like to be offered (you can also leave the field blank if " +"you don't know what the price should be) , and add the expected delivery " +"date in the Scheduled Date field. Click on **Save**, then **Print Rfq** or " +"**Send Rfq by email** (make sure an email address is specified for this " +"supplier or enter a new one)." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:51 +msgid "" +"After having clicked on **Send**, you will notice that the RFQ's status will" +" switch from **Draft** to **RFQ Sent**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:57 +msgid "" +"Once your supplier has replied with an offer, update the RfQ by clicking on " +"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, " +"payment terms, etc.), then click on **Save** to issue a Purchase Order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:62 +msgid "" +"To proceed with the order, click on **Confirm Order** to send the order to " +"the supplier. The RfQ's status will switch to **Purchase Order**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:68 +msgid "" +"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right" +" corner of the order will show 1 Shipment and 0 Invoice." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:3 +msgid "How to control product received? (entirely & partially)" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:5 +msgid "" +"The **Purchase** app allows you to manage your purchase orders, to control " +"products to receive and to control supplier bills." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:8 +msgid "" +"If you want to get product forecasts and receptions under control, the first" +" thing to do is to deploy the Odoo purchase process. Knowing what have been " +"purchased is the basis of forecasting and controlling receptions." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:17 +msgid "Install the Purchase and Inventory applications" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:19 +msgid "" +"Start by installing the Purchase application from the **Apps** module. This " +"will automatically trigger the installation of the **Inventory** app (among " +"others), which is required with **Purchase**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:27 +msgid "Create products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:29 +msgid "" +"Then, you need to create the products you want to purchase. Go to the " +"**Purchase** app, then :menuselection:`Purchase --> Products`, and click on " +"**Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:36 +msgid "When creating the product, the **Product Type** field is important:" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:38 +msgid "" +"**Stockable & Consumable**: products need to be received in the inventory." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:41 +msgid "" +"**Services & Digital Products** (only when the **eCommerce** app is " +"installed): there is no control about what you receive or not." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:45 +msgid "" +"It's always good to create a **Miscellaneous** product for all the products " +"you purchased rarely and for which you don't want to manage the stocks or " +"have purchase/sale statistics. If you create such a product, we recommend to" +" set his product type field as **Service**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:52 +msgid "Control products receptions" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:55 +msgid "Purchase products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:57 +msgid "" +"From the purchase application, create a purchase order with a few products. " +"If the vendor sent you a sale order or a quotation, put its reference in the" +" **Vendor Reference** field. This will allow you to easily do the matching " +"with the delivery order later on (as the delivery order will probably " +"include the **Vendor Reference** of his sale order)." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:67 +msgid "" +"See the documentation page :doc:`../../overview/process/from_po_to_invoice` " +"for a full overview of the purchase process." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:71 +msgid "Receive Products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:73 +msgid "" +"If you purchased physical goods (stockable or consumable products), you can " +"receive the products from the **Inventory** application. From the " +"**Inventory** dashboard, you should see a button **X To Receive**, on the " +"receipt box of the related warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:81 +msgid "" +"Click on this button and you access a list of all awaiting orders for this " +"warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:87 +msgid "" +"If you have a lot of awaiting orders, you can use the filter bar to search " +"on the **Vendor** (also called **Partner** in Odoo), the product or the " +"source document, which is the reference of your purchase order. You can open" +" the document that matches with the received delivery order and process all " +"the lines within it." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:96 +msgid "" +"You may validate the whole document at once by clicking on the **Validate** " +"button or you can control all products, one by one, by manually change the " +"**Done** quantity (what has actually been received). When a line is green, " +"it means the quantity received matches to what have been expected." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:103 +msgid "" +"If you work with lots or serial numbers, you can not set the processed " +"quantity, but you have to provide all the lots or serial numbers to record " +"the quantity received." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:107 +msgid "" +"When you validate the reception, if you have received less products than the" +" initial demand, Odoo will ask youthe permission to create a backorder." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:114 +msgid "" +"If you plan to receive the remaining product in the future, select **Create " +"Backorder**. Odoo will create a new documents for the awaiting products. If " +"you choose **No Backorder**, the order is considered as fulfilled." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:121 +msgid ":doc:`cancel`" +msgstr "" + +#: ../../purchase/purchases/tender.rst:3 +msgid "Purchase Tenders" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:3 +msgid "How to manage Purchase Tenders" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:12 +msgid "" +"For more information on best uses, please read the chapter `Request for " +"Quotation, Purchase Tender or Purchase Order? " +"`__" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:17 +msgid "Activate the Purchase Tender function" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:19 +msgid "" +"By default, the Purchase Tender is not activated. To be able to use PTs, you" +" must first activate the option." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:22 +msgid "" +"In the Purchases module, open the Configuration menu and click on Settings. " +"In the Purchase Order section, locate the **Calls for Tenders** and tick the" +" box Allow using call for tenders... (advanced), then click on **Apply**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:31 +msgid "Create a Purchase Tender" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:33 +msgid "" +"To create a new Purchase Tender, open :menuselection:`Purchase --> Purchase " +"Agreements (PA)`." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:39 +msgid "" +"In the Purchase Agreements window, click on **Create**. A new Purchase " +"Agreement window opens." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:42 +msgid "In the **Agreement Type** field, choose Purchase Tender." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:44 +msgid "You do not have to define a **Vendor**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:46 +msgid "" +"In the **Products** section, click on **Add an item**. Select products in " +"the Product list, then insert **Quantity**. You can add as many products as " +"you wish." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:53 +msgid "Click on **Confirm Call**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:55 +msgid "" +"Now click on the button **New Quotation**. A RfQ is created with the " +"products chosen on the PT. Choose a **Vendor** and send the RfQ to the " +"vendor. Repeat this operation for each vendor." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:62 +msgid "Once all the RfQs are sent, you can click on **Validate** on the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:64 +msgid "" +"The vendors will send their offers, you can update the RfQs accordingly. " +"Then, choose the ones you want to accept by clicking on **Confirm Order** on" +" the RfQs and **Cancel** the others." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:68 +msgid "You can now click on **Done** on the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:70 +msgid "" +"View `Purchase Tenders " +"`__" +" in our Online Demonstration." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:77 +msgid ":doc:`../../overview/process/difference`" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:3 +msgid "" +"How to purchase partially at two vendors for the same purchase tenders?" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:5 +msgid "" +"For some Purchase Tenders (PT), you might sometimes want to be able to " +"select only a part of some of the offers you received. In Odoo, this is made" +" possible through the advanced mode of the **Purchase** module." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:10 +msgid "" +"If you want to know how to handle a simple **Purchase Tender**, read the " +"document on :doc:`manage_multiple_offers`." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:19 +msgid "From the **Apps** menu, install the **Purchase Management** app." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:25 +msgid "Activating the Purchase Tender and Purchase Tender advanced mode" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:27 +msgid "" +"In order to be able to select elements of an offer, you must activate the " +"advanced mode." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:30 +msgid "" +"To do so, go into the **Purchases** module, open the **Configuration** menu " +"and click on **Settings**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:33 +msgid "" +"In the **Calls for Tenders** section, tick the option **Allow using call for" +" tenders to get quotes from multiple suppliers(...)**, and in the **Advanced" +" Calls for Tenders** section, tick the option **Advanced call for tender " +"(...)** then click on **Apply**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:42 +msgid "Selecting elements of a RFQ/Bid" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:44 +msgid "" +"Go to :menuselection:`Purchase --> Purchase Tenders`. Create a purchase " +"tender containing several products, and follow the usual sequence all the " +"way to the **Bid Selection** status." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:49 +msgid "" +"When you closed the call, click on **Choose Product Lines** to access the " +"list of products and the bids received for all of them." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:55 +msgid "" +"Unroll the list of offers you received for each product, and click on the " +"*v* symbol (**Confirm order**) next to the offers you wish to proceed with. " +"The lines for which you've confirmed the order turn blue. When you're " +"finished, click on **Generate PO** to create a purchase order for each " +"product and supplier." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:64 +msgid "" +"When you come back to you purchase tender, you can see that the status has " +"switched to **PO Created** and that the **Requests for Quotations** now have" +" a status of **Purchase Order** or **Cancelled**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:72 +msgid "" +"From there, follow the documentation " +":doc:`../../overview/process/from_po_to_invoice` to proceed with the " +"delivery and invoicing." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:76 +msgid ":doc:`manage_multiple_offers`" +msgstr "" + +#: ../../purchase/replenishment.rst:3 +msgid "Replenishment" +msgstr "" + +#: ../../purchase/replenishment/flows.rst:3 +msgid "Replenishment Flows" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:3 +msgid "How are the order date and scheduled dates computed?" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:5 +msgid "" +"Scheduled dates are computed in order to be able to plan deliveries, " +"receptions and so on. Depending on the habits of your company, Odoo " +"automatically generates scheduled dates via the scheduler. The Odoo " +"scheduler computes everything per line, whether it's a manufacturing order, " +"a delivery order, a sale order, etc. The dates that are computed are " +"dependent on the different leads times configured in Odoo." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:13 +msgid "Configuring lead times" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:15 +msgid "" +"Configuring **lead times** is an essential move in order to compute " +"scheduled dates. Lead times are the delays (in term of delivery, " +"manufacturing, ...) promised to your different partners and/or clients. " +"Configuration of the different lead times are made as follows:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:21 +msgid "On a product level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:24 +msgid "Supplier lead time:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:26 +msgid "" +"The supplier lead time is the time needed for the supplier to deliver your " +"purchased product. To configure the Supplier lead time select a product " +"(from the Purchase module, go to :menuselection:`Purchase --> Product`), and" +" go in the **Inventory** tab. You will have to add a **Vendor** to your " +"product in order to select a supplier lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:36 +msgid "" +"It is possible to add more than one vendor per product and thus different " +"delivery lead times depending on the vendor." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:39 +msgid "" +"Once a vendor is selected, click on it to open its form and indicate its " +"delivery lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:46 +msgid "" +"In this case security days have no influence, the scheduled delivery days " +"will be equal to: Date of the purchase order + Delivery Lead Time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:50 +msgid "Customer lead time" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:52 +msgid "" +"The customer lead time is the time needed to get your product from your " +"store/warehouse to your customer. It can be configured for any product. " +"Simply select a product (from the **Sales** module, go to " +":menuselection:`Sales --> Product`), and go into the **Sales** tab to " +"indicate your customer lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:62 +msgid "On the company level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:64 +msgid "" +"On company level, it is possible to parameter **security days** in order to " +"cope with eventual delays and to be sure to meet your engagements. The idea " +"is to subtract **backup** days from the computed scheduled date in case of " +"delays." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:70 +msgid "Sales Safety days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:72 +msgid "" +"Sales Safety days are **back-up** days to ensure you will be able to deliver" +" your clients engagements on time. They are margins of errors for delivery " +"lead times. Security days are the same logic as the early wristwatch, in " +"order to arrive on time. The idea is to subtract the numbers of security " +"days from the calculation and thus to compute a scheduled date earlier than " +"the one you promised to your client. That way you are sure to be able to " +"keep your commitment." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:80 +msgid "" +"To set up your security dates, go to the app :menuselection:`Settings --> " +"General settings`, and click on **Configure your company data**." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:87 +msgid "Go the **Configuration** tab to indicate the number of safety days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:93 +msgid "" +"Note that you can in this menu configure a default **Manufacturing** lead " +"time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:97 +msgid "Purchase days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:99 +msgid "Purchase days response to the same logic than sales security days." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:101 +msgid "" +"They are margins of error for vendor lead times. When the system generates " +"purchase orders for procuring products, they will be scheduled in order to " +"cope with unexpected vendor delays. Purchase lead time can be found in the " +"same menu as the sales safety days (see screenshot above)." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:108 +msgid "On route level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:110 +msgid "" +"The internal transfers due to the movement of stocks can also influence the " +"computed date." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:113 +msgid "" +"The delays due to internal transfers can be specified in the **Inventory** " +"module when creating a new push rule for a new route." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:117 +msgid "" +"Read the documentation " +":doc:`../../../../inventory/routes/concepts/push_rule` to learn more." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:125 +msgid "On document level:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:128 +msgid "Requested date" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:130 +msgid "" +"Odoo offers the possibility to indicate a requested date by the client " +"straight on the sale order, under the tab **Other information**. If this " +"date is earlier than the theoretically computed date, Odoo will " +"automatically display a warning." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:141 +msgid "" +"As an example, you may sell a car today (January 1st), that is purchased on " +"order, and you promise to deliver your customer within 20 days (January 20)." +" In such a scenario, the scheduler may trigger the following events, based " +"on your configuration:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:146 +msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:148 +msgid "" +"January 18: receive the product from your supplier (1 day of Purchase days)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:151 +msgid "" +"January 10: deadline to order at your supplier (9 days of supplier delivery " +"lead time)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:154 +msgid "" +"January 8: trigger a purchase request to your purchase team, since the team " +"needs on average 2 days to find the right supplier and order." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:3 +msgid "How to setup drop-shipping?" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:8 +msgid "" +"Drop shipping allows to deliver the goods directly from the supplier to the " +"customer. It means that the products does not transit through your stock." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:15 +msgid "" +"First, configure the **Routes** and **Dropshipping**. Go to " +":menuselection:`Inventory --> Configuration --> Settings`. Check **Advanced " +"routing of products using rules** in the **Routes** section and **Allow " +"suppliers to deliver directly to your customers** in the **Drop Shipping** " +"section." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:24 +msgid "" +"You have to allow the choice of the route on the sale order. Go to the " +"**Sales** application, :menuselection:`Configuration --> Settings` and tick " +"**Choose specific routes on sales order lines (advanced)**." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:32 +msgid "How to use drop-shipping?" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:34 +msgid "" +"Create the sale order and select the route as **Dropshipping** on the " +"concerned order lines." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:40 +msgid "" +"Once the order has been confirmed, no move will be created from your stock. " +"The goods will be delivered directly from your vendor to your customer." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:45 +msgid "" +"In order to be able to invoice the delivery, you must set the invoice policy" +" of your product on **Ordered quantities**." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:3 +msgid "How to trigger the purchase of products based on sales?" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:8 +msgid "" +"When you work in just-in-time, you don't manage stock so you directly order " +"the product you need from your vendor." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:11 +msgid "The usual flow is:" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:13 +msgid "Create a sale order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:15 +msgid "Purchase the product" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:17 +msgid "Receive and pay the bill" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:19 +msgid "Deliver your product" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:21 +msgid "Invoice your customer" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:24 +msgid "Product configuration" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:26 +msgid "" +"In the purchases application, open the **Purchase** menu and click on " +"**Products**. Open the product on which you want to do your purchases based " +"on sales." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:30 +msgid "" +"Next to Routes, tick **Buy** and **Make to order** as a procurement method. " +"When you are generating sales order, Odoo will automatically reorder the " +"same quantity through procurement." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:37 +msgid "Don't forget to set a vendor otherwise the rule won't be triggered." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:39 +msgid "" +"You can also configure minimum stock rules that will trigger the purchase " +"orders." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:43 +msgid "" +"To know how to configure a minimum stock rule, please read the document " +":doc:`setup_stock_rule`." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:50 +msgid "Sale order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:52 +msgid "" +"To create a sale order, go to the **Sales** application, " +":menuselection:`Sales --> Sales order` and create a new sale order." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:58 +msgid "" +"After confirming it, you will see one **Delivery** associated with this sale" +" order on the **button** on the top of it." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:64 +msgid "" +"Click on the **Delivery** button to see the transfer order. The status of " +"the outgoing shipment is **Waiting Another Operation**. It won't be done " +"until the purchase order is confirmed and received." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:69 +msgid "Purchase order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:71 +msgid "" +"The purchase order is automatically created. Go to the **Purchase** " +"application :menuselection:`Purchase --> Request for Quotation`. The source " +"document is the sale order that triggered the procurement." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:79 +msgid "" +"If you make some more sales that trigger procurements to the same vendor, it" +" will be added to the existing request for quotation. Once it is confirmed, " +"the next procurements will create a new request for quotation." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:85 +msgid "Receipt and delivery" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:87 +msgid "" +"Go the the **Inventory** application. Click on **# To Receive** on the " +"**Receipts** tile." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:93 +msgid "Select the receipt from your vendor and **Validate** it." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:98 +msgid "" +"Go back to the **Inventory** dashboard. In the delivery order, click on **# " +"To Do**. The delivery order is now ready to ship." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:104 +msgid "" +"The status of the delivery changed from **Waiting Availability** to " +"**Available**. Validate the transfer to confirm the delivery." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:111 +msgid ":doc:`setup_stock_rule`" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:112 +msgid ":doc:`warning_triggering`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:3 +msgid "How to setup a minimum stock rule?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:5 +msgid "" +"For some items you hold in stock, it might be useful to have rules making " +"sure you never run out of stocks (for example, products with a high demand, " +"or large items requiring a lot of storage space meaning they're harder to " +"stock)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:10 +msgid "" +"Odoo allows you to set up rules so that an automatic replenishment for those" +" items is made, based on minimum stocks available." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:14 +msgid "When should I use Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:16 +msgid "" +"Reordering Rules work best for items that have a high demand and high flow. " +"It will relieve you from a lot of work to focus on the rest of your " +"activities knowing that stocks will always be right." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:20 +msgid "" +"It can also be used when you have limited storage space and you need to keep" +" large items in stock. In this case, you can keep as little as 1 item in " +"stock, and have a new one ordered as a stock replenishment as soon as the " +"item in stock is sold." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:26 +msgid "When should I avoid Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:28 +msgid "" +"If you are offering a new product and don't know yet how fast it will go, " +"you should handle stocks yourself first, and setup reordering rules only a " +"few months into the sale to have better forecasts of the demand." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:32 +msgid "" +"If you sell items that have a limited lifetime, such as fashion items, " +"technology items, or products working together with a system that is meant " +"to evolve, you have to be very well informed on when to stop automated " +"replenishments, in order to avoid having to sell these items at a price that" +" will not allow you to break even." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:41 +msgid "" +"My company sells modern furniture. We sell a set of table and chairs that " +"are available in 4 seatings and 6 seatings." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:44 +msgid "" +"To keep things simple, we stock tables and chairs separately, but sell them " +"all together to our clients as a kit. In order to make sure we can always " +"deliver a complete set of table and chairs, I setup a Reordering Rule for " +"the chairs to make sure I always have at least 10 chairs in stock, but no " +"more than 20. This way, I can sell up to 5 sets of table at once while " +"keeping my stock low enough not to eat up all my storage space." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:52 +msgid "" +"The last table I sold was a 4 seatings, and there were 12 chairs left in my " +"stock. Because the stock in chairs is now only 8 chairs, Odoo will " +"automatically order 12 new chairs to fill up my stock to the maximum amount." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:61 +msgid "Set up your product" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:63 +msgid "" +"In the Purchases module, open the Purchase menu and click on Products. Open " +"the product to which you would like to add a Reordering Rule (or create a " +"new one)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:67 +msgid "3 conditions for correct reordering rule :" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:69 +msgid "" +"In :menuselection:`General information --> Product type`, make the product " +"stockable (as soon as this is done, the icon \"Reordering rule will appear)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:71 +msgid "" +"In :menuselection:`Inventory --> route`, tick the \"Buy\" box (and untick " +"the Make To Order box)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:73 +msgid "" +"Select a vendor (don't forget to put a minimal quantity greater than 0)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:76 +msgid "Create a reordering rule" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:78 +msgid "Click on the Reordering Rules tab, click on Create. A new page opens." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:83 +msgid "" +"By default, Reordering Rules in Odoo are named as \"OP/XXXXX\" but you are " +"free to use any nomenclature. You can modify it via the **Name** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:86 +msgid "The **Product** field is the product you are creating the rule for." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:88 +msgid "" +"Select the warehouse to which the product should be delivered in the " +"**Warehouse** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:91 +msgid "" +"If you have configured multiple warehouses and location, specify the " +"location in which the product will be stored in the **Location** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:96 +msgid "" +":doc:`../../../inventory/settings/warehouses/difference_warehouse_location`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:102 +msgid "" +"In the **Minimum Quantity** field, insert the quantity to which the system " +"will trigger a new order for replenishment." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:105 +msgid "" +"In the **Maximum Quantity** field, insert the maximum of items that has to " +"be stocked. The replenishing order will be based on that quantity to " +"reorder." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:109 +msgid "" +"The **Quantity Multiple** is the lowest number of items that can be ordered " +"at once. For instance, some items may be only available for purchase in a " +"set of 2." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:113 +msgid "" +"In the Misc section, the **Active** box allows you to activate or deactivate" +" the rule." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:116 +msgid "In the **Lead Time** section, you can enter:" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:118 +msgid "" +"the number of Day(s) to purchase: correspond to the number of days for the " +"supplier to receive the order" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:120 +msgid "the number of Day(s) to get the products" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:122 +msgid "" +"By default, the lead times are in calendar days. You can change that in " +":menuselection:`Inventory --> Configuration --> Settings --> Minimum Stock " +"Rules`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:125 +msgid "When you have entered all the info, click on Save." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:127 +msgid "" +"From now on, every time a product with a reordering rule reaches the minimum" +" stock, the system will automatically send a RfQ to your supplier based on " +"your maximum quantity to replenish your stock." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:131 +msgid "" +"The replenishments will take place when the scheduler in the Inventory " +"module runs. By default in Odoo, the schedulers will run every night at " +"12:00PM." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:135 +msgid "" +"To know how to configure and run the schedulers manually, read the document " +"on :doc:`../../../inventory/management/misc/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:140 +msgid ":doc:`../../../inventory/management/misc/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:3 +#: ../../purchase/replenishment/flows/warning_triggering.rst:69 +msgid "How to trigger a warning when purchasing at a specific vendor?" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:8 +msgid "" +"The **Warning Messages and Alerts** module allow you to configure alerts on " +"the customers and vendors or products." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:11 +msgid "" +"You can select the following types of warnings and create different warnings" +" for purchases and sales:" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:14 +msgid "" +"Warning: This option displays the warning message during the process, but " +"allows the user to continue." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:17 +msgid "" +"Blocking Message: The message displays a warning message, but the user " +"cannot continue the process further." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:24 +msgid "Module Installation" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:26 +msgid "" +"First, you need to install the **Warning Messages and Alerts** module. Go to" +" **Apps** and look for it (don't forget to remove the **Apps** filter)." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:33 +msgid "Vendor or Customer warnings" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:35 +msgid "" +"Go to :menuselection:`Purchases --> Vendors` or to :menuselection:`Sales -->" +" Customers`." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:37 +msgid "Open the vendor or the customer and click on the **Warnings** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:42 +#: ../../purchase/replenishment/flows/warning_triggering.rst:62 +msgid "The available warnings are:" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:44 +msgid "Warning on the **Sales Order**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:46 +msgid "Warning on the **Purchase Order**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:48 +msgid "Warning on the **Picking**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:50 +msgid "Warning on the **Invoice**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:53 +msgid "Product Warnings" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:55 +msgid "" +"Go to :menuselection:`Purchases --> Products` or to :menuselection:`Sales " +"--> Products`." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:57 +msgid "Open the product and click on the **Notes** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:64 +msgid "Warning when selling this product." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:66 +msgid "Warning when Purchasing this product." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:71 +msgid "" +"Go to the Purchases application, click on :menuselection:`Purchase --> " +"Vendors`. Go to the **Warnings** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:74 +msgid "" +"Under **Warning on the Purchase Order**, choose **Warning** and write your " +"warning." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:80 +msgid "" +"Create a **Request for Quotation**. Go to :menuselection:`Purchase --> " +"Request for Quotation` and click on **Create**. Choose the vendor on which a" +" warning was set." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:84 +msgid "When choosing the vendor, the warning will appear." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:90 +msgid "" +"If you set a blocking message instead of a warning message, you won't be " +"able to choose the vendor." +msgstr "" + +#: ../../purchase/replenishment/multicompany.rst:3 +msgid "Multi-Companies" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:3 +msgid "How to setup a multi-company sale/purchase flow?" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:8 +msgid "" +"Odoo is an outstanding solution to help small companies growing their " +"business. But it also perfectly meets the needs of multinational " +"companies.The inter-company feature helps you to buy and/or sell products " +"and services between different branches within your conglomerate." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:17 +msgid "" +"Purchase orders and sales orders can be related. If a company within your " +"group creates a purchase or a sales order, the corresponding document is " +"automatically created for your company. All you have to do is check that " +"everything is correct and confirm the sale. You can automate the validation " +"on your sales and purchase orders." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:24 +msgid "It is also possible to only handle invoices and refunds." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:27 +msgid "Manage intercompany rules" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:29 +msgid "" +"Go to :menuselection:`Settings --> General Settings`. Flag **Manage multiple" +" companies** and then **Manage Inter Company**." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:32 +msgid "Click on **Apply**." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:37 +msgid "New options will appear." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:42 +msgid "" +"In the drop-down list, choose the company on which you want to add rules." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:45 +msgid "" +"If you click on **SO and PO setting for inter company**, you will get extra " +"options." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:51 +msgid "" +"When you are done, click on **Apply**, then you can repeat the same steps " +"for the other companies." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:55 +msgid "" +"In order to be able to manage the inter-company rules, be sure that your " +"user has the rights to manage the companies." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting.rst:3 +msgid "Trouble-Shooting" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:3 +msgid "How to check that everything is working fine?" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:6 +msgid "Vendor Bills" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:8 +msgid "" +"Even if you don't have the rights to the accounting application, you can " +"still control the vendor bills." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:11 +msgid "" +"Go to the **Purchases** application: :menuselection:`Control --> Vendor " +"Bills`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:17 +msgid "Incoming Products" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:19 +msgid "" +"Even if you don't have the rights to the inventory application, you can " +"still control the incoming products." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:22 +msgid "" +"Go to the **Purchases** application: :menuselection:`Control --> Incoming " +"Products`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:28 +msgid "Procurements exceptions" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:30 +msgid "Here, you need the **Inventory Manager** access rights." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:32 +msgid "" +"Go to the **Inventory** application: :menuselection:`Control --> Procurement" +" Exceptions`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:37 +msgid "" +"To understand why the procurement is not running, open the exception and " +"check the message in the chatter." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:43 +msgid "" +"Usually, the problem is located on the procurement rules. Either there are " +"no stock rules, or there are no vendor associated to a product." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/recruitment.po b/locale/ru/LC_MESSAGES/recruitment.po new file mode 100644 index 000000000..c85b53bd8 --- /dev/null +++ b/locale/ru/LC_MESSAGES/recruitment.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2016-11-22 13:16+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../recruitment.rst:5 +msgid "Recruitment" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/sales.po b/locale/ru/LC_MESSAGES/sales.po new file mode 100644 index 000000000..d0bc23907 --- /dev/null +++ b/locale/ru/LC_MESSAGES/sales.po @@ -0,0 +1,1880 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Denis Baranov , 2017\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\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 "" +"Доступ к порталу Odoo предоставляется пользователям для просмотра документов" +" или информации в системе." + +#: ../../sales/advanced/portal.rst:12 +msgid "" +"For Example: 1. A long term client who needs to view online quotations. 2." +" Accounting consultant who needs to keep track of the company's financials." +msgstr "" +"Например: 1. Клиент, которому необходимо просмотреть on-line коммерческое " +"предложение. 2. Бухгалтер, которому необходимо отслеживать финансовую " +"информацию компании." + +#: ../../sales/advanced/portal.rst:16 +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:20 +msgid "How to give portal access to customers?" +msgstr "Как предоставить доступ к порталу клиентам?" + +#: ../../sales/advanced/portal.rst:23 +msgid "From Contacts Module" +msgstr "Из модуля Контакты" + +#: ../../sales/advanced/portal.rst:25 +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:35 +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:38 +msgid "Select **Portal Access Management**. A pop up window appears." +msgstr "" +"И из выпадающего списка выберите **Доступ к порталу**. Появится всплывающее " +"окно." + +#: ../../sales/advanced/portal.rst:43 +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 "" +"Введите логин **email ID**, установите галочку **В портале** и напишите " +"сопровождающее письмо, которое будет включено в письмо новому пользователю. " +"По окончанию нажмите **Применить**." + +#: ../../sales/advanced/portal.rst:49 +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 `_. 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/services.rst:3 +msgid "Services" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:3 +msgid "How to invoice milestones of a project?" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:5 +msgid "" +"There are different kind of service sales: prepaid volume of hours/days " +"(e.g. support contract), billing based on time and material (e.g. billing " +"consulting hours) or a fixed price contract (e.g. a project)." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:9 +msgid "" +"In this section, we will have a look at how to invoice milestones of a " +"project." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:12 +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. For example, a marketing agency" +" hired for a new product launch could break down a project into the " +"following milestones, each of them considered as one service with a fixed " +"price on the sale order :" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:19 +msgid "Milestone 1 : Marketing strategy audit - 5 000 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:21 +msgid "Milestone 2 : Brand Identity - 10 000 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:23 +msgid "Milestone 3 : Campaign launch & PR - 8 500 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:25 +msgid "" +"In this case, an invoice will be sent to the customer each time a milestone " +"will be successfully reached. That 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 times." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:32 +msgid "" +"You can also use milestones to invoice percentages of the entire project. " +"For example, for a million euros project, your company might require a 15% " +"upfront payment, 30% at the midpoint and the balance at the contract " +"conclusion. In that case, each payment will be considered as one milestone." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:39 +#: ../../sales/invoicing/services/reinvoice.rst:26 +#: ../../sales/invoicing/services/reinvoice.rst:95 +#: ../../sales/invoicing/services/support.rst:17 +#: ../../sales/quotation/online/creation.rst:6 +#: ../../sales/quotation/setup/different_addresses.rst:14 +#: ../../sales/quotation/setup/first_quote.rst:21 +#: ../../sales/quotation/setup/optional.rst:16 +msgid "Configuration" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:42 +msgid "Install the Sales application" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:44 +#: ../../sales/invoicing/services/reinvoice.rst:28 +msgid "" +"In order to sell services and to send invoices, you need to install the " +"**Sales** application, from the **Apps** icon." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:51 +msgid "Create products" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:53 +msgid "" +"In Odoo, each milestone of your project is considered as a product. From the" +" **Sales** application, use the menu :menuselection:`Sales --> Products`, " +"create a new product with the following setup:" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:57 +msgid "**Name**: Strategy audit" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:59 +#: ../../sales/invoicing/services/support.rst:50 +msgid "**Product Type**: Service" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:61 +msgid "" +"**Invoicing Policy**: Delivered Quantities, since you will invoice your " +"milestone after it has been delivered" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:64 +msgid "" +"**Track Service**: Manually set quantities on order, as you complete each " +"milestone, you will manually update their quantity from the **Delivered** " +"tab on your sale order" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:72 +msgid "Apply the same configuration for the others milestones." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:75 +msgid "Managing your project" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:78 +msgid "Quotations and sale orders" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:80 +msgid "" +"Now that your milestones (or products) are created, you can create a " +"quotation or a sale order with each line corresponding to one milestone. For" +" each line, set the **Ordered Quantity** to ``1`` as each milestone is " +"completed once. Once the quotation is confirmed and transformed into a sale " +"order, you will be able to change the delivered quantities when the " +"corresponding milestone has been achieved." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:91 +msgid "Invoice milestones" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:93 +msgid "" +"Let's assume that your first milestone (the strategy audit) has been " +"successfully delivered and you want to invoice it to your customer. On the " +"sale order, click on **Edit** and set the **Delivered Quantity** of the " +"related product to ``1``." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:99 +msgid "" +"As soon as the above modification has been saved, you will notice that the " +"color of the line has changed to blue, meaning that the service can now be " +"invoiced. In the same time, the invoice status of the SO has changed from " +"**Nothing To Invoice** to **To Invoice**" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:104 +msgid "" +"Click on **Create invoice** and, in the new window that pops up, select " +"**Invoiceable lines** and validate. It will create a new invoice (in draft " +"status) with only the **strategy audit** product as invoiceable." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:112 +msgid "" +"In order to be able to invoice a product, you need to set up the " +"**Accounting** application and to configure an accounting journal and a " +"chart of account. Click on the following link to learn more: " +":doc:`../../../accounting/overview/getting_started/setup`" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:117 +msgid "" +"Back on your sale order, you will notice that the **Invoiced** column of " +"your order line has been updated accordingly and that the **Invoice Status**" +" is back to **Nothing to Invoice**." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:121 +msgid "Follow the same workflow to invoice your remaining milestones." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:124 +msgid ":doc:`reinvoice`" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:125 +#: ../../sales/invoicing/services/reinvoice.rst:185 +msgid ":doc:`support`" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:3 +msgid "How to re-invoice expenses to your customers?" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.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 " +"employee paying a parking spot for a meeting with your client. As a company," +" you would like to be able to invoice that expense to your client." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:11 +msgid "" +"In this documentation we will see two use cases. The first, very basic, " +"consists of invoicing a simple expense to your client like you would do for " +"a product. The second, more advanced, will consist of invoicing expenses " +"entered in your expense system by your employees directly to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:18 +msgid "Use case 1: Simple expense invoicing" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:20 +msgid "" +"Let's take the following example. You are working on a promotion campaign " +"for one of your customers (``Agrolait``) and you have to print a lot of " +"copies. Those copies are an expense for your company and you would like to " +"invoice them." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:35 +msgid "Create product to be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:37 +msgid "You will need now to create a product called ``Copies``." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:39 +#: ../../sales/invoicing/services/reinvoice.rst:112 +msgid "" +"From your **Sales** module, go to :menuselection:`Sales --> Products` and " +"create a product as follows:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:42 +msgid "**Product type**: consumable" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:44 +msgid "" +"**Invoicing policy**: on delivered quantities (you will manually set the " +"quantities to invoice on the sale order)" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:51 +msgid "Create a sale order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:53 +msgid "" +"Now that your product is correctly set up, you can create a sale order for " +"that product (from the menu :menuselection:`Sales --> Sales Orders`) with " +"the ordered quantities set to 0. Click on **Confirm the Sale** to create the" +" sale order. You will be able then to manually change the delivered " +"quantities on the sale order to reinvoice the copies to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:64 +#: ../../sales/invoicing/services/reinvoice.rst:177 +msgid "Invoice expense to your client" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:66 +msgid "" +"At the end of the month, you have printed ``1000`` copies on behalf of your " +"client and you want to re-invoice them. From the related sale order, click " +"on **Delivered Quantities**, manually enter the correct amount of copies and" +" click on **Save**. Your order line will turn blue, meaning that it is ready" +" to be invoiced. Click on **Create invoice**." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:73 +msgid "" +"The total amount on your sale order will be of 0 as it is computed on the " +"ordered quantities. It is your invoice which will compute the correct amount" +" due by your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:77 +msgid "" +"The invoice generated is in draft, so you can always control the quantities " +"and change the amount if needed. You will notice that the amount to be " +"invoiced is based here on the delivered quantities." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:84 +msgid "Click on validate to issue the payment to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:87 +msgid "Use case 2: Invoice expenses via the expense module" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:89 +msgid "" +"To illustrate this case, let's imagine that your company sells some " +"consultancy service to your customer ``Agrolait`` and both parties agreed " +"that the distance covered by your consultant will be re-invoiced at cost." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:97 +msgid "Here, you will need to install two more modules:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:99 +msgid "Expense Tracker" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:101 +msgid "" +"Accounting, where you will need to activate the analytic accounting from the" +" settings" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:108 +msgid "Create a product to be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:110 +msgid "You will now need to create a product called ``Kilometers``." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:115 +msgid "Product can be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:117 +msgid "Product type: Service" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:119 +msgid "Invoicing policy: invoice based on time and material" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:121 +msgid "Expense invoicing policy: At cost" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:123 +msgid "Track service: manually set quantities on order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:129 +msgid "Create a sales order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:131 +msgid "" +"Still from the Sales module, go to :menuselection:`Sales --> Sales Orders` " +"and add your product **Consultancy** on the order line." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:135 +msgid "" +"If your product doesn't exist yet, you can configure it on the fly from the " +"SO. Just type the name on the **product** field and click on **Create and " +"edit** to configure it." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:139 +msgid "" +"Depending on your product configuration, an **Analytic Account** may have " +"been generated automatically. If not, you can easily create one in order to " +"link your expenses to the sale order. Do not forget to confirm the sale " +"order." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:148 +msgid "" +"Refer to the documentation :doc:`../../../accounting/others/analytic/usage` " +"to learn more about that concept." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:152 +msgid "Create expense and link it to SO" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:154 +msgid "" +"Let's assume that your consultant covered ``1.000km`` in October as part of " +"his consultancy project. We will create a expense for it and link it to the " +"related sales order thanks to the analytic account." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:158 +msgid "" +"Go to the **Expenses** module and click on **Create**. Record your expense " +"as follows:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:161 +msgid "**Expense description**: Kilometers October 2015" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:163 +msgid "**Product**: Kilometers" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:165 +msgid "**Quantity**: 1.000" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:167 +msgid "**Analytic account**: SO0019 - Agrolait" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:172 +msgid "" +"Click on **Submit to manager**. As soon as the expense has been validated " +"and posted to the journal entries, a new line corresponding to the expense " +"will automatically be generated on the sale order." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:179 +msgid "You can now invoice the invoiceable lines to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:186 +msgid ":doc:`milestones`" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:3 +msgid "How to invoice a support contract (prepaid hours)?" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:5 +msgid "" +"There are different kinds of service sales: prepaid volume of hours/days " +"(e.g. support contract), billing based on time and material (e.g. billing " +"consulting hours) and a fixed price contract (e.g. a project)." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:9 +msgid "" +"In this section, we will have a look at how to sell and keep track of a pre-" +"paid support contract." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:12 +msgid "" +"As an example, you may sell a pack of ``50 Hours`` of support at " +"``$25,000``. The price is fixed and charged initially. But you want to keep " +"track of the support service you did for the customer." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:20 +msgid "Install the Sales and Timesheet applications" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:22 +msgid "" +"In order to sell services, you need to install the **Sales** application, " +"from the **Apps** icon. Install also the **Timesheets** application if you " +"want to track support services you worked on every contract." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:33 +msgid "Create Products" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:35 +msgid "" +"By default, products are sold by number of units. In order to sell services " +"``per hour``, you must allow using multiple unit of measures. From the " +"**Sales** application, go to the menu :menuselection:`Configuration --> " +"Settings`. From this screen, activate the multiple **Unit of Measures** " +"option." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:44 +msgid "" +"In order to sell a support contract, you must create a product for every " +"support contract you sell. From the **Sales** application, use the menu " +":menuselection:`Sales --> Products`, create a new product with the following" +" setup:" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:48 +msgid "**Name**: Technical Support" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:52 +msgid "**Unit of Measure**: Hours" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:54 +msgid "" +"**Invoicing Policy**: Ordered Quantities, since the service is prepaid, we " +"will invoice the service based on what has been ordered, not based on " +"delivered quantities." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:58 +msgid "" +"**Track Service**: Timesheet on contracts. An analytic account will " +"automatically be created for every order containing this service so that you" +" can track hours in the related account." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:66 +msgid "" +"There are different ways to track the service related to a sales order or " +"product sold. With the above configuration, you can only sell one support " +"contract per order. If your customer orders several service contracts on " +"timesheet, you will have to split the quotation into several orders." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:72 +msgid "" +"Note that you can sell in different unit of measure than hours, example: " +"days, pack of 40h, etc. To do that, just create a new unit of measure in the" +" **Unit of Measure** category and set a conversion ratio compared to " +"**Hours** (example: ``1 day = 8 hours``)." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:78 +msgid "Managing support contract" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:81 +msgid "Quotations and Sales Orders" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:83 +msgid "" +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:93 +msgid "Timesheets" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:95 +msgid "" +"To track the service you do on a specific contract, you should use the " +"timesheet application. An analytic account related to the sale order has " +"been automatically created (``SO009 - Agrolait`` on the screenshot here " +"above), so you can start tracking services as soon as it has been sold." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:104 +msgid "Control delivered support on the sales order" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:106 +msgid "" +"From the **Sales** application, use the menu :menuselection:`Sales --> Sales" +" Orders` to control the progress of every order. On the sales order line " +"related to the support contract, you should see the **Delivered Quantities**" +" that are updated automatically, based on the number of hours in the " +"timesheet." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:116 +msgid "Upselling and renewal" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:118 +msgid "" +"If the number of hours you performed on the support contract is bigger or " +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:127 +msgid "" +"If you use Odoo CRM, a good practice is to create an opportunity for every " +"sale order in upselling invoice status so that you easily track your " +"upselling effort." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:131 +msgid "" +"If you sell an extra support contract, you can either add a new line on the " +"existing sales order (thus, you continue to timesheet on the same order) or " +"create a new order (thus, people will timesheet their hours on the new " +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:138 +msgid "Special Configuration" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:140 +msgid "" +"When creating the product form, you may set a different approach to track " +"the service:" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:143 +msgid "" +"**Create task and track hours**: in this mode, a task is created for every " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " +"contract). The advantage of this solution is that it allows to sell several " +"service contracts within the same sales order." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:150 +msgid "" +"**Manually**: you can use this mode if you don't record timesheets in Odoo. " +"The number of hours you worked on a specific contract can be recorded " +"manually on the sales order line directly, in the delivered quantity field." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:156 +msgid ":doc:`../../../inventory/settings/products/uom`" +msgstr "" + +#: ../../sales/overview.rst:3 +#: ../../sales/quotation/setup/different_addresses.rst:6 +#: ../../sales/quotation/setup/first_quote.rst:6 +#: ../../sales/quotation/setup/optional.rst:6 +#: ../../sales/quotation/setup/terms_conditions.rst:6 +msgid "Overview" +msgstr "" + +#: ../../sales/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo Sales" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:13 +msgid "" +"As a sales manager, closing opportunities with Odoo Sales is really simple." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:16 +msgid "" +"I selected a predefined quotation for a new product line offer. The " +"products, the service details are already in the quotation. Of course, I can" +" adapt the offer to fit my clients needs." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:20 +msgid "" +"The interface is really smooth. I can add references, some catchy phrases " +"such as closing triggers (*here, you save $500 if you sign the quote within " +"15 days*). I have a beautiful and modern design. This will help me close my " +"opportunities more easily." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:26 +msgid "" +"Plus, reviewing the offer from a mobile phone is easy. Really easy. The " +"customer got a clear quotation with a table of content. We can communicate " +"easily. I identified an upselling opportunity. So, I adapt the offer by " +"adding more products. When the offer is ready, the customer just need to " +"sign it online in just a few clicks. Odoo Sales is integrated with major " +"shipping services: UPS, Fedex, USPS and more. The signed offer creates a " +"delivery order automatically." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:35 +msgid "That's it, I sucesfully sold my products in just a few clicks." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:37 +msgid "" +"Oh, I also have the transaction and communication history at my fingertips. " +"It's easy for every stakeholder to know clearly the past interaction. And " +"any information related to the transaction." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:42 +msgid "" +"If you want to show information, I would do it from a customer form, " +"something like:" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:45 +msgid "Kanban of customers, click on one customer" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:47 +msgid "Click on opportunities, click on quotation" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:49 +msgid "Come back to customers (breadcrum)" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:51 +msgid "Click on customer statement letter" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:53 +msgid "" +"Anytime, I can get an in-depth report of my sales activity. Revenue by " +"salespeople or department. Revenue by category of product, drill-down to " +"specific products, by quarter or month,... I like this report: I can add it " +"to my dashboard in just a click." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:58 +msgid "" +"Odoo Sales is a powerful, yet easy-to-use app. At first, I used the sales " +"planner. Thanks to it, I got tips and tricks to boost my sales performance." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:62 +msgid "" +"Try Odoo Sales now and get beautiful quotations, amazing dashboards and " +"increase your success rate." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:3 +msgid "Overview of the invoicing process" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:16 +msgid ":menuselection:`Sales Order --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:18 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:22 +msgid "" +"Invoice on ordered quantity: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:25 +msgid "Invoice based on delivered quantity: see next section" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:27 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:31 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice ready" +" to invoice line, invoice a percentage (advance), invoice a fixed advance." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:36 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:41 +msgid ":menuselection:`Sales Order --> Delivery --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:43 +msgid "" +"Retailers and eCommerce usually invoice based on delivered quantity , " +"instead of sales order. This approach is suitable for businesses where the " +"quantities you deliver may differs from the ordered quantities: foods " +"(invoice based on actual Kg)." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:48 +msgid "" +"This way, if you deliver a partial order, you only invoice for what you " +"really delivered. If you do back orders (deliver partially and the rest " +"later), the customer will receive two invoices, one for each delivery order." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:57 +msgid ":menuselection:`Recurring Contracts (subscriptions) --> Invoices`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:59 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:67 +msgid ":menuselection:`eCommerce Order --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:69 +msgid "" +"An eCommerce order will also trigger the creation of the invoice when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:75 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:77 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:82 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:85 +msgid "if you need to create a refund" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:87 +msgid "If you need to give a discount" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:89 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:91 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:94 +msgid "Others" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:96 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:98 +msgid "membership: invoice your members every year" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:100 +msgid "repairs: invoice your after-sale services" +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. As pricelists only suggest prices, " +"they can be overridden by users completing sales orders. Choose your pricing" +" strategy from :menuselection:`Sales --> Settings`." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:16 +msgid "Several prices per product" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:18 +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:23 +msgid "Prices per customer segment" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:25 +msgid "" +"Create pricelists for your customer segments: e.g. registered, premium, etc." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:30 +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:38 +msgid "Temporary prices" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:40 +msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:46 +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:50 +msgid "Prices per minimum quantity" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:56 +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:60 +msgid "Discounts, margins, roundings" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:62 +msgid "" +"The third option 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:69 +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:77 +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:84 +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:86 +msgid "Make sure at least one pricelist item covers all your products." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:88 +msgid "There are 3 modes of computation: fix price, discount & formula." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:93 +msgid "Here are different price settings made possible thanks to formulas." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:96 +msgid "Discounts with roundings" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:98 +msgid "e.g. 20% discounts with prices rounded up to 9.99." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:104 +msgid "Costs with markups (retail)" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:106 +msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:112 +msgid "Prices per country" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:113 +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:116 +msgid "The default pricelist can be replaced when creating a sales order." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:118 +msgid "You can change the pricelists sequence by drag & drop in list view." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:121 +msgid "Compute and show discount % to customers" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:123 +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:125 +msgid "" +"Check *Allow discounts on sales order lines* in :menuselection:`Sales --> " +"Configuration --> Settings --> Quotations & Sales --> Discounts`." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:126 +msgid "Apply the option in the pricelist setup form." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:133 +msgid ":doc:`currencies`" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:134 +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/taxes.rst:3 +msgid "Set taxes" +msgstr "" + +#: ../../sales/quotation.rst:3 +msgid "Quotation" +msgstr "" + +#: ../../sales/quotation/online.rst:3 +msgid "Online Quotation" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:3 +msgid "How to create and edit an online quotation?" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:9 +msgid "Enable Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:11 +msgid "" +"To send online quotations, you must first enable online quotations in the " +"Sales app from :menuselection:`Configuration --> Settings`. Doing so will " +"prompt you to install the Website app if you haven't already." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:18 +msgid "" +"You can view the online version of each quotation you create after enabling " +"this setting by selecting **Preview** from the top of the quotation." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:25 +msgid "Edit Your Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:27 +msgid "" +"The online quotation page can be edited for each quotation template in the " +"Sales app via :menuselection:`Configuration --> Quotation Templates`. From " +"within any quotation template, select **Edit Template** to be taken to the " +"corresponding page of your website." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:34 +msgid "" +"You can add text, images, and structural elements to the quotation page by " +"dragging and dropping blocks from the pallet on the left sidebar menu. A " +"table of contents will be automatically generated based on the content you " +"add." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:38 +msgid "" +"Advanced descriptions for each product on a quotation are displayed on the " +"online quotation page. These descriptions are inherited from the product " +"page in your eCommerce Shop, and can be edited directly on the page through " +"the inline text editor." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:45 +msgid "" +"You can choose to allow payment immediately after the customer validates the" +" quote by selecting a payment option on the quotation template." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:48 +msgid "" +"You can edit the webpage of an individual quotation as you would for any web" +" page by clicking the **Edit** button. Changes made in this way will only " +"affect the individual quotation." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:52 +msgid "Using Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:54 +msgid "" +"To share an online quotation with your customer, copy the URL of the online " +"quotation, then share it with customer." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:60 +msgid "" +"Alternatively, your customer can access their online quotations by logging " +"into your website through the customer portal. Your customer can accept or " +"reject the quotation, print it, or negotiate the terms in the chat box. You " +"will also receive a notification in the chatter within Odoo whenever the " +"customer views the quotation." +msgstr "" + +#: ../../sales/quotation/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:3 +msgid "How to use different invoice and delivery addresses?" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:8 +msgid "" +"It is possible to configure different addresses for delivery and invoicing. " +"This is very useful, because it could happen that your clients have multiple" +" locations and that the invoice address differs from the delivery location." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:16 +msgid "" +"First, go to the Sales application, then click on " +":menuselection:`Configuration --> Settings` and activate the option **Enable" +" the multiple address configuration from menu**." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:24 +msgid "Set the addresses on the contact form" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:26 +msgid "" +"Invoice and/or shipping addresses and even other addresses are added on the " +"contact form. To do so, go to the contact application, select the customer " +"and in the **Contacts & Addresses** tab click on **Create**" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:33 +msgid "" +"A new window will open where you can specify the delivery or the invoice " +"address." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:39 +msgid "" +"Once you validated your addresses, it will appear in the **Contacts & " +"addresses** tab with distinctive logos." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:46 +msgid "On the quotations and sales orders" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:48 +msgid "" +"When you create a new quotation, the option to select an invoice address and" +" a delivery address is now available. Both addresses will automatically be " +"filled in when selecting the customer." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:56 +msgid "" +"Note that you can also create invoice and delivery addresses on the fly by " +"selecting **Create and edit** in the dropdown menu." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:59 +msgid "When printing your sales orders, you'll notice the two addresses." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:3 +msgid "How to create my first quotation?" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:8 +msgid "" +"Quotations are documents sent to customers to offer an estimated cost for a " +"particular set of goods or services. The customer can accept the quotation, " +"in which case the seller will have to issue a sales order, or refuse it." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:13 +msgid "" +"For example, my company sells electronic products and my client Agrolait " +"showed interest in buying ``3 iPads`` to facilitate their operations. I " +"would like to send them a quotation for those iPads with a sales price of " +"``320 USD`` by iPad with a ``5%`` discount." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:18 +msgid "This section will show you how to proceed." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:24 +msgid "Install the Sales Management module" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:26 +msgid "" +"In order to be able to issue your first quotation, you'll need to install " +"the **Sales Management** module from the app module in the Odoo backend." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:34 +msgid "Allow discounts on sales order line" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:36 +msgid "" +"Allowing discounts on quotations is a common sales practice to improve the " +"chances to convert the prospect into a client." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:39 +msgid "" +"In our example, we wanted to grant ``Agrolait`` with a ``5%`` discount on " +"the sale price. To enable the feature, go into the **Sales** application, " +"select :menuselection:`Configuration --> Settings` and, under **Quotations " +"and Sales**, tick **Allow discounts on sales order line** (see picture " +"below) and apply your changes." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:49 +msgid "Create your quotation" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:51 +msgid "" +"To create your first quotation, click on :menuselection:`Sales --> " +"Quotations` and click on **Create**. Then, complete your quotation as " +"follows:" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:55 +msgid "Customer and Products" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:57 +msgid "" +"The basic elements to add to any quotation are the customer (the person you " +"will send your quotation to) and the products you want to sell. From the " +"quotation view, choose the prospect from the **Customer** drop-down list and" +" under **Order Lines**, click on **Add an item** and select your product. Do" +" not forget to manually add the number of items under **Ordered Quantity** " +"and the discount if applicable." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:67 +msgid "" +"If you don't have any customer or product recorded on your Odoo environment " +"yet, you can create them on the fly directly from your quotations :" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:71 +msgid "" +"To add a new customer, click on the **Customer** drop-down menu and click on" +" **Create and edit**. In this new window, you will be able to record all the" +" customer details, such as the address, website, phone number and person of " +"contact." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:76 +msgid "" +"To add a new product, under **Order line**, click on add an item and on " +"**Create and Edit** from the drop-down list. You will be able to record your" +" product information (product type, cost, sale price, invoicing policy, " +"etc.) along with a picture." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:82 +msgid "Taxes" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:84 +msgid "" +"To parameter taxes, simply go on the taxes section of the product line and " +"click on **Create and Edit**. Fill in the details (for example if you are " +"subject to a ``21%`` taxe on your sales, simply fill in the right amount in " +"percentage) and save." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:93 +msgid "Terms and conditions" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:95 +msgid "" +"You can select the expiration date of your quotation and add your company's " +"terms and conditions directly in your quotation (see picture below)." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:103 +msgid "Preview and send quotation" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:105 +msgid "" +"If you want to see what your quotation looks like before sending it, click " +"on the **Print** button (upper left corner). It will give you a printable " +"PDF version with all your quotation details." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:113 +msgid "" +"Update your company's details (address, website, logo, etc) appearing on " +"your quotation from the the **Settings** menu on the app switcher, and on " +"click on the link :menuselection:`Settings --> General settings --> " +"Configure company data`." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:118 +msgid "" +"Click on **Send by email** to automatically send an email to your customer " +"with the quotation as an attachment. You can adjust the email body before " +"sending it and even save it as a template if you wish to reuse it." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:127 +msgid ":doc:`../online/creation`" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:128 +msgid ":doc:`optional`" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:129 +msgid ":doc:`terms_conditions`" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:3 +msgid "How to display optional products on a quotation?" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:8 +msgid "" +"The use of suggested products is a marketing strategy that attempts to " +"increase the amount a customer spends once they begin the buying process. " +"For instance, a customer purchasing a cell phone could be shown accessories " +"like a protective case, a screen cover, and headset. In Odoo, a customer can" +" be presented with additional products that are relevant to their chosen " +"purchase in one of several locations." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:18 +msgid "" +"Suggested products can be added to quotations directly, or to the ecommerce " +"platform via each product form. In order to use suggested products, you will" +" need to have the **Ecommerce** app installed:" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:23 +msgid "Quotations" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:25 +msgid "" +"To add suggested products to quotations, you must first enable online " +"quotations in the Sales app from :menuselection:`Configuration --> " +"Settings`. Doing so will prompt you to install the Website app if you " +"haven't already." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:32 +msgid "" +"You will then be able to add suggested products to your individual " +"quotations and quotation templates under the **Suggested Products** tab of a" +" quotation." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:39 +msgid "Website Sales" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:41 +msgid "" +"You can add suggested products to a product on its product form, under the " +"Website heading in the **Sales** tab. **Suggested products** will appear on " +"the *product* page, and **Accessory Products** will appear on the *cart* " +"page prior to checkout." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:3 +msgid "How to link terms and conditions to a quotation?" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:8 +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 so customer can read " +"all those terms before committing to anything." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:13 +msgid "" +"Thanks to Odoo you can easily include your default terms and conditions on " +"every quotation, sales order and invoice." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:16 +msgid "" +"Let's take the following example: Your company sells water bottles to " +"restaurants and you would like to add the following standard terms and " +"conditions on all your quotations:" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:20 +msgid "" +"*Safe storage of the products of MyCompany is necessary in order to ensure " +"their quality, MyCompany will not be held accountable in case of unsafe " +"storage of the products.*" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:25 +msgid "General terms and conditions" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:27 +msgid "" +"General terms and conditions can be specified in the Sales settings. They " +"will then automatically appear on every sales document from the quotation to" +" the invoice." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:31 +msgid "" +"To specify your Terms and Conditions go into : :menuselection:`Sales --> " +"Configuration --> Settings --> Default Terms and Conditions`." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:36 +msgid "" +"After saving, your terms and conditions will appear on your new quotations, " +"sales orders and invoices (in the system but also on your printed " +"documents)." +msgstr "" + +#: ../../sales/sale_ebay.rst:3 +msgid "eBay" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/website.po b/locale/ru/LC_MESSAGES/website.po new file mode 100644 index 000000000..7cae8abfa --- /dev/null +++ b/locale/ru/LC_MESSAGES/website.po @@ -0,0 +1,1383 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n" + +#: ../../website.rst:5 +msgid "Website" +msgstr "" + +#: ../../website/optimize.rst:3 +msgid "Optimize" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:3 +msgid "How to track your website's traffic in Google Analytics" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:5 +msgid "To follow your website's traffic with Google Analytics:" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:7 +msgid "" +"`Create a Google Analytics account `__ if" +" you don't have any." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:10 +msgid "" +"Go through the creation form and accept the conditions to get the tracking " +"ID." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:15 +msgid "Copy the tracking ID to insert it in Odoo." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:20 +msgid "" +"Go to the *Configuration* menu of your Odoo's Website app. In the settings, " +"turn on Google Analytics and paste the tracking ID. Then save the page." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:27 +msgid "" +"To make your first steps in Google Analytics, refer to `Google " +"Documentation. " +"`__" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:31 +msgid ":doc:`google_analytics_dashboard`" +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:3 +msgid "How to track your website's traffic from your Odoo Dashboard" +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:5 +msgid "" +"You can follow your traffic's statistics straight from your Odoo Website " +"Dashboard thanks to Google Analytics." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:8 +msgid "" +"A preliminary step is creating a Google Analytics account and entering the " +"tracking ID in your Website's settings (see :doc:`google_analytics`)." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:11 +msgid "" +"Go to `Google APIs platform `__ to " +"generate Analytics API credentials. Log in with your Google account." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:14 +msgid "Select Analytics API." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:19 +msgid "" +"Create a new project and give it a name (e.g. Google Analytics in Odoo)." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:24 +msgid "Enable the API." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:29 +msgid "" +"Create credentials to use in Odoo. Select *Web browser (Javascript)* as " +"calling source and *User data* as kind of data." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:38 +msgid "" +"Then enter the name of the application (e.g. Odoo) and the allowed pages on " +"which you will be redirected. The *Authorized JavaScript origin* is your " +"Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance " +"URL followed by /google_account/authentication." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:47 +msgid "" +"Go through the Consent Screen step by entering a product name (e.g. Google " +"Analytics in Odoo). Feel free to check the customizations options but this " +"is not mandatory. The Consent Screen will only show up when you enter the " +"Client ID in Odoo for the first time." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:52 +msgid "" +"Finally you are provided with your Client ID. Copy and paste it in Odoo." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:57 +msgid "" +"Open your Website Dashboard in Odoo and link your Analytics account. to past" +" your Client ID." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:63 +msgid "As a last step, authorize Odoo to access Google API." +msgstr "" + +#: ../../website/optimize/seo.rst:3 +msgid "How to do Search Engine Optimisation in Odoo" +msgstr "" + +#: ../../website/optimize/seo.rst:6 +msgid "How is SEO handled in Odoo?" +msgstr "" + +#: ../../website/optimize/seo.rst:8 +msgid "" +"Search Engine Optimization (SEO) is a set of good practices to optimize your" +" website so that you get a better ranking in search engines like Google. In " +"short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../website/optimize/seo.rst:12 +msgid "" +"Some examples of SEO rules: your web pages should load faster, your page " +"should have one and only one title ``

``, your website should have a " +"``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../website/optimize/seo.rst:16 +msgid "" +"The Odoo Website Builder is probably the most SEO-ready CMS out there. We " +"consider SEO a top priority. To guarantee Odoo Website and Odoo eCommerce " +"users have a great SEO, Odoo abstracts all the technical complexities of SEO" +" and handles everything for you, in the best possible way." +msgstr "" + +#: ../../website/optimize/seo.rst:23 +msgid "Page speed" +msgstr "" + +#: ../../website/optimize/seo.rst:26 +msgid "Introduction" +msgstr "" + +#: ../../website/optimize/seo.rst:28 +msgid "" +"The time to load a page is an important criteria for Google. A faster " +"website not only improves your visitor's experience, but Google gives you a " +"better page ranking if your page loads faster than your competitors. Some " +"studies have shown that, if you divide the time to load your pages by two " +"(e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also " +"divided by two. (25% to 12.5%). One extra second to load a page could `cost " +"$1.6b to Amazon in sales `__." +msgstr "" + +#: ../../website/optimize/seo.rst:40 +msgid "" +"Fortunately, Odoo does all the magic for you. Below, you will find the " +"tricks Odoo uses to speed up your page loading time. You can compare how " +"your website ranks using these two tools:" +msgstr "" + +#: ../../website/optimize/seo.rst:44 +msgid "" +"`Google Page Speed " +"`__" +msgstr "" + +#: ../../website/optimize/seo.rst:46 +msgid "`Pingdom Website Speed Test `__" +msgstr "" + +#: ../../website/optimize/seo.rst:49 +msgid "Static resources: CSS" +msgstr "" + +#: ../../website/optimize/seo.rst:51 +msgid "" +"All CSS files are pre-processed, concatenated, minified, compressed and " +"cached (server side and browser side). The result:" +msgstr "" + +#: ../../website/optimize/seo.rst:54 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../website/optimize/seo.rst:56 +msgid "" +"this CSS file is shared and cached amongst pages, so that when the visitor " +"clicks on another page, the browser doesn't have to even load a single CSS " +"resource." +msgstr "" + +#: ../../website/optimize/seo.rst:60 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../website/optimize/seo.rst:62 +msgid "" +"**Pre-processed:** The CSS framework used by Odoo 9 is bootstrap 3. Although" +" a theme might use another framework, most of `Odoo themes " +"`__ extend and customize bootstrap " +"directly. Since Odoo supports Less and Sass, so you can modify CSS rules, " +"instead of overwriting them through extra CSS lines, resulting in a smaller " +"file." +msgstr "" + +#: ../../website/optimize/seo.rst:70 +msgid "**Both files in the **" +msgstr "" + +#: ../../website/optimize/seo.rst:70 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../website/optimize/seo.rst:72 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:72 ../../website/optimize/seo.rst:73 +#: ../../website/optimize/seo.rst:79 ../../website/optimize/seo.rst:121 +msgid ".text-muted {" +msgstr "" + +#: ../../website/optimize/seo.rst:73 ../../website/optimize/seo.rst:80 +#: ../../website/optimize/seo.rst:122 +msgid "color: #666;" +msgstr "" + +#: ../../website/optimize/seo.rst:74 +msgid "color: #777;" +msgstr "" + +#: ../../website/optimize/seo.rst:74 +msgid "background: yellow" +msgstr "" + +#: ../../website/optimize/seo.rst:75 +msgid "background: yellow;" +msgstr "" + +#: ../../website/optimize/seo.rst:75 ../../website/optimize/seo.rst:76 +#: ../../website/optimize/seo.rst:81 ../../website/optimize/seo.rst:123 +msgid "}" +msgstr "" + +#: ../../website/optimize/seo.rst:78 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:84 +msgid "" +"**Concatenated:** every module or library you might use in Odoo has its own " +"set of CSS, Less or Sass files (eCommerce, blog, theme, etc.) Having several" +" CSS files is great for the modularity, but not good for the performance " +"because most browsers can only perform 6 requests in parallel resulting in " +"lots of files that are loaded in series. The latency time to transfer a file" +" is usually much longer than the actual data transfer time, for small files " +"like .JS and .CSS. Thus, the time to load CSS resources depends more on the " +"number of requests to be done than the actual file size." +msgstr "" + +#: ../../website/optimize/seo.rst:94 +msgid "" +"To address this issue, all CSS / Less / Sass files are concatenated into a " +"single .CSS file to send to the browser. So a visitor has **only one .CSS " +"file to load** per page, which is particularly efficient. As the CSS is " +"shared amongst all pages, when the visitor clicks on another page, the " +"browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../website/optimize/seo.rst:100 +msgid "" +"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. " +"By doing this, additional page views from the same visitor will not have to " +"load CSS files at all. But some modules might include huge CSS/Javascript " +"resources that you do not want to prefetch at the first page because they " +"are too big. In this case, Odoo splits this resource into a second bundle " +"that is loaded only when the page using it is requested. An example of this " +"is the backend that is only loaded when the visitor logs in and accesses the" +" backend (/web)." +msgstr "" + +#: ../../website/optimize/seo.rst:110 +msgid "" +"If the CSS file is very big, Odoo will split it into two smaller files to " +"avoid the 4095 selectors limit per sheet of Internet Explorer 8. But most " +"themes fit below this limit." +msgstr "" + +#: ../../website/optimize/seo.rst:114 +msgid "" +"**Minified:** After being pre-processed and concatenated, the resulting CSS " +"is minified to reduce its size." +msgstr "" + +#: ../../website/optimize/seo.rst:118 +msgid "**Before minification**" +msgstr "" + +#: ../../website/optimize/seo.rst:118 +msgid "**After minification**" +msgstr "" + +#: ../../website/optimize/seo.rst:120 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:120 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../website/optimize/seo.rst:126 +msgid "" +"The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../website/optimize/seo.rst:129 +msgid "" +"Then, a cached version is stored on the server side (so we do not have to " +"pre-process, concatenate, minify at every request) and the browser side (so " +"the same visitor will load the CSS only once for all pages he will visit)." +msgstr "" + +#: ../../website/optimize/seo.rst:135 +msgid "" +"If you are in debug mode, the CSS resources are neither concatenated nor " +"minified. That way, it's easier to debug (but it's much slower)" +msgstr "" + +#: ../../website/optimize/seo.rst:140 +msgid "Static resources: Javascript" +msgstr "" + +#: ../../website/optimize/seo.rst:142 +msgid "" +"As with CSS resources, Javascript resources are also concatenated, minified," +" compressed and cached (server side and browser side)." +msgstr "" + +#: ../../website/optimize/seo.rst:145 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../website/optimize/seo.rst:147 +msgid "" +"One for all pages of the website (including code for parallax effects, form " +"validation, …)" +msgstr "" + +#: ../../website/optimize/seo.rst:150 +msgid "" +"One for common Javascript code shared among frontend and backend (bootstrap)" +msgstr "" + +#: ../../website/optimize/seo.rst:153 +msgid "" +"One for backend specific Javascript code (Odoo Web Client interface for your" +" employees using Odoo)" +msgstr "" + +#: ../../website/optimize/seo.rst:156 +msgid "" +"Most visitors to your website will only need the first two bundles, " +"resulting in a maximum of two Javascript files to load to render one page. " +"As these files are shared across all pages, further clicks by the same " +"visitor will not load any other Javascript resource." +msgstr "" + +#: ../../website/optimize/seo.rst:162 +msgid "" +"If you work in debug mode, the CSS and javascript are neither concatenated, " +"nor minified. Thus, it's much slower. But it allows you to easily debug with" +" the Chrome debugger as CSS and Javascript resources are not transformed " +"from their original versions." +msgstr "" + +#: ../../website/optimize/seo.rst:168 +msgid "Images" +msgstr "" + +#: ../../website/optimize/seo.rst:170 +msgid "" +"When you upload new images using the website builder, Odoo automatically " +"compresses them to reduce their sizes. (lossless compression for .PNG and " +".GIF and lossy compression for .JPG)" +msgstr "" + +#: ../../website/optimize/seo.rst:174 +msgid "" +"From the upload button, you have the option to keep the original image " +"unmodified if you prefer to optimize the quality of the image rather than " +"performance." +msgstr "" + +#: ../../website/optimize/seo.rst:182 +msgid "" +"Odoo compresses images when they are uploaded to your website, not when " +"requested by the visitor. Thus, it's possible that, if you use a third-party" +" theme, it will provide images that are not compressed efficiently. But all " +"images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../website/optimize/seo.rst:188 +msgid "" +"When you click on an image, Odoo shows you the Alt and title attributes of " +"the ```` tag. You can click on it to set your own title and Alt " +"attributes for the image." +msgstr "" + +#: ../../website/optimize/seo.rst:195 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../website/optimize/seo.rst:200 +msgid "" +"Odoo's pictograms are implemented using a font (`Font Awesome " +"`__ in most Odoo themes)." +" Thus, you can use as many pictograms as you want in your page, they will " +"not result in extra requests to load the page." +msgstr "" + +#: ../../website/optimize/seo.rst:209 +msgid "CDN" +msgstr "" + +#: ../../website/optimize/seo.rst:211 +msgid "" +"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, " +"images) are loaded from a Content Delivery Network. Using a Content Delivery" +" Network has three advantages:" +msgstr "" + +#: ../../website/optimize/seo.rst:215 +msgid "" +"Load resources from a nearby server (most CDN have servers in main countries" +" around the globe)" +msgstr "" + +#: ../../website/optimize/seo.rst:218 +msgid "" +"Cache resources efficiently (no computation resources usage on your own " +"server)" +msgstr "" + +#: ../../website/optimize/seo.rst:221 +msgid "" +"Split the resource loading on different services allowing to load more " +"resources in parallel (since the Chrome limit of 6 parallel requests is by " +"domain)" +msgstr "" + +#: ../../website/optimize/seo.rst:225 +msgid "" +"You can configure your CDN options from the **Website Admin** app, using the" +" Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../website/optimize/seo.rst:232 +msgid "HTML Pages" +msgstr "" + +#: ../../website/optimize/seo.rst:234 +msgid "" +"Odoo allows to minify HTML pages, from the **Website Admin** app, using the " +":menuselection:`Configuration` menu. This will automatically remove extra " +"space and tabs in your HTML code, reduce some tags code, etc." +msgstr "" + +#: ../../website/optimize/seo.rst:241 +msgid "" +"On top of that, the HTML pages can be compressed, but this is usually " +"handled by your web server (NGINX or Apache)." +msgstr "" + +#: ../../website/optimize/seo.rst:244 +msgid "" +"The Odoo Website builder has been optimized to guarantee clean and short " +"HTML code. Building blocks have been developed to produce clean HTML code, " +"usually using bootstrap and the HTML editor." +msgstr "" + +#: ../../website/optimize/seo.rst:248 +msgid "" +"As an example, if you use the color picker to change the color of a " +"paragraph to the primary color of your website, Odoo will produce the " +"following code:" +msgstr "" + +#: ../../website/optimize/seo.rst:252 +msgid "``

My Text

``" +msgstr "" + +#: ../../website/optimize/seo.rst:254 +msgid "" +"Whereas most HTML editors (such as CKEditor) will produce the following " +"code:" +msgstr "" + +#: ../../website/optimize/seo.rst:257 +msgid "``

My Text

``" +msgstr "" + +#: ../../website/optimize/seo.rst:260 +msgid "Responsive Design" +msgstr "" + +#: ../../website/optimize/seo.rst:262 +msgid "" +"As of 2015, websites that are not mobile-friendly are negatively impacted in" +" Google Page ranking. All Odoo themes rely on Bootstrap 3 to render " +"efficiently according to the device: desktop, tablet or mobile phone." +msgstr "" + +#: ../../website/optimize/seo.rst:270 +msgid "" +"As all Odoo modules share the same technology, absolutely all pages in your " +"website are mobile friendly. (as opposed to traditional CMS which have " +"mobile friendly themes, but some specific modules or pages are not designed " +"to be mobile friendly as they all have their own CSS frameworks)" +msgstr "" + +#: ../../website/optimize/seo.rst:277 +msgid "Browser caching" +msgstr "" + +#: ../../website/optimize/seo.rst:279 +msgid "" +"Javascript, images and CSS resources have an URL that changes dynamically " +"when their content change. As an example, all CSS files are loaded through " +"this URL: " +"`http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css " +"`__. " +"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of " +"your website." +msgstr "" + +#: ../../website/optimize/seo.rst:286 +msgid "" +"This allows Odoo to set a very long cache delay (XXX) on these resources: " +"XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../website/optimize/seo.rst:294 +msgid "Scalability" +msgstr "" + +#: ../../website/optimize/seo.rst:296 +msgid "" +"In addition to being fast, Odoo is also more scalable than traditional CMS' " +"and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link " +"provides an analysis of the major open source CMS and eCommerce compared to " +"Odoo when it comes to high query volumes." +msgstr "" + +#: ../../website/optimize/seo.rst:301 +msgid "" +"`*https://www.odoo.com/slides/slide/197* `__" +msgstr "" + +#: ../../website/optimize/seo.rst:303 +msgid "" +"Here is the slide that summarizes the scalability of Odoo eCommerce and Odoo" +" CMS. (based on Odoo version 8, Odoo 9 is even faster)" +msgstr "" + +#: ../../website/optimize/seo.rst:310 +msgid "URLs handling" +msgstr "" + +#: ../../website/optimize/seo.rst:313 +msgid "URLs Structure" +msgstr "" + +#: ../../website/optimize/seo.rst:315 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../website/optimize/seo.rst:317 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../website/optimize/seo.rst:319 +msgid "With the following components:" +msgstr "" + +#: ../../website/optimize/seo.rst:321 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../website/optimize/seo.rst:323 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../website/optimize/seo.rst:325 +msgid "" +"**/fr\\_FR** = the language of the page. This part of the URL is removed if " +"the visitor browses the main language of the website (english by default, " +"but you can set another language as the main one). Thus, the English version" +" of this page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../website/optimize/seo.rst:331 +msgid "" +"**/shop/product** = every module defines its own namespace (/shop is for the" +" catalog of the eCommerce module, /shop/product is for a product page). This" +" name can not be customized to avoid conflicts in different URLs." +msgstr "" + +#: ../../website/optimize/seo.rst:336 +msgid "" +"**my-great-product** = by default, this is the slugified title of the " +"product this page refers to. But you can customize it for SEO purposes. A " +"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending " +"on the namespace, this could be different objects (blog post, page title, " +"forum post, forum comment, product category, etc)" +msgstr "" + +#: ../../website/optimize/seo.rst:343 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../website/optimize/seo.rst:345 +msgid "" +"Note that any dynamic component of an URL can be reduced to its ID. As an " +"example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../website/optimize/seo.rst:348 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../website/optimize/seo.rst:350 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../website/optimize/seo.rst:352 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../website/optimize/seo.rst:355 +msgid "" +"This could be useful to easily get shorter version of an URL and handle " +"efficiently 301 redirects when the name of your product changes over time." +msgstr "" + +#: ../../website/optimize/seo.rst:359 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../website/optimize/seo.rst:362 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../website/optimize/seo.rst:364 +msgid "In the above example:" +msgstr "" + +#: ../../website/optimize/seo.rst:366 +msgid "Company News: is the title of the blog" +msgstr "" + +#: ../../website/optimize/seo.rst:368 +msgid "The Odoo Story: is the title of a specific blog post" +msgstr "" + +#: ../../website/optimize/seo.rst:370 +msgid "" +"When an Odoo page has a pager, the page number is set directly in the URL " +"(does not have a GET argument). This allows every page to be indexed by " +"search engines. Example:" +msgstr "" + +#: ../../website/optimize/seo.rst:374 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../website/optimize/seo.rst:377 +msgid "" +"Having the language code as fr\\_FR is not perfect in terms of SEO. Although" +" most search engines treat now \"\\_\" as a word separator, it has not " +"always been the case. We plan to improve that for Odoo 10." +msgstr "" + +#: ../../website/optimize/seo.rst:382 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../website/optimize/seo.rst:384 +msgid "" +"When the URL of a page changes (e.g. a more SEO friendly version of your " +"product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../website/optimize/seo.rst:387 +msgid "Odoo will automatically update all its links to the new URL" +msgstr "" + +#: ../../website/optimize/seo.rst:389 +msgid "" +"If external websites still points to the old URL, a 301 redirect will be " +"done to route visitors to the new website" +msgstr "" + +#: ../../website/optimize/seo.rst:392 +msgid "As an example, this URL:" +msgstr "" + +#: ../../website/optimize/seo.rst:394 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:396 +msgid "Will automatically redirect to :" +msgstr "" + +#: ../../website/optimize/seo.rst:398 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:400 +msgid "" +"In short, just change the title of a blog post or the name of a product, and" +" the changes will apply automatically everywhere in your website. The old " +"link still works for links coming from external website. (with a 301 " +"redirect to not lose the SEO link juice)" +msgstr "" + +#: ../../website/optimize/seo.rst:406 +msgid "HTTPS" +msgstr "" + +#: ../../website/optimize/seo.rst:408 +msgid "" +"As of August 2014, Google started to add a ranking boost to secure HTTPS/SSL" +" websites. So, by default all Odoo Online instances are fully based on " +"HTTPS. If the visitor accesses your website through a non HTTPS url, it gets" +" a 301 redirect to its HTTPS equivalent." +msgstr "" + +#: ../../website/optimize/seo.rst:414 +msgid "Links: nofollow strategy" +msgstr "" + +#: ../../website/optimize/seo.rst:416 +msgid "" +"Having website that links to your own page plays an important role on how " +"your page ranks in the different search engines. The more your page is " +"linked from external and quality websites, the better is it for your SEO." +msgstr "" + +#: ../../website/optimize/seo.rst:421 +msgid "Odoo follows the following strategies to manage links:" +msgstr "" + +#: ../../website/optimize/seo.rst:423 +msgid "" +"Every link you create manually when creating page in Odoo is \"dofollow\", " +"which means that this link will contribute to the SEO Juice for the linked " +"page." +msgstr "" + +#: ../../website/optimize/seo.rst:427 +msgid "" +"Every link created by a contributor (forum post, blog comment, ...) that " +"links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../website/optimize/seo.rst:430 +msgid "" +"But every link posted by a contributor that links to an external website is " +"\"nofollow\". In that way, you do not run the risk of people posting links " +"on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../website/optimize/seo.rst:435 +msgid "" +"Note that, when using the forum, contributors having a lot of Karma can be " +"trusted. In such case, their links will not have a ``rel=\"nofollow\"`` " +"attribute." +msgstr "" + +#: ../../website/optimize/seo.rst:440 +msgid "Multi-language support" +msgstr "" + +#: ../../website/optimize/seo.rst:443 +msgid "Multi-language URLs" +msgstr "" + +#: ../../website/optimize/seo.rst:445 +msgid "" +"If you run a website in multiple languages, the same content will be " +"available in different URLs, depending on the language used:" +msgstr "" + +#: ../../website/optimize/seo.rst:448 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (English version = " +"default)" +msgstr "" + +#: ../../website/optimize/seo.rst:450 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../website/optimize/seo.rst:452 +msgid "" +"In this example, fr\\_FR is the language of the page. You can even have " +"several variations of the same language: pt\\_BR (Portuguese from Brazil) , " +"pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../website/optimize/seo.rst:457 +msgid "Language annotation" +msgstr "" + +#: ../../website/optimize/seo.rst:459 +msgid "" +"To tell Google that the second URL is the French translation of the first " +"URL, Odoo will add an HTML link element in the header. In the HTML " +"section of the English version, Odoo automatically adds a link element " +"pointing to the other versions of that webpage;" +msgstr "" + +#: ../../website/optimize/seo.rst:464 +msgid "" +"" +msgstr "" + +#: ../../website/optimize/seo.rst:467 +msgid "With this approach:" +msgstr "" + +#: ../../website/optimize/seo.rst:469 +msgid "" +"Google knows the different translated versions of your page and will propose" +" the right one according to the language of the visitor searching on Google" +msgstr "" + +#: ../../website/optimize/seo.rst:473 +msgid "" +"You do not get penalized by Google if your page is not translated yet, since" +" it is not a duplicated content, but a different version of the same " +"content." +msgstr "" + +#: ../../website/optimize/seo.rst:478 +msgid "Language detection" +msgstr "" + +#: ../../website/optimize/seo.rst:480 +msgid "" +"When a visitor lands for the first time at your website (e.g. " +"yourwebsite.com/shop), his may automatically be redirected to a translated " +"version according to his browser language preference: (e.g. " +"yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../website/optimize/seo.rst:485 +msgid "" +"Odoo redirects visitors to their prefered language only the first time " +"visitors land at your website. After that, it keeps a cookie of the current " +"language to avoid any redirection." +msgstr "" + +#: ../../website/optimize/seo.rst:489 +msgid "" +"To force a visitor to stick to the default language, you can use the code of" +" the default language in your link, example: yourwebsite.com/en\\_US/shop. " +"This will always land visitors to the English version of the page, without " +"using the browser language preferences." +msgstr "" + +#: ../../website/optimize/seo.rst:496 +msgid "Meta Tags" +msgstr "" + +#: ../../website/optimize/seo.rst:499 +msgid "Titles, Keywords and Description" +msgstr "" + +#: ../../website/optimize/seo.rst:501 +msgid "" +"Every web page should define the ````, ``<description>`` and " +"``<keywords>`` meta data. These information elements are used by search " +"engines to rank and categorize your website according to a specific search " +"query. So, it is important to have titles and keywords in line with what " +"people search in Google." +msgstr "" + +#: ../../website/optimize/seo.rst:507 +msgid "" +"In order to write quality meta tags, that will boost traffic to your " +"website, Odoo provides a **Promote** tool, in the top bar of the website " +"builder. This tool will contact Google to give you information about your " +"keywords and do the matching with titles and contents in your page." +msgstr "" + +#: ../../website/optimize/seo.rst:516 +msgid "" +"If your website is in multiple languages, you can use the Promote tool for " +"every language of a single page;" +msgstr "" + +#: ../../website/optimize/seo.rst:519 +msgid "" +"In terms of SEO, content is king. Thus, blogs play an important role in your" +" content strategy. In order to help you optimize all your blog post, Odoo " +"provides a page that allows you to quickly scan the meta tags of all your " +"blog posts." +msgstr "" + +#: ../../website/optimize/seo.rst:528 +msgid "" +"This /blog page renders differently for public visitors that are not logged " +"in as website administrator. They do not get the warnings and keyword " +"information." +msgstr "" + +#: ../../website/optimize/seo.rst:533 +msgid "Sitemap" +msgstr "" + +#: ../../website/optimize/seo.rst:535 +msgid "" +"Odoo will generate a ``/sitemap.xml`` file automatically for you. For " +"performance reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../website/optimize/seo.rst:538 +msgid "" +"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you " +"have a lot of pages, Odoo will automatically create a Sitemap Index file, " +"respecting the `sitemaps.org protocol " +"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 " +"chunks per file." +msgstr "" + +#: ../../website/optimize/seo.rst:544 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../website/optimize/seo.rst:546 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../website/optimize/seo.rst:548 +msgid "" +"``<lastmod>`` : last modification date of the resource, computed " +"automatically based on related object. For a page related to a product, this" +" could be the last modification date of the product or the page" +msgstr "" + +#: ../../website/optimize/seo.rst:553 +msgid "" +"``<priority>`` : modules may implement their own priority algorithm based on" +" their content (example: a forum might assign a priority based on the number" +" of votes on a specific post). The priority of a static page is defined by " +"it's priority field, which is normalized. (16 is the default)" +msgstr "" + +#: ../../website/optimize/seo.rst:560 +msgid "Structured Data Markup" +msgstr "" + +#: ../../website/optimize/seo.rst:562 +msgid "" +"Structured Data Markup is used to generate Rich Snippets in search engine " +"results. It is a way for website owners to send structured data to search " +"engine robots; helping them to understand your content and create well-" +"presented search results." +msgstr "" + +#: ../../website/optimize/seo.rst:567 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../website/optimize/seo.rst:570 +msgid "" +"Odoo implements micro data as defined in the `schema.org " +"<http://schema.org>`__ specification for events, eCommerce products, forum " +"posts and contact addresses. This allows your product pages to be displayed " +"in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../website/optimize/seo.rst:580 +msgid "robots.txt" +msgstr "" + +#: ../../website/optimize/seo.rst:582 +msgid "" +"Odoo automatically creates a ``/robots.txt`` file for your website. Its " +"content is:" +msgstr "" + +#: ../../website/optimize/seo.rst:585 +msgid "User-agent: \\*" +msgstr "" + +#: ../../website/optimize/seo.rst:587 +msgid "Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../website/optimize/seo.rst:590 +msgid "Content is king" +msgstr "" + +#: ../../website/optimize/seo.rst:592 +msgid "" +"When it comes to SEO, content is usually king. Odoo provides several modules" +" to help you build your contents on your website:" +msgstr "" + +#: ../../website/optimize/seo.rst:595 +msgid "" +"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their " +"content is automatically indexed on the web page. Example: " +"`https://www.odoo.com/slides/public-channel-1 <https://www.odoo.com/slides" +"/public-channel-1>`__" +msgstr "" + +#: ../../website/optimize/seo.rst:599 +msgid "" +"**Odoo Forum**: let your community create contents for you. Example: " +"`https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of" +" Odoo.com landing pages)" +msgstr "" + +#: ../../website/optimize/seo.rst:603 +msgid "" +"**Odoo Mailing List Archive**: publish mailing list archives on your " +"website. Example: `https://www.odoo.com/groups/community-59 " +"<https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)" +msgstr "" + +#: ../../website/optimize/seo.rst:608 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../website/optimize/seo.rst:611 +msgid "" +"The 404 page is a regular page, that you can edit like any other page in " +"Odoo. That way, you can build a great 404 page to redirect to the top " +"content of your website." +msgstr "" + +#: ../../website/optimize/seo.rst:616 +msgid "Social Features" +msgstr "" + +#: ../../website/optimize/seo.rst:619 +msgid "Twitter Cards" +msgstr "" + +#: ../../website/optimize/seo.rst:621 +msgid "" +"Odoo does not implement twitter cards yet. It will be done for the next " +"version." +msgstr "" + +#: ../../website/optimize/seo.rst:625 +msgid "Social Network" +msgstr "" + +#: ../../website/optimize/seo.rst:627 +msgid "" +"Odoo allows to link all your social network accounts in your website. All " +"you have to do is to refer all your accounts in the **Settings** menu of the" +" **Website Admin** application." +msgstr "" + +#: ../../website/optimize/seo.rst:632 +msgid "Test Your Website" +msgstr "" + +#: ../../website/optimize/seo.rst:634 +msgid "" +"You can compare how your website rank, in terms of SEO, against Odoo using " +"WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__" +msgstr "" + +#: ../../website/publish.rst:3 +msgid "Publish" +msgstr "" + +#: ../../website/publish/domain_name.rst:3 +msgid "How to use my own domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:5 +msgid "" +"By default, your Odoo Online instance and website have a *.odoo.com* domain " +"name, for both the URL and the emails. But you can change to a custom one " +"(e.g. www.yourcompany.com)." +msgstr "" + +#: ../../website/publish/domain_name.rst:10 +msgid "What is a good domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:11 +msgid "" +"Your website address is as important to your branding as the name of your " +"business or organization, so put some thought into changing it for a proper " +"domain. Here are some tips:" +msgstr "" + +#: ../../website/publish/domain_name.rst:15 +msgid "Simple and obvious" +msgstr "" + +#: ../../website/publish/domain_name.rst:16 +msgid "Easy to remember and spell" +msgstr "" + +#: ../../website/publish/domain_name.rst:17 +msgid "The shorter the better" +msgstr "" + +#: ../../website/publish/domain_name.rst:18 +msgid "Avoid special characters" +msgstr "" + +#: ../../website/publish/domain_name.rst:19 +msgid "Aim for a .com and/or your country extension" +msgstr "" + +#: ../../website/publish/domain_name.rst:21 +msgid "" +"Read more: `How to Choose a Domain Name for Maximum SEO " +"<https://www.searchenginejournal.com/choose-a-domain-name-maximum-" +"seo/158951/>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:24 +msgid "How to buy a domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:25 +msgid "Buy your domain name at a popular registrar:" +msgstr "" + +#: ../../website/publish/domain_name.rst:27 +msgid "`GoDaddy <https://www.godaddy.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:28 +msgid "`Namecheap <https://www.namecheap.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:29 +msgid "`OVH <https://www.ovh.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:31 +msgid "" +"Steps to buy a domain name are pretty much straight forward. In case of " +"issue, check out those easy tutorials:" +msgstr "" + +#: ../../website/publish/domain_name.rst:34 +msgid "`GoDaddy <https://roadtoblogging.com/buy-domain-name-from-godaddy>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:35 +msgid "" +"`Namecheap <https://www.loudtips.com/buy-domain-name-hosting-namecheap//>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:37 +msgid "" +"Feel free to buy an email server to have email addresses using your domain " +"name. However don't buy any extra service to create or host your website. " +"This is Odoo's job!" +msgstr "" + +#: ../../website/publish/domain_name.rst:42 +msgid "How to apply my domain name to my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:43 +msgid "" +"First let's authorize the redirection (yourcompany.com -> " +"yourcompany.odoo.com):" +msgstr "" + +#: ../../website/publish/domain_name.rst:45 +msgid "Open your Odoo.com account from your homepage." +msgstr "" + +#: ../../website/publish/domain_name.rst:50 +msgid "Go to the *Manage Databases* page." +msgstr "" + +#: ../../website/publish/domain_name.rst:55 +msgid "" +"Click on *Domains* to the right of the database you would like to redirect." +msgstr "" + +#: ../../website/publish/domain_name.rst:60 +msgid "" +"A database domain prompt will appear. Enter your custom domain (e.g. " +"www.yourcompany.com)." +msgstr "" + +#: ../../website/publish/domain_name.rst:67 +msgid "" +"We can now apply the redirection from your domain name's manager account:" +msgstr "" + +#: ../../website/publish/domain_name.rst:69 +msgid "Log in to your account and search for the DNS Zones management page." +msgstr "" + +#: ../../website/publish/domain_name.rst:71 +msgid "" +"Create a CNAME record *www.yourdomain.com* pointing to *mywebsite.odoo.com*." +" If you want to use the naked domain (e.g. yourdomain.com), you need to " +"redirect *yourdomain.com* to *www.yourdomain.com*." +msgstr "" + +#: ../../website/publish/domain_name.rst:75 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../website/publish/domain_name.rst:77 +msgid "`GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:78 +msgid "" +"`Namecheap " +"<https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-" +"can-i-set-up-a-cname-record-for-my-domain>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:79 +msgid "" +"`OVH " +"<https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:82 +msgid "How to enable SSL (HTTPS) for my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:84 +msgid "" +"To enable SSL, please use a third-party CDN service provider such as " +"CloudFlare.com." +msgstr "" + +#: ../../website/publish/domain_name.rst:90 +msgid ":doc:`../../discuss/email_servers`" +msgstr "" + +#: ../../website/publish/translate.rst:3 +msgid "How to translate my website" +msgstr "" + +#: ../../website/publish/translate.rst:6 +msgid "Overview" +msgstr "" + +#: ../../website/publish/translate.rst:8 +msgid "" +"In addition to creating great modern websites, Odoo gives you the " +"possibility to translate it in different languages." +msgstr "" + +#: ../../website/publish/translate.rst:12 +msgid "Process" +msgstr "" + +#: ../../website/publish/translate.rst:14 +msgid "" +"Once your website is created, you have the opportunity to translate it in as" +" many different languages as you want." +msgstr "" + +#: ../../website/publish/translate.rst:17 +msgid "" +"There are two ways to translate your website, you can do it manually or " +"automatically with the Gengo App. If you want to do it automatically, go to " +"the **App** module and Install **Automated translations through Gengo Api** " +"and **Website Gengo Translator**. If you want to do it manually, don't " +"install anything, and follow the next step." +msgstr "" + +#: ../../website/publish/translate.rst:23 +msgid "" +"Now go to your website. On the bottom right corner of the page, click on " +"**Add a language**." +msgstr "" + +#: ../../website/publish/translate.rst:29 +msgid "" +"Choose the language in which you want to translate your website and then " +"click on **Load.**" +msgstr "" + +#: ../../website/publish/translate.rst:35 +msgid "" +"You will see that Now, next to English there is also French, which means " +"that the page for the translation has been created. You can also see that " +"some of the text has been translated automatically." +msgstr "" + +#: ../../website/publish/translate.rst:42 +msgid "" +"To translate the content of the website, click on **Translate** (here " +"**Traduire** since we want to translate the website in French)." +msgstr "" + +#: ../../website/publish/translate.rst:45 +msgid "" +"There, if you have installed the Gengo Translator, You will see that next to" +" the **Translate** button you also have a button **Translate " +"automatically**. Once you click on that button, you will be asked some " +"information on your account. If you don't have an account yet, go to " +"`*https://gengo.com/auth/form/login/* " +"<https://gengo.com/auth/form/login/>`__ in order to create one. You need to " +"ask for a public key and a private key." +msgstr "" + +#: ../../website/publish/translate.rst:53 +msgid "" +"The content you wish to translate will then be translated automatically." +msgstr "" + +#: ../../website/publish/translate.rst:58 +msgid "" +"Now you can see that most of the content is highlighted in yellow or in " +"green. The yellow represents the content that you have to translate by " +"yourself. The green represents the content that has already been translated " +"automatically." +msgstr "" diff --git a/locale/sources/accounting.pot b/locale/sources/accounting.pot index 69295a513..9244876e5 100644 --- a/locale/sources/accounting.pot +++ b/locale/sources/accounting.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -79,7 +79,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:23 #: ../../accounting/receivables/getting_paid/automated_followups.rst:31 msgid "Configuration" msgstr "" @@ -574,7 +573,6 @@ msgstr "" #: ../../accounting/bank/misc/batch.rst:124 #: ../../accounting/payables/pay/sepa.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:134 msgid "Troubleshooting" msgstr "" @@ -1067,6 +1065,11 @@ msgstr "" msgid "In the tab Journal Entries, the Default Debit and Credit Account can be configured as well as the currency of the journal" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1083,83 +1086,164 @@ msgstr "" msgid "Select 'General' for miscellaneous operations journals." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Company related to this journal" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The journal entries of this journal will be named using this prefix." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Check this box if you don't want to share the same sequence for invoices and refunds made from this journal" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "This field contains the information related to the numbering of the journal entries of this journal." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "This field contains the information related to the numbering of the refund entries of this journal." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for debit amount" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for credit amount" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The currency used to enter statement" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Means of payment for collecting money. Odoo modules offer various payments handling facilities, but you can always use the 'Manual' payment method in order to manage payments outside of the software." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Means of payment for sending money. Odoo modules offer various payments handling facilities, but you can always use the 'Manual' payment method in order to manage payments outside of the software." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "If this box is checked, the system will try to group the accounting lines when generating them from invoices." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Used to register a profit when the ending balance of a cash register differs from what the system computes" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Used to register a loss when the ending balance of a cash register differs from what the system computes" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Whether this journal should be displayed on the dashboard or not" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Technical feature used to know whether check printing was enabled as payment method." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Checks numbering sequence." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 #: ../../accounting/payables/pay/check.rst:0 msgid "Check this option if your pre-printed checks are not numbered." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Sequence number of the next printed check." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Check this box if this journal define a payment method that can be used in a point of sale." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "This field depicts the maximum difference allowed between the ending balance and the theoretical cash when closing a session, for non-POS managers. If this maximum is reached, the user will have an error message at the closing of his session saying that he needs to contact his manager." msgstr "" @@ -1301,6 +1385,10 @@ msgstr "" msgid "Explanation of the fields:" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "When an asset is created, the status is 'Draft'." msgstr "" @@ -1313,22 +1401,42 @@ msgstr "" msgid "You can manually close an asset when the depreciation is over. If the last line of depreciation is posted, the asset automatically goes in that status." msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Category of asset" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Date of asset" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Gross value of asset" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "It is the amount you plan to have that you cannot depreciate." msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the amount of depreciation lines." msgstr "" @@ -1341,6 +1449,10 @@ msgstr "" msgid "* Degressive: Calculated on basis of: Residual Value * Degressive Factor" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the dates and number of depreciation lines." msgstr "" @@ -1353,14 +1465,26 @@ msgstr "" msgid "* Ending Date: Choose the time between 2 depreciations and the date the depreciations won't go beyond." msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Indicates that the first depreciation entry for this asset have to be done from the purchase date instead of the first January / Start date of fiscal year" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The number of depreciations needed to depreciate your asset" msgstr "" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The amount of time between two depreciations, in months" msgstr "" @@ -2036,6 +2160,9 @@ msgstr "" #: ../../accounting/others/analytic/usage.rst:64 #: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:48 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:62 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:74 #: ../../accounting/overview/process_overview/customer_invoice.rst:107 #: ../../accounting/overview/process_overview/customer_invoice.rst:128 msgid "**Debit**" @@ -2043,6 +2170,9 @@ msgstr "" #: ../../accounting/others/analytic/usage.rst:64 #: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:48 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:62 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:74 #: ../../accounting/overview/process_overview/customer_invoice.rst:107 #: ../../accounting/overview/process_overview/customer_invoice.rst:128 msgid "**Credit**" @@ -2489,18 +2619,34 @@ msgstr "" msgid "Account Type is used for information purpose, to generate country-specific legal reports, and set the rules to close a fiscal year and generate opening entries." msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Optional tags you may want to assign for custom reporting" msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Forces all moves for this account to have this account currency." msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "The 'Internal Type' is used for features available on different types of accounts: liquidity type is for cash or bank accounts, payable/receivable is for vendor/customer accounts." msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Check this box if this account allows invoices & payments matching of journal items." msgstr "" @@ -3735,6 +3881,86 @@ msgstr "" msgid ":doc:`B2B_B2C`" msgstr "" +#: ../../accounting/others/taxes/cash_basis_taxes.rst:3 +msgid "How to manage cash basis taxes" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:5 +msgid "The cash basis taxes are due when the payment has been done and not at the validation of the invoice (as it is the case with standard taxes). Reporting your income and expenses to the administration based on the cash basis method is legal in some countries and under some conditions." +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:10 +msgid "Example : You sell a product in the 1st quarter of your fiscal year and receive the payment the 2nd quarter of your fiscal year. Based on the cash basis method, the tax you have to pay to the administration is due for the 2nd quarter." +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:16 +msgid "How to configure cash basis taxes ?" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:18 +msgid "You first have to activate the setting in :menuselection:`Accounting --> Configuration --> Settings --> Allow Tax Cash Basis`. You will be asked to define the Tax Cash Basis Journal." +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:27 +msgid "Once this is done, you can configure your taxes in :menuselection:`Accounting --> Configuration --> Taxes`. You can open a tax and in the *Advanced Options* tab you will see the checkbox *Use Cash Basis*. You will then have to define the *Tax Received Account*." +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:39 +msgid "What is the impact of cash basis taxes in my accounting ?" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:41 +msgid "Let’s take an example. You make a sale of $100 with a 15% cash basis tax. When you validate the customer invoice, the following entry is created in your accounting:" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:46 +msgid "Customer Invoices Journal" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:50 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:66 +msgid "Receivables $115" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:52 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:76 +msgid "Tax Account $15" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:54 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:80 +#: ../../accounting/others/taxes/cash_basis_taxes.rst:82 +msgid "Income Account $100" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:57 +msgid "A few days later, you receive the payment:" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:60 +msgid "Bank Journal" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:64 +msgid "Bank $115" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:69 +msgid "When you reconcile the invoice and the payment, this entry is generated:" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:72 +msgid "Tax Cash Basis Journal" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:78 +msgid "Tax Received Account $15" +msgstr "" + +#: ../../accounting/others/taxes/cash_basis_taxes.rst:86 +msgid "The two journal items created in the Income Account are neutral but they are needed to insure correct tax reports in Odoo." +msgstr "" + #: ../../accounting/others/taxes/create.rst:3 msgid "How to create new taxes" msgstr "" @@ -5589,18 +5815,34 @@ msgstr "" msgid "Explanation of the fields of the payment screen:" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used for usability purposes" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used to hide the payment method if the selected journal has only one available which is 'manual'" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used to adapt the interface to the payment type selected." msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "The selected journal is configured to print check numbers. If your pre-printed check paper already has numbers or if the current numbering is wrong, you can change it in the journal configuration page." msgstr "" @@ -7109,7 +7351,7 @@ msgid "**Default credit account**: Credit cards" msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:50 -msgid "Once it's done, don't forget to set the \"Credit cards\" account as \"Allow Reconciliation\"." +msgid "The account type should be \"Credit Card\". Once it's done, don't forget to set the \"Credit cards\" account as \"Allow Reconciliation\"." msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:57 @@ -7189,7 +7431,7 @@ msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:167 #: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`paypal`" +msgid ":doc:`../../bank/feeds/paypal`" msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:169 @@ -7357,168 +7599,6 @@ msgstr "" msgid "You can get the DSO of your company from the Executive Summary report under Reporting (check the KPI average debtors days)." msgstr "" -#: ../../accounting/receivables/customer_payments/paypal.rst:3 -msgid "How to accept paypal payments on invoices?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:5 -msgid "The \"Paypal Payment Acquirer\" module allows you to accept payments via paypal, for your sales orders, invoices, or online orders. As paypal accepts payments through credit cards (VISA, Mastercard, …), you will be able to process most payment methods." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:10 -msgid "Paypal support two modes:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:12 -msgid "Paypal Merchant Account: the user is redirected to paypal to do the payment (either with a credit card or a paypal account)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:15 -msgid "PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to paypal and the payment can be done in the background. This method is mostly used for subscription businesses where you need to charge your customers periodically." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:20 -msgid "As of today, Odoo only support the normal Paypal Merchant Account." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:26 -msgid "Install the \"PayPal Payment Acquirer\" module" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:28 -msgid "Start by installing the **PayPal Payment Acquirer** module." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:30 -msgid "Once the module is installed, you should see a new payment acquirer in the Setting application, menu \"Payment Acquirers\"." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:36 -msgid "By default, Paypal is configured to work in a test environment, out-of-the-box. It means you can already test the full order to payment flow with the paypal sandbox, without having to configure the next steps." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:42 -msgid "Creating and configuring a PayPal merchant account" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:45 -msgid "Create a basic Paypal account" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:47 -msgid "Existing or newly created Personal Paypal account can be used." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:49 -msgid "Or upgrade your account to Business account (merchant) if needed" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:55 -msgid "Paypal Account Summary page" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:58 -msgid "Paypal Configuration" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:60 -msgid "Access \"Seller preferences\" menu from `PayPal website <https://www.paypal.com/myaccount/home>`__" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:66 -msgid "Access \"Website preferences\" and configure Auto Return (Payment Data Transfer must be left to Off)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:69 -msgid "**Database name**: yourcompany" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:70 -#: ../../accounting/receivables/customer_payments/paypal.rst:88 -msgid "**Website URL**: https://yourcompany.odoo.com/" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:71 -msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:76 -msgid "These settings will redirect your buyer to your web confirmation page." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:80 -msgid "Access and edit Instant payment notifications settings - IPN" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:85 -msgid "Example" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:87 -msgid "**Database name**: \"yourcompany\"" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:89 -msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:91 -msgid "Verify that your Notify URL uses the correct protocol (HTTP / HTTPS). If you use the odoo.com domain, we advise you to use HTTPS." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:94 -msgid "Set the encoding to UTF-8 from the menu :menuselection:`Settings --> Language Encoding --> More Options --> More selling tools`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:103 -msgid "Record your Merchant Paypal ID (personal or business account both will have it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> Account Options`." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:111 -msgid "If you want your customers to be able to pay through Paypal while not having a Paypal account- following setting \"Paypal Account Optional\" needs to be set to **ON**. All users will be able to choose Credit/debit card payment option - Paypal account not required." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:120 -msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:122 -msgid ":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:124 -msgid "**Paypal Email ID**: your paypal account email address" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:126 -msgid "**Paypal Merchant ID**: ID retrieved at previous step" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:136 -msgid "If your eCommerce customer gets this Error Message after completing Paypal payment instead of being redirected to your database:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:142 -msgid "Verify the settings you have `configured in Paypal <WebsitePreferences_>`_:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:144 -msgid "Auto Return should be on (the value can be quite generic, like <odoo_instance>/shop/confirmation; the correct URL will be set for each transaction)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:148 -msgid "Payment Data Transfer should be off" -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:150 -msgid "On-premise databases must be accessible through classic HTTP/HTTPS ports (80/443) for Paypal to work correctly, usually through a reverse proxy. Contact your integrating partner if you are unsure this is the case. Databases hosted on odoo.com are already configured correctly." -msgstr "" - -#: ../../accounting/receivables/customer_payments/paypal.rst:157 -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" -msgstr "" - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "" @@ -7619,6 +7699,10 @@ msgstr "" msgid "When making an internal transfer from one bank account to another, select the bank you want to apply the transfer from in the dashboard, and in the register payments screen, you select the transfer to account. Do not go through this process again in the other bank account or else you will end up with two journal entries for the same transaction." msgstr "" +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr "" + #: ../../accounting/receivables/getting_paid.rst:3 msgid "How to get paid?" msgstr "" diff --git a/locale/sources/applications.pot b/locale/sources/applications.pot index 0c57ced06..42b33aed2 100644 --- a/locale/sources/applications.pot +++ b/locale/sources/applications.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/crm.pot b/locale/sources/crm.pot index 9b8c981b5..365344af7 100644 --- a/locale/sources/crm.pot +++ b/locale/sources/crm.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -25,35 +25,71 @@ msgid "Calendar" msgstr "" #: ../../crm/calendar/google_calendar_credentials.rst:3 -msgid "How to synchronize your calendar with Google Calendar" +msgid "How to synchronize your Odoo Calendar with Google Calendar" msgstr "" #: ../../crm/calendar/google_calendar_credentials.rst:5 -msgid "Connect on your google account and go to `https://console.developers.google.com/ <https://console.developers.google.com/>`_." +msgid "Odoo is perfectly integrated with Google Calendar so that you can see & manage your meetings from both platforms (updates go through both directions)." msgstr "" -#: ../../crm/calendar/google_calendar_credentials.rst:7 -msgid "Click on **Create a project...** and enter a project name and change your id if you want. Don't forget to accept the Terms of Services" +#: ../../crm/calendar/google_calendar_credentials.rst:10 +msgid "Setup in Google" msgstr "" -#: ../../crm/calendar/google_calendar_credentials.rst:13 -msgid "In the menu on left side, select the sub menu APIs (from menu APIs and auth) and click on 'Calendar API'. Activate the Calendar API by clicking on the blue button 'Enable API'. When it's done, the Calendar API overview will be available" +#: ../../crm/calendar/google_calendar_credentials.rst:11 +msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Google Calendar API credentials. Log in with your Google account." msgstr "" -#: ../../crm/calendar/google_calendar_credentials.rst:26 -msgid "In the menu on left side, select the sub menu 'Credentials' (from menu APIs and auth) and click on button 'Create new Client ID'" +#: ../../crm/calendar/google_calendar_credentials.rst:14 +msgid "Choose *Calendar API*." msgstr "" -#: ../../crm/calendar/google_calendar_credentials.rst:32 -msgid "Check that the Application type is set on 'Web Application', then click on 'Configure consent screen'. Specify an email address and a product name, then save." +#: ../../crm/calendar/google_calendar_credentials.rst:19 +msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:25 +msgid "Enable the API." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:30 +msgid "Create credentials to use in Odoo." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:35 +msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data." msgstr "" #: ../../crm/calendar/google_calendar_credentials.rst:41 -msgid "You should now configure the allowed pages on which you will be redirected. To do it, you need to complete the field \"Authorized redirect URI\" and set as value (your own domain followed by '/google_account/authentication'): ==> http://mydomain.odoo.com/google_account/authentication You can now click on 'Create Client ID'" +msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'." msgstr "" -#: ../../crm/calendar/google_calendar_credentials.rst:48 -msgid "Once done, you will have the both informations (Client ID and Client Secret) that you need to insert in the 2 fields below!" +#: ../../crm/calendar/google_calendar_credentials.rst:50 +msgid "Go through the Consent Screen step by entering a product name (e.g. Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:55 +msgid "Finally you are provided with your **Client ID**. Go to *Credentials* to get the **Client secret** as well. You will need both of them in Odoo." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:62 +msgid "Setup in Odoo" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:64 +msgid "Install **Google Calendar** app." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:69 +msgid "Go to :menuselection:`Settings --> General Settings` and enter your credentials in Google Calendar option." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:75 +msgid "The setup is now ready. Open your Odoo Calendar and sync with Google. The first time you do it you are redirected to Google to authorize the connection. Once back in Odoo, click the sync button again. You can click it whenever you want to synchronize your calendar." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:83 +msgid "As of now you no longer have excuses to miss a meeting!" msgstr "" #: ../../crm/leads.rst:3 @@ -230,22 +266,22 @@ msgid "Go to :menuselection:`Sales --> Leads` and click the **Create** button." msgstr "" #: ../../crm/leads/generate/manual.rst:33 -msgid "From the contact form, provide all the details in your possession (contact name, email, phone, address, etc.) as well as some additional information in the **Internal notes** field. You can also link the lead to an existing company by editing the**Customer** field. Click on save and the contact will be visible as a lead in your pipeline ." +msgid "From the contact form, provide all the details in your possession (contact name, email, phone, address, etc.) as well as some additional information in the **Internal notes** field." msgstr "" -#: ../../crm/leads/generate/manual.rst:41 +#: ../../crm/leads/generate/manual.rst:39 msgid "your lead can be directly handed over to specific sales team and salesperson by clicking on **Convert to Opportunity** on the upper left corner of the screen." msgstr "" -#: ../../crm/leads/generate/manual.rst:45 +#: ../../crm/leads/generate/manual.rst:43 msgid "Create a new opportunity" msgstr "" -#: ../../crm/leads/generate/manual.rst:47 +#: ../../crm/leads/generate/manual.rst:45 msgid "You can also directly add a contact into a specific sales team without having to convert the lead first. On the Sales module, go to your dashboard and click on the **Pipeline** button of the desired sales team. If you don't have any sales team yet, :doc:`you need to create one first <../../salesteam/setup/create_team>`. Then, click on **Create** and fill in the contact details as shown here above. By default, the newly created opportunity will appear on the first stage of your sales pipeline." msgstr "" -#: ../../crm/leads/generate/manual.rst:55 +#: ../../crm/leads/generate/manual.rst:53 msgid "Another way to create an opportunity is by adding it directly on a specific stage. For example, if you have have spoken to Mr. Smith at a meeting and you want to send him a quotation right away, you can add his contact details on the fly directly into the **Proposition** stage. From the Kanban view of your sales team, just click on the **+** icon at the right of your stage to create the contact. The new opportunity will then pop up into the corresponding stage and you can then fill in the contact details by clicking on it." msgstr "" diff --git a/locale/sources/db_management.pot b/locale/sources/db_management.pot index 6baf2ec4f..f5834cbc3 100644 --- a/locale/sources/db_management.pot +++ b/locale/sources/db_management.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -313,7 +313,7 @@ msgid "Uninstalling Apps" msgstr "" #: ../../db_management/documentation.rst:73 -msgid "Make sure you first test what you are about to do on a :ref:`duplicate <duplicate>` of your database before making any changes (*especially* installing/uninstalling apps)." +msgid "Make sure you first test what you are about to do on a :ref:`duplicate <duplicate_online>` of your database before making any changes (*especially* installing/uninstalling apps)." msgstr "" #: ../../db_management/documentation.rst:77 diff --git a/locale/sources/discuss.pot b/locale/sources/discuss.pot index 5beb64c9b..b0aa8fdb1 100644 --- a/locale/sources/discuss.pot +++ b/locale/sources/discuss.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -21,7 +21,7 @@ msgid "Discuss" msgstr "" #: ../../discuss/email_servers.rst:3 -msgid "How to use my own email servers to send and receive messages in Odoo" +msgid "How to use my own email servers to send and receive email in Odoo" msgstr "" #: ../../discuss/email_servers.rst:6 @@ -29,95 +29,155 @@ msgid "When is it needed" msgstr "" #: ../../discuss/email_servers.rst:7 -msgid "You need it if you use Odoo Community or Enterprise." +msgid "Using your own email servers is required to send and receive messages in Odoo Community or Enterprise. Odoo Online embeds an out-of-box email solution that works straight away. However you can still use your own email servers with the online edition. Some insights are provided here below." msgstr "" -#: ../../discuss/email_servers.rst:10 -msgid "What if I use Odoo Online" -msgstr "" - -#: ../../discuss/email_servers.rst:11 -msgid "You are done! Odoo Online comes up with an embedded and ready-to-use email server (*@yourcompany.odoo.com*). We recommend to keep this default setting as is as it is really convenient." +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" msgstr "" #: ../../discuss/email_servers.rst:15 -msgid "Indeed, while it is branded by Odoo, the visible source of any message sent from Odoo will be your personal email address (your Odoo login). Your contacts will therefore trust your messages." -msgstr "" - -#: ../../discuss/email_servers.rst:20 -msgid "How does it work when a contact replies to an email sent from Odoo" +msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers* (watch out: this checkbox only shows up after Odoo 10). Then, go through the following steps." msgstr "" #: ../../discuss/email_servers.rst:21 -msgid "Default reply-to is a generic address used to automatically route any incoming email to the discussion thread of the origin business object (opportunity, order, task, etc.) and to the inbox of all its followers. By default this address is \"catchall@\" but it can be changed. Thanks to it, you get a perfect message thread in Odoo and you don't pollute your external email box with Odoo-related topics." +msgid "Office 365 doesn't allow external hosts like Odoo. Consequently you can't use Office 365 email servers to send or receive messages in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:29 -msgid "How to use my own email servers" -msgstr "" - -#: ../../discuss/email_servers.rst:30 -msgid "You need to be a system admin to set this up. Go to :menuselection:`Settings --> General Settings` and check *External Email Servers* (watch out: this checkbox only shows up after Odoo 10). Then, go through the following steps." -msgstr "" - -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/email_servers.rst:26 msgid "Set an outgoing email server for outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:37 +#: ../../discuss/email_servers.rst:27 msgid "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, etc.) as well as your admin credentials. Once all the information has been filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:45 +#: ../../discuss/email_servers.rst:35 msgid "Set an incoming email server for inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:46 +#: ../../discuss/email_servers.rst:36 msgid "Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:53 +#: ../../discuss/email_servers.rst:43 msgid "By default inbound messages are fetched every 5 minutes. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/email_servers.rst:59 +#: ../../discuss/email_servers.rst:49 msgid "Set the domain name" msgstr "" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/email_servers.rst:50 msgid "Enter the domain name of your email servers (e.g. mycompany.com) in General Settings." msgstr "" -#: ../../discuss/email_servers.rst:67 +#: ../../discuss/email_servers.rst:57 msgid "Create a catchall address" msgstr "" -#: ../../discuss/email_servers.rst:68 +#: ../../discuss/email_servers.rst:58 +msgid "When a contact replies to an email sent from Odoo, the *reply-to* address is a generic address used to route the reply to the right discussion thread in Odoo (opportunity, order, task, etc.) and to the inbox of all its followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 msgid "Create a catchall address in your email server settings. We advise you to use \"catchall@\" so that everything works out straight away. If you want to use another alias, you have extra steps in Odoo:" msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/email_servers.rst:67 msgid "Activate the developer mode from your Settings Dashboard." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/email_servers.rst:72 msgid "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and enter your custom catchall alias in *mail.catchall.alias*." msgstr "" -#: ../../discuss/email_servers.rst:84 +#: ../../discuss/email_servers.rst:79 msgid "You can edit the email alias used for bounced messages the same way." msgstr "" -#: ../../discuss/email_servers.rst:87 -msgid "How to perfectly combine Odoo Discuss and my traditional email tool" +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" msgstr "" -#: ../../discuss/email_servers.rst:88 -msgid "Odoo Discuss is a perfect tool to send and read messages related to business objects. But it doesn't aim to replace a full-featured email software (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of both systems without mingling them: What is related to Odoo business objects or applications goes into Odoo; What is not stays into your external email boxes." +#: ../../discuss/email_servers.rst:83 +msgid "Odoo Online comes up with an embedded and ready-to-use email server (*@yourcompany.odoo.com*). We recommend to keep this default setting as it is really convenient. Indeed, while it is Odoo-labelled, the visible source of any message sent from Odoo will be your personal email address (your Odoo login). Your contacts will therefore trust your messages." msgstr "" -#: ../../discuss/email_servers.rst:95 -msgid "To do so, create specific email aliases to use in Odoo (to generate leads or opportunities, helpdesk tickets, etc.). If you take an email alias already used for messaging outside of Odoo, incoming messages will land into both systems. This will negatively impact your productivity when it comes to process them." +#: ../../discuss/email_servers.rst:90 +msgid "You can still use your own email servers if you want your contacts to see your historic email address when they reply to your messages or if you want to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "[Recommended] **Use a catchall redirection** (your server -> Odoo server) to receive emails in Odoo in real time thanks to the Odoo email server. Create a catchall address in your email server settings. Then apply following redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "**Use a catchall mailbox** to exclusively use your own email server. That way you can also manage your email server reputation (blacklisting, etc). However, incoming messages are fetched from the email server thanks to a cron running every hour. This is the shortest time lap for crons in Online instances. If you opt for this solution, simply follow the procedure of above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "Sender Policy Framework (SPF) is an email-validation system that checks that incoming mail from a domain comes from a host authorized by that domain's administrator. Such a security system is used in most email servers. If you don't comply with it, your emails sent from Odoo will be likely flagged as spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "To be SPF-compliant, you need to authorize Odoo as a sending host in your domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "If no TXT record is set, create one with following definition: v=spf1 include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 +msgid "Odoo Discuss is a perfect tool to send and read messages related to business documents. However it doesn't aim to replace a full-featured email solution (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of both systems without mingling them: What is related to Odoo business objects or applications goes into Odoo; What is not can be managed into your external email box." +msgstr "" + +#: ../../discuss/email_servers.rst:150 +msgid "To do so, create specific email aliases to use in Odoo (to generate leads or opportunities, helpdesk tickets, etc.). If you take an email alias already used for messaging outside of Odoo, incoming messages will land into both systems. This will negatively impact your productivity." msgstr "" #: ../../discuss/mail_twitter.rst:3 diff --git a/locale/sources/ecommerce.pot b/locale/sources/ecommerce.pot index b1c26b510..beae6c4ba 100644 --- a/locale/sources/ecommerce.pot +++ b/locale/sources/ecommerce.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -165,94 +165,94 @@ msgid "How to manage product variants" msgstr "" #: ../../ecommerce/managing_products/variants.rst:5 -msgid "Product variants are used to offer variations of the same product to your customers on the products page. For example, the customer chooses a T-shirt and then selects its size and color." -msgstr "" - -#: ../../ecommerce/managing_products/variants.rst:13 -msgid "How to create attributes & variants" +msgid "Product variants are used to offer variations of the same product to your customers on the products page. For example, the customer chooses a T-shirt and then selects its size and color. In the example below, the customer chooses a phone, and then selects the memory; color and Wi-Fi band from the available options." msgstr "" #: ../../ecommerce/managing_products/variants.rst:15 +msgid "How to create attributes & variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:17 msgid "Turn on *Products can have several attributes, defining variants (Example: size, color,...)* in :menuselection:`Sales --> Settings`." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:18 +#: ../../ecommerce/managing_products/variants.rst:20 msgid "Select a product from the Products list, go to the *Variants* tab." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:20 +#: ../../ecommerce/managing_products/variants.rst:22 msgid "Add as many attributes as you need from 3 different types: radio buttons, drop-down menu or color buttons. You get several variants as soon as there are 2 values for 1 attribute." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:28 +#: ../../ecommerce/managing_products/variants.rst:30 msgid "How to edit variants" msgstr "" -#: ../../ecommerce/managing_products/variants.rst:30 +#: ../../ecommerce/managing_products/variants.rst:32 msgid "See all the variants from the product template detail form." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:38 +#: ../../ecommerce/managing_products/variants.rst:40 msgid "You can edit following data:" msgstr "" -#: ../../ecommerce/managing_products/variants.rst:40 +#: ../../ecommerce/managing_products/variants.rst:42 msgid "Picture (will update in real time on the website)," msgstr "" -#: ../../ecommerce/managing_products/variants.rst:41 +#: ../../ecommerce/managing_products/variants.rst:43 msgid "Barcode," msgstr "" -#: ../../ecommerce/managing_products/variants.rst:42 +#: ../../ecommerce/managing_products/variants.rst:44 msgid "Internal Reference (SKU #)," msgstr "" -#: ../../ecommerce/managing_products/variants.rst:43 +#: ../../ecommerce/managing_products/variants.rst:45 msgid "Volume," msgstr "" -#: ../../ecommerce/managing_products/variants.rst:44 +#: ../../ecommerce/managing_products/variants.rst:46 msgid "Weight," msgstr "" -#: ../../ecommerce/managing_products/variants.rst:45 +#: ../../ecommerce/managing_products/variants.rst:47 msgid "Active (available in quotes & website)." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:48 +#: ../../ecommerce/managing_products/variants.rst:50 msgid "Both the Barcode and the Internal Reference are variant-specific. You need to populate them once the variants generated." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:52 +#: ../../ecommerce/managing_products/variants.rst:54 msgid "See and edit all the variants from :menuselection:`Sales --> Sales --> Product Variants` as well. This might be quicker if you manage lots of variants." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:56 +#: ../../ecommerce/managing_products/variants.rst:58 msgid "How to set specific prices per variant" msgstr "" -#: ../../ecommerce/managing_products/variants.rst:58 +#: ../../ecommerce/managing_products/variants.rst:60 msgid "You can also set a specific public price per variant by clicking *Variant Prices* in the product detail form (action in top-left corner)." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:64 +#: ../../ecommerce/managing_products/variants.rst:66 msgid "The Price Extra is added to the product price whenever the corresponding attribute value is selected." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:74 +#: ../../ecommerce/managing_products/variants.rst:76 msgid "Pricelist formulas let you set advanced price computation methods for product variants. See :doc:`../maximizing_revenue/pricing`." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:78 +#: ../../ecommerce/managing_products/variants.rst:80 msgid "How to disable/archive variants" msgstr "" -#: ../../ecommerce/managing_products/variants.rst:80 +#: ../../ecommerce/managing_products/variants.rst:82 msgid "You can disable/archive specific variants so that they are no longer available in quotes & website (not existing in your stock, deprecated, etc.). Simply uncheck *Active* in their detail form." msgstr "" -#: ../../ecommerce/managing_products/variants.rst:86 +#: ../../ecommerce/managing_products/variants.rst:88 msgid "To retrieve such archived items, hit *Archived* on searching the variants list. You can reactivate them the same way." msgstr "" @@ -534,19 +534,19 @@ msgid "Launch my website" msgstr "" #: ../../ecommerce/shopper_experience.rst:3 -msgid "Improve shopper experience" +msgid "Get paid" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to set up payment methods" +msgid "How to get paid with payment acquirers" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:5 -msgid "To collect payments, you can either request your customers to process it manually (e.g. wire transfer) or redirect them to payment acquirers. The payment process described hereunder is common to both eCommerce and online quotations." +msgid "Odoo embeds several payment methods to get paid on eCommerce, Sales and Invoicing apps." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "Payment methods" +msgid "What are the payment methods available" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:13 @@ -554,323 +554,417 @@ msgid "Wire transfer" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:15 -msgid "Wire Transfer is the default payment method available. The aim is providing your customers with your bank details so that they can pay via their bank. This is very easy to start with but slow and inefficient process-wise. Opt for online acquirers as soon as you can!" +msgid "Wire Transfer is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own via their bank. This is very easy to start with but slow and inefficient process-wise. Opt for online acquirers as soon as you can!" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "For B2B users: you can create new manually-processed payment methods (check, purchase order, etc.) by renaming 'Wire Transfer' or duplicating it." +msgid "Payment acquirers" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:25 -msgid "Online payment acquirers" +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "Redirect your customers to payment platforms to collect money effortless and track the payment status (call-back). Odoo supports more and more platforms over time:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "Redirect your customers to payment acquirer platforms to collect money effortless. Odoo supports more and more platforms over time: Paypal, Ingenico, Authorize.net, etc. Once the payment accepted, orders are confirmed in Odoo so that the delivery & invoicing processes are triggered automatically." +msgid "`Paypal <paypal.html>`__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Custom (advanced)" +msgid "Sips" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:35 -msgid "Can be used to request payments to any payment acquirer not listed in Odoo." +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "Edit a payment method" +msgid "How to go live" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:40 -msgid "To make payment methods intuitive for your customers feel free to customize them by editing:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:42 -msgid "the name," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:44 -msgid "the picture," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:46 -msgid "the notification messages (thank you & next step, error, cancellation)." +msgid "Once the payment method ready, make it visible in the payment interface and activate the **Production** mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:48 -msgid "Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers` to do so." +msgid "How to let customers save and reuse credit cards" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:51 -msgid "Generic setup" +#: ../../ecommerce/shopper_experience/payment.rst:49 +msgid "To ease the payment of returning customers, you can let them save and reuse a credit card if they want to. If so, a payment token will be saved in Odoo. This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:53 -msgid "Review the elements here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:55 -msgid "Enter your credentials (online acquirers only)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:57 -msgid "Choose your order confirmation preference (see below)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:59 -msgid "Publish the payment method." +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "Test the payment flow in *Test* mode (default mode)." +msgid "How to debit credit cards to pay subscriptions" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:63 -msgid "Switch to *Production* mode." +#: ../../ecommerce/shopper_experience/payment.rst:62 +msgid "`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to bill services automatically on a recurring basis. Along with it, you can have an automatic debit of the customer's credit card." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:65 -msgid "Se your default payment acquirer in :menuselection:`Accounting --> Configuration --> Settings`. It will be auto-selected for your customers when they enter the payment screen." +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:69 -msgid "Rely on the documentation related to your payment acquirer to go through step 2, 5 and 6. Some acquirers provides you with specific credentials for test and production modes (Paypal). Others let you switch mode in their setup interface (Authorize.net)." +#: ../../ecommerce/shopper_experience/payment.rst:73 +msgid "That way a payment token will be recorded when the customer goes for the subscription and an automatic debit will occur whenever an invoice is issued from the subscription." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:74 -msgid "With Ingenico and Authorize.net, you can let your customers save and reuse a payment card to accelerate the process on next checkouts. See *Store Card Data* in Configuration tab." +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:78 -msgid "Payment flow" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:80 -msgid "When choosing the payment method, the customer is taken to the payment acquirer interface to process the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:83 -msgid "Once done he is taken back to Odoo's confirmation page. The transaction status shows up:" +#: ../../ecommerce/shopper_experience/payment.rst:81 +msgid "Odoo can submit single payment requests and redirect to any payment acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction status. So you will confirm orders manually once you get paid." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "*Pending*: the order will be confirmed as soon as you authorize the transaction in the acquirer interface." +msgid "How to:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "*Confirmed*: the payment has been authorized automatically." +msgid "Switch to developer mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "A confirmation email is sent to the customer with a copy of the order in pdf. It shows the payment status." +msgid "Take the **Custom** payment method." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Launch the delivery and invoicing from:" +msgid "Set up the payment form (S2S Form Template) as instructed by your payment acquirer. You can start from *default_acquirer_button* that you can duplicate." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:93 -msgid "eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`," +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:95 -msgid "online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales Orders`." +#: ../../ecommerce/shopper_experience/payment.rst:98 +msgid "Odoo can also be used for more advanced payment processes like installment plans (e.g. `Paypal Installment Plans <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons>`__)." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:97 -msgid "For internal tracking purposes, a link to the transaction status is provided in the sales order." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:100 -msgid "If the customer cancels the payment while on the payment acquirer form, it is taken back to the store page (or online quotation) in order to reprocess the order. The payment is marked as *Cancelled* in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:105 -msgid "You can edit the confirmation email template from :menuselection:`Website Admin --> Configuration --> Settings`." +#: ../../ecommerce/shopper_experience/payment.rst:102 +msgid "Such a customization service is made on-demand by our technical experts based on your own requirements. A business advisor can reach you out for such matter. `Contact us. <https://www.odoo.com/page/contactus>`__" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:109 -msgid "Order confirmation preferences" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid "There are 4 different behaviors available for any payment acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:114 -msgid "No automatic confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:116 -msgid "This is the default mode for *Wire Transfer*. It means Odoo does not confirm orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid Order*). Once you get the payment, you are expected to confirm the order manually to pursue the process (delivery, invoicing)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:121 -msgid "Authorize the amount and confirm the SO on acquirer confirmation (capture manually)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:123 -msgid "Odoo confirms the order as soon as the payment success notification comes in. To get the money however, you need to capture it from your payment transaction. In lots of countries you are indeed requested to deliver your goods before capturing the amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:128 -msgid "Authorize & capture the amount and confirm the SO on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:130 -msgid "This is the default mode for payment acquirers. The amount is captured automatically." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:133 -msgid "For B2B: if you use a manual payment method like *Wire Transfer* and don't expect any upfront payment to launch the delivery, switch to this mode as well." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:137 -msgid "Authorize & capture the amount, confirm the SO and auto-validate the invoice on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:139 -msgid "If you invoice upfront and not at the delivery, switch to this last mode to automate everything. You are requested to select a Payment Journal to record such payments (see :doc:`../../accounting/receivables/customer_payments/credit_cards`)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:144 -msgid "Custom payment acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:146 -msgid "Odoo can submit payment requests and redirect to any payment acquirer. In such a case, you need to confirm the sale manually in Odoo once you get paid because Odoo cannot read any payment status sent by the acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:150 -msgid "To configure this:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:152 -msgid "switch to developer mode," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:154 -msgid "edit the *Custom* payment method," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:156 -msgid "set up the payment form (S2S Form Template) as instructed by your payment acquirer. You can start from *default_acquirer_button* that you can duplicate." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:160 -msgid "Recurring payments & Installment plans" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:162 -msgid "The Ingenico integration allows you to process and manage recurring payments from Odoo Subscriptions app out-of-the-box (more information coming soon)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:165 -msgid "With some customization, Odoo can also trigger installment plans if this is permitted by your payment acquirer’s API:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:168 -msgid "e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:170 -msgid "Such a service is made on-demand by our technical experts based on your own requirements. Ask our business advisors at info@odoo.com." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:175 msgid ":doc:`paypal`" msgstr "" +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "Odoo confirms orders automatically as soon as the payment is authorized by a payment acquirer. This triggers the delivery. If you invoice based on ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "*Pending*: the payment acquirer keeps the transaction on hold and you need to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "*Authorized*: the payment has been authorized but not yet captured. In Odoo, the order is already confirmed. Once the delivery done, you can capture the amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "*Done*: the payment is authorized and captured. The order has been confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "*Error*: an error has occured during the transaction. The customer needs to retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "*Cancelled*: when the customer cancels the payment in the payment acquirer form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "Specific messages are provided to your customers for every payment status, when they are redirected to Odoo after the transaction. To edit such messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "When the order is confirmed you can also have an invoice automatically issued and paid. This fully-automated made for businesses that invoice orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see `How to register credit card payments <../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "With this mode, the order is confirmed but the amount is kept on hold. Once the delivery processed, you can capture the payment from Odoo. This mode is only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "To capture the payment, open the transaction from the order. Then click *Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo." +msgstr "" + #: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "How to collect payments with Paypal" +msgid "How to get paid with Paypal" msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:5 -msgid "Paypal is the easiest payment method to configure. It is also the only one without any subscription free." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:9 -msgid "Setup your Paypal account" +msgid "Paypal is the easiest online payment method to configure. It is also the only one without any subscription fee. We definitely advise it to any starter." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:11 -msgid "1. Create a business account at Paypal.com (see: https://www.paypal.com/in/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-outside) or upgrade your account to Business account (merchant) if you have a basic account." +msgid "Set up your Paypal account" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:15 -msgid "2. Log in to your account at Paypal.com and go to :menuselection:`My Account --> Profile --> My Selling Tools`. There click *PayPal button language encoding* under *More Selling Tools* section. Then, click *More Options* and replace the two default encoding formats by *UTF-8*." +#: ../../ecommerce/shopper_experience/paypal.rst:13 +msgid "Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade your account to *Business account* if you have a basic account." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:20 -msgid "Open Paypal setup form in Odoo and enter your *Email ID*." +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your **Profile**." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:22 -msgid "4. The Paypal Merchant ID is not mandatory (extra verification level). It is provided in Paypal under :menuselection:`My Account --> Overview`." +msgid "Now enter the menu **My selling tools**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:25 -msgid "5. Configure the IPN feedback (Paypal contacting your Odoo instance without needing the redirection). The setting can be found in :menuselection:`Profile --> My Selling Tools --> Instant payment notification`. Activate it and set it to <odoo_instance_url>/payment/paypal/ipn." +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:30 -msgid "6. To test the workflow, you can create sandbox accounts by logging in at https://developer.paypal.com/webapps/developer/applications/myapps with the same Paypal credentials. Two default sandbox accounts are automatically generated when you register to Paypal: one is a buyer, the other is a shopper." +#: ../../ecommerce/shopper_experience/paypal.rst:29 +msgid "Turn on **Auto Return** and enter the **Return URL**: <odoo_instance_url>/shop/confirmation. Verify that this address uses the correct protocol (HTTP/HTTPS)." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:35 -msgid "7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com (same password than real account) and apply the same format change." +#: ../../ecommerce/shopper_experience/paypal.rst:36 +msgid "Turn on **Payment Data Transfer**. When saving, an **Identity Token** is generated. You will be later requested to enter it in Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:39 -msgid "To automatically redirect your customers when the payment is completed, go to your Website Preferences and turn *Auto Return* on. Set *Return URL* to <odoo_instance_url>/shop/confirmation. Verify that your *Notify URL* uses the correct protocol (HTTP/HTTPS)." +#: ../../ecommerce/shopper_experience/paypal.rst:43 +msgid "Then, get back to your profile to activate the **Instant Payment Notification (IPN)** in *My selling tools*." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "If you want your customers to pay without creating a Paypal account, *Paypal Account Optional* needs to be turned on." +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:48 +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "Now you must change the encoding format of the payment request sent by Odoo to Paypal. To do so, get back to *My selling tools* and click **PayPal button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "If you want your customers to pay without creating a Paypal account, **Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "Open Paypal setup form in :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers+`. Enter both your **Email ID** and your **Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "They are both provided in your Paypal profile, under :menuselection:`My business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so, open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "Your configuration is now ready! You can make Paypal visible on your merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 msgid "Transaction fees" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:50 +#: ../../ecommerce/shopper_experience/paypal.rst:114 msgid "You can charge an extra to the customer to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:53 -msgid "To activate this, go to the *Configuration* tab and check *Add Extra Fees*. Default fees are the ones charged by Paypal." +#: ../../ecommerce/shopper_experience/paypal.rst:117 +msgid "To activate this, go to the *Configuration* tab of Paypal config form in Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "To apply the right fees for your country, please refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "A business account (to use as merchant, e.g. pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "A default personal account (to use as shopper, e.g. pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test* mode. Also, make sure the confirmation mode of Paypal is not *Authorize & capture the amount, confirm the SO and auto-validate the invoice on acquirer confirmation*. Otherwise a confirmed invoice will be automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:3 -msgid "How customers can access their portal" +msgid "How customers can access their customer account" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:5 -msgid "It has never been so easy for your customers to access their documents through a portal. Forget endless signup forms, Odoo makes it as easy as ABC. With eCommerce and Online Quotation apps, your customers are requested to create a portal account (name, email, password only) from the very first order confirmation or online quotation email they get from you." -msgstr "" - -#: ../../ecommerce/shopper_experience/portal.rst:12 -msgid "Sign up" +msgid "It has never been so easy for your customers to access their customer account. Forget endless signup forms, Odoo makes it as easy as ABC. They are suggested to sign up (name, email, password) when the order is placed, and not before. Indeed, nothing is more annoying than going through a signup process before buying something." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:14 -msgid "When clicking the link in the email or when clicking *Sign up* in the checkout process, your customer is directed to the *Sign up* page." +msgid "Sign up" msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:21 -msgid "Customer account" +#: ../../ecommerce/shopper_experience/portal.rst:16 +msgid "The invitation to sign up shows up when the customer wants to visualize the order from order confirmation email." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:23 -msgid "Once logged in the customer will access his account by clicking *My Account* in the login dropdown menu." +msgid "Customer account" msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:29 -msgid "From the portal menu all the customer history can be reviewed. The main address (billing) can also be modified." +#: ../../ecommerce/shopper_experience/portal.rst:25 +msgid "Once logged in the customer will access the account by clicking *My Account* in the login dropdown menu." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:36 -msgid "If a portal user is a contact of a company (*Company* field set in customer detail form), this last will see all the documents of the company and all its other contacts through the portal." +#: ../../ecommerce/shopper_experience/portal.rst:31 +msgid "THere they find all their history. The main address (billing) can also be modified." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:37 +msgid "If the customer is set as a contact of a company in your address book, they will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "**Wire Transfer** is the default payment method available. The aim is providing your customers with your bank details so they can pay on their own. This is very easy to start with but slow and inefficient process-wise. Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "Put your payment instructions in the **Thanks Message** of your payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "Whenever a customer pays by wire transfer, the order stays in an intermediary stage **Quotation Sent** (i.e. unpaid order). When you get paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "If you manage a B2B business, you can create other manually-processed payment methods like paying by check. To do so, just rename *Wire Transfer* or duplicate it." msgstr "" #: ../../ecommerce/taxes.rst:3 diff --git a/locale/sources/expense.pot b/locale/sources/expense.pot index 93fbbb0e9..ecbfe1cc2 100644 --- a/locale/sources/expense.pot +++ b/locale/sources/expense.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 8bfb4434f..d1493a610 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -21,7 +21,7 @@ msgid "General" msgstr "" #: ../../general/auth.rst:3 -msgid "Authentification" +msgid "Authentication" msgstr "" #: ../../general/auth/google.rst:3 @@ -65,310 +65,403 @@ msgid "Once done, you receive two information (your Client ID and Client Secret) msgstr "" #: ../../general/base_import.rst:3 -msgid "BASE IMPORT" +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "Remove columns you don't need. We advise to not remove the *ID* one (see why here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field of the system. If so, find the corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "Then, use the label you found in your import template in order to make it work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "Update imports: you can import the same file several times without creating duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" #: ../../general/base_import/import_faq.rst:3 -msgid "Import CSV file to Odoo" +msgid "How to import data into Odoo" msgstr "" -#: ../../general/base_import/import_faq.rst:8 -msgid "Frequently Asked Questions" +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" msgstr "" -#: ../../general/base_import/import_faq.rst:12 -msgid "Need to import data from an other application?" +#: ../../general/base_import/import_faq.rst:7 +msgid "You can import data on any Odoo's business object using either Excel (.xlsx) or CSV (.csv) formats: contacts, products, bank statements, journal entries and even orders!" msgstr "" -#: ../../general/base_import/import_faq.rst:14 -msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import an other record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier." +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." msgstr "" #: ../../general/base_import/import_faq.rst:16 -msgid "The **ID** (External ID) will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible." +msgid "There you are provided with templates you can easily populate with your own data. Such templates can be imported in one click; The data mapping is already done." msgstr "" -#: ../../general/base_import/import_faq.rst:21 -msgid "I cannot find the field I want to map my column to?" +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" msgstr "" -#: ../../general/base_import/import_faq.rst:23 -msgid "Odoo try to find with some heuristic, based on the first ten lines of the files, the type of field for each columns inside your file. For example if you have a column only containing numbers, only the fields that are of type integer will be displayed for you to choose from. While this behaviour might be good and easy for most cases scenarios, it is also possible that it goes wrong sometimes or that you want to map your column to a field that is not proposed by default." +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" #: ../../general/base_import/import_faq.rst:25 -msgid "If that happens, you just have to check the **Show all fields for completion (advanced)** option, you will then be able to choose from the complete list of fields for each columns." +msgid "We advise to not remove the **ID** one (see why in the next section)." msgstr "" -#: ../../general/base_import/import_faq.rst:30 -msgid "Where can I change the date import format?" +#: ../../general/base_import/import_faq.rst:31 +msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field in Odoo. Don't worry! You can map new columns manually when you test the import. Search the list for the corresponding field." msgstr "" -#: ../../general/base_import/import_faq.rst:32 -msgid "Odoo can automatically detect if a column is a date and it will try to guess the date format from a set of most used date format. While this process can work for a lot of simple date format, some exotic date format will not be recognize and it is also possible to have some confusion (day and month inverted as example) as it is difficult to guess correctly which part is the day and which one is the month in a date like '01-03-2016'." -msgstr "" - -#: ../../general/base_import/import_faq.rst:34 -msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format." -msgstr "" - -#: ../../general/base_import/import_faq.rst:37 -msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is." -msgstr "" - -#: ../../general/base_import/import_faq.rst:42 -msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +#: ../../general/base_import/import_faq.rst:39 +msgid "Then, use this field's label in your file in order to make it work straight on the very next time." msgstr "" #: ../../general/base_import/import_faq.rst:44 -msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash." +msgid "How to import from another application" msgstr "" #: ../../general/base_import/import_faq.rst:46 -msgid "Examples of supported numbers (using thirty-two thousands as an example):" -msgstr "" - -#: ../../general/base_import/import_faq.rst:48 -msgid "32.000,00" -msgstr "" - -#: ../../general/base_import/import_faq.rst:49 -msgid "32000,00" -msgstr "" - -#: ../../general/base_import/import_faq.rst:50 -msgid "32,000.00" -msgstr "" - -#: ../../general/base_import/import_faq.rst:51 -msgid "-32000.00" -msgstr "" - -#: ../../general/base_import/import_faq.rst:52 -msgid "(32000.00)" -msgstr "" - -#: ../../general/base_import/import_faq.rst:53 -msgid "$ 32.000,00" +msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import another record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier. You can also find this record using its name but you will be stuck if at least 2 records have the same name." msgstr "" #: ../../general/base_import/import_faq.rst:54 -msgid "(32000.00 €)" +msgid "The **ID** will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible." msgstr "" -#: ../../general/base_import/import_faq.rst:56 -msgid "Example that will not work:" +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" msgstr "" -#: ../../general/base_import/import_faq.rst:58 -msgid "ABC 32.000,00" +#: ../../general/base_import/import_faq.rst:62 +msgid "Odoo tries to find with some heuristic, based on the first ten lines of the files, the type of field for each column inside your file. For example if you have a column only containing numbers, only the fields that are of type *Integer* will be displayed for you to choose from. While this behavior might be good and easy for most cases, it is also possible that it goes wrong or that you want to map your column to a field that is not proposed by default." msgstr "" -#: ../../general/base_import/import_faq.rst:59 -msgid "$ (32.000,00)" +#: ../../general/base_import/import_faq.rst:71 +msgid "If that happens, you just have to check the ** Show fields of relation fields (advanced)** option, you will then be able to choose from the complete list of fields for each column." msgstr "" -#: ../../general/base_import/import_faq.rst:64 -msgid "What can I do when the Import preview table isn't displayed correctly?" +#: ../../general/base_import/import_faq.rst:79 +msgid "Where can I change the date import format?" msgstr "" -#: ../../general/base_import/import_faq.rst:66 -msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)." +#: ../../general/base_import/import_faq.rst:81 +msgid "Odoo can automatically detect if a column is a date and it will try to guess the date format from a set of most used date format. While this process can work for a lot of simple date format, some exotic date format will not be recognize and it is also possible to have some confusion (day and month inverted as example) as it is difficult to guess correctly which part is the day and which one is the month in a date like '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:68 -msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question." -msgstr "" - -#: ../../general/base_import/import_faq.rst:73 -msgid "How can I change the CSV file format options when saving in my spreadsheet application?" -msgstr "" - -#: ../../general/base_import/import_faq.rst:75 -msgid "If you edit and save CSV files in speadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in 'Save As' dialog box > Check the box 'Edit filter settings' > Save)." -msgstr "" - -#: ../../general/base_import/import_faq.rst:77 -msgid "Microsoft Excel will allow you to modify only the encoding when saving (in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." -msgstr "" - -#: ../../general/base_import/import_faq.rst:82 -msgid "What's the difference between Database ID and External ID?" -msgstr "" - -#: ../../general/base_import/import_faq.rst:84 -msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides 3 mechanisms. You must use one and only one mechanism per field you want to import." +#: ../../general/base_import/import_faq.rst:83 +msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format." msgstr "" #: ../../general/base_import/import_faq.rst:86 -msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" +msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:88 -msgid "Country: the name or code of the country" +#: ../../general/base_import/import_faq.rst:91 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" msgstr "" -#: ../../general/base_import/import_faq.rst:89 -msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" -msgstr "" - -#: ../../general/base_import/import_faq.rst:90 -msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)" -msgstr "" - -#: ../../general/base_import/import_faq.rst:92 -msgid "For the country Belgium, you can use one of these 3 ways to import:" -msgstr "" - -#: ../../general/base_import/import_faq.rst:94 -msgid "Country: Belgium" +#: ../../general/base_import/import_faq.rst:93 +msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash." msgstr "" #: ../../general/base_import/import_faq.rst:95 -msgid "Country/Database ID: 21" +msgid "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:96 -msgid "Country/External ID: base.be" +#: ../../general/base_import/import_faq.rst:97 +msgid "32.000,00" msgstr "" #: ../../general/base_import/import_faq.rst:98 -msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:" +msgid "32000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:99 +msgid "32,000.00" msgstr "" #: ../../general/base_import/import_faq.rst:100 -msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually." +msgid "-32000.00" msgstr "" #: ../../general/base_import/import_faq.rst:101 -msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)" +msgid "(32000.00)" msgstr "" #: ../../general/base_import/import_faq.rst:102 -msgid "Use Country/External ID: Use External ID when you import data from a third party application." +msgid "$ 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:104 -msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories." +#: ../../general/base_import/import_faq.rst:103 +msgid "(32000.00 €)" msgstr "" -#: ../../general/base_import/import_faq.rst:106 -msgid "`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." +#: ../../general/base_import/import_faq.rst:105 +msgid "Example that will not work:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:107 +msgid "ABC 32.000,00" msgstr "" #: ../../general/base_import/import_faq.rst:108 -msgid "`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`_." +msgid "$ (32.000,00)" msgstr "" -#: ../../general/base_import/import_faq.rst:112 -msgid "What can I do if I have multiple matches for a field?" +#: ../../general/base_import/import_faq.rst:113 +msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" -#: ../../general/base_import/import_faq.rst:114 -msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy." +#: ../../general/base_import/import_faq.rst:115 +msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:116 -msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'." +#: ../../general/base_import/import_faq.rst:117 +msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:121 -msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" +#: ../../general/base_import/import_faq.rst:122 +msgid "How can I change the CSV file format options when saving in my spreadsheet application?" msgstr "" -#: ../../general/base_import/import_faq.rst:123 -msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file." +#: ../../general/base_import/import_faq.rst:124 +msgid "If you edit and save CSV files in speadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in 'Save As' dialog box > Check the box 'Edit filter settings' > Save)." msgstr "" -#: ../../general/base_import/import_faq.rst:125 -msgid "`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`_." +#: ../../general/base_import/import_faq.rst:126 +msgid "Microsoft Excel will allow you to modify only the encoding when saving (in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." msgstr "" -#: ../../general/base_import/import_faq.rst:130 -msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" +#: ../../general/base_import/import_faq.rst:131 +msgid "What's the difference between Database ID and External ID?" msgstr "" -#: ../../general/base_import/import_faq.rst:132 -msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an addtional row that does not have any information in the fields relative to the order. As an example, here is purchase.order_functional_error_line_cant_adpat.CSV file of some quotations you can import, based on demo data." +#: ../../general/base_import/import_faq.rst:133 +msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides 3 mechanisms. You must use one and only one mechanism per field you want to import." msgstr "" #: ../../general/base_import/import_faq.rst:135 -msgid "`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." +msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" msgstr "" #: ../../general/base_import/import_faq.rst:137 -msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../general/base_import/import_faq.rst:138 +msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" msgstr "" #: ../../general/base_import/import_faq.rst:139 -msgid "`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`_." +msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)" msgstr "" #: ../../general/base_import/import_faq.rst:141 -msgid "The following CSV file shows how to import customers and their respective contacts:" +msgid "For the country Belgium, you can use one of these 3 ways to import:" msgstr "" #: ../../general/base_import/import_faq.rst:143 -msgid "`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`_." +msgid "Country: Belgium" msgstr "" -#: ../../general/base_import/import_faq.rst:148 -msgid "Can I import several times the same record?" +#: ../../general/base_import/import_faq.rst:144 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../general/base_import/import_faq.rst:145 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../general/base_import/import_faq.rst:147 +msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:149 +msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually." msgstr "" #: ../../general/base_import/import_faq.rst:150 -msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not." +msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:152 -msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application." +#: ../../general/base_import/import_faq.rst:151 +msgid "Use Country/External ID: Use External ID when you import data from a third party application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:153 +msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories." +msgstr "" + +#: ../../general/base_import/import_faq.rst:155 +msgid "`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." msgstr "" #: ../../general/base_import/import_faq.rst:157 -msgid "What happens if I do not provide a value for a specific field?" +msgid "`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:159 -msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value." +#: ../../general/base_import/import_faq.rst:161 +msgid "What can I do if I have multiple matches for a field?" msgstr "" -#: ../../general/base_import/import_faq.rst:164 -msgid "How to export/import different tables from an SQL application to Odoo?" +#: ../../general/base_import/import_faq.rst:163 +msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:166 -msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)." -msgstr "" - -#: ../../general/base_import/import_faq.rst:168 -msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique accoss all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')" +#: ../../general/base_import/import_faq.rst:165 +msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'." msgstr "" #: ../../general/base_import/import_faq.rst:170 -msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a <a href=\"/base_import/static/csv/database_import_test.sql\">dump of such a PostgreSQL database</a>)" +msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" msgstr "" #: ../../general/base_import/import_faq.rst:172 -msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file." msgstr "" -#: ../../general/base_import/import_faq.rst:178 -msgid "This SQL command will create the following CSV file::" +#: ../../general/base_import/import_faq.rst:174 +msgid "`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:185 -msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:" +#: ../../general/base_import/import_faq.rst:179 +msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:191 -msgid "It will produce the following CSV file::" +#: ../../general/base_import/import_faq.rst:181 +msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an addtional row that does not have any information in the fields relative to the order. As an example, here is purchase.order_functional_error_line_cant_adpat.CSV file of some quotations you can import, based on demo data." +msgstr "" + +#: ../../general/base_import/import_faq.rst:184 +msgid "`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:186 +msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:188 +msgid "`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:190 +msgid "The following CSV file shows how to import customers and their respective contacts:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:192 +msgid "`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:197 +msgid "Can I import several times the same record?" msgstr "" #: ../../general/base_import/import_faq.rst:199 -msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the orignial database)." +msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not." msgstr "" #: ../../general/base_import/import_faq.rst:201 +msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:206 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:208 +msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value." +msgstr "" + +#: ../../general/base_import/import_faq.rst:213 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:215 +msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:217 +msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique accoss all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../general/base_import/import_faq.rst:219 +msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a <a href=\"/base_import/static/csv/database_import_test.sql\">dump of such a PostgreSQL database</a>)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:221 +msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:227 +msgid "This SQL command will create the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:234 +msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:240 +msgid "It will produce the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:248 +msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the orignial database)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:250 msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons." msgstr "" diff --git a/locale/sources/getting_started.pot b/locale/sources/getting_started.pot index 2946fb205..863eea185 100644 --- a/locale/sources/getting_started.pot +++ b/locale/sources/getting_started.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -313,114 +313,130 @@ msgid "**Data Import**: we can do it or assist you on how to do it with a templa msgstr "" #: ../../getting_started/documentation.rst:283 -msgid "If you have subscribed to a **Custom App**, you benefit from following extra services:" +msgid "If you have subscribed to **Studio**, you benefit from following extra services:" msgstr "" #: ../../getting_started/documentation.rst:286 -msgid "**Customization of screens**" +msgid "**Customization of screens:** Studio takes the Drag and Drop approach to customize most screens in any way you see fit." msgstr "" -#: ../../getting_started/documentation.rst:288 -msgid "**Customization of reports (PDF):** our project managers have access to developers for advanced customizations." +#: ../../getting_started/documentation.rst:289 +msgid "**Customization of reports (PDF):** Studio itself will not allow you to customize the reports yourself, however our project managers have access to developers for advanced customizations." msgstr "" -#: ../../getting_started/documentation.rst:291 +#: ../../getting_started/documentation.rst:293 msgid "**Website Design:** standard themes are provided to get started at no extra cost. However, our project manager can coach you on how to utilize the building blocks of the website designer. The time spent will consume hours of your success pack." msgstr "" -#: ../../getting_started/documentation.rst:296 +#: ../../getting_started/documentation.rst:298 msgid "**Workflow automations:** e.g. setting values in fields based on triggers, sending reminders by emails, automating actions, etc. For very advanced automations, our project managers have access to Odoo developers." msgstr "" -#: ../../getting_started/documentation.rst:302 -msgid "Implementation Methodology" -msgstr "" - -#: ../../getting_started/documentation.rst:304 -msgid "We follow a **lean and hands-on methodology**, that is used to put customers in production in a short period of time and at a low cost." +#: ../../getting_started/documentation.rst:303 +msgid "If any customization is needed, Odoo Studio App will be required. Customizations made through Odoo Studio App will be maintained and upgraded at each Odoo upgrade, at no extra cost." msgstr "" #: ../../getting_started/documentation.rst:307 -msgid "After the kick-off meeting, we define a phasing plan to deploy Odoo progressively, by groups of apps." +msgid "All time spent to perform these customizations by our Business Analysts will be deducted from your Success Pack." msgstr "" -#: ../../getting_started/documentation.rst:313 -msgid "The goal of the **Kick-off call** is for our project manager to come to an understanding of your business in order to propose an implementation plan (phasing). Each phase is the deployment of a set applications that you will fully use in production at the end of the phase." +#: ../../getting_started/documentation.rst:310 +msgid "In case of customizations that would require a developer’s intervention, a recurring maintenance fee will be charged on the customer subscription, to cover maintenance and upgrade services. This cost will be based on hours spent by the developer: 4€ or $5/month, per hour of development will be added to the subscription fee." msgstr "" -#: ../../getting_started/documentation.rst:319 -msgid "For every phase, the steps are the following:" +#: ../../getting_started/documentation.rst:316 +msgid "**Example:** a customization that took 2 hours of development will cost: 2 hours deducted from the Success Pack for the customization development 2 * $5 = $10/month as recurring fee for the maintenance of this customization" msgstr "" #: ../../getting_started/documentation.rst:321 -msgid "**On Boarding:** Odoo's project manager will review Odoo's business flows with you, according to your business. The goal is to train you, validate the business process and configure according to your specific needs." +msgid "Implementation Methodology" +msgstr "" + +#: ../../getting_started/documentation.rst:323 +msgid "We follow a **lean and hands-on methodology**, that is used to put customers in production in a short period of time and at a low cost." msgstr "" #: ../../getting_started/documentation.rst:326 -msgid "**Data:** created manually or imported from your existing system. You are responsible to export the data from your existing system and Odoo's project manager will import them in Odoo." +msgid "After the kick-off meeting, we define a phasing plan to deploy Odoo progressively, by groups of apps." msgstr "" -#: ../../getting_started/documentation.rst:330 -msgid "**Training:** once your applications are set up, your data imported, and the system is working smoothly, you will train your users. There will be some back and forth with your Odoo project manager to answer questions and process your feedback." -msgstr "" - -#: ../../getting_started/documentation.rst:335 -msgid "**Production**: Once everyone is trained, your users start using Odoo." +#: ../../getting_started/documentation.rst:332 +msgid "The goal of the **Kick-off call** is for our project manager to come to an understanding of your business in order to propose an implementation plan (phasing). Each phase is the deployment of a set applications that you will fully use in production at the end of the phase." msgstr "" #: ../../getting_started/documentation.rst:338 +msgid "For every phase, the steps are the following:" +msgstr "" + +#: ../../getting_started/documentation.rst:340 +msgid "**On Boarding:** Odoo's project manager will review Odoo's business flows with you, according to your business. The goal is to train you, validate the business process and configure according to your specific needs." +msgstr "" + +#: ../../getting_started/documentation.rst:345 +msgid "**Data:** created manually or imported from your existing system. You are responsible to export the data from your existing system and Odoo's project manager will import them in Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:349 +msgid "**Training:** once your applications are set up, your data imported, and the system is working smoothly, you will train your users. There will be some back and forth with your Odoo project manager to answer questions and process your feedback." +msgstr "" + +#: ../../getting_started/documentation.rst:354 +msgid "**Production**: Once everyone is trained, your users start using Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:357 msgid "Once you are comfortable using Odoo, we will fine-tune the process and **automate** some tasks and do the remaining customizations (**extra screens and reports**)." msgstr "" -#: ../../getting_started/documentation.rst:342 +#: ../../getting_started/documentation.rst:361 msgid "Once all applications are deployed and users are comfortable on Odoo, our project manager will not work on your project anymore (unless you have new needs) and you will use the support service if you have further questions." msgstr "" -#: ../../getting_started/documentation.rst:348 +#: ../../getting_started/documentation.rst:367 msgid "Managing your databases" msgstr "" -#: ../../getting_started/documentation.rst:350 +#: ../../getting_started/documentation.rst:369 msgid "To access your databases, go to Odoo.com, sign in and click **My Databases** in the drop-down menu at the top right corner." msgstr "" -#: ../../getting_started/documentation.rst:356 +#: ../../getting_started/documentation.rst:375 msgid "Odoo gives you the opportunity to test the system before going live or before upgrading to a newer version. Do not mess up your working environment with test data!" msgstr "" -#: ../../getting_started/documentation.rst:360 +#: ../../getting_started/documentation.rst:379 msgid "In that purpose, you can create as many free trials as you want (available for 15 days). Those instances can be instant copies of your working environment. To do so, go to the Odoo.com account in **My Organizations** page and click **Duplicate**." msgstr "" -#: ../../getting_started/documentation.rst:371 +#: ../../getting_started/documentation.rst:390 msgid "You can find more information on how to manage your databases :ref:`here <db_management/documentation>`." msgstr "" -#: ../../getting_started/documentation.rst:375 +#: ../../getting_started/documentation.rst:394 msgid "Customer Success" msgstr "" -#: ../../getting_started/documentation.rst:377 +#: ../../getting_started/documentation.rst:396 msgid "Odoo is passionate about delighting our customers and ensuring that they have all the resources needed to complete their project." msgstr "" -#: ../../getting_started/documentation.rst:380 +#: ../../getting_started/documentation.rst:399 msgid "During the implementation phase, your point of contact is the project manager and eventually the support team." msgstr "" -#: ../../getting_started/documentation.rst:383 +#: ../../getting_started/documentation.rst:402 msgid "Once you are in production, you will probably have less interaction with your project manager. At that time, we will assign a member of our Client Success Team to you. They are specialized in the long-term relationship with our customers. They will contact you to showcase new versions, improve the way you work with Odoo, assess your new needs, etc..." msgstr "" -#: ../../getting_started/documentation.rst:390 +#: ../../getting_started/documentation.rst:409 msgid "Our internal goal is to keep customers for at least 10 years and offer them a solution that grows with their needs!" msgstr "" -#: ../../getting_started/documentation.rst:393 +#: ../../getting_started/documentation.rst:412 msgid "Welcome aboard and enjoy your Odoo experience!" msgstr "" -#: ../../getting_started/documentation.rst:396 +#: ../../getting_started/documentation.rst:415 msgid ":doc:`../../db_management/documentation`" msgstr "" diff --git a/locale/sources/index.pot b/locale/sources/index.pot index ba8a88c2e..f657a1074 100644 --- a/locale/sources/index.pot +++ b/locale/sources/index.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/inventory.pot b/locale/sources/inventory.pot index fe9dd8bf1..62a45ff79 100644 --- a/locale/sources/inventory.pot +++ b/locale/sources/inventory.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-16 15:59+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -524,30 +524,58 @@ msgstr "" msgid "The Minimum Stock Rules configuration is available through the menu :menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the drop down menu. There, click on **Create** to set minimum and maximum stock values for a given product." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "If the active field is set to False, it will allow you to hide the orderpoint without removing it." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Default Unit of Measure used for all stock operation." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by procurement rules will be grouped into one big picking." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "When the virtual stock goes below the Min Quantity specified for this field, Odoo generates a procurement to bring the forecasted quantity to the Max Quantity." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "When the virtual stock goes below the Min Quantity, Odoo generates a procurement to bring the forecasted quantity to the Quantity specified as Max Quantity." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "The procurement quantity will be rounded up to this multiple. If it is 0, the exact quantity will be used." msgstr "" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Number of days after the orderpoint is triggered to receive the products or to order to the vendor" msgstr "" @@ -986,7 +1014,7 @@ msgid "Configuring lead times" msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:15 -msgid "Configuring **lead times** is a first essentiel move in order to compute scheduled dates. Lead times are the delays (in term of delivery, manufacturing, ...) promised to your different partners and/or clients." +msgid "Configuring **lead times** is a first essential move in order to compute scheduled dates. Lead times are the delays (in term of delivery, manufacturing, ...) promised to your different partners and/or clients." msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:19 diff --git a/locale/sources/legal.pot b/locale/sources/legal.pot index 598bfe45c..68f2db5ce 100644 --- a/locale/sources/legal.pot +++ b/locale/sources/legal.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -35,28 +35,36 @@ msgstr "" msgid "Terms and Conditions" msgstr "" -#: ../../legal.rst:38 +#: ../../legal.rst:46 msgid ":ref:`enterprise_agreement` |nbsp| |nbsp| |download_enterprise|" msgstr "" -#: ../../legal.rst:40 +#: ../../legal.rst:48 msgid ":ref:`enterprise_agreement_fr` |nbsp| |nbsp| |download_enterprise_fr|" msgstr "" -#: ../../legal.rst:47 +#: ../../legal.rst:50 +msgid ":ref:`terms_of_sale` |nbsp| |nbsp| |download_terms_of_sale|" +msgstr "" + +#: ../../legal.rst:51 +msgid ":ref:`terms_of_sale_fr` |nbsp| |nbsp| |download_terms_of_sale_fr|" +msgstr "" + +#: ../../legal.rst:58 #: ../../legal/others.rst:5 msgid "Other legal references" msgstr "" -#: ../../legal.rst:49 +#: ../../legal.rst:60 msgid "`Odoo Online Service Level Agreement <https://www.odoo.com/page/odoo-online-sla>`_" msgstr "" -#: ../../legal.rst:50 +#: ../../legal.rst:61 msgid "`Odoo Online Acceptable Use Policy <https://www.odoo.com/page/odoo-online-acceptable-use-policy>`_" msgstr "" -#: ../../legal.rst:51 +#: ../../legal.rst:62 msgid ":ref:`cla`" msgstr "" @@ -78,34 +86,42 @@ msgstr "" #: ../../legal/licenses/enterprise_license.txt:1 #: ../../legal/terms/i18n/enterprise_fr.rst:487 +#: ../../legal/licenses/enterprise_license.txt:1 msgid "Odoo Enterprise Edition License v1.0" msgstr "" +#: ../../legal/licenses/enterprise_license.txt:3 #: ../../legal/licenses/enterprise_license.txt:3 msgid "This software and associated files (the \"Software\") can only be used (executed, modified, executed after modifications) with a valid Odoo Enterprise Subscription for the correct number of users." msgstr "" +#: ../../legal/licenses/enterprise_license.txt:7 #: ../../legal/licenses/enterprise_license.txt:7 msgid "With a valid Partnership Agreement with Odoo S.A., the above permissions are also granted, as long as the usage is limited to a testing or development environment." msgstr "" +#: ../../legal/licenses/enterprise_license.txt:11 #: ../../legal/licenses/enterprise_license.txt:11 msgid "You may develop Odoo modules based on the Software and distribute them under the license of your choice, provided that it is compatible with the terms of the Odoo Enterprise Edition License (For example: LGPL, MIT, or proprietary licenses similar to this one)." msgstr "" +#: ../../legal/licenses/enterprise_license.txt:16 #: ../../legal/licenses/enterprise_license.txt:16 msgid "You may use Odoo modules published under any license along with the Software, provided that their license is compatible with the terms of the Odoo Enterprise License (Including, but not limited to, any module published on the Odoo Apps Store on odoo.com/apps)" msgstr "" #: ../../legal/licenses/enterprise_license.txt:21 #: ../../legal/licenses/licenses.rst:69 +#: ../../legal/licenses/enterprise_license.txt:21 msgid "It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software." msgstr "" +#: ../../legal/licenses/enterprise_license.txt:24 #: ../../legal/licenses/enterprise_license.txt:24 msgid "The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software." msgstr "" +#: ../../legal/licenses/enterprise_license.txt:27 #: ../../legal/licenses/enterprise_license.txt:27 msgid "THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE." msgstr "" @@ -553,6 +569,47 @@ msgstr "" msgid "9 Appendix A: Odoo Enterprise Edition License" msgstr "" +#: ../../legal/terms/enterprise.rst:431 +msgid "Odoo 9 Enterprise Edition is licensed under the Odoo Enterprise Edition License v1.0, defined as follows:" +msgstr "" + +#: ../../legal/terms/enterprise.rst:439 +#: ../../legal/terms/partnership.rst:228 +msgid "See :ref:`odoo_enterprise_license`." +msgstr "" + +#: ../../legal/terms/enterprise.rst:450 +msgid "Agreement Registration" +msgstr "" + +#: ../../legal/terms/enterprise.rst:453 +msgid "Customer contact information" +msgstr "" + +#: ../../legal/terms/enterprise.rst:455 +msgid "Company name: Company address: VAT number (if applicable): Contact name: Email: Phone:" +msgstr "" + +#: ../../legal/terms/enterprise.rst:463 +msgid "Technical contact information (can be an Odoo partner):" +msgstr "" + +#: ../../legal/terms/enterprise.rst:464 +msgid "Company name: Contact name: Email: Phone:" +msgstr "" + +#: ../../legal/terms/enterprise.rst:470 +msgid "By signing this Agreement I confirm I am a legal representative of Customer as stated in the resent section and approve all provisions and conditions of the present Agreement:" +msgstr "" + +#: ../../legal/terms/enterprise.rst:473 +msgid "For and on behalf of (company name): Last name, first name: Title: Date:" +msgstr "" + +#: ../../legal/terms/enterprise.rst:478 +msgid "Signature:" +msgstr "" + #: ../../legal/terms/i18n/enterprise_fr.rst:6 msgid "Odoo Enterprise Subscription Agreement (FR)" msgstr "" @@ -690,7 +747,7 @@ msgid "Les demandes de migration doivent inclure une copie de sauvegarde complè msgstr "" #: ../../legal/terms/i18n/enterprise_fr.rst:160 -msgid "Ce service est fourni par le biais d'une plateforme automatisée, afin de permettre au Client d'effectuer des migration sans intervention humain, dès lors qu’une version précédente de la base de données du Client a été migrée avec succès pour une Version Couverte donnée. Le client peut soumettre des demandes de migration successives pour une base de données, et accepte de soumettre au moins 1 demande de mifration de test avant de soumettre la demande de migration finale." +msgid "Ce service est fourni par le biais d'une plateforme automatisée, afin de permettre au Client d'effectuer des migration sans intervention humain, dès lors qu’une version précédente de la base de données du Client a été migrée avec succès pour une Version Couverte donnée. Le client peut soumettre des demandes de migration successives pour une base de données, et accepte de soumettre au moins 1 demande de migration de test avant de soumettre la demande de migration finale." msgstr "" #: ../../legal/terms/i18n/enterprise_fr.rst:167 @@ -973,6 +1030,62 @@ msgstr "" msgid "EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION RELATIVE AU LOGICIEL." msgstr "" +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:5 +msgid "Conditions Générales de Vente" +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:7 +msgid "Dernière modification: 5 mai 2017." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:9 +msgid "Ces conditions régissent la vente de produits et services entre Odoo S.A. et ses filiales (collectivement, \"Odoo S.A.\") et le client. Des conditions supplémentaires peuvent s'appliquer pour d'autres services offerts par Odoo S.A. (par exemple, l'Odoo Enterprise Subscription Agreement). Si ces conditions supplémentaires entrent en contradiction avec les Conditions Générales de Vente, les conditions supplémentaires prévaudront." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:16 +msgid "Veuillez lire ces conditions attentivement avant de faire une commande auprès d'Odoo S.A. En commandant auprès d'Odoo S.A., le client marque son accord avec les présentes conditions." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:20 +msgid "Le client renonce explicitement à ses propres conditions générales, même dans le cas où celles-ci seraient postérieures aux présentes conditions générales. Toute dérogation doit, pour être valable, être convenue de manière expresse, préalable et par écrit. Les présentes conditions sont une prolongation du contrat signé entre parties et font en tant que telles partie intégrante de la relation contractuelle entre parties." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:27 +msgid "Toutes les offres, tarifs ou listes de prix d’Odoo S.A. s’entendent, sauf stipulation contraire, sans engagement. Sauf stipulation contraire, toutes les factures sont payables à Odoo S.A. au comptant, au moment de la livraison. L'endroit de paiement est le siège social de Odoo S.A. peut envoyer des factures pour des marchandises déjà livrées même avant la livraison complète des marchandises. Le Client ne peut en aucun cas compenser une quelconque créance sur Odoo S.A. avec son obligation de paiement, sauf stipulation contraire." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:35 +msgid "Si la facture n’est pas payée à son échéance, elle sera, à titre d’indemnité forfaitaire, majorée de 15% et majorée d'autres indemnités, éventuellement dues pour tout préjudice, à démontrer par Odoo S.A.. Le non-paiement de tout ou partie d’une facture à son échéance rend immédiatement exigibles toutes sommes ou toutes factures dues non-encore échue. En cas de non-paiement d’une facture, Odoo S.A.  a le droit de rompre toutes les conventions de vente qui restent encore à exécuter." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:43 +msgid "Si le Client est autorisé à effectuer des paiements à terme, l’absence de paiement d’un seul terme entraînera de plein droit et sans mise en demeure l’exigibilité de toute la dette, nonobstant toute indemnité supplémentaire." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:47 +msgid "Certains pays appliquent une retenue à la source sur le montant de la facture, conformément à leur législation interne. La retenue à la source sera réglée par le client, auprès de l'administration fiscale. En aucun cas, Odoo S.A. ne sera impliquée dans les coûts liés à la législation du pays. Le montant de la facture est donc dû à Odoo S.A. dans son intégralité et n’inclus pas les coûts relatifs à la législation du pays où se trouve le client." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:54 +msgid "Odoo S.A. s'engage à faire ses meilleurs efforts en vue de fournir en temps utile des services performants. Toutefois, aucune de ses obligations ne peut être considérée comme étant une obligation de résultat. Odoo S.A. ne peut, en aucun cas, être appelée en garantie par le client dans le cadre de demandes en dommages et intérêts formulée par le consommateur final à l'encontre du client." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:60 +msgid "Dans la limite autorisée par la loi, la responsabilité globale de chaque partie, ainsi que de ses filiales ne dépassera pas 50% du montant total réglé par le Client en vertu des présentes conditions au cours des 12 mois précédant la date de l'événement donnant lieu à une telle réclamation. Des réclamations multiples n'augmenteront pas cette limite." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:66 +msgid "Toute réclamation doit, pour être recevable, être notifiée à Odoo S.A., à son siège social, par courrier recommandé dans les 8 jours suivant la livraison des marchandises ou la prestation des services." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:70 +msgid "Odoo S.A. se réserve le droit de modifier ces conditions à n'importe quel moment et sans notification préalable. Le client est soumis aux conditions en application au moment de son acceptation de ces conditions." +msgstr "" + +#: ../../legal/terms/i18n/terms_of_sale_fr.rst:74 +msgid "Tout litige résultant de la présente convention ressort de l’application du droit belge et est de la compétence des Tribunaux de l’arrondissement du siège social d’Odoo S.A. hormis le droit d’Odoo S.A. de porter le litige devant une autre juridiction compétente." +msgstr "" + #: ../../legal/terms/online.rst:3 msgid "Odoo Online Terms & Conditions" msgstr "" @@ -1185,3 +1298,55 @@ msgstr "" msgid "10 Appendix A: Odoo Enterprise Edition License" msgstr "" +#: ../../legal/terms/terms_of_sale.rst:5 +msgid "General Terms of Sale" +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:7 +msgid "Last revision: May 5, 2017." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:9 +msgid "These General Terms of Sale govern the sale of products and services by Odoo S.A. and its affiliates (collectively, \"Odoo S.A.\") to the client. Additional terms may apply for services provided by Odoo S.A. (for example, the Enterprise Subscription Agreement). If these additional terms are inconsistent with the General Terms of Sale, the additional terms will prevail over these General Terms of Sale." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:16 +msgid "Please read these terms carefully before placing an order with Odoo S.A. By accepting an order with Odoo S.A., the client marks his acceptance with these terms." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:20 +msgid "The client explicitly waives its own standard terms and conditions, even if these were drawn up after these standard terms and conditions of sale. In order to be valid, any derogation must be expressly agreed to in advance in writing." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:25 +msgid "Our invoices are payable within 21 working days, unless another payment timeframe is indicated on either the invoice or the order. In the event of non-payment by the due date, Odoo S.A. reserves the right to request a fixed interest payment amounting to 15% of the sum remaining due. Odoo S.A. will be authorised to suspend any provision of services without prior warning in the event of late payment." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:32 +msgid "If a payment is still outstanding more than sixty (60) days after the due payment date, Odoo S.A. reserves the right to call on the services of a debt recovery company. All legal expenses will be payable by the client." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:36 +msgid "Certain countries apply withholding at source on the amount of invoices, in accordance with their internal legislation. Any withholding at source will be paid by the client to the tax authorities. Under no circumstances can Odoo S.A. become involved in costs related to a country's legislation. The amount of the invoice will therefore be due to Odoo S.A. in its entirety and does not include any costs relating to the legislation of the country in which the client is located." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:44 +msgid "Odoo S.A. undertakes to do its best to supply services in due time in accordance with the agreed timeframes. However, none of its obligations can be considered as being an obligation to achieve results. Odoo S.A. cannot, under any circumstances, be required by the client to appear as a third party in the context of any claim for damages filed against the client by an end consumer." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:50 +msgid "In order for it to be admissible, Odoo S.A. must be notified of any claim by means of a letter sent by recorded delivery to its registered office within 8 days of the delivery of the goods or the provision of the services." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:54 +msgid "To the maximum extent permitted by law, the aggregate liability of each party together with its affiliates arising will not exceed 50% of the total amount paid by the Customer under these terms during the 12 months immediately preceding the date of the event giving rise to such claim. Multiple claims shall not enlarge this limitation." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:60 +msgid "Odoo S.A. reserves the right to modify these terms at any time without prior notice. The client will be subject to the terms in force at the time of acceptation of those terms." +msgstr "" + +#: ../../legal/terms/terms_of_sale.rst:64 +msgid "All our contractual relations will be governed exclusively by Belgian law. Moreover, any dispute that may arise will be subject exclusively to the jurisdiction of the courts of the Nivelles arrondissement (Belgium)." +msgstr "" + diff --git a/locale/sources/manufacturing.pot b/locale/sources/manufacturing.pot index 127673b18..a3a87ac67 100644 --- a/locale/sources/manufacturing.pot +++ b/locale/sources/manufacturing.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/point_of_sale.pot b/locale/sources/point_of_sale.pot index d9eb02a6d..0285a70c8 100644 --- a/locale/sources/point_of_sale.pot +++ b/locale/sources/point_of_sale.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -1455,118 +1455,234 @@ msgstr "" msgid "You can configure each point of sale according to your hardware, location,..." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "An internal identification of the point of sale" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to post sales entries." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to create invoices." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check this if you want to group the Journal Items by Product while closing a Session" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Defines what kind of barcodes are available and how they are assigned to products, customers and cashiers" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "This sequence is automatically created by Odoo but you can change it to customize the reference numbers of your orders." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "This Point of sale's sales will be related to this Sales Channel." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables an integrated Virtual Keyboard" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables invoice generation from the Point of Sale" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The payment input will behave similarily to bank payment input, and will be prefilled with the exact due amount" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The point of sale will display this product category by default. If no category is specified, all available products will be shown" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product used to encode the customer tip. Leave empty if you do not accept tips." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The displayed prices will always include all taxes, even if the taxes have been setup differently" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "For imprecise industrial touchscreens" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product categories will be displayed with pictures." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The hostname or ip address of the hardware proxy, Will be autodetected if left empty" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enable barcode scanning with a remotely connected barcode scanner" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Electronic Scale integration" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Automatically open the cashdrawer" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Bypass browser printing and prints via the hardware proxy" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt will automatically be printed at the end of each order" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt screen will be skipped if the receipt can be printed automatically." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a header in the printed receipt" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a footer in the printed receipt" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check the amount of the cashbox at opening and closing." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Bill Splitting in the Point of Sale" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allows to print the Bill before payment" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allow custom notes on Orderlines" msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "The restaurant floors served by this point of sale" msgstr "" @@ -2195,10 +2311,18 @@ msgstr "" msgid "Create a **Pricelist** for your point of sale. Each pricelist can contain several items with different prices and different dates. It can be done on all products or only on specific ones. Click on **Add an item**." msgstr "" +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "If unchecked, it will allow you to hide the pricelist without removing it." msgstr "" +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "Allow the end user to choose this price list" msgstr "" diff --git a/locale/sources/practical.pot b/locale/sources/practical.pot index e3f63683e..cf53b4973 100644 --- a/locale/sources/practical.pot +++ b/locale/sources/practical.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/project.pot b/locale/sources/project.pot index 4d5240929..952a1628b 100644 --- a/locale/sources/project.pot +++ b/locale/sources/project.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" diff --git a/locale/sources/purchase.pot b/locale/sources/purchase.pot index 78df4ce35..d936fbb92 100644 --- a/locale/sources/purchase.pot +++ b/locale/sources/purchase.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -1136,34 +1136,66 @@ msgstr "" msgid "Select your supplier in the **Vendor** menu, or create it on-the-fly by clicking on **Create and Edit**. In the **Order Date** field, select the date to which you wish to proceed to the actual order." msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Incoming Shipments" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Reference of the sales order or bid sent by the vendor. It's used to do the matching when you receive the products as this reference is usually written on the delivery order sent by your vendor." msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Depicts the date where the Quotation should be validated and converted into a purchase order." msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Reference of the document that generated this purchase order request (e.g. a sales order or an internal procurement request)" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "This will determine picking type of incoming shipment" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Put an address if you want to deliver directly from the vendor to the customer. Otherwise, keep empty to deliver to your own company." msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Technical field used to display the Drop Ship Address" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "International Commercial Terms are a series of predefined commercial terms used in international transactions." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 090a36cc4..4539214c5 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -529,7 +529,7 @@ msgid "**Track Service**: Timesheet on contracts. An analytic account will autom msgstr "" #: ../../sales/invoicing/services/support.rst:66 -msgid "There are different ways to track the service related to a sale order or product sold. With the above configuration, you can only sell one support contract per order. If your customer orders several service contracts on timesheet, you will have to split the quotation into several orders." +msgid "There are different ways to track the service related to a sales order or product sold. With the above configuration, you can only sell one support contract per order. If your customer orders several service contracts on timesheet, you will have to split the quotation into several orders." msgstr "" #: ../../sales/invoicing/services/support.rst:72 @@ -541,11 +541,11 @@ msgid "Managing support contract" msgstr "" #: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sale Orders" +msgid "Quotations and Sales Orders" msgstr "" #: ../../sales/invoicing/services/support.rst:83 -msgid "Once the product is created, you can create a quotation or a sale order with the related product. Once the quotation is confirmed and transformed into a sale order, your users will be able to record services related to this support contract using the timesheet application." +msgid "Once the product is created, you can create a quotation or a sales order with the related product. Once the quotation is confirmed and transformed into a sales order, your users will be able to record services related to this support contract using the timesheet application." msgstr "" #: ../../sales/invoicing/services/support.rst:93 @@ -557,7 +557,7 @@ msgid "To track the service you do on a specific contract, you should use the ti msgstr "" #: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sale order" +msgid "Control delivered support on the sales order" msgstr "" #: ../../sales/invoicing/services/support.rst:106 @@ -569,38 +569,34 @@ msgid "Upselling and renewal" msgstr "" #: ../../sales/invoicing/services/support.rst:118 -msgid "If the number of hours you performed on the support contract is bigger or equal to the number of hours the customer purchased, the sale order **Invoicing Status** is automatically set to **Upselling**. This means you have an opportunity to sell an extra contract to the customer since he used all his quota of service." +msgid "If the number of hours you performed on the support contract is bigger or equal to the number of hours the customer purchased, you are suggested to sell an extra contract to the customer since they used all their quota of service. Periodically (ideally once every two weeks), you should check the sales order that are in such a case. To do so, go to :menuselection:`Sales --> Invoicing --> Orders to Upsell`." msgstr "" -#: ../../sales/invoicing/services/support.rst:124 -msgid "Periodically (ideally once every two weeks), you should check the sales order that are in an upselling status. To do this, go to the :menuselection:`Sales --> Sales Order` menu and use the **Upselling** filter to get all orders that are in upselling." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:130 +#: ../../sales/invoicing/services/support.rst:127 msgid "If you use Odoo CRM, a good practice is to create an opportunity for every sale order in upselling invoice status so that you easily track your upselling effort." msgstr "" -#: ../../sales/invoicing/services/support.rst:134 -msgid "If you sell an extra support contract, you can either add a new line on the existing sale order (thus, you continue to timesheet on the same order) or create a new order (thus, people will timesheet their hours on the new contract). To unmark the sale order as **Upselling**, you can set the sale order as done and it will disappear from your upselling list." +#: ../../sales/invoicing/services/support.rst:131 +msgid "If you sell an extra support contract, you can either add a new line on the existing sales order (thus, you continue to timesheet on the same order) or create a new order (thus, people will timesheet their hours on the new contract). To unmark the sales order as **Upselling**, you can set the sales order as done and it will disappear from your upselling list." msgstr "" -#: ../../sales/invoicing/services/support.rst:141 +#: ../../sales/invoicing/services/support.rst:138 msgid "Special Configuration" msgstr "" -#: ../../sales/invoicing/services/support.rst:143 +#: ../../sales/invoicing/services/support.rst:140 msgid "When creating the product form, you may set a different approach to track the service:" msgstr "" -#: ../../sales/invoicing/services/support.rst:146 -msgid "**Create task and track hours**: in this mode, a task is created for every sale order line. Then when you do the timesheet, you don't record hours on a sale order/contract, but you record hours on a task (that represents the contract). The advantage of this solution is that it allows to sell several service contracts within the same sale order." +#: ../../sales/invoicing/services/support.rst:143 +msgid "**Create task and track hours**: in this mode, a task is created for every sales order line. Then when you do the timesheet, you don't record hours on a sales order/contract, but you record hours on a task (that represents the contract). The advantage of this solution is that it allows to sell several service contracts within the same sales order." msgstr "" -#: ../../sales/invoicing/services/support.rst:153 -msgid "**Manually**: you can use this mode if you don't record timesheets in Odoo. The number of hours you worked on a specific contract can be recorded manually on the sale order line directly, in the delivered quantity field." +#: ../../sales/invoicing/services/support.rst:150 +msgid "**Manually**: you can use this mode if you don't record timesheets in Odoo. The number of hours you worked on a specific contract can be recorded manually on the sales order line directly, in the delivered quantity field." msgstr "" -#: ../../sales/invoicing/services/support.rst:159 +#: ../../sales/invoicing/services/support.rst:156 msgid ":doc:`../../../inventory/settings/products/uom`" msgstr "" @@ -745,7 +741,7 @@ msgid ":menuselection:`eCommerce Order --> Invoice`" msgstr "" #: ../../sales/overview/main_concepts/invoicing.rst:69 -msgid "An eCommerce order will also trigger the creation of the order when it is fully paid. If you allow paying orders by check or wire transfer, Odoo only creates an order and the invoice will be triggered once the payment is received." +msgid "An eCommerce order will also trigger the creation of the invoice when it is fully paid. If you allow paying orders by check or wire transfer, Odoo only creates an order and the invoice will be triggered once the payment is received." msgstr "" #: ../../sales/overview/main_concepts/invoicing.rst:75 @@ -989,122 +985,62 @@ msgid "Manage your products" msgstr "" #: ../../sales/products_prices/products/import.rst:3 -msgid "How to import my products" +msgid "How to import products with categories and variants" msgstr "" -#: ../../sales/products_prices/products/import.rst:6 -msgid "How to start" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:8 -msgid "Download the following import templates:" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:10 -msgid "Partners: customers, vendors (no relation field, can be imported as is)" +#: ../../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 "Products (no relation field, can be imported as is)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:12 -msgid "Product Website Categories" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:13 -msgid "Product Attributes & Values" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:14 -msgid "Products with Categories & Attributes (3 & 4 must be imported first)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:16 -msgid "Download link: https://drive.google.com/drive/folders/0B1uIL9E_zXrrTEp5eGI2dXJSUjg?usp=sharing" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:18 -msgid "You can open them with any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, etc.)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:21 msgid "How to customize the file" msgstr "" -#: ../../sales/products_prices/products/import.rst:23 -msgid "Remove columns you don't need. Don't remove the first one (called *ID*, see why here below)." +#: ../../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:25 -msgid "Don't change labels of columns you want to import. Otherwse Odoo won't match the columns automatically." +#: ../../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:27 -msgid "Feel free to add new columns but the fields need to exist in Odoo. If Odoo fails in matching the column name with a field, you can make it manually when importing by browsing a list of available fields." +#: ../../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:30 -msgid "Once modified, keep your file in .csv format." +#: ../../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:33 -msgid "How to import the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:35 -msgid "Go to the Products menu in Sales, Purchase, Website Admin, etc." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:36 -msgid "Switch to list view (top-right corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:37 -msgid "Click the *Import* button (top-left corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:38 -msgid "Make sure all the columns match an existing field. If not select it manually from the drop-down list." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:40 -msgid "Press * Validate* to test the import." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:41 -msgid "If you get \"Everything seems valid.\" as result message, press *Import* to process the real import. Otherwise correct the issues spotted during the test." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:45 +#: ../../sales/products_prices/products/import.rst:24 msgid "Why an “ID” column" msgstr "" -#: ../../sales/products_prices/products/import.rst:47 +#: ../../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:50 +#: ../../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:52 +#: ../../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:53 +#: ../../sales/products_prices/products/import.rst:32 msgid "Import relation fields (see here below)." msgstr "" -#: ../../sales/products_prices/products/import.rst:56 +#: ../../sales/products_prices/products/import.rst:35 msgid "How to import relation fields" msgstr "" -#: ../../sales/products_prices/products/import.rst:58 +#: ../../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:62 +#: ../../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 "" diff --git a/locale/sources/website.pot b/locale/sources/website.pot index a87694c9e..fe33ce568 100644 --- a/locale/sources/website.pot +++ b/locale/sources/website.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-06-07 09:30+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -57,11 +57,11 @@ msgid ":doc:`google_analytics_dashboard`" msgstr "" #: ../../website/optimize/google_analytics_dashboard.rst:3 -msgid "How to track your website's traffic from your Odoo Dashboard" +msgid "How to track your website traffic from your Odoo Dashboard" msgstr "" #: ../../website/optimize/google_analytics_dashboard.rst:5 -msgid "You can follow your traffic's statistics straight from your Odoo Website Dashboard thanks to Google Analytics." +msgid "You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics." msgstr "" #: ../../website/optimize/google_analytics_dashboard.rst:8 @@ -77,34 +77,38 @@ msgid "Select Analytics API." msgstr "" #: ../../website/optimize/google_analytics_dashboard.rst:19 -msgid "Create a new project and give it a name (e.g. Google Analytics in Odoo)." +msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:24 +#: ../../website/optimize/google_analytics_dashboard.rst:25 msgid "Enable the API." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:29 -msgid "Create credentials to use in Odoo. Select *Web browser (Javascript)* as calling source and *User data* as kind of data." +#: ../../website/optimize/google_analytics_dashboard.rst:30 +msgid "Create credentials to use in Odoo." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:38 -msgid "Then enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by /google_account/authentication." +#: ../../website/optimize/google_analytics_dashboard.rst:35 +msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:47 +#: ../../website/optimize/google_analytics_dashboard.rst:41 +msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:51 msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:52 +#: ../../website/optimize/google_analytics_dashboard.rst:56 msgid "Finally you are provided with your Client ID. Copy and paste it in Odoo." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:57 +#: ../../website/optimize/google_analytics_dashboard.rst:61 msgid "Open your Website Dashboard in Odoo and link your Analytics account. to past your Client ID." msgstr "" -#: ../../website/optimize/google_analytics_dashboard.rst:63 +#: ../../website/optimize/google_analytics_dashboard.rst:67 msgid "As a last step, authorize Odoo to access Google API." msgstr "" diff --git a/locale/tr/LC_MESSAGES/accounting.po b/locale/tr/LC_MESSAGES/accounting.po new file mode 100644 index 000000000..ea950525d --- /dev/null +++ b/locale/tr/LC_MESSAGES/accounting.po @@ -0,0 +1,10522 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Güven YILMAZ <guvenyilmaz@outlook.com.tr>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../accounting.rst:5 +msgid "Accounting" +msgstr "Muhasebe" + +#: ../../accounting/bank.rst:3 +msgid "Bank & Cash" +msgstr "Banka & Nakit" + +#: ../../accounting/bank/feeds.rst:3 +msgid "Bank Feeds" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:3 +msgid "Import Coda statement files (Belgium only)" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:5 +msgid "" +"CODA is a file format for bank statements in Belgium. Most Belgian banks, as" +" well as the Isabel software, allows to download a CODA file with all your " +"bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:9 +msgid "" +"With Odoo, you can download an CODA file from your bank or accounting " +"software and import it directly in Odoo. This will create all bank " +"statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:14 +msgid "" +"Test now the feature `with this sample CODA file " +"<https://drive.google.com/file/d/0B5BDHVRYo-" +"q5UVVMbGRxUmtpVDg/view?usp=sharing>`__" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:17 +#: ../../accounting/bank/feeds/manual.rst:12 +#: ../../accounting/bank/feeds/ofx.rst:18 +#: ../../accounting/bank/feeds/paypal.rst:11 +#: ../../accounting/bank/feeds/qif.rst:19 +#: ../../accounting/bank/feeds/synchronize.rst:26 +#: ../../accounting/bank/misc/batch.rst:21 +#: ../../accounting/bank/misc/interbank.rst:14 +#: ../../accounting/bank/reconciliation/use_cases.rst:20 +#: ../../accounting/bank/setup/foreign_currency.rst:22 +#: ../../accounting/bank/setup/manage_cash_register.rst:9 +#: ../../accounting/others/adviser/assets.rst:24 +#: ../../accounting/others/adviser/budget.rst:18 +#: ../../accounting/others/analytic/purchases_expenses.rst:18 +#: ../../accounting/others/analytic/timesheets.rst:16 +#: ../../accounting/others/configuration.rst:3 +#: ../../accounting/others/multicurrencies/exchange.rst:16 +#: ../../accounting/others/multicurrencies/how_it_works.rst:15 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:22 +#: ../../accounting/others/taxes/B2B_B2C.rst:60 +#: ../../accounting/others/taxes/retention.rst:23 +#: ../../accounting/others/taxes/taxcloud.rst:12 +#: ../../accounting/payables/misc/employee_expense.rst:17 +#: ../../accounting/payables/pay/check.rst:11 +#: ../../accounting/payables/pay/sepa.rst:26 +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:30 +#: ../../accounting/payables/supplier_bills/manage.rst:31 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:15 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:24 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:20 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:19 +#: ../../accounting/receivables/customer_payments/check.rst:39 +#: ../../accounting/receivables/customer_payments/check.rst:103 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:40 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:113 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:31 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../accounting/bank/feeds/coda.rst:20 +msgid "Install the CODA feature" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:22 +msgid "" +"If you have installed the Belgian Chart of Account provided with Odoo, the " +"CODA import feature is already installed by default. In such a case, you can" +" move directly to the next section `Import your first coda file " +"<InstallCoda_>`_" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:27 +msgid "" +"If CODA is not activated yet, you need to do it first. In the Accounting " +"application, go to the menu :menuselection:`Configuration --> Settings`. " +"From the accounting settings, check the option **Import of Bank Statements " +"in .CODA Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:33 +msgid "Import your first CODA file" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:35 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"**Dashboard**, and click on the button **More** on the bank account card. " +"Then, click on **Import Statement** to load your first CODA file." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:43 +msgid "" +"Load your CODA file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:49 +#: ../../accounting/bank/feeds/ofx.rst:42 +#: ../../accounting/bank/feeds/qif.rst:43 +msgid "" +"If the file is successfully loaded, you will get redirected to the bank " +"reconciliation screen with all the transactions to reconcile." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:55 +msgid "Importing CODA files" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:57 +msgid "" +"After having imported your first file, the Odoo accounting dashboard will " +"automatically propose you to import more files for your bank. For the next " +"import, you don't need to go to the **More** button anymore, you can " +"directly click on the link **Import Statement**." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:65 +msgid "" +"Every time you get a statement related to a new customer / supplier, Odoo " +"will ask you to select the right contact to reconcile the transaction. Odoo " +"learns from that operation and will automatically complete the next payments" +" you get or make to these contacts. This will speed up a lot the " +"reconciliation process." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:72 +msgid "" +"Odoo is able to automatically detect if some files or transactions have " +"already been imported. So, you should not worry about avoiding to import two" +" times the same file: Odoo will check everything for you before creating new" +" bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:78 +#: ../../accounting/bank/feeds/qif.rst:65 +msgid ":doc:`ofx`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:79 +#: ../../accounting/bank/feeds/ofx.rst:64 +msgid ":doc:`qif`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:80 +#: ../../accounting/bank/feeds/ofx.rst:66 +#: ../../accounting/bank/feeds/qif.rst:67 +msgid ":doc:`synchronize`" +msgstr "" + +#: ../../accounting/bank/feeds/coda.rst:81 +#: ../../accounting/bank/feeds/ofx.rst:67 +#: ../../accounting/bank/feeds/qif.rst:68 +msgid ":doc:`manual`" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:3 +#: ../../accounting/bank/feeds/manual.rst:21 +msgid "Register bank statements manually" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:6 +#: ../../accounting/bank/reconciliation/configure.rst:6 +#: ../../accounting/bank/reconciliation/use_cases.rst:6 +#: ../../accounting/others/adviser/budget.rst:6 +#: ../../accounting/others/analytic/purchases_expenses.rst:6 +#: ../../accounting/others/multicurrencies.rst:3 +#: ../../accounting/others/multicurrencies/exchange.rst:6 +#: ../../accounting/others/multicurrencies/how_it_works.rst:6 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:6 +#: ../../accounting/others/reporting/customize.rst:6 +#: ../../accounting/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:8 +msgid "" +"With Odoo, you can import your bank statements, synchronize with your bank " +"but also register your bank statements manually." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:14 +msgid "" +"No special configuration is necessary to register invoices. All you need to " +"do is install the accounting app." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:24 +msgid "Create your Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:26 +msgid "" +"In the Dashboard, click on the button **New Statement** related to the bank " +"journal. If some reconciliations need to be done, the New Statement link " +"will be found underneath." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:33 +msgid "" +"Just fill in the fields according the the information written on your bank " +"statement. The reference can be filled in manually or you can leave it " +"empty. We recommend to fill in the partner to ease the reconciliation " +"process." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:38 +msgid "" +"The difference between the starting balance and the ending balance should be" +" equal to the computed balance." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:44 +msgid "When you are done, click on **Save**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:47 +msgid "Reconcile your Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:49 +msgid "" +"You can choose to directly reconcile the statement by clicking on the button" +" |manual04|" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:54 +msgid "" +"You can also start the reconciliation process from the dashboard by clicking" +" on **Reconcile # Items**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:60 +msgid "" +"Click on **Validate** to reconcile your bank statement. If the partner is " +"missing, Odoo will ask you to **select a partner**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:68 +msgid "Hit CTRL-Enter to reconcile all the balanced items on the sheets." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:71 +msgid "Close Bank Statements from the reconciliation" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:73 +msgid "" +"If the balance is correct, you can directly close the statement from the " +"reconciliation by clicking on |manual07|." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:78 +msgid "" +"Otherwise, click on |manual08| to open the statement and correct the issue." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:84 +msgid "Close Bank Statements" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:86 +msgid "" +"On the accounting dashboard, click on the More button of your bank journal, " +"then click on Bank Statements." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:92 +msgid "To close the bank statement, just click on **Validate**." +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:99 +msgid ":doc:`../reconciliation/use_cases`" +msgstr "" + +#: ../../accounting/bank/feeds/manual.rst:100 +#: ../../accounting/bank/reconciliation/use_cases.rst:115 +msgid ":doc:`../feeds/synchronize`" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:3 +msgid "Import OFX statement files" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:5 +msgid "" +"Open Financial Exchange (OFX) is a unified specification for the electronic " +"exchange of financial data between financial institutions, businesses and " +"consumers via the Internet." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:9 +msgid "" +"With Odoo, you can download an OFX file from your bank or accounting " +"software and import it directly in your Odoo instance. This will create all " +"bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:15 +msgid "" +"Test now the feature `with this sample OFX file " +"<https://drive.google.com/file/d/0B5BDHVRYo-q5Mmg4T3oxTWszeEk/view>`__" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:20 +msgid "" +"In order to import OFX statements, you need to activate the feature in Odoo." +" In the Accounting application, go to the menu :menuselection:`Configuration" +" --> Settings`. From the accounting settings, check the bank statements " +"option **Import in .OFX Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:28 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"Dashboard, and click on the **More** button of the bank account. Then, click" +" on **Import Statement** to load your first OFX file." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:36 +msgid "" +"Load your OFX file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:46 +msgid "Importing OFX files" +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:48 +#: ../../accounting/bank/feeds/qif.rst:49 +msgid "" +"After having imported your first file, the Odoo accounting dashboard will " +"automatically propose you to import more files for your bank. For the next " +"import, you don't need to go to the **More** menu anymore, you can directly " +"click on the link **Import Statement**." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:56 +#: ../../accounting/bank/feeds/qif.rst:57 +msgid "" +"Every time you get a statement related to a new customer / supplier, Odoo " +"will ask you to select the right contact to reconcile the transaction. Odoo " +"learns from that operation and will automatically complete the next payments" +" you get or do to these contacts. This will speed up a lot the " +"reconciliation process." +msgstr "" + +#: ../../accounting/bank/feeds/ofx.rst:65 +#: ../../accounting/bank/feeds/qif.rst:66 +msgid ":doc:`coda`" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:3 +msgid "How to synchronize your PayPal account with Odoo?" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:5 +msgid "" +"With Odoo, you can synchronize your PayPal account. That way, you don't have" +" to record all your PayPal transaction in your favorite accounting software." +" The synchronization is done every 4 hours, and you can start reconciling " +"PayPal payments in just a click." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:14 +msgid "Install the account_yodlee module" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:16 +msgid "" +"Start by installing the **account_yodlee** module, if it is not already " +"installed. To do that, got the the menu :menuselection:`Accounting --> " +"Configuration --> Settings` of the accounting application. In the section " +"**Bank & Cash**, set the option **Bank Interface - Sync your bank feeds " +"automatically**." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:25 +msgid "Click on the apply button once it's done." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:28 +msgid "Setup your PayPal account" +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:30 +msgid "" +"A PayPal account in Odoo is managed like a bank account. To setup your " +"PayPal account, use the menu :menuselection:`Configuration --> Bank " +"Accounts`. Create a new bank account and name it **PayPal**. In the bank " +"field, you can set **PayPal**." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:38 +msgid "" +"Once the PayPal account is created, go back to the **Accounting** dashboard " +"and click on the **Synchronize** button. In the dialog, choose **PayPal** as" +" the online institution and click on the configure button." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:45 +msgid "Then, you will have to provide your credentials to connect to PayPal." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:49 +msgid "" +"Your Paypal **must be in English** (if it is not the case you must change " +"the langage of your Paypal account) and if you use a Paypal business account" +" you must switch back to the old interface in order for it to work with " +"Online feeds (you can switch from new to old interface in your Paypal " +"account)." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:54 +msgid "" +"If you don't do this you will get a message either saying to put Paypal in " +"English or that the site is not supported." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:57 +msgid "" +"If you configured your Paypal account correctly you should get to the next " +"step of the Online feeds configuration. There you will have a screen with a " +"date to fetch transaction from and a list of account to choose. You must " +"choose the **Paypal balance** account." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:62 +msgid "" +"Once everything is done, you should see your PayPal transactions right in " +"Odoo and you can start reconciling your payments." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:65 +msgid "" +"Enjoy a full integration! You don't need to record transaction manually " +"anymore." +msgstr "" + +#: ../../accounting/bank/feeds/paypal.rst:69 +msgid "" +"You only have to provide your credentials the first time. Once done, Odoo " +"will synchronize with PayPal every 4 hours automatically." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:3 +msgid "Import QIF statement files" +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:5 +msgid "" +"Quicken Interchange Format (QIF) is an open specification for reading and " +"writing financial data to media (i.e. files). Although still widely used, " +"QIF is an older format than Open Financial Exchange (OFX) and you should use" +" the OFX version if you can export to both file formats." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:10 +msgid "" +"With Odoo, you can download a QIF file from your bank or accounting software" +" and import it directly in your Odoo instance. This will create all bank " +"statements." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:16 +msgid "" +"Test now the feature `with this sample QIF file " +"<https://drive.google.com/file/d/0B5BDHVRYo-q5X1ZkUWYzWmtCX0E/view>`__" +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:21 +msgid "" +"In order to import QIF statements, you need to activate the feature in Odoo." +" In the Accounting application, go to the menu :menuselection:`Configuration" +" --> Settings`. From the accounting settings, check the bank statements " +"option **Import in .QIF Format** and apply." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:29 +msgid "" +"Once you have installed this feature, you can setup your bank account to " +"allow importing bank statement files. To do this, go to the accounting " +"Dashboard, and click on the **More** button of the bank account. Then, click" +" on **Import Statement** to load your first QIF file." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:37 +msgid "" +"Load your QIF file in the following screen and click **Import** to create " +"all your bank statements." +msgstr "" + +#: ../../accounting/bank/feeds/qif.rst:47 +msgid "Importing QIF files" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:3 +msgid "How to synchronize Odoo with your bank?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:5 +msgid "" +"Odoo is able to synchronize directly with your bank in order to get all bank" +" statements imported automatically in Odoo every 4 hours. Before moving " +"forward in this tutorial, you should check if your bank is supported. You " +"can find it out from the `Odoo Accounting Features " +"<https://www.odoo.com/page/accounting-features>`__" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:13 +msgid "" +"Search for your bank name in the above page. If your bank appears in the " +"proposition, it means it is supported by Odoo. The countries which are fully" +" supported (meaning more than 95% of the banks) include: United States, " +"Canada, New Zealand, Austria. More than 30 countries are partially " +"supported, including: Colombia, India, France, Spain, etc." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:19 +msgid "In order to connect with the banks, Odoo uses two web-services:" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:21 +msgid "Plaid: for the main banks in the U.S." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:23 +msgid "Yodlee: for all other banks" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:29 +msgid "Odoo Online Users" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:31 +msgid "" +"If you we support banks of your country, the bank integration feature should" +" already been installed. If it's not installed, you can manually install the" +" module **account_yodlee**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:36 +msgid "Odoo Enterprise Users" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:38 +msgid "" +"If you plan to use a bank interface with your Odoo Enterprise subscription, " +"you don't have to do anything special, just make sure that your database is " +"registered with your Odoo Enterprise contract." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:42 +msgid "" +"you might want to check that you don't have a firewall/proxy blocking the " +"following addresses" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:44 +msgid "https://onlinesync.odoo.com/" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:45 +msgid "https://api.plaid.com/" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:49 +msgid "Sync your bank feeds" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:51 +msgid "" +"Once the Plaid or Yodlee interface is installed, you can connect Odoo to " +"your bank. To do that, click on **More** on the bank of your choice from the" +" accounting dashboard. In the menu, click on Settings to configure this bank" +" account." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:59 +msgid "" +"In the bank form, from the Bank Account tab, set the bank feeds option to " +"**Bank Synchronization**." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:65 +msgid "" +"Once it's done, go back to your accounting dashboard. You should see a " +"**Online Synchronization** button on your bank card. Click on this button " +"and fill in your bank credentials." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:69 +msgid "" +"Once you filled in your credentials, your bank feeds will be synchronized " +"every 4 hours." +msgstr "" + +#: ../../accounting/bank/misc.rst:3 +#: ../../accounting/payables/misc/employee_expense.rst:187 +msgid "Miscellaneous" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:3 +msgid "How to manage batch deposits of checks?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:5 +msgid "" +"When your company's collections group receives checks from customers they " +"will often place this money into their bank account in batches. As this " +"money has been received in a physical form, someone in your company must " +"manually bring the checks to the bank." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:10 +msgid "" +"The bank will ask for a deposit ticket (also referred to as deposit slip) to" +" be filled-in with the details of the checks or cash to be included in the " +"transactions." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:14 +msgid "" +"The bank statement will reflect the total amount that was deposited and the " +"reference to the deposit ticket, not the individual checks." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:17 +msgid "" +"Odoo assists you to prepare and print your deposit tickets, and later on " +"reconcile them with your bank statement easily." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:24 +msgid "Install the batch deposit feature" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:26 +msgid "" +"In order to use the batch deposit feature, you need the module **Batch " +"Deposit** to be installed." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:31 +msgid "" +"Usually, this module is automatically installed if checks are widely used in" +" your country." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:34 +msgid "" +"To verify that the **Batch Deposit** feature is installed, go to the " +":menuselection:`Configuration --> Settings` menu of the accounting " +"application. Check the feature: **Allow batch deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:42 +msgid "Activate the feature on your bank accounts" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:44 +msgid "" +"Once you have installed this feature, Odoo automatically activate bank " +"deposits on your main bank accounts." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:47 +msgid "" +"To control which bank account can do batch deposit and which can not, go to " +"the journal that you defined to pay your checks, usually called 'Checks' or " +"'Bank' (see :doc:`../../receivables/customer_payments/check`, in the " +"Accounting apps, :menuselection:`Configuration --> Accounting --> Journals`." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:52 +msgid "" +"In **Advanced Settings** tab, in section **Miscellaneous**, set Debit Method" +" to **Batch Deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:58 +msgid "" +"If you check **Batch Deposit** in your debit method field, it means that " +"payments created using this Journal (called Payment method when you want to " +"make or receive a payment) will be applicable for the creation of Batch " +"Deposits afterwards." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:64 +msgid "From checks received to the bank" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:67 +msgid "Receive customer checks" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:69 +msgid "" +"Once your record checks received, record them on the bank account on which " +"you plan to deposit them. Once you select the bank account (or check journal" +" is you configured Odoo that way), Odoo proposes you to use a batch deposit." +" Select this option if you plan to deposit the check to your bank." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:78 +msgid "In the memo field, you can set the reference of the check." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:82 +msgid "" +"payments can be registered from the menu :menuselection:`Sales --> " +"Payments`, or directly on the related invoice, using the **Register " +"Payment** button." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:86 +msgid "Prepare a batch deposit" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:88 +msgid "" +"From the Accounting application, go to the menu :menuselection:`Sales --> " +"Batch Deposit`, and create a new **Batch Deposit**." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:94 +msgid "" +"Select the bank, then select the payments (checks) you want to add in this " +"deposit. By default, Odoo proposes you all the checks that have not been " +"deposit yet. That way, you can verify that you do not forget or lost a " +"check." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:102 +msgid "" +"You can then print the batch deposit, which will be very useful to prepare " +"the deposit slip that the bank usually requires to complete." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:106 +msgid "Reconciling the Deposit with the Bank Statement" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:108 +msgid "" +"When you process the bank statement reconciliation you will see the deposit " +"ticket number referenced in the statement. When the reconciliation process " +"is run, the user will be able to select the batch deposit that matches with " +"the bank statement line." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:116 +msgid "" +"If you select a batch deposit, Odoo will automatically fills all the checks " +"contained in this deposit for the matching. (2 checks were in this batch " +"deposit the example below)" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:124 +#: ../../accounting/payables/pay/sepa.rst:113 +msgid "Troubleshooting" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:127 +msgid "I don't see the batch deposit link on bank statements?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:129 +msgid "" +"If you don't have a batch deposit link in your bank statement, there could " +"be two reasons:" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:132 +msgid "" +"After having installed the batch deposit features, you need to reload the " +"page so that the browser is aware of this new feature. Just click the reload" +" button of your browser." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:136 +msgid "You do not have a batch deposit created for this bank account." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:139 +msgid "What happens if a check was refused?" +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:141 +msgid "" +"If you have a smaller amount in your bank statement than the actual amount " +"in your batch deposit, it probably means that one of your check has been " +"refused." +msgstr "" + +#: ../../accounting/bank/misc/batch.rst:145 +msgid "" +"In this case, click on the line related to this check to remove it from the " +"bank statement matching." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:3 +msgid "How to do a bank wire transfer from one bank to another?" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:5 +msgid "" +"A company might have several bank accounts or cash registers. Within odoo it" +" is possible to handle internal transfers of money with only a couple of " +"clicks." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:9 +msgid "" +"We will take the following example to illustrate. My company has two bank " +"accounts and I want to transfer 50.000 euros from one of our bank accounts " +"to the another one." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:17 +msgid "Check your Chart of Accounts and default transfer account" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:19 +msgid "" +"To handle internal transfers you need a transfer account in your charts of " +"account. Odoo will generate an account automatically based on the country of" +" your chart of account. To parameter your chart of account and check the " +"default transfer account go into your the accounting module, select " +":menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:25 +msgid "" +"Your chart of accounts will be pre-installed depending on the country " +"specified during your registration, it cannot be changed." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:31 +msgid "" +"The default transfer account will automatically be generated as well " +"depending on your country's legislation. If necessary it can be modified " +"from the same page." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:39 +msgid "Create a second bank account / Journal" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:41 +msgid "" +"Before we can register an internal transfer we need to add a new bank to our" +" accounting dashboard. To do so enter the accounting module, click on " +":menuselection:`Configuration --> Bank Accounts`. Create a new bank account." +" You should fill in the **Account Number**. You can also create and edit " +"your bank to specify your bank's details." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:50 +msgid "By saving the changes you now have 2 bank accounts." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:56 +msgid "Register an internal transfer from one bank to another." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:58 +msgid "" +"We will now transfer 50.000 euros from our **Bank** to our **Bank BE57 0633 " +"9533 1498** account." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:62 +msgid "Log an internal transfer" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:64 +msgid "" +"The first step is to register the internal paiement. To do so, go into your " +"accounting dashboard. click on the **more** button of one of your banks and " +"select :menuselection:`New --> Internal transfer`." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:71 +msgid "" +"Create a new payment. The payment type will automatically be set to internal" +" transfer. Select the **Bank** you want to transfer to, specify the " +"**Amount** and add a **Memo** if you wish." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:76 +msgid "" +"The memo is important if you wish to automatically reconcile (`see " +"<Reconcile_>`_)." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:81 +msgid "Save and confirm the changes to register the payment." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:83 +msgid "" +"In terms of accounting the money is now booked in the transfer account. " +"We'll need to import bank statements to book the money in the final " +"accounts." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:90 +msgid "Import bank statements and reconcile" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:92 +msgid "" +"Note that the bank balance computed by Odoo is different that the last " +"statement of your bank." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:98 +msgid "" +"That is because we did not import the bank statement confirming the " +"departure and arrival of the money. It's thus necessary to import your bank " +"statement and reconcile the payment with the correct bank statement line. " +"Once you receive your bank statements click the **new statement** button of " +"the corresponding bank to import them." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:107 +msgid "" +"Fill in your **Transactions line**. Once done, Odoo will display a " +"**Computed Balance**. that computed balance is the theorical end balance of " +"your bank account. If it's corresponding to the bank statement, it means " +"that no errors were made. Fill in the **Ending balance** and click on the " +"**Reconcile** button." +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:115 +msgid "The following window will open:" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:120 +msgid "" +"You need to choose counterparts for the paiement. Select the correct bank " +"statement line corresponding to the paiement and click on the **reconcile** " +"button. Close the statement to finish the transaction" +msgstr "" + +#: ../../accounting/bank/misc/interbank.rst:127 +msgid "" +"The same steps will need to be repeated once you receive your second bank " +"statement. Note that if you specify the correct amount, and the same memo in" +" both bank statement and payment transaction then the reconciliation will " +"happen automatically." +msgstr "" + +#: ../../accounting/bank/reconciliation.rst:3 +#: ../../accounting/others/reporting/main_reports.rst:153 +#: ../../accounting/overview/main_concepts/memento.rst:177 +#: ../../accounting/overview/main_concepts/terminologies.rst:19 +msgid "Bank Reconciliation" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:3 +msgid "Configure model of entries" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:8 +msgid "" +"In Odoo you have the possibility to pre-fill some accounting entries in " +"order to easily reconcile recurrent entries such as bank fees." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:11 +msgid "" +"We will take the following example to illustrate the concept : Every month " +"my company receives a bank fee cost, which depends of our bank account " +"current balance. This fee is thus variable." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:16 +msgid "Create Reconciliation Models" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:18 +msgid "" +"First, we need to configure two model reconciliation entries. To do so, go " +"to the accounting application dashboard. On your bank journal, click on " +":menuselection:`More --> Reconciliation Models`." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:25 +msgid "" +"We want to be able to book our bank fees easily. Our bank deducts fees " +"depending on our balance, meaning that it can vary every month." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:28 +msgid "" +"We create a button Label called Bank fees, select the correct account to " +"book those fees. Moreover we also need to specify that the amount type is " +"\"Percentage of balance\" with an Amount of 100%. This parameter will tell " +"Odoo to take the entire fee into account." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:36 +msgid "Save your changes when you are done." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:40 +msgid "" +"If the amount of your bank fee is fixed, you can as well select **Fixed** " +"under amount type and specify the amount in the amount tap." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:45 +msgid "" +"You can also use this functionality to handle discounts. Please refer to " +":doc:`../../receivables/customer_invoices/cash_discounts`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:49 +msgid "Register your payments based on a reconciliation model" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:51 +msgid "" +"Register your payment by importing your bank statements that will be " +"impacted by the payment of the bank fee." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:54 +msgid "" +"When doing the reconciliation, you can select an open balance and click the " +"**Reconciliation Model** button (in this case, **Bank Fees**) to get all the" +" relevant data instantly." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:61 +msgid "Finally, click on **Reconcile** to finish the process." +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:65 +#: ../../accounting/bank/reconciliation/use_cases.rst:116 +msgid ":doc:`../feeds/manual`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:66 +#: ../../accounting/bank/reconciliation/use_cases.rst:114 +msgid ":doc:`../feeds/ofx`" +msgstr "" + +#: ../../accounting/bank/reconciliation/configure.rst:67 +msgid ":doc:`use_cases`" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:3 +msgid "Use cases in the bank reconciliation process?" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:8 +msgid "" +"Linking your bank statements with your accounting can be a lot of work. You " +"need to find invoices back, relate payments and that amount of " +"administration can cast a lot of time. Luckily, with Odoo you can very " +"easily link your invoices or any other payment with your bank statements." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:14 +msgid "Two reconciliation processes exist in Odoo." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:16 +msgid "We can directly register a payment on the invoices" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:17 +msgid "We can reconcile open invoices with bank statements" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:22 +msgid "" +"No special configuration is necessary to register invoices. All we need to " +"do is install the accounting app." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:29 +msgid "User cases" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:32 +msgid "Case 1: Payments registration" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:34 +msgid "" +"We received the payment proof for our invoice of 2100 euros issued to Smith " +"& Co." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:37 +msgid "" +"We start at our issued Invoice of 2100 euros for Smith & Co. Because the " +"sold product is a service we demand an immediate payment. Our accountant " +"only handles the bank statements at the end of week, so we have to mark the " +"invoice as paid so we can remember we can start the service with our " +"customer." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:43 +msgid "" +"Our customer send us a payment confirmation. We can thus register a payment " +"and mark the invoice as paid." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:49 +msgid "" +"By clicking on **register payment,** we are telling Odoo that our customer " +"paid the Invoice. We thus have to specify the amount and the payment method" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:56 +msgid "" +"We can always find the payment back from the Invoice by clicking on the " +":menuselection:`Info --> Open Payment`." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:62 +msgid "" +"The invoice has been paid and **the reconciliation has been done " +"automatically.**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:66 +msgid "Case 2: Bank statements reconciliations" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:68 +msgid "" +"We start at our issued Invoice of 3000 euros for Smith & Co. Let's also " +"assume that other Invoices are open for different customers." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:74 +msgid "" +"We receive our bank statement and not only the invoice of Smith & Co has " +"been paid, the one of Buzz of 92 euros as well." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:77 +msgid "" +"**Import** or **Create** the bank statements. Please refer to the documents " +"from the Bank Feeds section." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:83 +msgid "On the dashboard, click on **Reconcile # Items**" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:88 +msgid "" +"If everything was right (correct partner name, right amount) odoo will do " +"the reconciliations **automatically**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:94 +msgid "If some issues are found, you will need to take **manual actions**." +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:96 +msgid "" +"For example, if the partner is missing from your bank statement, just fill " +"it in :" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:102 +msgid "" +"If the payment is done with a down payment, just check if it is all right " +"and validate all related payments :" +msgstr "" + +#: ../../accounting/bank/reconciliation/use_cases.rst:110 +msgid "Hit CTRL-Enter to reconcile all the balanced items in the sheet." +msgstr "" + +#: ../../accounting/bank/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:3 +msgid "How to setup a new bank account?" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:5 +msgid "" +"In Odoo, you can manage multiple bank accounts. In this page, you will be " +"guided in the creation, modification or deletion of a bank or a credit card " +"account." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:10 +msgid "Edit a bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:12 +msgid "" +"To ease the process, a bank account is already there. We suggest you to edit" +" it first before filling your own bank information." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:15 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts` and " +"click on the **Bank** item. Edit it." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:23 +msgid "" +"Odoo will detect the bank account type (e.g. IBAN) to allow some payment " +"method like SEPA" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:28 +msgid "Create a bank account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:30 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Bank Accounts`. Click" +" on **create** and fill in the form. You can decide to show the bank account" +" number in you intend to send documents like sales orders or invoices. " +"Select the payments methods you support with this bank account." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:41 +msgid "" +"If you are working in a multi-company environnement, you'll have to switch " +"the company on your user preferences in order to add, edit or delete bank " +"accounts from another company." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:49 +msgid "View *Bank Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:60 +msgid "" +"The initial balance of a bank statement will be set to the closing balance " +"of the previous one within the same journal automatically." +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:63 +msgid "Delete a bank account or credit card account" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:65 +msgid "" +"From the list of bank accounts, select items to delete and delete them from " +"the action menu or go to the form and delete a single item from the action " +"menu" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:3 +msgid "How to manage a bank in a foreign currency?" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:5 +msgid "" +"In Odoo, every transaction is recorded in the default currency of the " +"company. Reports are all based on the currency of the company. But for " +"transactions occurring in another currency, Odoo stores both the value in " +"the currency of the company and the value in the currency of the " +"transaction." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:11 +msgid "" +"When you have a bank account in a foreign currencies, for every transaction," +" Odoo stores two values:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:14 +msgid "The debit/credit in the currency of the company" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:16 +msgid "The debit/credit in the currency of the bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:18 +msgid "" +"Currency rates are updated automatically using yahoo.com, or the European " +"Central bank web-services." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:25 +msgid "Activate the multi-currency feature" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:27 +msgid "" +"In order to allow your company to work with multiple currencies, you should " +"activate the multi-currency mode. In the accounting application, go into " +":menuselection:`Configuration --> Settings --> Accounting & Finance " +"Features` make sure the **Allow Multi-currencies** box is ticked. Provide a " +"**Currency Exchange Gain / Loss** account, then click on **Apply**." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:34 +msgid "Configure currencies" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:36 +msgid "" +"Once the Odoo is configured to support multiple currencies, you should " +"activate the currencies you plan to work with. To do that, go the menu " +":menuselection:`Configuration --> Currencies`. All the currencies are " +"created by default, but you should activate the ones you plan to support. " +"(to activate a currency, check his active field)" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:42 +msgid "" +"After having activated the currencies, you can configure the parameters to " +"automate the currency rate update. These options are also in the settings of" +" the Accounting application, in the bottom of the page:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:49 +msgid "Click on the **Update Now** link to update the currency rates now." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:52 +msgid "Create a new bank account" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:54 +msgid "" +"In the accounting application, we first go to :menuselection:`Configuration " +"--> Accounting / Bank account`, and we create a new one." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:60 +msgid "" +"Once you save this bank account, Odoo will create all the documents for you:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:63 +msgid "An account in the trial balance" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:65 +msgid "A journal in your dashboard" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:67 +msgid "" +"Information about the bank account in the footer of your invoices if checked" +" the box **Show in Invoices Footer**" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:71 +msgid "Example: A vendor bill in a foreign currency" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:73 +msgid "" +"Based on the above example, let's assume we receive the following bill from " +"a supplier in China." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:76 +msgid "" +"In the :menuselection:`Purchase --> Vendor Bills` , this is what you could " +"see:" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:81 +msgid "" +"Once you are ready to pay this bill, click on register payment on the bill " +"to record a payment." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:87 +msgid "" +"That's all you have to do. Odoo will automatically post the foreign exchange" +" gain or loss at the reconciliation of the payment with the invoice, " +"depending if the currency rate increased or decreased between the invoice " +"and the payment date." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:92 +msgid "" +"Note that you can pay a foreign bill with another currency. In such a case, " +"Odoo will automatically convert between the two currencies." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:96 +msgid "Customers Statements" +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:98 +msgid "" +"Customers and vendor statements are managed in the currency of the invoice. " +"So, the amount due by your customer (to your vendor) is always expressed in " +"the currency of the invoice." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:102 +msgid "" +"If you have several invoices with different currencies for the same " +"customer, Odoo will split the customer statement by currency, as shown in " +"the report below." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:109 +msgid "" +"In the above report, the account receivable associated to Camptocamp is not " +"managed in a secondary currency, which means that it keeps every transaction" +" in his own currency. If you prefer, you can set the account receivable of " +"this customer with a secondary currency and all his debts will automatically" +" be converted in this currency." +msgstr "" + +#: ../../accounting/bank/setup/foreign_currency.rst:115 +msgid "" +"In such a case, the customer statement always has only one currency. In " +"general, this is not what the customer expect as he prefers to see the " +"amounts in the currency of the invoices he received;" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:3 +msgid "How to manage a cash register?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:5 +msgid "" +"The cash register is a journal to register receivings and payments " +"transactions. It calculates the total money in and out, computing the total " +"balance." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:14 +msgid "" +"Configure the Cash journal in :menuselection:`Accounting --> Configuration " +"--> Journals`." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:17 +msgid "" +"In the tab Journal Entries, the Default Debit and Credit Account can be " +"configured as well as the currency of the journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'Sale' for customer invoices journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'Purchase' for vendor bills journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Select 'Cash' or 'Bank' for journals that are used in customer or vendor " +"payments." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Select 'General' for miscellaneous operations journals." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company related to this journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The journal entries of this journal will be named using this prefix." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Check this box if you don't want to share the same sequence for invoices and" +" refunds made from this journal" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field contains the information related to the numbering of the journal " +"entries of this journal." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field contains the information related to the numbering of the refund " +"entries of this journal." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for debit amount" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for credit amount" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The currency used to enter statement" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Means of payment for collecting money. Odoo modules offer various payments " +"handling facilities, but you can always use the 'Manual' payment method in " +"order to manage payments outside of the software." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Means of payment for sending money. Odoo modules offer various payments " +"handling facilities, but you can always use the 'Manual' payment method in " +"order to manage payments outside of the software." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"If this box is checked, the system will try to group the accounting lines " +"when generating them from invoices." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Used to register a profit when the ending balance of a cash register differs" +" from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Used to register a loss when the ending balance of a cash register differs " +"from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Whether this journal should be displayed on the dashboard or not" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Technical feature used to know whether check printing was enabled as payment" +" method." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Checks numbering sequence." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check this option if your pre-printed checks are not numbered." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Sequence number of the next printed check." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Check this box if this journal define a payment method that can be used in a" +" point of sale." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field depicts the maximum difference allowed between the ending balance" +" and the theoretical cash when closing a session, for non-POS managers. If " +"this maximum is reached, the user will have an error message at the closing " +"of his session saying that he needs to contact his manager." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:25 +msgid "Usage" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:28 +msgid "How to register cash payments?" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:30 +msgid "" +"To register a cash payment specific to another customer, you should follow " +"these steps:" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:33 +msgid "" +"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register " +"Transactions`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:36 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:38 +msgid "" +"Register the transactions, specifying the customers linked to the " +"transaction" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:41 +msgid "Put money in" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:43 +msgid "" +"Put money in is used to placed your cash manually before starting your " +"transactions. From the Register Transactions window, go to " +":menuselection:`More --> Put money in`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:51 +msgid "Take money out" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:53 +msgid "" +"Take money out is used to collect/get yor your cash manually after ending " +"all your transactions. From the Register Transaction windows, go to " +":menuselection:`More --> Take money out`" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:60 +msgid "" +"The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../accounting/others.rst:3 +#: ../../accounting/receivables/customer_invoices/overview.rst:108 +msgid "Others" +msgstr "" + +#: ../../accounting/others/adviser.rst:3 +msgid "Adviser" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:3 +msgid "Manage your fixed assets" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:5 +msgid "" +"The \"Assets\" module allows you to keep track of your fixed assets like " +"machinery, land and building. The module allows you to generate monthly " +"depreciation entries automatically, get depreciation board, sell or dispose " +"assets and perform reports on your company assets." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:10 +msgid "" +"As an example, you may buy a car for $36,000 (gross value) and you plan to " +"amortize it over 36 months (3 years). Every months (periodicity), Odoo will " +"create a depreciation entry automatically reducing your assets value by " +"$1,000 and passing $1,000 as an expense. After 3 years, this assets accounts" +" for $0 (salvage value) in your balance sheet." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:16 +msgid "" +"The different types of assets are grouped into \"Assets Types\" that " +"describe how to deprecate an asset. Here are two examples of assets types:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:20 +msgid "Building: 10 years, yearly linear depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:21 +msgid "Car: 5 years, monthly linear depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:27 +msgid "Install the Asset module" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:29 +msgid "Start by *installing the Asset module.*" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:31 +msgid "" +"Once the module is installed, you should see two new menus in the accounting" +" application:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:34 +msgid ":menuselection:`Adviser --> Assets`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:35 +msgid ":menuselection:`Configuration --> Asset Types`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:37 +msgid "" +"Before registering your first asset, you must :ref:`define your Asset Types " +"<accounting/adviser/assets_management/defining>`." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:43 +msgid "Defining Asset Types" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:45 +msgid "" +"Asset type are used to configure all information about an assets: asset and " +"deprecation accounts, amortization method, etc. That way, advisers can " +"configure asset types and users can further record assets without having to " +"provide any complex accounting information. They just need to provide an " +"asset type on the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:51 +msgid "" +"You should create asset types for every group of assets you frequently buy " +"like \"Cars: 5 years\", \"Computer Hardware: 3 years\". For all other " +"assets, you can create generic asset types. Name them according to the " +"duration of the asset like \"36 Months\", \"10 Years\", ..." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:56 +msgid "" +"To define asset types, go to :menuselection:`Configuration --> Asset Types`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:63 +msgid "Create assets manually" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:65 +msgid "" +"To register an asset manually, go to the menu :menuselection:`Adviser --> " +"Assets`." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:71 +msgid "" +"Once your asset is created, don't forget to Confirm it. You can also click " +"on the Compute Depreciation button to check the depreciation board before " +"confirming the asset." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:77 +msgid "" +"if you create asset manually, you still need to create the supplier bill for" +" this asset. The asset document will only produce the depreciation journal " +"entries, not those related to the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:82 +msgid "Explanation of the fields:" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "When an asset is created, the status is 'Draft'." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"If the asset is confirmed, the status goes in 'Running' and the depreciation" +" lines can be posted in the accounting." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"You can manually close an asset when the depreciation is over. If the last " +"line of depreciation is posted, the asset automatically goes in that status." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross value of asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "It is the amount you plan to have that you cannot depreciate." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Choose the method to use to compute the amount of depreciation lines." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Linear: Calculated on basis of: Gross Value / Number of Depreciations" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Degressive: Calculated on basis of: Residual Value * Degressive Factor" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Choose the method to use to compute the dates and number of depreciation " +"lines." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Number of Depreciations: Fix the number of depreciation lines and the time" +" between 2 depreciations." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Ending Date: Choose the time between 2 depreciations and the date the " +"depreciations won't go beyond." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Indicates that the first depreciation entry for this asset have to be done " +"from the purchase date instead of the first January / Start date of fiscal " +"year" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The number of depreciations needed to depreciate your asset" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The amount of time between two depreciations, in months" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:88 +msgid "Try creating an *Asset* in our online demonstration" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:91 +msgid "Create assets automatically from a supplier bill" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:93 +msgid "" +"Assets can be automatically created from supplier bills. All you need to do " +"is to set an asset category on your bill line. When the user will validate " +"the bill, an asset will be automatically created, using the information of " +"the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:100 +msgid "" +"Depending on the information on the asset category, the asset will be " +"created in draft or directly validated\\ *.* It's easier to confirm assets " +"directly so that you won't forget to confirm it afterwards. (check the field" +" *Skip Draft State* on *Asset Category)* Generate assets in draft only when " +"you want your adviser to control all the assets before posting them to your " +"accounts." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:107 +msgid "" +"if you put the asset on the product, the asset category will automatically " +"be filled in the supplier bill." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:111 +msgid "How to deprecate an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:113 +msgid "" +"Odoo will create depreciation journal entries automatically at the right " +"date for every confirmed asset. (not the draft ones). You can control in the" +" depreciation board: a green bullet point means that the journal entry has " +"been created for this line." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:118 +msgid "" +"But you can also post journal entries before the expected date by clicking " +"on the green bullet and forcing the creation of related depreciation entry." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:125 +msgid "" +"In the Depreciation board, click on the red bullet to post the journal " +"entry. Click on the :guilabel:`Items` button on the top to see the journal " +"entries which are already posted." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:130 +msgid "How to modify an existing asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:132 +msgid "Click on :guilabel:`Modify Depreciation`" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:133 +msgid "Change the number of depreciation" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:135 +msgid "Odoo will automatically recompute a new depreciation board." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:138 +msgid "How to record the sale or disposal of an asset?" +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:140 +msgid "" +"If you sell or dispose an asset, you need to deprecate completly this asset." +" Click on the button :guilabel:`Sell or Dispose`. This action will post the " +"full costs of this assets but it will not record the sales transaction that " +"should be registered through a customer invoice." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:3 +msgid "How to manage a financial budget?" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:8 +msgid "" +"Managing budgets is an essential part of running a business. It allows you " +"to measure your actual financial performance against the planned one. Odoo " +"manages its budgets using both General and Analytic Accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:12 +msgid "" +"We will use the following example to illustrate. We just started a project " +"with Smith&Co and we would like to budget the incomes and expenses of that " +"project. We plan to have a revenue of 1000 and we don't want to spend more " +"than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:20 +msgid "" +"First we need to install the relevant apps to use budgeting. The main module" +" is the accounting app. Go in the app module and install the **Accounting " +"and Finance** app." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:27 +msgid "" +"Further configuration is as well necessary. Go to :menuselection:`Accounting" +" module --> Configuration --> Settings` and enable the **Budget management**" +" feature" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:34 +msgid "" +"If we want to be precise and point specific invoices and vendors bills to " +"our budget, you should enable the Analytic accounting as well. If we don't " +"we will only be able to budget the total amount of general accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:40 +msgid "Budgetary Positions" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:42 +msgid "" +"Budgetary positions are the general accounts for which you want to keep " +"budgets (typically expense or income accounts). They need to be defined so " +"Odoo can know it which accounts he needs to go get the budget information. " +"Some might be already installed with your chart of accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:48 +msgid "" +"To define the positions enter the :menuselection:`Accounting module --> " +"Configuration --> Budgetary Positions`." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:51 +msgid "" +"For our example we need to define what accounts relates to our project's " +"expenses. Create a position and add items to select the accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:57 +msgid "" +"In this case we select the three relevant accounts used wherein we will book" +" our expenses." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:63 +msgid "Click on *Select*." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:68 +msgid "Save the changes to confirm your Budgetary position." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:70 +msgid "" +"Repeat this steps to create a revenue budgetary position. Only in this case " +"select the relevant income accounts." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:74 +msgid "Analytical account" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:76 +msgid "" +"If you wish to point specific invoices or vendor bills to your budget you " +"need to use analytical accounting. Odoo needs to know which costs or " +"expenses are relevant to a specified budget. To do so we need to link our " +"invoices and expenses to a defined analytical account. Create an analytical " +"account by entering the Accounting module and clicking " +":menuselection:`Advisers --> Analytic Accounts --> Open Charts`. Create a " +"new Account called Smith&Co project and select the related partner." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:88 +msgid "Set a budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:90 +msgid "" +"Let's now set our targets for our budget. We specified that we expect to " +"gain 1000 with this project and we would like not to spend more than 700." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:94 +msgid "" +"To set those targets, enter the accounting app, select " +":menuselection:`Advisers --> Budgets` and create a new Budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:97 +msgid "" +"We have to give a name to the budget. In this case we'll call it \"Smith " +"Project\". Select the period wherein the budget will be applicable. Next add" +" an item to specify your targets in the Budget Line." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:104 +msgid "" +"Select the Budgetary Position related to the Budget Line. In other words, " +"select the position that points to the accounts you want to budget. In this " +"case we will start with our 700 maximum charge target. Select the \"Cost\" " +"Budgetary Position and specify the Planned Amount. As we are recording a " +"cost, we need to specify a **negative amount**. Finally, select the " +"corresponding analytic account." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:114 +msgid "" +"Click on **Save & new** to input the revenue budget. The Budgetary Position " +"is Revenue and the Planned Amount is 1000. Save and close" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:117 +msgid "You'll need to **Confirm** and **Approve** the budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:120 +msgid "Check your budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:122 +msgid "" +"You can check your budget at any time. To see the evolution, let's book some" +" Invoices and Vendors Bills." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:127 +msgid "" +"if you use analytical accounts remember that you need to specify the account" +" in the invoice and / or purchase line." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:131 +msgid "for more information about booking invoices and purchase orders see:" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:133 +msgid ":doc:`../../receivables/customer_invoices/overview`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:134 +msgid ":doc:`../../../purchase/overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:136 +msgid "Go back in the budget list and find the Smith Project." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:138 +msgid "" +"Via the analytical account, Odoo can account the invoice lines and purchase " +"lines booked in the accounts and will display them in the **Practical " +"Amount** column." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:147 +msgid "" +"The theoretical amount represents the amount of money you theoretically " +"could have spend / should have received in function of the date. When your " +"budget is 1200 for 12 months (january to december), and today is 31 of " +"january, the theoretical amount will be 1000, since this is the actual " +"amount that could have been realised." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:3 +msgid "How to do a year end in Odoo? (close a fiscal year)" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:5 +msgid "" +"Before going ahead with closing a fiscal year, there are a few steps one " +"should typically take to ensure that your accounting is correct, up to date," +" and accurate:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:9 +msgid "" +"Make sure you have fully reconciled your **bank account(s)** up to year end " +"and confirm that your ending book balances agree with your bank statement " +"balances." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:13 +msgid "Verify that all **customer invoices** have been entered and approved." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:15 +msgid "Confirm that you have entered and agreed all **vendor bills**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:17 +msgid "Validate all **expenses**, ensuring their accuracy." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:19 +msgid "" +"Corroborate that all **received payments** have been entered and recorded " +"accurately." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:23 +msgid "Year-end checklist" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:25 +msgid "Run a **Tax report**, and verify that your tax information is correct." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:27 +msgid "Reconcile all accounts on your **Balance Sheet**:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:29 +msgid "" +"Agree your bank balances in Odoo against your actual bank balances on your " +"statements. Utilize the **Bank Reconciliation** report to assist with this." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:33 +msgid "" +"Reconcile all transactions in your cash and bank accounts by running your " +"**Aged Receivables** and **Aged Payables** reports." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:36 +msgid "" +"Audit your accounts, being sure to fully understand the transactions " +"affecting them and the nature of the transactions, making sure to include " +"loans and fixed assets." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:40 +msgid "" +"Run the optional **Payments Matching** feature, under the **More** dropdown " +"on the dashboard, validating any open **Vendor Bills** and **Customer " +"Invoices** with their payments. This step is optional, however it may assist" +" the year-end process if all outstanding payments and invoices are " +"reconciled, and could lead finding errors or mistakes in the system." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:47 +msgid "" +"Your accountant/bookkeeper will likely verify your balance sheet items and " +"book entries for:" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:50 +msgid "" +"Year-end manual adjustments, using the **Adviser Journal Entries** menu (For" +" example, the **Current Year Earnings** and **Retained Earnings** reports)." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:54 +msgid "**Work in Progress**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:56 +msgid "**Depreciation Journal Entries**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:58 +msgid "**Loans**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:60 +msgid "**Tax adjustments**." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:62 +msgid "" +"If your accountant/bookkeeper is going through end of the year auditing, " +"they may want to have paper copies of all balance sheet items (such as " +"loans, bank accounts, prepayments, sales tax statements, etc...) to agree " +"these against your Odoo balances." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:67 +msgid "" +"During this process, it is good practice to set the **Lock date for Non-" +"Advisers** to the last day of the preceding financial year, which is set " +"under the accounting configuration. This way, the accountant can be " +"confident that nobody is changing the previous year transactions while " +"auditing the books." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:77 +msgid "Closing the fiscal year" +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:79 +msgid "" +"In Odoo there is no need to do a specific year end closing entry in order to" +" close out income statement accounts. The reports are created in real-time, " +"meaning that the **Income statement** corresponds directly with the year-end" +" date you specify in Odoo. Therefore, any time you generate the **Income " +"Statement**, the beginning date will correspond with the beginning of the " +"**Fiscal Year** and the account balances will all be 0." +msgstr "" + +#: ../../accounting/others/adviser/fiscalyear.rst:86 +msgid "" +"Once the accountant/bookkeeper has created the journal entry to allocate the" +" **Current Year Earnings**, you should set the **Lock Date** to the last day" +" of the fiscal year. Making sure that before doing so, you confirm whether " +"or not the current year earnings in the **Balance Sheet** is correctly " +"reporting a 0 balance." +msgstr "" + +#: ../../accounting/others/analytic.rst:3 +msgid "Analytic" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:3 +msgid "How to track costs of purchases, expenses, subcontracting?" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:8 +msgid "" +"Thanks to analytical accounting we can track costs of purchases, expenses " +"and subcontracting in the accounting module." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:11 +msgid "" +"We'll take the following example. We sold a consulting package for a " +"customer. The package is all inclusive meaning no extra cost can be added. " +"We would however like to follow which cost were attached to this transaction" +" as we need to pay for purchases, expenses, and subcontracting costs related" +" to the project." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:20 +msgid "" +"The following modules needs to be installed to track cost. Enter the app " +"module and install the following apps:" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:28 +msgid "" +"Please note that the applications provided by these apps only allows us to " +"**track** the costs. We won't be able to automatically re invoice those " +"costs to our customers. To track and **re invoice costs** you should install" +" the Sales management app as well." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:37 +msgid "Enable Analytical accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:39 +msgid "" +"Next step is to activate the analytical accounting. In the accounting app, " +"select :menuselection:`Configuration --> Settings` and thick the Analytic " +"accounting box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:46 +msgid "" +"Moreover, scroll down and tick the **Analytic accounting for purchases** " +"box." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:52 +msgid "Don't forget to save your changes." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:55 +msgid "Create an Analytical account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:57 +msgid "" +"First of all you should create an Analytical account on which you can point " +"all your expenses. Enter the accounting app, select " +":menuselection:`Configuration --> Analytic Accounts`. Create a new one. In " +"this case we will call it \"consulting pack\" for our customer Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:65 +msgid "We will point all our costs to this account to keep track of them." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:68 +msgid "Record an expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:70 +msgid "" +"We start by booking an expense. Our IT technician had to take a train to go " +"see our customer. He paid for his ticket himself." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:75 +msgid "Create an expense product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:77 +msgid "" +"We first need to create an expense product. Enter the **Expense** module, " +"Click on :menuselection:`Configuration --> Expense Products`. Create a new " +"product called Train ticket and set the cost price to 15.50 euros. Make sure" +" the **Can be expensed** box is ticked." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:86 +msgid "Book the expense" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:88 +msgid "" +"Enter the Expense module, click on :menuselection:`My expenses --> Create`. " +"Select the Train ticket product and link it to the analytical account " +"discussed above." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:95 +msgid "" +"Submit to manager and wait for the manager to approve and post the journal " +"entries." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:99 +msgid "Create a Purchase Order linked to the analytical account" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:102 +msgid "Purchase Product" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:104 +msgid "" +"We also need to buy a software for our customers. In the purchase app create" +" a purchase order for the software product. (please refer to the following " +"document: :doc:`../../../purchase/overview/process/from_po_to_invoice`). " +"Within the line we can link the product's cost with the analytical account. " +"Specify the order line and select the correct analytical account. Confirm " +"the sale." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:114 +msgid "" +"Accept the delivery and enter the invoice. Once the invoice is entered the " +"cost price (**Vendor Price** field) will be booked in the analytical " +"account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:118 +msgid "Subcontracting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:120 +msgid "" +"The purchase module can be used in the same way as seen previously to handle" +" subcontracting. if we purchase a service from another company we can re " +"invoice this cost by linking the purchase order line to the correct " +"analytical account. We simply need to create the correct vendors product." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:128 +msgid "You can also track cost with timesheets, see: :doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:131 +msgid "Track costs in accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:133 +msgid "" +"Now that everything is booked and points to the analytical account. Simply " +"open it to check the costs related to that account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:136 +msgid "" +"Enter the accounting module, click on :menuselection:`Advisers --> Analytic " +"Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:139 +msgid "" +"Select \"consulting pack - Smith\" and click on the cost and revenue button " +"to have an overview of all cost linked to the account." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:147 +msgid "" +"If you would like to have the revenue as well you should invoice the " +"Consulting Pack in the Invoice menu and link the invoice line to this same " +"analytical account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:3 +msgid "How to track costs of human resources with timesheets?" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:5 +msgid "" +"Human resource of course has a cost. It is interesting to see how much a " +"particular contract costs the company in term of human power in relation to " +"the invoiced amounts." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:9 +msgid "" +"We will take the following example: Our two employees **Harry Potter** and " +"**Cedric Digory** both work on a **Consultancy pack** for our customer " +"**Smith&Co**. Harry is paid 18€ p.h. and Cedric's salary is 12€ p.h. We " +"would like to track their timesheet costs within the accounting app, and " +"compare them with the revenue of the consultancy service." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:18 +msgid "" +"First, install the three applications necessary to use this functionality, " +"namely **Accounting**, **Sales** and **Timesheet**. Enter the apps module " +"name and install them." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:31 +msgid "" +"Next you will need to enable analytical accounting. To do so enter the " +"**Accounting app**. Select :menuselection:`Configuration --> Settings` and " +"tick the **Analytic accounting** option (see picture below)" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:38 +msgid "Apply your changes." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:41 +msgid "Create an employee" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:43 +msgid "" +"In order to check the revenue of an employee you need to have one. To create" +" an employee enter the **Employee** app. Select **Employees** and create a " +"new employee, fill in the name and the basic information." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:47 +msgid "" +"On the employee sheet enter the **HR settings** tab. Here you are able to " +"specify the **Timesheet Cost** of your employee. In this case Harry has a " +"cost of 18 euros / hours. We will thus fill in 18 in this field." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:55 +msgid "" +"If you want the employee to be able to enter timesheets he needs to be " +"related to a User." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:58 +msgid "" +"Repeat the operation to create the Cedric Digory employee. Don't forget to " +"specify its related user and **Timesheet Costs**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:62 +msgid "Issue a Sales Order" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:64 +msgid "" +"We created two employees called Harry Potter and Cedric Diggory in the " +"**Employee** app. Both of them will work on a consultancy contract for our " +"customer Smith&Co where they will point their hours on a timesheet." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:68 +msgid "" +"We thus need to create a **sales order** with a **service** product invoiced" +" **based on time and material** and tracked by timesheets with **hours** as " +"unit of measures." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:75 +msgid "" +"For more information on how to create a sales order based on time and " +"material please see: *How to invoice based on time and material* (Work in " +"Progress)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:82 +msgid "" +"We save a Sales Order with the service product **External Consulting**. An " +"analytical account will automatically be generated once the **Sales Order** " +"is confirmed. Our employees will have to point to that account (in this case" +" **SO002-Smith&Co**) in order to be able to invoice their hours (see picture" +" below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:92 +msgid "Fill in timesheet" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:94 +msgid "" +"As an employee linked to a user, Harry can enter the **Timesheet** app and " +"specify his timesheets for the contract. Logged on Harry's account we enter " +"the **Timesheet** app and enter a detailed line pointing to the **Analytical" +" Account** discussed above." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:99 +msgid "Harry worked three hours on a SWOT analysis for Smith&Co." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:104 +msgid "" +"In the meantime, Cedric discussed businesses needs with the customer for 1 " +"hour and specified it as well in his personal timesheet, pointing as well on" +" the **Analytic Account**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:108 +msgid "" +"In the **Sales Order** we notice that the delivered amounts of hours is " +"automatically computed (see picture below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:115 +msgid "Analytic accounting" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:117 +msgid "" +"Thanks to analytic accounts we are able to have an overview of HR cost and " +"revenues. All the revenues and cost of this transactions have been " +"registered in the **SO002-Smith&Co** account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:121 +msgid "We can use two methods to analyze this situation." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:124 +msgid "Without filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:126 +msgid "" +"If we pointed all our costs and revenues of the project on the correct " +"analytical account we can easily retrieve the cost and revenues related to " +"this analytical account. Enter the *Accounting* app, select " +":menuselection:`Adviser --> Analytic Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:131 +msgid "" +"Note : you can specify a period for **Analysis**. If you want to open the " +"current situation you should keep the fields empty. We can already note the " +"credit and debit balance of the account." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:138 +msgid "" +"If we click on the account a special button is provided to have the details " +"of cost and revenues (see picture below)." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:144 +msgid "" +"Click the button **Cost/Revenue** to have an overview of cost and revenues " +"with the corresponding description." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:148 +msgid "With filters" +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:150 +msgid "We can thus filter this information from the **Analytic Entries**." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:152 +msgid "" +"Enter the **Accounting** app, and click on :menuselection:`Adviser --> " +"Analytic Entries`. In this menu we have several options to analyse the human" +" resource cost." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:155 +msgid "" +"We filter on the **Analytic account** so we can see the cost and revenues of" +" the project. Add a custom **Filter** where the **Analytic Account** " +"contains the **Sales Order** number." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:162 +msgid "" +"In the results we see timesheets activities and invoiced lines with the " +"corresponding costs and revenues." +msgstr "" + +#: ../../accounting/others/analytic/timesheets.rst:168 +msgid "" +"We can group the different analytical accounts together and check their " +"respective revenues. Simply group by **Analytic account** and select the " +"**Graph view** to have a clear overview." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:3 +msgid "Analytic account use cases" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:5 +msgid "The analytic accounting can be used for several purposes:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:7 +msgid "analyse costs of a company" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:9 +msgid "reinvoice time to a customer" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:11 +msgid "analyse performance of a service or a project" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:13 +msgid "" +"To manage analytic accounting, you have to activate it in " +":menuselection:`Configuration --> Settings`:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:19 +msgid "" +"To illustrate analytic accounts clearly, you will follow three use cases, " +"each in one of three different types of company:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:22 +msgid "Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:24 +msgid "Law Firm: reinvoice spent hours" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:26 +msgid "IT/Services Company: performance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:29 +msgid "Case 1: Industrial company: Costs Analyse" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:31 +msgid "" +"In industry, you will often find analytic charts of accounts structured into" +" departments and products the company itself is built on." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:34 +msgid "" +"The objective is to examine the costs, sales and margins by " +"department/resources and by product. The first level of the structure " +"comprises the different departments, and the lower levels represent the " +"product ranges the company makes and sells." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:39 +msgid "" +"**Analytic Chart of Accounts for an Industrial Manufacturing Company**:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:41 +msgid "Marketing Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:43 +msgid "Commercial Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:45 +msgid "Administration Department" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:47 +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:80 +msgid "Production Range 1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:49 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "Production Range 2" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:51 +msgid "" +"In daily use, it is useful to mark the analytic account on each purchase " +"invoice. When the invoice is approved, it will automatically generate the " +"entries for both the general and the corresponding analytic accounts. For " +"each entry on the general accounts, there is at least one analytic entry " +"that allocates costs to the department which incurred them." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:58 +msgid "" +"Here is a possible breakdown of some general accounting entries for the " +"example above, allocated to various analytic accounts:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**General accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:62 +msgid "**Analytic accounts**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Title**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Account**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Debit**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +#: ../../accounting/others/analytic/usage.rst:157 +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Credit**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:64 +msgid "**Value**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "Purchase of Raw Material" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "2122" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "1500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:66 +msgid "-1 500" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +msgid "Subcontractors" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:68 +#: ../../accounting/others/analytic/usage.rst:72 +msgid "-450" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +msgid "Credit Note for defective materials" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:70 +#: ../../accounting/others/analytic/usage.rst:70 +msgid "200" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:72 +msgid "Transport charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "Staff costs" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "2121" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +msgid "10000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:84 +msgid "Marketing" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:74 +#: ../../accounting/others/analytic/usage.rst:80 +#: ../../accounting/others/analytic/usage.rst:82 +msgid "-2 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "Commercial" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:76 +msgid "-3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Administrative" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:78 +msgid "-1 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "PR" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:84 +msgid "-400" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:87 +msgid "" +"The analytic representation by department enables you to investigate the " +"costs allocated to each department in the company. The analytic chart of " +"accounts shows the distribution of the company's costs using the example " +"above:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:94 +msgid "" +"In this example of a hierarchical structure in Odoo, you can analyse not " +"only the costs of each product range, but also the costs of the whole " +"production. A report that relates both general accounts and analytic " +"accounts enables you to get a breakdown of costs within a given department." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:103 +msgid "" +"The examples above are based on a breakdown of the costs of the company. " +"Analytic allocations can be just as effective for sales. That gives you the " +"profitability (sales - costs) of different departments." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:107 +msgid "" +"This analytic representation by department is generally used by trading " +"companies and industries." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:110 +msgid "" +"A variantion of this, is not to break it down by sales and marketing " +"departments, but to assign each cost to its corresponding product range. " +"This will give you an analysis of the profitability of each product range." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:115 +msgid "" +"Choosing one over the other depends on how you look at your marketing " +"effort. Is it a global cost allocated in some general way, or is each " +"product range responsible for its own marketing costs?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:120 +msgid "Case 2: Law Firm: costs of human resources?" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:122 +msgid "" +"Law firms generally adopt management by case, where each case represents a " +"current client file. All of the expenses and products are then attached to a" +" given file/analytic account." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:126 +msgid "" +"A principal preoccupation of law firms is the invoicing of hours worked, and" +" the profitability by case and by employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:129 +msgid "" +"Mechanisms used for encoding the hours worked will be covered in detail in " +"timesheet documentation. Like most system processes, hours worked are " +"integrated into the analytic accounting. In the employee form, specify the " +"cost of the employee. The hourly charge is a function of the employee's " +"cost." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:135 +msgid "" +"So a law firm will opt for an analytic representation which reflects the " +"management of the time that employees work on the different customer cases." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:139 +msgid "" +"Billing for the different cases is a bit unusual. The cases do not match any" +" entry in the general account nor do they come from purchase or sales " +"invoices. They are represented by the various analytic operations and do not" +" have exact counterparts in the general accounts. They are calculated on the" +" basis of the hourly cost per employee." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:145 +msgid "" +"At the end of the month when you pay salaries and benefits, you integrate " +"them into the general accounts but not in the analytic accounts, because " +"they have already been accounted for in billing each account. A report that " +"relates data from the analytic and general accounts then lets you compare " +"the totals, so you can readjust your estimates of hourly cost per employee " +"depending on the time actually worked." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:153 +msgid "" +"The following table shows an example of different analytic entries that you " +"can find for your analytic account:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**Amount**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:157 +msgid "**General Account**" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "Study the file (1 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +#: ../../accounting/others/analytic/usage.rst:161 +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Case 1.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:159 +msgid "-15" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "Search for information (3 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:161 +msgid "-45" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Consultation (4 h)" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "Case 2.1" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:163 +msgid "-60" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "Service charges" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +#: ../../accounting/others/analytic/usage.rst:165 +msgid "280" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:165 +msgid "705 – Billing services" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "Stationery purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "-42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "601 – Furniture purchase" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:167 +msgid "42" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "Fuel Cost -Client trip" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "-35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "613 – Transports" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:169 +msgid "35" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "Staff salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "6201 – Salaries" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:171 +msgid "3 000" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:174 +msgid "" +"Such a structure allows you to make a detailed study of the profitability of" +" various transactions." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:177 +msgid "" +"For more details about profitablity, please read the following document: " +":doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:180 +msgid "" +"But analytical accounting is not limited to a simple analysis of the " +"profitability of different customer. The same data can be used for automatic" +" recharging of the services to the customer at the end of the month. To " +"invoice customers, just link the analytic account to a sale order and sell " +"products that manage timesheet or expenses ." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:187 +msgid "Case 3: IT Services Company: perfomance analysis" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:189 +msgid "Most IT service companies face the following problems:" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:191 +msgid "project planning," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:193 +msgid "invoicing, profitability and financial follow-up of projects," +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:195 +msgid "managing support contracts." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:197 +msgid "" +"To deal with these problems, you would use an analytic chart of accounts " +"structured by project and by sale order." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:200 +msgid "" +"The management of services, expenditures and sales is similar to that " +"presented above for lawyers. Invoicing and the study of profitability are " +"also similar." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:204 +msgid "" +"But now look at support contracts. These contracts are usually limited to a " +"prepaid number of hours. Each service posted in the analytic accounts shows " +"the remaining hours of support. To manage support contracts, you would " +"create a product configured to invoice on order and link the sale order to " +"an analytic account" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:210 +msgid "" +"In Odoo, each analytic line lists the number of units sold or used, as well " +"as what you would usually find there – the amount in currency units (USD or " +"GBP, or whatever other choice you make). So you can sum the quantities sold " +"and used on each sale order to determine whether any hours of the support " +"contract remain." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:217 +msgid "Conclusion" +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:219 +msgid "" +"Analytic accounting helps you to analyse costs and revenues whatever the use" +" case. You can sell or purchase services, track time or analyse the " +"production performance." +msgstr "" + +#: ../../accounting/others/analytic/usage.rst:223 +msgid "" +"Analytic accounting is flexible and easy to use through all Odoo " +"applications (sales, purchase, timesheet, production, invoice, …)." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:3 +msgid "What is an account type and how do I configure it?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:6 +msgid "What is an account type ?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:8 +msgid "" +"An account type is a name or code given to an account that indicates the " +"account's purpose." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:11 +msgid "" +"In Odoo, Account Types are used for information purpose, to generate " +"country-specific legal reports, set the rules to close a fiscal year and " +"generate opening entries." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:15 +msgid "" +"Basically Account types categorize general account with some specific " +"category according to its behaviour or purpose." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:19 +msgid "Which are the account types in Odoo ?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:21 +msgid "" +"Odoo covers all accounting types. Therefore, you cannot create new account " +"types. Just pick the one related to your account." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:25 +msgid "**List of account types**" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:27 +msgid "Receivable" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:29 +msgid "Payable" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:31 +msgid "Bank and Cash" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:33 +msgid "Current Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:35 +msgid "Non-current Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:37 +msgid "Prepayments" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:39 +#: ../../accounting/overview/main_concepts/terminologies.rst:77 +msgid "Fixed Assets" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:41 +msgid "Current Liabilities" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:43 +msgid "Non-current Liabilities" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:45 +msgid "Equity" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:47 +msgid "Current Year Earnings" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:49 +msgid "Other Income" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:51 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 +msgid "Income" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:53 +msgid "Depreciation" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:55 +msgid "Expenses" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:57 +msgid "Direct Costs" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:61 +msgid "How do I configure my accounts?" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:63 +msgid "" +"Account types are automatically created when installing a chart of account. " +"By default, Odoo provides a lot of chart of accounts, just install the one " +"related to your country." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:67 +msgid "" +"It will install generic accounts. But if it does not cover all your cases, " +"you can create your own accounts too." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:72 +msgid "" +"If you are a Saas User, your country chart of account is automatically " +"installed." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:75 +msgid "" +"To create a new accounts, go to the Accounting application. Open the menu " +":menuselection:`Adviser --> Chart of Accounts`, the click on the **Create** " +"button." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"Account Type is used for information purpose, to generate country-specific " +"legal reports, and set the rules to close a fiscal year and generate opening" +" entries." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Optional tags you may want to assign for custom reporting" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Forces all moves for this account to have this account currency." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"The 'Internal Type' is used for features available on different types of " +"accounts: liquidity type is for cash or bank accounts, payable/receivable is" +" for vendor/customer accounts." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "" +"Check this box if this account allows invoices & payments matching of " +"journal items." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:86 +msgid "View *Create Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/others/inventory.rst:3 +msgid "Inventory" +msgstr "Stok" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:3 +msgid "Impact on the average price valuation when returning goods" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:5 +msgid "" +"As stated in the `*inventory valuation page* " +"<https://www.odoo.com/documentation/functional/valuation.html>`__, one of " +"the possible costing method you can use in perpetual stock valuation, is the" +" average cost." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:10 +msgid "" +"This document answers to one recurrent question for companies using that " +"method to make their stock valuation: how does a shipping returned to its " +"supplier impact the average cost and the accounting entries? This document " +"is **only** for the specific use case of a perpetual valuation (as opposed " +"to the periodic one) and in average price costing method (as opposed to " +"standard of FIFO)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:18 +msgid "Definition of average cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:20 +msgid "" +"The average cost method calculates the cost of ending inventory and cost of " +"goods sold on the basis of weighted average cost per unit of inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:24 +msgid "" +"The weighted average cost per unit is calculated using the following " +"formula:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:27 +msgid "" +"When new products arrive in a warehouse, the new average cost is recomputed " +"as:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:33 +msgid "" +"When products leave the warehouse: the average cost **does not** change" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:36 +msgid "Defining the purchase price" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:38 +msgid "" +"The purchase price is estimated at the reception of the products (you might " +"not have received the vendor bill yet) and reevaluated at the reception of " +"the vendor bill. The purchase price includes the cost you pay for the " +"products, but it may also includes additional costs, like landed costs." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:45 +msgid "Average cost example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Operation" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +msgid "Delta Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Inventory Value" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Qty On Hand" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:48 +#: ../../accounting/others/inventory/avg_price_valuation.rst:82 +#: ../../accounting/others/inventory/avg_price_valuation.rst:101 +#: ../../accounting/others/inventory/avg_price_valuation.rst:117 +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "Avg Cost" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:50 +#: ../../accounting/others/inventory/avg_price_valuation.rst:146 +msgid "0" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +msgid "+8\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "8" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:52 +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +msgid "+4\\*$16" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "$144" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:54 +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +msgid "-10\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "$24" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:56 +#: ../../accounting/others/inventory/avg_price_valuation.rst:84 +#: ../../accounting/others/inventory/avg_price_valuation.rst:103 +#: ../../accounting/others/inventory/avg_price_valuation.rst:119 +#: ../../accounting/others/inventory/avg_price_valuation.rst:156 +msgid "2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:60 +msgid "" +"At the beginning, the Avg Cost is set to 0 set as there is no product in the" +" inventory. When the first reception is made, the average cost becomes " +"logically the purchase price." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:64 +msgid "" +"At the second reception, the average cost is updated because the total " +"inventory value is now ``$80 + 4*$16 = $144``. As we have 12 units on hand, " +"the average price per unit is ``$144 / 12 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:68 +msgid "" +"By definition, the delivery of 10 products does not change the average cost." +" Indeed, the inventory value is now $24 as we have only 2 units remaining of" +" each ``$24 / 2 = $12``." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:73 +msgid "Purchase return use case" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:75 +msgid "" +"In case of a product returned to its supplier after reception, the inventory" +" value is reduced using the average cost formulae (not at the initial price " +"of these products!)." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:79 +msgid "Which means that the above table will be updated as follow:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "Return of 1 Product initially bought at $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "-1\\*$12" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:86 +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "1" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:90 +msgid "Explanation: counter example" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:92 +msgid "" +"Remember the definition of **Average Cost**, saying that we do not update " +"the average cost of a product leaving the inventory. If you break this rule," +" you may lead to inconsistencies in your inventory." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:96 +msgid "" +"As an example, here is the scenario when you deliver one piece to the " +"customer and return the other one to your supplier (at the cost you " +"purchased it). Here is the operation:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:105 +#: ../../accounting/others/inventory/avg_price_valuation.rst:121 +msgid "Customer Shipping 1 product" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +msgid "-1\\*$10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$2**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:107 +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:110 +msgid "" +"As you can see in this example, this is not correct: an inventory valuation " +"of $2 for 0 pieces in the warehouse." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:113 +msgid "" +"The correct scenario should be to return the goods at the current average " +"cost:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:123 +msgid "**$0**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:126 +msgid "" +"On the other hand, using the average cost to value the return ensure a " +"correct inventory value at all times." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:130 +msgid "Further thoughts on anglo saxon mode" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:132 +msgid "" +"For people in using the **anglo saxon accounting** principles, there is " +"another concept to take into account: the stock input account of the " +"product, which is intended to hold at any time the value of vendor bills to " +"receive. So the stock input account will increase on reception of incoming " +"shipments and will decrease when receiving the related vendor bills." +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:139 +msgid "" +"Back to our example, we see that when the return is valued at the average " +"price, the amount booked in the stock input account is the original purchase" +" price:" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "stock input" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:144 +msgid "price diff" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:148 +msgid "($80)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:150 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:152 +msgid "($64)" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:154 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$10**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:158 +msgid "**$12**" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:160 +msgid "$2" +msgstr "" + +#: ../../accounting/others/inventory/avg_price_valuation.rst:163 +msgid "" +"This is because the vendor refund will be made using the original purchase " +"price, so to zero out the effect of the return in the stock input in last " +"operation, we need to reuse the original price. The price difference account" +" located on the product category is used to book the difference between the " +"average cost and the original purchase price." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:3 +msgid "Record exchange rates at payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:8 +msgid "" +"Any company doing international trade faces the case where the payments are " +"in a different currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:11 +msgid "" +"After receiving their payments, you have the option to convert the amount " +"into your company currency. Multi currency payment implies rates " +"fluctuations. The rate differences are automatically recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:19 +msgid "Enable multi-currencies" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:21 +msgid "" +"In the accounting module, Go to :menuselection:`Configuration --> Settings` " +"and flag **Allow multi currencies**, then click on **apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:27 +msgid "" +"Configure the currency rates in :menuselection:`Configuration --> " +"Currencies`. Write down the rate and make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:33 +msgid "" +"In this document, the base currency is **Euro** and we will record payments " +"in **Dollars**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:40 +msgid "" +"You can automatically fetch the currency rates from the **European Central " +"Bank** or from **Yahoo**. Please read the document : :doc:`how_it_works`." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:45 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:31 +msgid "Configure your journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:47 +msgid "" +"In order to register payments in other currencies, you have to **remove the " +"currency constraint** on the journal. Go to the accounting application, " +"Click on **More** on the journal and **Settings**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:54 +msgid "" +"Check if the **Currency** field is empty or in the foreign currency in which" +" you will register the payments. If a currency is filled in, it means that " +"you can register payments only in this currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:62 +msgid "Record a payment in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:64 +msgid "" +"In the **Accounting** application, go to :menuselection:`Sales --> " +"Payments`. Register the payment and indicate that it was done in the foreign" +" currency. Then click on **confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:71 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:83 +msgid "The journal entry has been posted but not allocated." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:73 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:85 +msgid "" +"Go back to your invoice (:menuselection:`Sales --> Customer Invoices`) and " +"click on **Add** to allocate the payment." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:80 +msgid "Record a bank statement in a different currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:82 +msgid "" +"Create or import the bank statement of your payment. The **Amount** is in " +"the company currency. There are two complementary fields, the **Amount " +"currency**, which is the amount that was actually paid and the **Currency** " +"in which it was paid." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:89 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"**Invoice**. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:97 +msgid "Check the exchange rate differences" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:99 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the " +"**Exchange difference** journal entries. All the exchange rates differences " +"are recorded in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:106 +msgid "" +"The Exchange difference journal can be changed in your accounting settings." +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:109 +#: ../../accounting/payables/pay/multiple.rst:153 +msgid ":doc:`../../bank/reconciliation/configure`" +msgstr "" + +#: ../../accounting/others/multicurrencies/exchange.rst:110 +#: ../../accounting/payables/pay/multiple.rst:103 +msgid ":doc:`../../bank/reconciliation/use_cases`" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:3 +#: ../../accounting/others/multicurrencies/how_it_works.rst:111 +msgid "How is Odoo's multi-currency working?" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:8 +msgid "" +"Choosing to use the multi-currency option in Odoo will allow you to send " +"sales invoices, quotes and purchase orders or receive bills and payments in " +"currencies other than your own. With multi-currency, you can also set up " +"bank accounts in other currencies and run reports on your foreign currency " +"activities." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:18 +msgid "Turn on multi-currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:20 +msgid "" +"In the accounting module, Go to :menuselection:`Configuration --> Settings` " +"and flag **Allow multi currencies**, then click on **Apply**." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:27 +#: ../../accounting/others/multicurrencies/how_it_works.rst:160 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:109 +msgid "Exchange Rate Journal" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:29 +msgid "" +"The **Rate Difference Journal** records the differences between the payment " +"registration and the expected amount. For example, if a payment is paid 1 " +"month after the invoice was issued, the exchange rate has probably changed. " +"The fluctuation implies some loss or profit that are recorded by Odoo." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:35 +msgid "You can change it in the settings:" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:41 +msgid "View or edit rate being used" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:43 +msgid "" +"You can manually configure the currency rates in " +":menuselection:`Configuration --> Currencies`. Open the currencies you want " +"to use in Odoo and edit it. Make sure the currency is active." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:50 +msgid "Click on **View Rates** to edit it and to see the history :" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:55 +msgid "" +"Click on **Create** to add the rate. Fill in the date and the rate. Click on" +" **Save** when you are done." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:62 +msgid "Live Currency Rate" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:64 +msgid "" +"By default, the currencies need to be updated manually. But you can " +"synchronize it with `Yahoo <https://finance.yahoo.com/currency-" +"converter/>`__ or the `European Central Bank <http://www.ecb.europa.eu>`__. " +"In :menuselection:`Configuration --> Settings`, go to the **Live Currency " +"Rate** section." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:69 +msgid "" +"Choose the interval : Manually, Daily, Weekly or Monthly. You can always " +"force the update by clicking on **Update Now**. Select the provider, and you" +" are set !" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:78 +msgid "Only the **active** currencies are updated" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:81 +msgid "Configure your charts of account" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:83 +msgid "" +"In the accounting application, go to :menuselection:`Adviser --> Charts of " +"Accounts`. On each account, you can set a currency. It will force all moves " +"for this account to have the account currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:87 +msgid "" +"If you leave it empty, it means that it can handle all currencies that are " +"Active." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:94 +msgid "Configure your journals" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:96 +msgid "" +"In order to register payments in other currencies, you have to remove the " +"currency constraint on the journal. Go to the accounting application, Click " +"on **More** on the journal and **Settings**." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:103 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:40 +msgid "" +"Check if the currency field is empty or in the foreign currency in which you" +" will register the payments. If a currency is filled in, it means that you " +"can register payments only in this currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:113 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:50 +msgid "" +"Now that you are working in a multi-currency environment, all accountable " +"items will be linked to a currency, domestic or foreign." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:117 +msgid "Sales Orders and Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:119 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:56 +msgid "" +"You are now able to set a different currency than the company one on your " +"sale orders and on your invoices. The currency is set for the whole " +"document." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:127 +msgid "Purchases orders and Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:129 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:66 +msgid "" +"You are now able to set a different currency than the company one on your " +"purchase orders and on your vendor bills. The currency is set for the whole " +"document." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:137 +msgid "Payment Registrations" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:139 +msgid "" +"In the accounting application, go to **Sales > Payments**. Register the " +"payment and set the currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:146 +msgid "Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:148 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:94 +msgid "" +"When creating or importing bank statements, the amount is in the company " +"currency. But there are now two complementary fields, the amount that was " +"actually paid and the currency in which it was paid." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:155 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"Invoice. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:162 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the Exchange" +" difference journal entries. All the exchange rates differences are recorded" +" in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:170 +msgid ":doc:`invoices_payments`" +msgstr "" + +#: ../../accounting/others/multicurrencies/how_it_works.rst:171 +#: ../../accounting/others/multicurrencies/invoices_payments.rst:120 +msgid ":doc:`exchange`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:3 +msgid "How to manage invoices & payment in multiple currencies?" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:8 +msgid "" +"Odoo provides multi-currency support with automatic currency gross or loss " +"entry adjustment. There are a few things Odoo has been to ease the user's " +"life." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:12 +msgid "" +"All the account transactions will be done using the company currency. " +"However you can see two extra fields with the journal entry where secondary " +"currency and amount will visible. You can create multi-currency journals of " +"force a specific currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:17 +msgid "" +"When creating an invoice, the currency can be changed very easily; however " +"Odoo takes the company currency as a default assignment. It will convert all" +" the amounts automatically using that currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:25 +msgid "Enable Multi-Currency" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:27 +msgid "" +"For information about enabling Multi-Currency, please read the document: " +":doc:`how_it_works`" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:33 +msgid "" +"In order to register payments in other currencies, you have to remove the " +"currency constraint on the journal. Go to the accounting application, on the" +" journal, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:48 +msgid "Multi-currency invoices & Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:54 +msgid "Invoices" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 +msgid "Vendor Bills" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:74 +msgid "Multi-currency Payments" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:76 +msgid "" +"In the accounting application, go to :menuselection:`Sales --> Payments`. " +"Register the payment and indicate that it was done in the foreign currency. " +"Then click on **Confirm**." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:92 +msgid "Multi- Currency Bank Statements" +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:101 +msgid "" +"When reconciling it, Odoo will directly match the payment with the right " +"invoice. You will get the invoice price in the invoice currency and the " +"amount in your company currency." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:111 +msgid "" +"Go to :menuselection:`Adviser --> Journal Entries` and look for the " +"**Exchange Difference** journal entries. All the exchange rates differences " +"are recorded in it." +msgstr "" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:119 +msgid ":doc:`how_it_works`" +msgstr "" + +#: ../../accounting/others/reporting.rst:3 +#: ../../accounting/overview/process_overview/supplier_bill.rst:124 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:106 +msgid "Reporting" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:3 +msgid "How to create a customized reports with your own formulas?" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:8 +msgid "" +"Odoo 9 comes with a powerful and easy-to-use reporting framework. Creating " +"new reports (such as a tax report or a balance sheet for a specific country)" +" to suit your needs is now easier than ever." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:13 +msgid "Activate the developer mode" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:15 +msgid "" +"In order to have access to the financial report creation interface, the " +"**developer mode** needs to be activated. To do that, first click on the " +"user profile in the top right menu, then **About**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:22 +msgid "Click on : **Activate the developer mode**." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:28 +msgid "Create your financial report" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:30 +msgid "" +"First, you need to create your financial report. To do that, go to " +":menuselection:`Accounting --> Configuration --> Financial Reports`" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:36 +msgid "" +"Once the name is filled, there are two other parameters that need to be " +"configured:" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:39 +msgid "**Show Credit and Debit Columns**" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:41 +msgid "**Analysis Period** :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:43 +msgid "Based on date ranges (eg Profit and Loss)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:45 +msgid "Based on a single date (eg Balance Sheet)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:47 +msgid "" +"Based on date ranges with 'older' and 'total' columns and last 3 months (eg." +" Aged Partner Balances)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:50 +msgid "Bases on date ranges and cash basis method (eg Cash Flow Statement)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:54 +msgid "Add lines in your custom reports" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:56 +msgid "" +"After you've created the report, you need to fill it with lines. They all " +"need a **name**, a **code** (that is used to refer to the line), a " +"**sequence number** and a **level** (Used for the line rendering)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:63 +msgid "" +"In the **formulas** field you can add one or more formulas to assign a value" +" to the balance column (and debit and credit column if applicable – " +"separated by ;)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:67 +msgid "You have several objects available in the formula :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:69 +msgid "" +"``Ndays`` : The number of days in the selected period (for reports with a " +"date range)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:72 +msgid "" +"Another report, referenced by its code. Use ``.balance`` to get its balance " +"value (also available are ``.credit``, ``.debit`` and ``.amount_residual``)" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:76 +msgid "" +"A line can also be based on the sum of account move lines on a selected " +"domain. In which case you need to fill the domain field with an Odoo domain " +"on the account move line object. Then an extra object is available in the " +"formulas field, namely ``sum``, the sum of the account move lines in the " +"domain. You can also use the group by field to group the account move lines " +"by one of their columns." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:83 +msgid "Other useful fields :" +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:85 +msgid "**Type** : Type of the result of the formula." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:87 +msgid "" +"**Is growth good when positive** : Used when computing the comparison " +"column. Check if growth is good (displayed in green) or not." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:90 +msgid "" +"**Special date changer** : If a specific line in a report should not use the" +" same dates as the rest of the report." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:93 +msgid "" +"**Show domain** : How the domain of a line is displayed. Can be foldable " +"(``default``, hidden at the start but can be unfolded), ``always`` (always " +"displayed) or ``never`` (never shown)." +msgstr "" + +#: ../../accounting/others/reporting/customize.rst:98 +msgid ":doc:`main_reports`" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:3 +msgid "What are the main reports available?" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:5 +msgid "" +"Besides the reports created specifically in each localisation module, a few " +"very useful **generic** and **dynamic reports** are available for all " +"countries :" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:9 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:10 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:11 +msgid "**Chart of Account**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:12 +msgid "**Executive Summary**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:13 +msgid "**General Ledger**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:14 +msgid "**Aged Payable**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:15 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:16 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:17 +msgid "**Tax Report**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:18 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:20 +msgid "" +"You can annotate every reports to print them and report to your adviser. " +"Export to xls to manage extra analysis. Drill down in the reports to see " +"more details (payments, invoices, journal items, etc.)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:24 +msgid "" +"You can also compare values with another period. Choose how many periods you" +" want to compare the chosen time period with. You can choose up to 12 " +"periods back from the date of the report if you don't want to use the " +"default **Previous 1 Period** option." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:30 +msgid "Balance Sheet" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:32 +msgid "" +"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity" +" of your organisation as at a particular date." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:39 +msgid "Profit and Loss" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:41 +msgid "" +"The **Profit and Loss** report (or **Income Statement**) shows your " +"organisation's net income, by deducting expenses from revenue for the report" +" period." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:49 +msgid "Chart of account" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:51 +msgid "A listing of all your accounts grouped by class." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:57 +msgid "Executive Summary" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:59 +msgid "" +"The **Executive Summary** allows for a quick look at all the important " +"figures you need to run your company." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:62 +msgid "" +"In very basic terms, this is what each of the items in this section is " +"reporting :" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "**Performance:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:68 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:67 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales (things like labour, materials, etc)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:74 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:71 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales, as well as any fixed overheads your " +"company has (things like rent, electricity, taxes you need to pay as a " +"result of those sales)." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:77 +msgid "" +"The ratio of net profit made, to the amount of assets the company used to " +"make those profits." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:97 +msgid "**Position:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:81 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:81 +msgid "" +"The average number of days it takes your customers to pay you (fully), " +"across all your customer invoices." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:84 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:84 +msgid "" +"The average number of days it takes you to pay your suppliers (fully) across" +" all your bills." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:89 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:87 +msgid "" +"How much cash is expected in or out of your organisation in the next month " +"i.e. balance of your **Sales account** for the month less the balance of " +"your **Purchases account** for the month." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:97 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:92 +msgid "" +"Also referred to as **current ratio**, this is the ratio of current assets " +"(assets that could be turned into cash within a year) to the current " +"liabilities (liabilities which will be due in the next year). This is " +"typically used as as a measure of a company's ability to service its debt." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:103 +msgid "General Ledger" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:105 +msgid "" +"The **General Ledger Report** shows all transactions from all accounts for a" +" chosen date range. The initial summary report shows the totals for each " +"account and from there you can view a detailed transaction report or any " +"exceptions. This report is useful for checking every transaction that " +"occurred during a certain period of time." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:115 +msgid "Aged Payable" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:117 +msgid "" +"Run the **Aged Payable Details** report to display information on individual" +" bills, credit notes and overpayments owed by you, and how long these have " +"gone unpaid." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:125 +msgid "Aged Receivable" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:127 +msgid "" +"The **Aged Receivables** report shows the sales invoices that were awaiting " +"payment during a selected month and several months prior." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:134 +msgid "Cash Flow Statement" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:136 +msgid "" +"The **Cash Flow Statement** shows how changes in balance sheet accounts and " +"income affect cash and cash equivalents, and breaks the analysis down to " +"operating, investing and financing activities." +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:144 +msgid "Tax Report" +msgstr "" + +#: ../../accounting/others/reporting/main_reports.rst:146 +msgid "" +"This report allows you to see the **net** and **tax amounts** for all the " +"taxes grouped by type (sale/purchase)." +msgstr "" + +#: ../../accounting/others/taxes.rst:3 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "Taxes" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:3 +msgid "How to manage prices for B2B (tax excluded) and B2C (tax included)?" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:5 +msgid "" +"When working with consumers, prices are usually expressed with taxes " +"included in the price (e.g., in most eCommerce). But, when you work in a B2B" +" environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:9 +msgid "" +"Odoo manages both use cases easily, as long as you register your prices on " +"the product with taxes excluded or included, but not both together. If you " +"manage all your prices with tax included (or excluded) only, you can still " +"easily do sales order with a price having taxes excluded (or included): " +"that's easy." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:15 +msgid "" +"This documentation is only for the specific use case where you need to have " +"two references for the price (tax included or excluded), for the same " +"product. The reason of the complexity is that there is not a symmetrical " +"relationship with prices included and prices excluded, as shown in this use " +"case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:25 +msgid "" +"But for the same use case, if you register the price without taxes on the " +"product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:31 +msgid "" +"So, depending on how you register your prices on the product form, you will " +"have different results for the price including taxes and the price excluding" +" taxes:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:40 +msgid "" +"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You " +"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** " +"Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:45 +msgid "" +"This documentation explains how to handle the very specific use case where " +"you need to handle the two prices (tax excluded and included) on the product" +" form within the same company." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:50 +msgid "" +"In terms of finance, you have no more revenues selling your product at 10€ " +"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the " +"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in " +"Belgium, make your customer a favor and set your price at 9.99€ instead of " +"10€. Please note that this does not apply to 20€ or 30€, or other tax rates," +" or a quantity >1. You will also make you a favor since you can manage " +"everything tax excluded, which is less error prone and easier for your " +"salespeople." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:63 +msgid "Introduction" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:65 +msgid "" +"The best way to avoid this complexity is to choose only one way of managing " +"your prices and stick to it: price without taxes or price with taxes " +"included. Define which one is the default stored on the product form (on the" +" default tax related to the product), and let Odoo compute the other one " +"automatically, based on the pricelist and fiscal position. Negotiate your " +"contracts with customers accordingly. This perfectly works out-of-the-box " +"and you have no specific configuration to do." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:73 +msgid "" +"If you can not do that and if you really negotiate some prices with tax " +"excluded and, for other customers, others prices with tax included, you " +"must:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:77 +msgid "" +"always store the default price TAX EXCLUDED on the product form, and apply a" +" tax (price included on the product form)" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:80 +msgid "create a pricelist with prices in TAX INCLUDED, for specific customers" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:83 +msgid "" +"create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:86 +msgid "" +"assign both the pricelist and the fiscal position to customers who want to " +"benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ price excluded" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, price included, in our shops or eCommerce " +"website" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:97 +msgid "Setting your products" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:99 +msgid "" +"Your company must be configured with price excluded by default. This is " +"usually the default configuration, but you can check your **Default Sale " +"Tax** from the menu :menuselection:`Configuration --> Settings` of the " +"Accounting application." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:107 +msgid "" +"Once done, you can create a **B2C** pricelist. You can activate the " +"pricelist feature per customer from the menu: :menuselection:`Configuration " +"--> Settings` of the Sale application. Choose the option **different prices " +"per customer segment**." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:112 +msgid "" +"Once done, create a B2C pricelist from the menu " +":menuselection:`Configuration --> Pricelists`. It's also good to rename the " +"default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:116 +msgid "" +"Then, create a product at 8.26€, with a tax of 21% (defined as tax not " +"included in price) and set a price on this product for B2C customers at 10€," +" from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:125 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:127 +msgid "" +"From the accounting application, create a B2C fiscal position from this " +"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal " +"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax " +"included in price)" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:136 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:138 +msgid "" +"Create a quotation from the Sale application, using the " +":menuselection:`Sales --> Quotations` menu. You should have the following " +"result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:145 +msgid "" +"Then, create a quotation but **change the pricelist to B2C and the fiscal " +"position to B2C** on the quotation, before adding your product. You should " +"have the expected result, which is a total price of 10€ for the customer: " +"8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:153 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:156 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:158 +msgid "" +"If you negotiate a contract with a customer, whether you negotiate price " +"included or price excluded, you can set the pricelist and the fiscal " +"position on the customer form so that it will be applied automatically at " +"every sale of this customer." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:163 +msgid "" +"The pricelist is in the **Sales & Purchases** tab of the customer form, and " +"the fiscal position is in the accounting tab." +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:166 +msgid "" +"Note that this is error prone: if you set a fiscal position with tax " +"included in prices but use a pricelist that is not included, you might have " +"wrong prices calculated for you. That's why we usually recommend companies " +"to only work with one price reference." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:3 +msgid "How to adapt taxes to my customer status or localization" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:5 +msgid "" +"Most often sales tax rates depend on your customer status or localization. " +"To map taxes, Odoo brings the so-called *Fiscal Positions*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:9 +msgid "Create tax mapping" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:11 +msgid "" +"A fiscal position is just a set of rules that maps default taxes (as defined" +" on product form) into other taxes. In the screenshot below, foreign " +"customers get a 0% tax instead of the default 15%, for both sales and " +"purchases." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:18 +msgid "" +"The main fiscal positions are automatically created according to your " +"localization. But you may have to create fiscal positions for specific use " +"cases. To define fiscal positions, go to " +":menuselection:`Invoicing/Accounting --> Configuration --> Fiscal " +"Positions`." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:24 +msgid "" +"If you use Odoo Accounting, you can also map the Income/Expense accounts " +"according to the fiscal position. For example, in some countries, revenues " +"from sales are not posted in the same account than revenues from sales in " +"foreign countries." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:29 +msgid "Adapt taxes to your customer status" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:31 +msgid "" +"If a customer falls into a specific taxation rule, you need to apply a tax-" +"mapping. To do so, create a fiscal position and assign it to your customers." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:37 +msgid "" +"Odoo will use this specific fiscal position for any order/invoice recorded " +"for the customer." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:40 +msgid "" +"If you set the fiscal position in the sales order or invoice manually, it " +"will only apply to this document and not to future orders/invoices of the " +"same customer." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:44 +msgid "Adapt taxes to your customer address (destination-based)" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:46 +msgid "" +"Depending on your localization, sales taxes may be origin-based or " +"destination-based. Most states or countries require you to collect taxes at " +"the rate of the destination (i.e. your buyer’s address) while some others " +"require to collect them at the rate effective at the point of origin (i.e. " +"your office or warehouse)." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:51 +msgid "" +"If you are under the destination-based rule, create one fiscal position per " +"tax-mapping to apply." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:53 +msgid "Check the box *Detect Automatically*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:54 +msgid "" +"Select a country group, country, state or city to trigger the tax-mapping." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:59 +msgid "" +"This way if no fiscal position is set on the customer, Odoo will choose the " +"fiscal position matching the shipping address on creating an order." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:63 +msgid "" +"For eCommerce orders, the tax of the visitor's cart will automatically " +"update and apply the new tax after the visitor has logged in or filled in " +"his shipping address." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:68 +msgid "Specific use cases" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:70 +msgid "" +"If, for some fiscal positions, you want to remove a tax, instead of " +"replacing by another, just keep the *Tax to Apply* field empty." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:76 +msgid "" +"If, for some fiscal positions, you want to replace a tax by two other taxes," +" just create two lines having the same *Tax on Product*." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:82 +#: ../../accounting/others/taxes/default_taxes.rst:27 +#: ../../accounting/others/taxes/retention.rst:70 +msgid ":doc:`create`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:83 +#: ../../accounting/others/taxes/default_taxes.rst:29 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:84 +#: ../../accounting/others/taxes/create.rst:70 +#: ../../accounting/others/taxes/default_taxes.rst:31 +msgid ":doc:`tax_included`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:85 +#: ../../accounting/others/taxes/default_taxes.rst:30 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:3 +msgid "How to create new taxes" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:5 +msgid "" +"Odoo's tax engine is very flexible and support many different type of taxes:" +" value added taxes (VAT), eco-taxes, federal/states/city taxes, retention, " +"withholding taxes, etc. For most countries, your system is pre-configured " +"with the right taxes." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:10 +msgid "" +"This section details how you can define new taxes for specific use cases." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:12 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Taxes`. From this " +"menu, you get all the taxes you can use: sales taxes and purchase taxes." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:18 +msgid "Choose a scope: Sales, Purchase or None (e.g. deprecated tax)." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:20 +msgid "Select a computation method:" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:22 +msgid "**Fixed**: eco-taxes, etc." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:24 +msgid "**Percentage of Price**: most common (e.g. 15% sales tax)" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:26 +msgid "**Percentage of Price Tax Included**: used in Brazil, etc." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:28 +msgid "**Group of taxes**: allows to have a compound tax" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:34 +msgid "" +"If you use Odoo Accounting, set a tax account (i.e. where the tax journal " +"item will be posted). This field is optional, if you keep it empty, Odoo " +"posts the tax journal item in the income account." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:39 +msgid "" +"If you want to avoid using a tax, you can not delete it because the tax is " +"probably used in several invoices. So, in order to avoid users to continue " +"using this tax, you should set the field *Tax Scope* to *None*." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:44 +msgid "" +"If you need more advanced tax mechanism, you can install the module " +"**account_tax_python** and you will be able to define new taxes with Python " +"code." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:49 +msgid "Advanced configuration" +msgstr "" + +#: ../../accounting/others/taxes/create.rst:51 +msgid "" +"**Label on Invoices**: a short text on how you want this tax to be printed " +"on invoice line. For example, a tax named \"15% on Services\" can have the " +"following label on invoice \"15%\"." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:55 +msgid "" +"**Tax Group**: defines where this tax is summed in the invoice footer. All " +"the tax belonging to the same tax group will be grouped on the invoice " +"footer. Examples of tax group: VAT, Retention." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:59 +msgid "" +"**Include in Analytic Cost**: the tax is counted as a cost and, thus, " +"generate an analytic entry if your invoice uses analytic accounts." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:63 +msgid "" +"**Tags**: are used for custom reports. Usually, you can keep this field " +"empty." +msgstr "" + +#: ../../accounting/others/taxes/create.rst:69 +#: ../../accounting/others/taxes/default_taxes.rst:28 +#: ../../accounting/others/taxes/taxcloud.rst:87 +msgid ":doc:`application`" +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:3 +msgid "How to set default taxes" +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:5 +msgid "" +"Taxes applied in your country are installed automatically for most " +"localizations." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:7 +msgid "" +"Default taxes set in orders and invoices come from each product's Invoicing " +"tab. Such taxes are used when you sell to companies that are in the same " +"country/state than you." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:13 +msgid "" +"To change the default taxes set for any new product created go to " +":menuselection:`Invoicing/Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../accounting/others/taxes/default_taxes.rst:20 +msgid "" +"If you work in a multi-companies environment, the sales and purchase taxes " +"may have a different value according to the company you work for. You can " +"login into two different companies and change this field for each company." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:3 +msgid "How to manage withholding taxes?" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:5 +msgid "" +"A withholding tax, also called a retention tax, is a government requirement " +"for the payer of a customer invoice to withhold or deduct tax from the " +"payment, and pay that tax to the government. In most jurisdictions, " +"withholding tax applies to employment income." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:10 +msgid "" +"With normal taxes, the tax is added to the subtotal to give you the total to" +" pay. As opposed to normal taxes, withholding taxes are deducted from the " +"amount to pay, as the tax will be paid by the customer." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:14 +msgid "As, an example, in Colombia you may have the following invoice:" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:19 +msgid "" +"In this example, the **company** who sent the invoice owes $20 of taxes to " +"the **government** and the **customer** owes $10 of taxes to the " +"**government**." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:25 +msgid "" +"In Odoo, a withholding tax is defined by creating a negative tax. For a " +"retention of 10%, you would configure the following tax (accessible through " +":menuselection:`Configuration --> Taxes`):" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:32 +msgid "" +"In order to make it appear as a retention on the invoice, you should set a " +"specific tax group **Retention** on your tax, in the **Advanced Options** " +"tab." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:39 +msgid "" +"Once the tax is defined, you can use it in your products, sales order or " +"invoices." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:43 +msgid "" +"If the retention is a percentage of a regular tax, create a Tax with a **Tax" +" Computation** as a **Tax Group** and set the two taxes in this group " +"(normal tax and retention)." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:48 +msgid "Applying retention taxes on invoices" +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:50 +msgid "" +"Once your tax is created, you can use it on customer forms, sales order or " +"customer invoices. You can apply several taxes on a single customer invoice " +"line." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:58 +msgid "" +"When you see the customer invoice on the screen, you get only a **Taxes " +"line** summarizing all the taxes (normal taxes & retentions). But when you " +"print or send the invoice, Odoo does the correct grouping amongst all the " +"taxes." +msgstr "" + +#: ../../accounting/others/taxes/retention.rst:63 +msgid "The printed invoice will show the different amounts in each tax group." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:3 +msgid "How to set tax-included prices" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:5 +msgid "" +"In most countries, B2C prices are tax-included. To do that in Odoo, check " +"*Included in Price* for your sales taxes in :menuselection:`Accounting --> " +"Configuration --> Taxes`." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:12 +msgid "" +"This way the price set on the product form includes the tax. As an example, " +"let's say you have a product with a sales tax of 10%. The sales price on the" +" product form is $100." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:16 +msgid "If the tax is not included in the price, you will get:" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:18 +msgid "Price without tax: $100" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:20 +msgid "Taxes: $10" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:22 +msgid "Total to pay: $110" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:24 +msgid "If the tax is included in the price" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:26 +msgid "Price without tax: 90.91" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:28 +msgid "Taxes: $9.09" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:30 +msgid "Total to pay: $100" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:32 +msgid "" +"You can rely on following documentation if you need both tax-included (B2C) " +"and tax-excluded prices (B2B): :doc:`B2B_B2C`." +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:36 +msgid "Show tax-included prices in eCommerce catalog" +msgstr "" + +#: ../../accounting/others/taxes/tax_included.rst:38 +msgid "" +"By default prices displayed in your eCommerce catalog are tax-excluded. To " +"display it in tax-included, check *Show line subtotals with taxes included " +"(B2C)* in :menuselection:`Sales --> Configuration --> Settings` (Tax " +"Display)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:3 +msgid "How to get correct tax rates in the US thanks to TaxCloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:5 +msgid "" +"The **TaxCloud** integration allows you to calculate the sales tax for every" +" address in the United States and keeps track of which product types are " +"exempt from sales tax and in which states each exemption applies. TaxCloud " +"calculates sales tax in real-time for every state, city, and special " +"jurisdiction in the United States." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:15 +msgid "In Tax Cloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:16 +msgid "" +"Create a free account on `*TaxCloud* <https://taxcloud.net/#register>`__ " +"website." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:18 +msgid "Register your website on TaxCloud to get an *API ID* and an *API Key*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:24 +msgid "In Odoo" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:25 +msgid "" +"Go to :menuselection:`Invoicing/Accounting --> Configuration --> Settings` " +"and check *Compute sales tax automatically using TaxCloud*. Click *Apply*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:31 +msgid "Still in those settings, enter your TaxCloud credentials." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:32 +msgid "" +"Hit *Sync TaxCloud Categories (TIC)* to import TIC product categories from " +"TaxCloud (Taxability Information Codes). Some categories may imply specific " +"rates." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:39 +msgid "" +"Set default *TIC Code* and taxe rates. This will apply to any new product " +"created. A default sales tax is needed to trigger the tax computation." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:43 +msgid "" +"For products under a specific category, select it in its detail form (in " +"*Sales* tab)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:46 +msgid "" +"Make sure your company address is well defined (especially the state and the" +" zip code). Go to :menuselection:`Settings --> General Settings` and click " +"*Configure your company data*." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:51 +msgid "How it works" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:53 +msgid "" +"Automatic tax assignation works thanks to fiscal positions (see " +":doc:`application`). A specific fiscal position is created when installing " +"*TaxCloud*. Everything works out-of-the-box." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:58 +msgid "" +"This fiscal position is set on any sales order, web order, or invoice when " +"the customer country is *United States*. This is triggering the automated " +"tax computation." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:65 +msgid "" +"Add a product with a default sales tax. Odoo will automatically send a " +"request to TaxCloud, get the correct tax percentage based on the customer " +"location (state and zip code) and product TIC category, create a new tax " +"rate if that tax percentage does not already exist in your system and return" +" it in the order item line (e.g. 7.0%)." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:75 +msgid "How to create specific tax mappings using TaxCloud" +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:77 +msgid "" +"You can create several fiscal positions using TaxCloud. Check *Use TaxCloud " +"API* to do so. Such fiscal postions can be assigned to customers in their " +"detail form in order to get them by default whenever they buy you something." +msgstr "" + +#: ../../accounting/others/taxes/taxcloud.rst:86 +msgid ":doc:`default_taxes`" +msgstr "" + +#: ../../accounting/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:3 +msgid "How to setup Odoo Accounting?" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:5 +msgid "" +"The Odoo Accounting application has an implementation guide that you should " +"follow to configure it. It's a step-by-step wizard with links to the " +"different screens you will need." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:9 +msgid "" +"Once you have `installed the Accounting application " +"<https://www.odoo.com/apps/modules/online/account_accountant/>`__, you " +"should click on the top-right progressbar to get access to the " +"implementation guide." +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:17 +msgid "The implementation guide will help you through the following steps:" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:19 +msgid "Completing your company settings" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:20 +msgid "Entering in your bank accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:21 +msgid "Selecting your chart of accounts" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:22 +msgid "Confirming your usual tax rates" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:23 +msgid "Setting up any foreign currencies" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:24 +msgid "Importing your customers" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:25 +msgid "Importing your suppliers" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:26 +msgid "Importing your products" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:27 +msgid "Importing your outstanding transactions" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:28 +msgid "Importing your starting balances" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:29 +msgid "Define the users for accounting" +msgstr "" + +#: ../../accounting/overview/getting_started/setup.rst:34 +msgid "" +"Once a step is done, you can click on the \"Mark as Done\" button, in the " +"bottom of the screen. That way, you can track the progress of your overall " +"configuration of Odoo." +msgstr "" + +#: ../../accounting/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:3 +msgid "The Accounting behind Odoo" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:5 +msgid "" +"This page summarises the way Odoo deals with typical accounts and " +"transactions." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:9 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:11 +msgid "" +"Odoo automatically creates all the behind-the-scenes journal entries for " +"each of your accounting transactions: customer invoices, point of sale " +"order, expenses, inventory moves, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:15 +msgid "" +"Odoo uses the rules of double-entry bookkeeping system: all journal entries " +"are automatically balanced (sum of debits = sum of credits)." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:20 +msgid "" +"`Understand Odoo's accounting transactions per document " +"<https://odoo.com/documentation/functional/accounting.html>`__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:23 +msgid "Accrual and Cash Basis Methods" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:25 +msgid "" +"Odoo support both accrual and cash basis reporting. This allows you to " +"report income / expense at the time transactions occur (i.e., accrual " +"basis), or when payment is made or received (i.e., cash basis)." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:30 +msgid "Multi-companies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:32 +msgid "" +"Odoo allows to manage several companies within the same database. Each " +"company has its own chart of accounts and rules. You can get consolidation " +"reports following your consolidation rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:36 +msgid "" +"Users can access several companies but always work in one company at a time." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:40 +msgid "Multi-currencies" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:42 +msgid "" +"Every transaction is recorded in the default currency of the company. For " +"transactions occurring in another currency, Odoo stores both the value in " +"the currency of the company and the value in the currency of the " +"transaction. Odoo can generate currencies gains and losses after the " +"reconciliation of the journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:48 +msgid "" +"Currency rates are updated once a day using a yahoo.com online web-service." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:52 +msgid "International Standards" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:54 +msgid "" +"Odoo accounting support more than 50 countries. The Odoo core accounting " +"implement accounting standards that is common to all countries and specific " +"modules exists per country for the specificities of the country like the " +"chart of accounts, taxes, or bank interfaces." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:60 +msgid "In particular, Odoo's core accounting engine supports:" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:62 +msgid "" +"Anglo-Saxon Accounting (U.S., U.K.,, and other English-speaking countries " +"including Ireland, Canada, Australia, and New Zealand) where cost of good " +"sold are reported when products are sold/delivered." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:66 +msgid "European accounting where expenses are accounted at the supplier bill." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:68 +msgid "" +"Storno accounting (Italy) where refund invoices have negative credit/debit " +"instead of a reverting the original journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:71 +msgid "Odoo also have modules to comply with IFRS rules." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:74 +msgid "Accounts Receivable & Payable" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:76 +msgid "" +"By default, Odoo uses a single account for all account receivable entries " +"and one for all accounts payable entries. You can create separate accounts " +"per customers/suppliers, but you don't need to." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:81 +msgid "" +"As transactions are associated to customers or suppliers, you get reports to" +" perform analysis per customer/supplier such as the customer statement, " +"revenues per customers, aged receivable/payables, ..." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:86 +msgid "Wide range of financial reports" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:88 +msgid "" +"In Odoo, you can generate financial reports in real time. Odoo's reports " +"range from basic accounting reports to advanced management reports. Odoo's " +"reports include:" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:92 +msgid "Performance reports (such as Profit and Loss, Budget Variance)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:93 +msgid "" +"Position reports (such as Balance Sheet, Aged Payables, Aged Receivables)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:95 +msgid "Cash reports (such as Bank Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:96 +msgid "Detail reports (such as Trial Balance and General Ledger)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:97 +msgid "Management reports (such as Budgets, Executive Summary)" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:99 +msgid "" +"Odoo's report engine allows you to customize your own report based on your " +"own formulae." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:103 +msgid "Import bank feeds automatically" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:105 +msgid "" +"Bank reconciliation is a process that matches your bank statement lines, as " +"supplied by the bank, to your accounting transactions in the general ledger." +" Odoo makes bank reconciliation easy by frequently importing bank statement " +"lines from your bank directly into your Odoo account. This means you can " +"have a daily view of your cashflow without having to log into your online " +"banking or wait for your paper bank statements." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:113 +msgid "" +"Odoo speeds up bank reconciliation by matching most of your imported bank " +"statement lines to your accounting transactions. Odoo also remembers how " +"you've treated other bank statement lines and provides suggested general " +"ledger transactions." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:119 +msgid "Calculates the tax you owe your tax authority" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:121 +msgid "" +"Odoo totals all your accounting transactions for your tax period and uses " +"these totals to calculate your tax obligation. You can then check your sales" +" tax by running Odoo's Tax Report." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:126 +msgid "Inventory Valuation" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:128 +msgid "" +"Odoo support both periodic (manual) and perpetual (automated) inventory " +"valuations. The available methods are standard price, average price, LIFO " +"(for countries allowing it) and FIFO." +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:134 +msgid "" +"`View impact of the valuation method on your transactions " +"<https://odoo.com/documentation/functional/valuation.html>`__" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:137 +msgid "Easy retained earnings" +msgstr "" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:139 +msgid "" +"Retained earnings is the portion of income retained by your business. Odoo " +"automatically calculates your current year earnings in real time so no year-" +"end journal or rollover is required. This is calculated by reporting the " +"profit and loss balance to your balance sheet report automatically." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:3 +msgid "Introduction to Odoo Accounting" +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:13 +msgid "" +"Odoo is beautiful accounting software designed for the needs of the 21st " +"century." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:15 +msgid "" +"Odoo connects directly to your bank or paypal account. Transactions are " +"synchronized every hour and reconciliation is blazing fast. It's like magic." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:18 +msgid "" +"Instantly create invoices and send them with just a click. No need to print " +"them." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:20 +msgid "Odoo can send them for you by email or regular mail." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:22 +msgid "Your customers pay online, meaning you get your money right away." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:24 +msgid "" +"Odoo accounting is connected with all Odoo our apps such as sale, purchase, " +"inventory and subscriptions." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:27 +msgid "" +"This way, recording vendor bills is also super quick. Set a vendor, select " +"the purchase order and Odoo fills in everything for you automatically." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:30 +msgid "" +"Then, just use the SEPA protocol or print checks to pay vendors in batches." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:33 +msgid "It's that easy with Odoo." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:35 +msgid "" +"Wait, there is more. You will love the Odoo reports. From legal statements " +"to executive summaries, they are fast and dynamic. Use Odoo's business " +"intelligence feature to navigate through all your companies data." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:39 +msgid "" +"Of course, Odoo is mobile too. You can use it to check your accounts on the " +"go." +msgstr "" + +#: ../../accounting/overview/main_concepts/intro.rst:41 +msgid "Try Odoo now, and join 2 millions of happy users." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:5 +msgid "Accounting Memento For Entrepreneurs (US GAAP)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:11 +msgid "" +"The **Profit and Loss** (P&L) report shows the performance of the company " +"over a specific period (usually the current year)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:16 +msgid "" +"The **Gross Profit** equals the revenues from sales minus the cost of goods " +"sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:21 +msgid "" +"**Operating Expenses** (OPEX) include administration, sales and R&D salaries" +" as well as rent and utilities, miscellaneous costs, insurances, … anything " +"beyond the costs of products sold." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:27 +msgid "" +"The **Balance Sheet** is a snapshot of the company's finances at a specific " +"date (as opposed to the Profit and Loss which is an analysis over a period)" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:32 +msgid "" +"**Assets** represent the company's wealth, things it owns. Fixed assets " +"includes building and offices, current assets include bank accounts and " +"cash. A client owing money is an asset. An employee is not an asset." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:38 +msgid "" +"**Liabilities** are obligations from past events that the company will have " +"to pay in the future (utility bills, debts, unpaid suppliers)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:43 +msgid "" +"**Equity** is the amount of the funds contributed by the owners (founders or" +" shareholders) plus previously retained earnings (or losses)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:48 +msgid "Each year, net profits (or losses) are reported to retained earnings." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:54 +msgid "" +"What is owned (an asset) has been financed through debts to reimburse " +"(liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:57 +msgid "" +"A difference is made between buying an assets (e.g. a building) and expenses" +" (e.g. fuel). Assets have an intrinsic value over time, versus expenses " +"having value in them being consumed for the company to \"work\"." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:64 +msgid "Assets = Liabilities + Equity" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:67 +msgid "Chart of Accounts" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:69 +msgid "" +"The **chart of accounts** lists all the accounts, whether they are balance " +"sheet accounts or P&L accounts. Every financial transaction (e.g. a payment," +" an invoice) impacts accounts by moving value from one account (credit) to " +"an other account (debit)." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:76 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:84 +msgid "Journal Entries" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:86 +msgid "" +"Every financial document of the company (e.g. an invoice, a bank statement, " +"a pay slip, a capital increase contract) is recorded as a journal entry, " +"impacting several accounts." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:90 +msgid "" +"For a journal entry to be *balanced*, the sum of all its debits must be " +"equal to the sum of all its credits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:95 +msgid "examples of accounting entries for various transactions. Example:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:97 +msgid "Example 1: Customer Invoice:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:99 +#: ../../accounting/overview/main_concepts/memento.rst:117 +msgid "Explanation:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:101 +msgid "You generate a revenue of $1,000" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:102 +msgid "You have a tax to pay of $90" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:103 +msgid "The customer owes $1,090" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:105 +#: ../../accounting/overview/main_concepts/memento.rst:122 +msgid "Configuration:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:107 +msgid "Income: defined on the product, or the product category" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:108 +#: ../../accounting/overview/main_concepts/memento.rst:125 +msgid "Account Receivable: defined on the customer" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:109 +msgid "Tax: defined on the tax set on the invoice line" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:111 +msgid "" +"The fiscal position used on the invoice may have a rule that replaces the " +"Income Account or the tax defined on the product by another one." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:115 +msgid "Example 2: Customer Payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:119 +msgid "Your customer owes $1,090 less" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:120 +msgid "Your receive $1,090 on your bank account" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:124 +msgid "Bank Account: defined on the related bank journal" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:130 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/overview/main_concepts/terminologies.rst:26 +msgid "Reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:132 +msgid "" +"Reconciliation is the process of linking journal items of a specific " +"account, matching credits and debits." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:135 +msgid "" +"Its primary purpose is to link payments to their related invoices in order " +"to mark invoices that are paid and clear the customer statement. This is " +"done by doing a reconciliation on the *Accounts Receivable* account." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:139 +msgid "" +"An invoice is marked as paid when its Accounts Receivable journal items are " +"reconciled with the related payment journal items." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:142 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:144 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:145 +msgid "" +"the links between the payments and the invoices are detected at the bank " +"matching process" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Accounts Receivable" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Debit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:156 +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Credit" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:158 +msgid "Invoice 1" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:158 +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:244 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:63 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:77 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:62 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:76 +msgid "100" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:160 +msgid "Payment 1.1" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:160 +msgid "70" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +msgid "Invoice 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:162 +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "65" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "Payment 1.2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:164 +msgid "30" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:166 +msgid "Payment 2" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +msgid "Invoice 3" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:168 +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "50" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:172 +msgid "Total To Pay" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:179 +msgid "" +"Bank reconciliation is the matching of bank statement lines (provided by " +"your bank) with transactions recorded internally (payments to suppliers or " +"from customers). For each line in a bank statement, it can be:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "matched with a previously recorded payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:184 +msgid "" +"a payment is registered when a check is received from a customer, then " +"matched when checking the bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:188 +msgid "recorded as a new payment:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:187 +msgid "" +"the payment's journal entry is created and :ref:`reconciled " +"<accounting/reconciliation>` with the related invoice when processing the " +"bank statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "recorded as another transaction:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:191 +msgid "bank transfer, direct charge, etc." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:193 +msgid "" +"Odoo should automatically reconcile most transactions, only a few of them " +"should need manual review. When the bank reconciliation process is finished," +" the balance on the bank account in Odoo should match the bank statement's " +"balance." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:201 +msgid "Checks Handling" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:203 +msgid "There are two approaches to manage checks and internal wire transfer:" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:205 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:206 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:210 +msgid "" +"The first journal entry is created by registering the payment on the " +"invoice. The second one is created when registering the bank statement." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:216 +#: ../../accounting/overview/main_concepts/memento.rst:226 +#: ../../accounting/overview/main_concepts/memento.rst:242 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Account" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:244 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:61 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:60 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +#: ../../accounting/receivables/customer_payments/check.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +msgid "Account Receivable" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:218 +#: ../../accounting/overview/main_concepts/memento.rst:244 +msgid "Invoice ABC" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Undeposited funds" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:220 +#: ../../accounting/overview/main_concepts/memento.rst:228 +msgid "Check 0123" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:230 +#: ../../accounting/overview/main_concepts/memento.rst:246 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/receivables/customer_payments/check.rst:85 +#: ../../accounting/receivables/customer_payments/check.rst:135 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 +msgid "Bank" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:235 +msgid "" +"A journal entry is created by registering the payment on the invoice. When " +"reconciling the bank statement, the statement line is linked to the existing" +" journal entry." +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:242 +msgid "Bank Statement" +msgstr "" + +#: ../../accounting/overview/main_concepts/memento.rst:246 +msgid "Statement XYZ" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:3 +msgid "Accounting Terminologies" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:6 +msgid "Journal" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:9 +msgid "" +"A journal is like a folder in which you record all transactions of the same " +"type: all the statements of a bank account, all customer invoices, all " +"supplier bills. It's used to organize similar transactions together." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:13 +msgid "Payment Terms" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:16 +msgid "" +"Payment terms describe how and when a customer invoice (or supplier bill) " +"should be paid over the time. Example: 30% direct payment, balance due in " +"two months." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:22 +msgid "" +"Bank reconciliation is the process of matching transactions from your bank " +"records with existing journal items or creating new journal items on the " +"fly. It is a process of verification to ensure that your bank and your " +"records in Odoo say the same thing." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:29 +msgid "" +"Journal items reconciliation is the process of linking several journal items" +" together like an invoice and a payment. This allows you to mark invoices as" +" paid. It is also useful when comparing values of 'goods received not " +"invoiced' and 'goods shipped not billed' accounts." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:33 +msgid "Deposit Ticket" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:36 +msgid "" +"Deposit tickets group several payment orders (usually checks) that are " +"deposited together at the bank at the same time. This allows an easy " +"reconciliation with the bank statement line if the line has one line per " +"deposit." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:40 +msgid "Journal Entry" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:43 +msgid "" +"A journal entry is an accounting transaction, usually related to a financial" +" document: invoice, payment, receipt, etc. A journal entry always consists " +"of at least two lines, described here as journal items, which credit or " +"debit specific accounts. The sum of the credits of all journal items of a " +"journal entry must be equal to the sum of their debits for the entry to be " +"valid." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:50 +msgid "Journal Item" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:53 +msgid "" +"A line of a journal entry, with a monetary debit or credit associated with a" +" specific account." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:55 +msgid "Analytic Accounts" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:58 +msgid "" +"Sometimes called **Cost Accounts**, are accounts that are not part of the " +"chart of accounts and that allow you to track costs and revenues. Analytic " +"accounts are usually grouped by projects, departments, etc. for analysis of " +"a company's expenditures. Every journal item is posted in a regular account " +"in the chart of account and can be posted to an analytic account for the " +"purpose of reporting or analysis." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:65 +msgid "Analytic Entries" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:68 +msgid "" +"Costs or revenues posted to analytic accounts, usually related to journal " +"entries." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:70 +msgid "Sales Receipt" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:73 +msgid "" +"A receipt or other slip of paper issued by a store or other vendor " +"describing the details of a purchase (amount, date, department, etc.). Sales" +" receipt are usually used instead of invoices if the sale is paid in cash in" +" a store." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:80 +msgid "" +"Property owned by the company, usually with a useful life greater than one " +"reporting period. Odoo Asset management is used to manage the depreciation /" +" amortization of the asset over the time. Typical examples would be capital " +"equipment, vehicles, and real estate." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:84 +msgid "Deferred Revenues" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:87 +msgid "" +"Are used to recognize revenues for sales of services that are provided over " +"a long period of time. If you sell a 3 year maintenance contract, you can " +"use the deferred revenue mechanism to recognize 1/36 of the revenue every " +"month until the contract expires, rather than taking it all initially or at " +"the end." +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:93 +msgid "Fiscal Position" +msgstr "" + +#: ../../accounting/overview/main_concepts/terminologies.rst:96 +msgid "" +"Define the taxes that should be applied for a specific customer/vendor or " +"invoice. Example: If some customers benefit from specific taxes (government," +" construction companies, EU companies that are VAT subjected,…), you can " +"assign a fiscal position to them and the right tax will be selected " +"according to the products they buy." +msgstr "" + +#: ../../accounting/overview/process_overview.rst:3 +msgid "Process overview" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:3 +msgid "From Invoice to Payment Collection" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:5 +msgid "" +"Odoo supports multiple invoicing and payment workflows, so you can choose " +"and use the ones that match your business needs. Whether you want to accept " +"a single payment for a single invoice, or process a payment spanning " +"multiple invoices and taking discounts for early payments, you can do so " +"efficiently and accurately." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:12 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:14 +msgid "" +"If we pick up at the end of a typical 'order to cash' scenario, after the " +"goods have been shipped, you will: issue an invoice; receive payment; " +"deposit that payment at the bank; make sure the Customer Invoice is closed; " +"follow up if Customers are late; and finally present your Income on the " +"Profit and Loss report and show the decrease in Assets on the Balance Sheet " +"report." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:21 +msgid "" +"Invoicing in most countries occurs when a contractual obligation is met. If " +"you ship a box to a customer, you have met the terms of the contract and can" +" bill them. If your supplier sends you a shipment, they have met the terms " +"of that contract and can bill you. Therefore, the terms of the contract is " +"fulfilled when the box moves to or from the truck. At this point, Odoo " +"supports the creation of what is called a Draft Invoice by Warehouse staff." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:30 +msgid "Invoice creation" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:32 +msgid "" +"Draft invoices can be manually generated from other documents such as Sales " +"Orders, Purchase Orders,etc. Although you can create a draft invoice " +"directly if you would like." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:36 +msgid "" +"An invoice must be provided to the customer with the necessary information " +"in order for them to pay for the goods and services ordered and delivered. " +"It must also include other information needed to pay the invoice in a timely" +" and precise manner." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:42 +msgid "Draft invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:44 +msgid "" +"The system generates invoice which are initially set to the Draft state. " +"While these invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:47 +msgid "" +"remain unvalidated, they have no accounting impact within the system. There " +"is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:50 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:52 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:53 +msgid "Product: iMac" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:54 +msgid "Quantity: 1" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:55 +msgid "Unit Price: 100" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:56 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:64 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:66 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:67 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:68 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:71 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:73 +msgid "" +"An invoice will usually include the quantity and price the of goods and/or " +"services, the date, any parties involved, the unique invoice number, and any" +" tax information." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:77 +msgid "" +"\"Validate\" the invoice when you are ready to approve it. The invoice then " +"moves from the Draft state to the Open state." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:80 +msgid "" +"When you have validated an invoice, Odoo gives it a unique number from a " +"defined, and modifiable, sequence." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:86 +msgid "" +"Accounting entries corresponding to this invoice are automatically generated" +" when you validate the invoice. You can see the details by clicking on the " +"entry in the Journal Entry field in the \"Other Info\" tab." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:95 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:97 +msgid "" +"After validating the customer invoice, you can directly send it to the " +"customer via the 'Send by email' functionality." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:103 +msgid "" +"A typical journal entry generated from a validated invoice will look like as" +" follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:107 +#: ../../accounting/overview/process_overview/customer_invoice.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:109 +#: ../../accounting/overview/process_overview/customer_invoice.rst:130 +#: ../../accounting/overview/process_overview/customer_invoice.rst:132 +msgid "115" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:111 +msgid "15" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/overview.rst:16 +msgid "Sales" +msgstr "Satış" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:117 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:89 +msgid "Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:119 +msgid "" +"In Odoo, an invoice is considered to be paid when the associated accounting " +"entry has been reconciled with the payment entries. If there has not been a " +"reconciliation, the invoice will remain in the Open state until you have " +"entered the payment." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:124 +msgid "" +"A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:138 +msgid "" +"You can manually enter your bank statements in Odoo, or you can import them " +"in from a csv file or from several other predefined formats according to " +"your accounting localisation." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:142 +msgid "" +"Create a bank statement from the accounting dashboard with the related " +"journal and enter an amount of $100 ." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:149 +msgid "Reconcile" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:151 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:156 +msgid "" +"You can now go through every transaction and reconcile them or you can mass " +"reconcile with instructions at the bottom." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:158 +msgid "" +"After reconciling the items in the sheet, the related invoice will now " +"display \"You have outstanding payments for this customer. You can reconcile" +" them to pay this invoice. \"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:168 +msgid "" +"Apply the payment. Below, you can see that the payment has been added to the" +" invoice." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:175 +msgid "Payment Followup" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:177 +msgid "" +"There's a growing trend of customers paying bills later and later. " +"Therefore, collectors must make every effort to collect money and collect it" +" faster." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:181 +msgid "" +"Odoo will help you define your follow-up strategy. To remind customers to " +"pay their outstanding invoices, you can define different actions depending " +"on how severely overdue the customer is. These actions are bundled into " +"follow-up levels that are triggered when the due date of an invoice has " +"passed a certain number of days. If there are other overdue invoices for the" +" same customer, the actions of the most overdue invoice will be executed." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:189 +msgid "" +"By going to the customer record and diving into the \"Overdue Payments\" you" +" will see the follow-up message and all overdue invoices." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:199 +msgid "Customer aging report:" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:201 +msgid "" +"The customer aging report will be an additional key tool for the collector " +"to understand the customer credit issues, and to prioritize their work." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:205 +msgid "" +"Use the aging report to determine which customers are overdue and begin your" +" collection efforts." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:212 +msgid "Profit and loss" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:214 +msgid "" +"The Profit and Loss statement displays your revenue and expense details. " +"Ultimately, this gives you a clear image of your Net Profit and Loss. It is " +"sometimes referred to as the \"Income Statement\" or \"Statement of Revenues" +" and Expenses.\"" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:223 +msgid "Balance sheet" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:225 +msgid "" +"The balance sheet summarizes the your company's liabilities, assets and " +"equity at a specific moment in time." +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:234 +msgid "" +"For example, if you manage your inventory using the perpetual accounting " +"method, you should expect a decrease in account \"Current Assets\" once the " +"material has been shipped to the customer." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:3 +msgid "From Vendor Bills to Payments" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:5 +msgid "" +"Once vendor bills are registered in Odoo, you can easily pay vendors for the" +" correct amount and at the right time (not too late, not too early; " +"depending on your vendor policy). Odoo also offers reports to track your " +"aged payable balances." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:10 +msgid "" +"If you want to control vendor bills received from your vendors, you can use " +"the Odoo Purchase application that allows you to control and pre-complete " +"them automatically based on past purchase orders." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:15 +msgid "From Vendor Bill to Payment" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:18 +msgid "Record a new vendor bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:20 +msgid "" +"When a vendor bill is received, you can record it from " +":menuselection:`Purchases --> Vendor Bills` in the Accounting application. " +"As a shortcut, you can also use the **New Bill** feature on the accounting " +"dashboard." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:27 +msgid "" +"To register a new vendor bill, start by selecting a vendor and inputting " +"their invoice as the **Vendor Reference**, then add and confirm the product " +"lines, making sure to have the right product quantities, taxes and prices." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:35 +msgid "" +"Save the invoice to update the pre tax and tax amounts at the bottom of the " +"screen. You will most likely need to configure the prices of your products " +"without taxes as Odoo will compute the tax for you." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:40 +msgid "" +"On the bottom left corner, Odoo shows a summary table of all taxes on the " +"vendor bill. In several countries, different methods are accepted to round " +"the totals (round per line, or round globally). The default rounding method " +"in Odoo is to round the final prices per line (as you may have different " +"taxes per product. E.g. Alcohol and cigarettes). However if your vendor has " +"a different tax amount on their bill, you can change the amount in the " +"bottom left table to adjust and match." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:48 +msgid "Validate The Vendor Bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:50 +msgid "" +"Once the vendor bill is validated, a journal entry will be generated based " +"on the configuration on the invoice. This journal entry may differ depending" +" on the the accounting package you choose to use." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:54 +msgid "" +"For most European countries, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:57 +#: ../../accounting/overview/process_overview/supplier_bill.rst:66 +msgid "**Accounts Payable:** defined on the vendor form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:59 +#: ../../accounting/overview/process_overview/supplier_bill.rst:68 +msgid "**Taxes:** defined on the products and per line" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:61 +msgid "**Expenses:** defined on the line item product used" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:63 +msgid "" +"For Anglo-Saxon (US) accounting, the journal entry will use the following " +"accounts:" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:70 +msgid "**Goods Received:** defined on the product form" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:72 +msgid "" +"You can check your Profit & Loss or the Balance Sheet reports after having " +"validated a couple of vendor bills to see the impact on your general ledger." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:77 +msgid "Pay a bill" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:79 +msgid "" +"To create a payment for an open vendor bill directly, you can click on " +"**Register a Payment** at the top of the form." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:82 +msgid "" +"From there, you select the payment method (i.e. Checking account, credit " +"card, check, etc…) and the amount you wish to pay. By default, Odoo will " +"propose the entire remaining balance on the bill for payment. In the memo " +"field, we recommend you set the vendor invoice number as a reference (Odoo " +"will auto fill this field from the from the vendor bill if set it " +"correctly)." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:94 +msgid "" +"You can also register a payment to a vendor directly without applying it to " +"a vendor bill. To do that, :menuselection:`Purchases --> Payments`. Then, " +"from the vendor bill you will be able to reconcile this payment with " +"directly." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:99 +msgid "Printing vendor Checks" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:101 +msgid "" +"If you choose to pay your vendor bills by check, Odoo offers a method to do " +"so directly from your vendor payments within Odoo. Whether you do so on a " +"daily basis or prefer to do so at the end of the week, you can print in " +"checks in batches." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:106 +msgid "" +"If you have checks to print, Odoo's accounting dashboard acts as a to do " +"list and reminds you of how many checks you have left to be printed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:112 +msgid "" +"By selecting the amount of checks to be printed, you can dive right into a " +"list of all payments that are ready to be processed." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:115 +msgid "" +"Select all the checks you wish to print (use the first checkbox to select " +"them all) and set the action to **Print Checks**. Odoo will ask you to set " +"the next check number in the sequence and will then print all the checks at " +"once." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:127 +msgid "Aged payable balance" +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:129 +msgid "" +"In order to get a list of open vendor bills and their related due dates, you" +" can use the **Aged Payable** report, under the reporting menu, (in " +":menuselection:`Reporting --> Business Statement --> Aged payable`) to get a" +" visual of all of your outstanding bills." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:137 +msgid "" +"From here, you can click directly on a vendors name to open up the details " +"of all outstanding bills and the amounts due, or you can annotate any line " +"for managements information. At any point in time while you're looking " +"through the report, you can print directly to Excel or PDF and get exactly " +"what you see on the screen." +msgstr "" + +#: ../../accounting/overview/process_overview/supplier_bill.rst:144 +msgid ":doc:`customer_invoice`" +msgstr "" + +#: ../../accounting/payables.rst:3 +msgid "Account Payables" +msgstr "" + +#: ../../accounting/payables/misc.rst:3 +msgid "Misc" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:3 +msgid "How to keep track of employee expenses?" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:5 +msgid "" +"Employee expenses are charges incurred on behalf of the company. The company" +" then reimburses these expenses to the employee. The receipts encountered " +"most frequently are:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:9 +msgid "car travel, reimbursed per unit of distance (mile or kilometer)," +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:11 +msgid "subsistence expenses, reimbursed based on the bill," +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:13 +msgid "" +"other purchases, such as stationery and books, destined for the company but " +"carried out by the employee." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:19 +msgid "" +"To manage expenses, you need to install the **Expense Tracker** application " +"from the Apps module." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:22 +msgid "" +"You will also need to install the **Sales Management** module in order to " +"re-invoice your expenses to your customers." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:25 +msgid "" +"Once these applications are installed you can configure the different " +"products that represent the types of expenses. To create the firsts " +"products, go to the menu :menuselection:`Configuration --> Expenses " +"Products` in the **Expenses** application." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:30 +msgid "Some examples of products can be:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:32 +msgid "**Travel (car)**" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:34 +#: ../../accounting/payables/misc/employee_expense.rst:50 +msgid "Product Type: Service" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:36 +#: ../../accounting/payables/misc/employee_expense.rst:52 +msgid "Invoicing Policy: Invoice based on time and material" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:38 +msgid "Expense Invoice Policy: At sales price" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:40 +msgid "Sale Price: 0.32" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:42 +msgid "" +"Unit of Measure: Km or mile (you will need to enable the **Multiple Unit of " +"Measures** option from :menuselection:`Sales module --> Configuration`)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:48 +msgid "**Hotel**" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:54 +msgid "Expense Invoice Policy: At cost" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:56 +msgid "Unit of Measure: Unit" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:58 +msgid "" +"In these examples, the first product will be an expense we reimburse to the " +"employee based on the number of km he did with his own car (e.g. to visit a " +"customer): 0.32€ / km. The hotel is reimbursed based on the real cost of the" +" hotel." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:63 +msgid "" +"Be sure that all these products have the checkbox **Can be expensed** " +"checked and the invoicing policy set to **Invoice Based on time and " +"material**. This invoicing policy means that, if the expense is related to a" +" customer project/sale order, Odoo will re-invoice this expense to the " +"customer." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:69 +msgid "Odoo support two types of expenses:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:71 +msgid "expenses paid by employee with their own money" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:73 +msgid "expenses paid with a company credit card" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:76 +msgid "The expenses workflow" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:79 +msgid "Record a new expense" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:81 +msgid "" +"Every employee of the company can register their expenses from " +":menuselection:`Expenses application --> My Expenses`. The workflow for " +"personal expenses work that way:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:85 +msgid "an employee record his expense, and submit it to the manager" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:87 +msgid "the manager approve or refuse the expense" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:89 +msgid "the accountant post journal entries" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:91 +msgid "" +"the company reimburse the employee expense (the employee is like a vendor, " +"with a payable account)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:94 +msgid "" +"if the expense is linked to an analytic account, the company can reinvoice " +"the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:97 +msgid "For every expense, the employee should record at least:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:99 +msgid "a description: that should include the reference of the ticket / bill" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:101 +msgid "a product: the expense type" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:103 +msgid "" +"a price (e.g. hotel) or a quantity (e.g. reimburse km if travel with his own" +" car)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:106 +msgid "" +"Depending of the policy of the company, he might have to attach a scan or a " +"photo of the expense. To do that, just a write a message in the bottom of " +"the expense with the scan of the bill/ticket in attachment." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:113 +msgid "" +"If the expense is linked to a customer project, you should not forget to set" +" an analytic account, related to the customer project or sale order (you " +"might have to activate analytic accounts in the accounting settings to get " +"this feature)." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:118 +msgid "" +"Once the expense is fully recorded, the employee has to click the button " +"**Submit to Manager**. In some companies, employees should submit their " +"expenses grouped at the end of the month, or at the end of a business trip." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:123 +msgid "" +"An employee can submit all his expenses in batch, using the Submit Expenses " +"action from the list view of expenses, or the small icons in the list view." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:128 +msgid "Validation by the manager" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:130 +msgid "" +"Managers should receive an email for every expense to be approved (the " +"manager of an employee is defined on the employee form). They can use the " +"menu **To Approve** to check all expenses that are waiting for validation." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:135 +msgid "The manager can:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:137 +msgid "" +"discuss on an expense to ask for more information (e.g., if a scan of the " +"bill is missing);" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:140 +msgid "reject an expense;" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:142 +msgid "approve an expense." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:145 +msgid "Control by the accountant" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:147 +msgid "" +"Then, all expenses that have been validated by the manager should be posted " +"by the accountant. When an expense is posted, the related journal entry is " +"created and posted in your accounting." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:151 +msgid "" +"If the accountant wants to create only one journal entry for a batch of " +"expenses, he can post expenses in batch from the list view of all expenses." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:156 +msgid "Reinvoice expenses to customers" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:158 +msgid "" +"If the expense was linked to an analytic account related to a sale order, " +"the sale order has a new line related to the expense. This line is not " +"invoiced to the customer yet and will be included in the next invoice that " +"will be send to the customer (charge travel and accommodations on a customer" +" project)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:164 +msgid "" +"To invoice the customer, just click on the invoice button on his sale order." +" (or it will be done automatically at the end of the week/month if you " +"invoice all your orders in batch)" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:176 +msgid "Reimburse the employee" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:178 +msgid "" +"If the expense was paid with the employee's own money, the company should " +"reimburse the employee. In such a case, the employee will appear in the aged" +" payable balance until the company reimburse him his expenses." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:183 +msgid "" +"All you have to do is to create a payment to this employee for the amount " +"due." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:190 +msgid "Expenses that are not reinvoiced to customers" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:192 +msgid "" +"If some expenses should not be reinvoiced to customers, you have two " +"options:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:195 +msgid "" +"if the decision to invoice or not is related to the product, change the " +"invoicing policy on the product:" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:198 +msgid "**based on time and material**: reinvoice the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:200 +msgid "**based on sale orders**: do not reinvoice the customer" +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:202 +msgid "" +"if you have to make an exception for one invoice that should not be " +"reinvoiced to the customer, do not set the related analytic account for this" +" invoice." +msgstr "" + +#: ../../accounting/payables/misc/employee_expense.rst:208 +msgid ":doc:`forecast`" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:3 +msgid "How to forecast future bills to pay?" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:5 +msgid "" +"When you get hundreds of vendor bills per month with each of them having " +"different payment terms, it could be complex to follow what you have to pay " +"and when. Paying your vendors too early can decrease your cash " +"availabilities and paying too late can lead to extra charges." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:10 +msgid "" +"Fortunately, Odoo provides you the right tools to manage payment orders to " +"vendors efficiently." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:14 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:16 +msgid "" +"In order to track the vendor conditions, we use payment terms in Odoo. " +"Payment terms allow to keep track of the conditions to compute the due date " +"on an invoice. As an example, a payment term can be:" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:20 +msgid "50% within 30 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:22 +msgid "50% within 45 days" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:24 +msgid "" +"To create your most common payment terms, use the menu: " +":menuselection:`Configuration --> Management --> Payment Terms` in the " +"**Accounting** application. The following example show a payment term of 30%" +" directly and the balance after 30 days." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:32 +msgid "" +"Once payment terms are defined, you can assign them to your vendor by " +"default. Set the Vendor Payment Term field on the Accounting tab of a vendor" +" form. That way, every time you will purchase to this vendor, Odoo will " +"propose you automatically the right payment term." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:42 +msgid "" +"If you do not set a specific payment term on a vendor, you will still be " +"able to set a specific payment term on the vendor bill." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:46 +msgid "Forecast bills to pay with the Aged Payables report" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:48 +msgid "" +"In order to track amounts to be paid to the vendors, use the Aged Payable " +"report. You can get it from the Reports menu of the Accounting application. " +"This report gives you a summary per vendor of the amounts to pay, compared " +"to their due date (the due date being computed on each bill using the " +"payment term)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:57 +msgid "" +"This reports tells you how much you will have to pay within the next months." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:61 +msgid "Select bills to pay" +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:63 +msgid "" +"Using the menu :menuselection:`Purchases --> Vendor Bills`, you can get a " +"list of vendor bills. Using the advanced filters, you can list all the bills" +" that you should pay or the bills that are overdue (you are late on the " +"payment)." +msgstr "" + +#: ../../accounting/payables/misc/forecast.rst:70 +msgid "" +"From this screen, you can also switch to the pivot table or the graph view " +"to get statistics on the amount due over the next month, using the group by " +"\"Due Date\" feature." +msgstr "" + +#: ../../accounting/payables/pay.rst:3 +msgid "Pay supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:3 +msgid "Pay by Checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:5 +msgid "" +"Once you decide to pay a supplier bill, you can select to pay by check. " +"Then, at the end of the day, the manager can print all checks by batch. " +"Finally, the bank reconciliation process will match the checks you sent to " +"suppliers with actual bank statements." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:14 +#: ../../accounting/payables/pay/sepa.rst:29 +msgid "Install the required module" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:16 +msgid "" +"To record supplier payments by checks, you must install the **Check " +"Writing** module. This module handle the process of recording checks in " +"Odoo. Others modules are necessary to print checks, according to the " +"country. As an example, the **U.S. Check Printing** module is required to " +"print U.S. checks." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:24 +msgid "" +"According to your country and the chart of account you use, those modules " +"may be installed by default. (example: United States users have nothing to " +"install, it's configured by default)." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:29 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:31 +msgid "" +"In order to allow payments by checks, you must activate the payment method " +"on related bank journals. From the accounting dashboard (the screen you get " +"when you enter the accounting application), click on your bank account on " +":menuselection:`More --> Settings` option. On the **Payment Method** field, " +"set **Check**." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:41 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:44 +msgid "United States" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:46 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:48 +msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:49 +msgid "**Peachtree**: check in the middle, stubs on top and bottom" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:50 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:52 +msgid "" +"It is also possible to customize your own check format through " +"customizations." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:55 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:57 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:59 +msgid "registering a payment you'd like to do on the bill" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:60 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:61 +msgid "reconcile bank statements" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:64 +msgid "Register a payment by check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:66 +msgid "" +"To register a payment on a bill, open any supplier bill from the menu " +":menuselection:`Purchases --> Supplier Bills`. Once the supplier bill is " +"validated, you can register a payment. Set the **Payment Method** to " +"**Check** and validate the payment dialog." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:74 +msgid "Explanation of the fields of the payment screen:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field used for usability purposes" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to hide the payment method if the selected journal has " +"only one available which is 'manual'" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to adapt the interface to the payment type selected." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"The selected journal is configured to print check numbers. If your pre-" +"printed check paper already has numbers or if the current numbering is " +"wrong, you can change it in the journal configuration page." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:80 +msgid "Try paying a supplier bill with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:85 +msgid "Print checks" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:87 +msgid "" +"From the accounting dashboard, on your bank account, you should see a link " +"\"X checks to print\". Click on this link and you will get the list of all " +"checks that are not printed yet. From this screen, you can print all checks " +"in batch or review them one by one." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:92 +msgid "" +"If you want to review every payment one by one before printing the check, " +"open on the payment and click on **Print Check** if you accept it. A dialog " +"will ask you the number of the check. It automatically proposes you the next" +" number, but you can change it if it does not match your next check number." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:98 +msgid "" +"To print all checks in batch, select all payments from the list view and " +"Print Check from the top \"print\" menu." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:107 +msgid "Reconcile Bank Statements" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:109 +msgid "" +"Once you process your bank statement, when the check is credited from your " +"bank account, Odoo will propose you automatically to match it with the " +"payment. This will mark the payment as **Reconciled**." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:115 +msgid "" +"to review checks that have not been credited, open the list of payments and " +"filter on the Sent state. Review those payments that have a date more than 2" +" weeks ago." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:120 +msgid "Pay anything with a check" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:122 +msgid "" +"You can register a payment that is not related to a supplier bill. To do so," +" use the top menu :menuselection:`Purchases --> Payments`. Register your " +"payment and select a payment method by check." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:126 +msgid "" +"If you pay a specific supplier bill, put the reference of the bill in the " +"**Memo** field." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:132 +msgid "" +"Once your payment by check is registered, don't forget to **Confirm** it. " +"Once confirmed, you can use **Print Check** directly or follow the preceding" +" flow to print checks in batch:" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:136 +msgid "`Print checks <PrintChecks_>`_" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:138 +msgid "`Reconcile bank statements <ReconicleBankStatements_>`_" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:3 +msgid "How to pay several bills at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:5 +msgid "" +"Odoo provides a simple and effective way to handle several bills at once, " +"with various quick or complex options. With one single process, anyone is " +"able to handle bills and payment in just a few clicks." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:10 +msgid "Pay multiple bills with one payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:13 +msgid "Record several payments" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:15 +msgid "" +"In the following example, we will generate some bills. You can control the " +"whole process from your accounting dashboard (first screen you get when you " +"open the accounting application)." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:22 +msgid "" +"To create a bill, open the Dashboard menu and click on **Vendor Bills**. In " +"the Vendor Bills window, click on **Create**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:28 +msgid "" +"Choose the vendor from which you wish to purchase the product, and click on " +"Add an item to add one (or more) product(s). Click on **Save** and then " +"**Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:33 +msgid "Pay supplier bills, one after the other" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:38 +msgid "" +"We will now record a payment for one bill only. Open the bill, then click on" +" **Register Payment**. Insert the Payment Method, Date and Amount, and click" +" on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:45 +msgid "" +"Once you have validated the payment, the system will automatically reconcile" +" the payment with the bill, and set the bill as **Paid**. The system will " +"also generate a move from the payment account and reconcile it with the " +"expense transaction." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:51 +msgid "Pay several bills altogether" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:53 +msgid "" +"In order to illustrate the process thoroughly, create at least 2 more bills " +"following the above standing guide. **Make sure all bills come from the same" +" vendor.**" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:60 +msgid "" +"In the Vendors Bills, select the new bills you have just created by checking" +" the box next to each of them. In the Action menu located in the middle of " +"the page, click on **Register Payment**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:67 +msgid "" +"Insert the details of the payment. The system calculated the total amount " +"for both bills, but you can modify it freely. Click on **Validate**." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:71 +msgid "Record the payment, reconcile afterwards" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:73 +msgid "" +"You can also reconcile a payment with bills after the payment has been " +"recorded." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:76 +msgid "First, we need to create a payment" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:78 +msgid "" +"This will handle from :menuselection:`Dashboard --> Bank journal --> More " +"Option --> Send Money`" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:84 +msgid "" +"Creating payment order with check payment method. Selecting related Vendor " +"and amount which remain to pay. After filling all details, we will confirm " +"the payment order which will generate payment transaction with the system." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:92 +msgid "" +"As you can see, bill payment status show what is posted and what is " +"remaining to reconcile." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:95 +msgid "" +"After receiving bank statement from the bank with payment detail, you can " +"reconcile the transaction from the Dashboard. It will automatically map the " +"transaction amount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:101 +msgid "For more detail on the bank reconciliation process, please read:" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:106 +msgid "Partial payments of several supplier bills" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:109 +msgid "How to pay several supplier bills having cash discounts at once?" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:111 +msgid "" +"You already learned how to pay bills in various way but what about partial " +"payment? We are taking another example where we will do partial payment for " +"various bills." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:115 +msgid "" +"We are creating multiple bills and partially pay them through bank " +"statements." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:118 +msgid "" +"We are adding payment terms which allow some cash discount where vendor " +"offer us early payment discount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:124 +msgid "" +"We are creating the following bills with the assignment of the above payment" +" term." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:130 +msgid "We have created the following bills:" +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:135 +msgid "" +"We will pay the invoices by creating bank statement where we will adjust the" +" cash discount our vendor provided under payment terms." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:141 +msgid "" +"Before reconciling this bank statement, we need to create one statement " +"model for cash discount." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:147 +msgid "Now we are going back to bank statement and opening reconcile view." +msgstr "" + +#: ../../accounting/payables/pay/multiple.rst:151 +msgid "For bank statement reconciliation with model option, see" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:3 +#: ../../accounting/payables/pay/sepa.rst:67 +msgid "Pay with SEPA" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European union for simplification of bank transfers denominated in EURO." +" SEPA allows you to send payment orders to your bank to automate bank wire " +"transfer." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:10 +msgid "" +"SEPA is supported by the banks of the 28 EU member states as well as " +"Iceland, Norway, Switzerland, Andorra, Monaco and San Marino." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:13 +msgid "" +"With Odoo, once you decide to pay a vendor, you can select to pay the bill " +"with SEPA. Then, at the end of the day, the manager can generate the SEPA " +"file containing all bank wire transfers and send it to the bank. The file " +"follows the SEPA Credit Transfer 'PAIN.001.001.03' specifications. This is a" +" well-defined standard that makes consensus among banks." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:20 +msgid "" +"Once the payments are processed by your bank, you can directly import the " +"account statement inside Odoo. The bank reconciliation process will " +"seamlessly match the SEPA orders you sent to your bank with actual bank " +"statements." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:31 +msgid "" +"To pay suppliers with SEPA, you must install the **SEPA Credit Transfer** " +"module. This module handle the process of generating SEPA files based on " +"Odoo payments." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:37 +msgid "" +"According to your country and the chart of account you use, this module may " +"be installed by default." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:41 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:43 +msgid "" +"In order to allow payments by SEPA, you must activate the payment method on " +"related bank journals. From the accounting dashboard (the screen you get " +"when you enter the accounting application), click on \"More\" on your bank " +"account and select the \"Settings\" option." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:48 +msgid "" +"To activate SEPA, click the **Advanced Settings** tab and, in the **Payment " +"Methods** part of the **Miscellaneous** section, check the box **Sepa Credit" +" Transfer**." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:52 +msgid "" +"Make sure to specify the IBAN account number (domestic account number won't " +"work with SEPA) and the BIC (bank identifier code) on your bank journal." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:58 +msgid "" +"By default, the payments you send using SEPA will use your company name as " +"initiating party name. This is what appears on the recipient's bank " +"statement in the **payment from** field. You can customize it in your " +"company settings, in the tab **Configuration**, under the **SEPA** section." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:70 +msgid "Register your payments" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:72 +msgid "" +"You can register a payment that is not related to a supplier bill. To do so," +" use the top menu :menuselection:`Purchases --> Payments`. Register your " +"payment and select a payment method by Sepa Credit Transfer." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:76 +msgid "" +"If it's the first time you pay this vendor, you will have to fill in the " +"Recipient Bank Account field with, at least, the bank name, IBAN and BIC " +"(Bank Identifier Code). Odoo will automatically verify the IBAN format." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:80 +msgid "" +"For future payments to this vendor, Odoo will propose you automatically the " +"bank accounts but you will be able to select another one or create a new " +"one." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:84 +msgid "" +"If you pay a specific supplier bill, put the reference of the bill in the " +"**memo** field." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:90 +msgid "" +"Once your payment is registered, don't forget to Confirm it. You can also " +"pay vendor bills from the bill directly using the Register Payment button on" +" top of a vendor bill. The form is the same, but the payment is directly " +"linked to the bill and will be automatically reconciled to it." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:96 +msgid "Generate SEPA files" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:98 +msgid "" +"From your accounting dashboard, you should see if there are SEPA files to " +"generate for every bank account." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:104 +msgid "" +"Click on the link to check all the payments that are ready to transfer via " +"SEPA. Then, select all the payments you want to send (or check the top box " +"to select all payment at once) and click on :menuselection:`More --> " +"Download SEPA Payments`." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:116 +msgid "The bank refuses my SEPA file" +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:118 +msgid "" +"Ask your bank if they support **PAIN.001.001.03 SEPA Credit Transfers**. If " +"they don't, or cannot provide relevant informations, please forward the " +"error message to your Odoo partner." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:123 +msgid "There is no Bank Identifier Code recorded for bank account ..." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:125 +msgid "" +"In order to send a SEPA payment, the recipient must be identified by a valid" +" IBAN and BIC. If this message appear, you probably encoded an IBAN account " +"for the partner you are paying but forgot to fill in the BIC field." +msgstr "" + +#: ../../accounting/payables/pay/sepa.rst:132 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:168 +#: ../../accounting/receivables/customer_payments/followup.rst:168 +#: ../../accounting/receivables/customer_payments/recording.rst:129 +msgid ":doc:`check`" +msgstr "" + +#: ../../accounting/payables/supplier_bills.rst:3 +msgid "Supplier Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3 +msgid "When should I use supplier bills or purchase receipts?" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:5 +msgid "" +"Purchase receipts are different than vendor bills. Vendor bills are requests" +" for payment. If I issue a Purchase Order my vendor will in most business " +"cases send me a Vendor Bill. Depending on his invoice policy I then have a " +"defined amount of time to pay the Bill. A Purchase receipts are " +"confirmations of received payments. They are my day-to-day ticket receipts." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:12 +msgid "" +"From an accounting point of view this makes a difference as a Vendor Bill " +"will first credit a debt account before reconciling with the bank account. " +"On the other hand we usually immediately pay the purchase receipts, which " +"means no debt account is necessary." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:17 +msgid "" +"Moreover purchase receipts can have a different tax amount per product line," +" as vendors bills apply one tax amount over the entire bill." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:20 +msgid "" +"If my company's bank account is used to pay for goods where only a purchase " +"receipt are issued I should use the purchase receipts function in Odoo to " +"handle them in accounting." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:24 +msgid "" +"Let's take the following example: we need to buy tea for our customers from " +"a local tea store that doesn't issue bills. We go every week buy 50 euros " +"worth of tea and a teapot worth 20 euros. We pay with the company's bank " +"account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:32 +msgid "" +"To handle purchase receipts in Odoo one module and one app has to be " +"installed. Go into the app module and install the accounting app." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:38 +msgid "" +"Then, go in the search bar, delete the default module search, and search for" +" \"purchase\". Install the **Sale & Purchase Vouchers** module." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:45 +msgid "Register a receipt" +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:47 +msgid "" +"By installing the **Sale & Purchase Vouchers** I've made the new **Purchase " +"Receipts** drop down menu visible in the accounting app." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:50 +msgid "" +"To import our 50 euros worth of tea purchase receipt, enter the accounting " +"app, select :menuselection:`Purchases --> Purchase Receipts`." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:53 +msgid "" +"Create a new Purchase Receipt and fill in all the necessary information. " +"Note that you have the choice in the Payment field between **Pay Later** or " +"**Pay Now**. It's a significant difference as Pay Later will generate a debt" +" accounting entry whereas Pay Now will immediately credit the Bank account." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:59 +msgid "" +"In most cases you immediately pay, we will thus select the Pay Directly " +"option. Add the products, the related account and the appropriate taxe. For " +"the example we suppose the tea is a 12% taxe and the Tea Pott 21%." +msgstr "" + +#: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:66 +msgid "" +"Validate the Purchase Receipt to post it. Don't forget you need to " +":doc:`reconcile payments <../../bank/reconciliation/use_cases>` in order to " +"completely close the transaction in your accounting." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:3 +msgid "How to manage vendor Bills?" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:5 +msgid "" +"The **Purchase** application allows you to manage your purchase orders, " +"incoming products, and vendor bills all seamlessly in one place." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:8 +msgid "" +"If you want to set up a vendor bill control process, the first thing you " +"need to do is to have purchase data in Odoo. Knowing what has been purchased" +" and received is the first step towards understanding your purchase " +"management processes." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:13 +msgid "Here is the standard work flow in Odoo:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:15 +msgid "" +"You begin with a **Request for Quotation (RFQ)** to send out to your " +"vendor(s)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:18 +msgid "" +"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase " +"Order (PO)**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:21 +msgid "" +"Confirming the PO generates an **Incoming Shipment** if you purchased any " +"stockable products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:24 +msgid "" +"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with " +"products received in the previous step to ensure accuracy." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:27 +msgid "" +"This process may be done by three different people within the company, or " +"only one." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:34 +msgid "Installing the Purchase and Inventory applications" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:36 +msgid "" +"From the **Apps** application, search for the **Purchase** module and " +"install it. Due to certain dependencies, Installing Purchase will " +"automatically install the **Inventory** and **Accounting** applications." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:41 +msgid "Creating products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:43 +msgid "" +"Creating products in Odoo is essential for quick and efficient purchasing " +"within Odoo. Simply navigate to the Products submenu under Purchase, and " +"click create." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:50 +msgid "" +"When creating the product, Pay attention to the **Product Type** field, as " +"it is important:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:53 +msgid "" +"Products that are set as **Stockable or Consumable** will allow you to keep " +"track of their inventory levels. These options imply stock management and " +"will allow for receiving these kinds of products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:58 +msgid "" +"Conversely, products that are set as a **Service or Digital Product** will " +"not imply stock management, simply due to the fact that there is no " +"inventory to manage. You will not be able to receive products under either " +"of these designations." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:65 +msgid "" +"It is recommended that you create a **Miscellaneous** product for all " +"purchases that occur infrequently and do not require inventory valuation or " +"management. If you create such a product, it is recommend to set the product" +" type to **Service**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:70 +msgid "Managing your Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:73 +msgid "Purchasing products or services" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:75 +msgid "" +"From the purchase application, you can create a purchase order with as many " +"products as you need. If the vendor sends you a confirmation or quotation " +"for an order, you may record the order reference number in the **Vendor " +"Reference** field. This will enable you to easily match the PO with the the " +"vendor bill later (as the vendor bill will probably include the Vendor " +"Reference)" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:85 +msgid "" +"Validate the purchase order and receive the products from the Inventory " +"application." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:89 +msgid "Receiving Products" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:91 +msgid "" +"If you purchased any stockable products that you manage the inventory of, " +"you will need to receive the products from the Inventory application after " +"you confirm a Purchase Order. From the **Inventory dashboard**, you should " +"see a button linking you directly to the transfer of products. This button " +"is outlined in red below:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:100 +msgid "" +"Navigating this route will take you to a list of all orders awaiting to be " +"received." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:106 +msgid "" +"If you have a lot of awaiting orders, apply a filter using the search bar in" +" the upper right. With this search bar, you may filter based on the Vendor " +"(Partner), the product, or the source document, also known as the reference " +"of your purchase order. You also have the capability to group the orders by " +"different criteria under **Group By**. Selecting an item from this list will" +" open the following screen where you then will receive the products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:117 +msgid "Purchasing service products does not trigger a delivery order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:120 +msgid "Managing Vendor Bills" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:122 +msgid "" +"When you receive a Vendor Bill for a previous purchase, be sure to record it" +" in the Purchases application under the **Control Menu**. You need to create" +" a new vendor bill even if you already registered a purchase order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:130 +msgid "" +"The first thing you will need to do upon creating a Vendor Bill is to select" +" the appropriate Vendor as this will also pull up any associated accounting " +"or pricelist information. From there, you can choose to specify any one or " +"multiple Purchase Orders to populate the Vendor Bill with. When you select a" +" Purchase Order from the list, Odoo will pull any uninvoiced products " +"associated to that Purchase Order and automatically populate that " +"information below. If you are having a hard time finding the appropriate " +"Vendor bill, you may search through the list by inputting the vendor " +"reference number or your internal purchase order number." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:144 +msgid "" +"While the invoice is in draft state, you can make any modifications you need" +" (i.e. remove or add product lines, modify quantities, and change prices)." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:150 +msgid "Your vendor may send you several bills for the same Purchase Order if:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:152 +msgid "" +"Your vendor is in back-order and is sending you invoices as they ship the " +"products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:153 +msgid "Your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:155 +msgid "" +"Every time you record a new vendor bill, Odoo will automatically populate " +"the product quantities based on what has been received from the vendor. If " +"this value is showing a zero, this means that you have not yet received this" +" product and simply serves as a reminder that the product is not in hand and" +" you may need to inquire further into this. At any point in time, before you" +" validate the Vendor Bill, you may override this zero quantity." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:164 +msgid "Vendor Bill Matching" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:167 +msgid "What to do if your vendor bill does not match what you received" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:169 +msgid "" +"If the bill you receive from the vendor has different quantities than what " +"Odoo automatically populates as quantities, this could be due to several " +"reasons:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:173 +msgid "" +"the vendor is incorrectly charging you for products and/or services that you" +" have not ordered," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:176 +msgid "" +"the vendor is billing you for products that you might not have received yet," +" as the invoicing control may be based on ordered or received quantities," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:180 +msgid "or the vendor did not bill you for previously purchased products." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:182 +msgid "" +"In these instances it is recommended that you verify that the bill, and any " +"associated purchase order to the vendor, are accurate and that you " +"understand what you have ordered and what you have already received." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:186 +msgid "" +"If you are unable to find a purchase order related to a vendor bill, this " +"could be due to one of a few reasons:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:189 +msgid "" +"the vendor has already invoiced you for this purchase order, therefore it is" +" not going to appear anywhere in the selection," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:192 +msgid "" +"someone in the company forgot to record a purchase order for this vendor," +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:195 +msgid "or the vendor is charging you for something you did not order." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:200 +msgid "How product quantities are managed" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:202 +msgid "" +"By default, services are managed based on ordered quantities, while " +"stockables and consumables are managed based on received quantities." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:205 +msgid "" +"If you need to manage products based on ordered quantities over received " +"quantities, you will need to belong to the group **Purchase Manager**. Ask " +"your system administrator to enable these access on :menuselection:`Settings" +" --> Users --> Users --> Access Rights`. Once you belong to the correct " +"group, select the product(s) you wish to modify, and you should see a new " +"field appear, labeled **Control Purchase Bills**." +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:215 +msgid "" +"You can then change the default management method for the selected product " +"to be based on either:" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:218 +msgid "Ordered quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:220 +msgid "or Received quantities" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:223 +msgid "Batch Billing" +msgstr "" + +#: ../../accounting/payables/supplier_bills/manage.rst:225 +msgid "" +"When creating a vendor bill and selecting the appropriate purchase order, " +"you may continue to select additional purchase orders and Odoo will add the " +"additional line items from that purchase order.. If you have not deleted the" +" previous line items from the first purchase order the bill will be linked " +"to all the appropriate purchase orders." +msgstr "" + +#: ../../accounting/receivables.rst:3 +msgid "Account Receivables" +msgstr "" + +#: ../../accounting/receivables/customer_invoices.rst:3 +msgid "Customer Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3 +msgid "How to setup cash discounts?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5 +msgid "" +"Cash discounts are an incentive (usually a small percentage) that you offer " +"to customers in return for paying a bill owed before the scheduled due date." +" If used properly, cash discounts improve the Days Sales Outstanding aspect " +"of a business's cash conversion cycle." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:10 +msgid "" +"For example, a typical cash discount would be: you offer a 2% discount on an" +" invoice due in 30 days if the customer were to pay within the first 5 days " +"of receiving the invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:18 +msgid "Payment terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:20 +msgid "" +"In order to manage cash discounts, we will use the payment terms concept of " +"Odoo (From the Accounting module, go to :menuselection:`Configuration --> " +"Management --> Payment terms --> Create`)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:24 +msgid "" +"Let's start with the above example: a 2% discount on an invoice due in 30 " +"days if the customer were to pay within the first 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27 +msgid "" +"A typical payment term of 30 days would have only one installment: balance " +"in 30 days. But, in order to configure the cash discount, you can configure " +"the payment term with two installments:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:31 +msgid "98% within 5 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:32 +msgid "balance within 30 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:37 +msgid "" +"To make it clear that it's not a payment term but a cash discount, don't " +"forget to set a clear description that will appear on the invoice: Invoice " +"is due within 30 days, but you can benefit from a 2% cash discount if you " +"pay within 5 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:43 +msgid "Bank reconciliation model" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:45 +msgid "" +"In order to speed up the bank reconciliation process, we can create a model " +"of entry for all cash discounts. To do that, from the Accounting application" +" dashboard, click on the \"More\" link on the bank and choose the option " +"\"Reconciliation Models\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:53 +msgid "Create a new model for cash discounts as follow:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:55 +msgid "**Button Label**: Cash Discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:56 +msgid "**Account**: Cash Discount (according to your country)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:57 +msgid "**Amount Type**: Percentage" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58 +msgid "**Amount**: 100%" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "**Taxes**: depending on your country, you may put a tax on the cash" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 +msgid "discount if taxes have to be deduced" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:67 +msgid "" +"Even if it's a 2% cash discount, set a 100% amount on the reconciliation " +"model as it means 100% of the remaining balance (the 2%). You can use the " +"same reconciliation model for all your cash discount. No need to create a " +"model per payment term." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:73 +msgid "Creating an invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:75 +msgid "" +"When you create a customer invoice, set the right payment term \"30 days, 2%" +" cash discount\" right after having selected the customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:81 +msgid "" +"Once the invoice is validated, Odoo will automatically split the account " +"receivable part of the journal entry with two installments having a " +"different due date: 98% within 5 days, 2% within 30 days." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:92 +msgid "Paying the invoice with a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:94 +msgid "" +"If the customer pays with a cash discount, when processing the bank " +"statement, you will match the payment (98%) with the related line in the " +"journal entry." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:101 +msgid "" +"As you can see in the above screenshot, when selecting the customer, you " +"also see the 2% remaining of 3$. If you want to accept the cash discount (if" +" the customer paid within the 5 days), you can click on this line with 2%, " +"click on \"Open Balance\", and select your \"Cash Discount\" reconciliation " +"model. That way, the invoice is marked as fully paid." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:109 +msgid "" +"from now on, matching the remaining 2% has to be done manually. In the " +"future, we plan to automate the reconciliation of the 2% if the 98% are paid" +" on time." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:113 +msgid "Paying the invoice in full" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:115 +msgid "" +"If the customer pays the invoice fully, without benefiting from the cash " +"discount, you will reconcile the payment (in full) with the two lines from " +"the invoice (98% and 2%). Just click on the two lines to match them with the" +" payment." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:125 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:116 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 +msgid ":doc:`overview`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues: how to automate them?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:5 +msgid "" +"Deferred/unearned revenue is an advance payment recorded on the recipient's " +"balance sheet as a liability account until either the services have been " +"rendered or the products have been delivered. Deferred revenue is a " +"liability account because it refers to revenue that has not yet been earned," +" but represents products or services that are owed to the customer. As the " +"products or services are delivered over time, the revenue is recognized and " +"posted on the income statement." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:13 +msgid "" +"For example: let's say you sell a 2 year support contract for $24,000 that " +"begins next month for a period of 24 months. Once you validate the customer " +"invoice, the $24.000 should be posted into a deferred revenues account. This" +" is because the $24,000 you received has not yet been earned." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:19 +msgid "" +"Over the next 24 months, you will be reducing the deferred revenues account " +"by $1,000 ($24,000/24) on a monthly basis and recognizing that amount as " +"revenue." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:27 +msgid "Module installation" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:29 +msgid "" +"In order to automate deferred revenues, go to the settings menu under the " +"application :menuselection:`Accounting --> Configuration` and activate the " +"**Assets management & revenue recognition** option. This will install the " +"**Revenue Recognition Management** module." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:36 +msgid "" +"In some version of Odoo 9, besides checking this option, you need to install" +" the \"Revenue Recognition Management\" module. If you are using Odoo 9, you" +" might check if the module is correctly installed." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:41 +msgid "Define deferred revenue types" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:43 +msgid "" +"Once the module is installed, you need to create deferred revenue types. " +"From the Accounting application, go to the menu " +":menuselection:`Configuration --> Deferred Revenues Types`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:51 +msgid "Example: 12 months maintenance contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:53 +msgid "Some example of deferred revenues types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:55 +msgid "1 year service contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:56 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 +msgid "3 years service contracts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:59 +msgid "Set deferred revenues on products" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:61 +msgid "" +"Once deferred revenues types are defined, you can set them on the related " +"products. On the product form, in the Accounting tab, you can set a deferred" +" revenue type." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:65 +msgid "" +"Here are some examples of products and their related deferred revenue types:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Product" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Deferred Revenue Type" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:71 +msgid "Support Contract: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:73 +msgid "Netflix subscription: 3 years" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "Flowers every month" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:75 +msgid "1 year product contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:79 +msgid "Sell and invoice products" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:81 +msgid "" +"Once the products are configured, you can create a customer invoice using " +"this product. Once the customer invoice is validated, Odoo will " +"automatically create a deferred revenue for you, and the related journal " +"entry." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Dr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:87 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:98 +msgid "**Cr**" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +msgid "Accounts receivable" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:89 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +msgid "24000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:91 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +msgid "Deferred revenue account" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:94 +msgid "" +"Then, every month, Odoo will post a journal entry for the revenue " +"recognition." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:100 +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "1000" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:102 +msgid "Service revenue account" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:108 +msgid "" +"To analyze all your current contracts having a deferred revenue, you can use" +" the menu Reporting > Deferred Revenue Analysis." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:3 +msgid "How to define an installment plan on customer invoices?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:4 +msgid "" +"In order to manage installment plans related to an invoice, you should use " +"payment terms in Odoo. They apply on both customer invoices and supplier " +"bills." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:8 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:8 +msgid "Example, for a specific invoice:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:10 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:10 +msgid "Pay 50% within 10 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:11 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:12 +msgid "Pay the remaining balance within 30 days" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:15 +msgid "" +"payment terms are not to be confused with a payment in several parts. If, " +"for a specific order, you invoice the customer in two parts, that's not a " +"payment term but an invoice policy." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:22 +msgid "" +"Configure your usual installment plans from the application " +":menuselection:`Accounting --> Configuration > Payment Terms`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:25 +msgid "" +"A payment term may have one line (ex: 21 days) or several lines (10% within " +"3 days and the balance within 21 days). If you create a payment term with " +"several lines, make sure the latest one is the balance. (avoid doing 50% in " +"10 days and 50% in 21 days because, with the rounding, it may not compute " +"exactly 100%)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:36 +msgid "" +"The description of the payment term will appear on the invoice or the sale " +"order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:39 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:38 +msgid "Payment terms for customers" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:41 +msgid "You can set payment terms on:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:43 +msgid "" +"**a customer**: the payment term automatically applies on new sales orders " +"or invoices for this customer. Set payment terms on customers if you grant " +"this payment term for all future orders for this customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:48 +msgid "" +"**a quotation**: the payment term will apply on all invoices created from " +"this quotation or sale order, but not on other quotations" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:51 +msgid "**an invoice**: the payment term will apply on this invoice only" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:53 +msgid "" +"If an invoice contains a payment term, the journal entry related to the " +"invoice is different. Without payment term, an invoice of $100 will produce " +"the following journal entry (for the clarity of the example, we did not set " +"any tax on the invoice):" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:59 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:71 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:58 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:70 +msgid "Due date" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:66 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:65 +msgid "" +"If you do an invoice the 1st of January with a payment term of 10% within 3 " +"days and the balance within 30 days, you get the following journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "Jan 03" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:73 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:72 +msgid "10" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +msgid "Jan 30" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:75 +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:74 +msgid "90" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:80 +msgid "" +"On the customer statement, you will see two lines with different due dates. " +"To get the customer statement, use the menu Sales > Customers Statement." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:87 +msgid ":doc:`payment_terms`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:3 +msgid "How to modify a validated invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:5 +msgid "" +"In most accounting legislation over the word, it's not allowed to modify an " +"invoice that is validated and sent to the customer. However, you sometimes " +"need to change an invoice for different reasons: the sale has changed, the " +"made a mistake while recording the invoice, etc." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:10 +msgid "Thus, the right way to modify an invoice is to:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:12 +msgid "Refund the original invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:13 +msgid "Create a new invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:15 +msgid "" +"Odoo's refund mechanism helps you handle the whole process in just a few " +"clicks." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:19 +msgid "Modify an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:21 +msgid "" +"If your invoice is still in draft, you can modify it the way you want. " +"However, if your invoice is validated, you can not change it anymore. If you" +" need to modify it, the right operations to do are:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:25 +msgid "Refund the original invoice;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:26 +msgid "Reconcile the original invoice with the refund to void them;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:27 +msgid "Create a new draft invoice, a copy of the original;" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:28 +msgid "Validate the new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:30 +msgid "" +"All those steps are automated by Odoo. All you have to do is to click on the" +" Refund button on an invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:36 +msgid "" +"In the refund dialog, select the option \"Modify: create a refund, reconcile" +" and create a draft invoice\". Once you click on the \"Create Refund\" " +"button, Odoo will void your existing invoice and create a new draft invoice " +"that is a duplicate of the original one." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:41 +msgid "Edit this new draft invoice and validate it when it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:45 +msgid "" +"if you already sent the original invoice to your customer, you should send " +"the new invoice and the refund to the customer so that he gets all the " +"documents." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/modify_validated.rst:50 +msgid ":doc:`refund`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:3 +msgid "Overview of the invoicing process" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:21 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:25 +msgid "" +"Invoice manually: use a button on the sale order to trigger the draft " +"invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:28 +msgid "" +"Invoice before delivery: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:33 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:37 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice the " +"whole order, invoice a percentage (advance), invoice some lines, invoice a " +"fixed advance." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:47 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:49 +msgid "" +"Retailers and eCommerce usually invoice based on delivery orders, instead of" +" sales order. This approach is suitable for businesses where the quantities " +"you deliver may differs from the ordered quantities: foods (invoice based on" +" actual Kg)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:54 +msgid "" +"This way, if you deliver a partial order, you only invoice for what you " +"really delivered. If you do back orders (deliver partially and the rest " +"later), the customer will receive two invoices, one for each delivery order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:62 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:64 +msgid "" +"An eCommerce order will also trigger the creation of the order when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:70 +msgid "Contracts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:73 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:75 +msgid "" +"If you use contracts, you can trigger invoice based on time and material " +"spent, expenses or fixed lines of services/products. Every month, the " +"salesperson will trigger invoice based on activities on the contract." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:79 +msgid "Activities can be:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:81 +msgid "" +"fixed products/services, coming from a sale order linked to this contract" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:83 +msgid "materials purchased (that you will re-invoiced)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:85 +msgid "time and material based on timesheets or purchases (subcontracting)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:87 +msgid "" +"expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:89 +msgid "" +"You can invoice at the end of the contract or trigger intermediate invoices." +" This approach is used by services companies that invoice mostly based on " +"time and material. For services companies that invoice on fix price, they " +"use a regular sales order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:101 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:111 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:113 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:118 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:121 +msgid "if you need to create a refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:123 +msgid "If you need to give a discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:125 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:127 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:130 +msgid "Specific modules" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:132 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:134 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/overview.rst:136 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:3 +msgid "How to setup and use payment terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:5 +msgid "" +"Payment terms define the conditions to pay an invoice. They apply on both " +"customer invoices and supplier bills." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:14 +msgid "" +"Payment terms are different from invoicing in several areas. If, for a " +"specific order, you invoice the customer in two parts, that's not a payment " +"term but invoice conditions." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:21 +msgid "" +"Configure your usual payment terms from the Configuration menu of the " +"Account application. The description of the payment term is the one that " +"appear on the invoice or the sale order." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:25 +msgid "" +"A payment term may have one line (ex: 21 days) or several lines (10% within " +"3 days and the balance within 21 days). If you create a payment term with " +"several lines, be sure the latest one is the balance. (avoid doing 50% in 10" +" days and 50% in 21 days because, with the rounding, it may not do exactly " +"100%)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:35 +msgid "Using Payment Terms" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:40 +msgid "Payment terms can be set on:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:42 +msgid "" +"**a customer**: to apply this payment term automatically on new sale orders " +"or invoices for this customer. Set payment terms on customers if you grant " +"this payment term for all future orders of this customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:47 +msgid "" +"**a quotation**: to apply this payment term on all invoices created from " +"this quotation or sale order, but not on other quotations" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:51 +msgid "**an invoice**: to apply the payment term on this invoice only" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:53 +msgid "" +"If an invoice has a payment term, the journal entry related to the invoice " +"is different. Without payment term or tax, an invoice of $100 will produce " +"this journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:79 +msgid "" +"In the customer statement, you will see two lines with different due dates." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:83 +msgid "Payment terms for vendor bills" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:85 +msgid "" +"The easiest way to manage payment terms for vendor bills is to record a due " +"date on the bill. You don't need to assign a payment term, just the due date" +" is enough." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:89 +msgid "" +"But if you need to manage vendor terms with several installments, you can " +"still use payment terms, exactly like in customer invoices. If you set a " +"payment term on the vendor bill, you don't need to set a due date. The exact" +" due date for all installments will be automatically created." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/payment_terms.rst:96 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:3 +msgid "How to edit or refund an invoice?" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:4 +msgid "" +"In Odoo, it's not possible to modify an invoice that has been validated and " +"sent to the customer. If a mistake was made on a validated invoice, the " +"legal way to handle that is to refund the invoice, reconcile it with the " +"original invoice to close them and create a new invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:10 +msgid "Modifying a validated invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:12 +msgid "" +"If you need to modify an existing invoice, use the Refund Invoice button on " +"the invoice. In the refund method field, select \"Modify: create a refund, " +"reconcile, and create a new draft invoice\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:19 +#: ../../accounting/receivables/customer_invoices/refund.rst:37 +msgid "Odoo will automatically:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:21 +#: ../../accounting/receivables/customer_invoices/refund.rst:39 +msgid "Create a refund for your invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:22 +#: ../../accounting/receivables/customer_invoices/refund.rst:40 +msgid "" +"Reconcile the refund invoice with the original invoice (marking both as " +"Paid)" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:23 +msgid "Create a new draft invoice you can modify" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:25 +msgid "" +"Then, you can modify the draft invoice and validate it once it's correct." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:28 +msgid "Cancelling an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:30 +msgid "" +"If you need to cancel an existing invoice, use the Refund Invoice button on " +"the invoice. In the refund method field, select \"Cancel: create a refund " +"and reconcile\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:42 +msgid "" +"Nothing else needs to be done. You can send the refund by regular mail or " +"email to your customer, if you already sent the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:46 +msgid "Refunding part of an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:48 +msgid "" +"If you need to refund an existing invoice partially, use the Refund Invoice " +"button on the invoice. In the refund method field, select \"Create a draft " +"refund\"." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:55 +msgid "" +"Odoo will automatically create a draft refund. You may modify the refund " +"(example: remove the lines you do not want to refund) and validate it. Then," +" send the refund by regular mail or email to your customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/refund.rst:61 +msgid "" +"Refunding an invoice is different from refunding a payment. Usually, a " +"refund invoice is sent before the customer has done a payment. If the " +"customer has already paid, they should be reimbursed by doing a customer " +"payment refund." +msgstr "" + +#: ../../accounting/receivables/customer_payments.rst:3 +msgid "Customer Payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:3 +msgid "How to register customer payments by checks?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:5 +msgid "" +"There are two ways to handle payments received by checks. Odoo support both " +"approaches so that you can use the one that better fits your habits." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:9 +msgid "" +"**Undeposited Funds:** once you receive the check, you record a payment by " +"check on the invoice. (using a Check journal and posted on the Undeposited " +"Fund account) Then, once the check arrives in your bank account, move money " +"from Undeposited Funds to your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:16 +msgid "" +"**One journal entry only:** once your receive the check, you record a " +"payment on your bank, paid by check, without going through the **Undeposited" +" Funds**. Once you process your bank statement, you do the matching with " +"your bank feed and the check payment, without creating a dedicated journal " +"entry." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:23 +msgid "" +"We recommend the first approach as it is more accurate (your bank account " +"balance is accurate, taking into accounts checks that have not been cashed " +"yet). Both approaches require the same effort." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:27 +msgid "" +"Even if the first method is cleaner, Odoo support the second approach " +"because some accountants are used to it (quickbooks and peachtree users)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:32 +msgid "" +"You may have a look at the *Deposit Ticket feature* if you deposit several " +"checks to your bank accounts in batch." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:36 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:37 +msgid "Option 1: Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:41 +msgid "Create a journal **Checks**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:43 +msgid "Set **Undeposited Checks** as a defaut credit/debit account" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:45 +msgid "" +"Set the bank account related to this journal as **Allow Reconciliation**" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:48 +#: ../../accounting/receivables/customer_payments/check.rst:109 +msgid "From check payments to bank statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:50 +msgid "" +"The first way to handle checks is to create a check journal. Thus, checks " +"become a payment method in itself and you will record two transactions." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:54 +#: ../../accounting/receivables/customer_payments/check.rst:111 +msgid "" +"Once you receive a customer check, go to the related invoice and click on " +"**Register Payment**. Fill in the information about the payment:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:57 +msgid "" +"Payment method: Check Journal (that you configured with the debit and credit" +" default accounts as **Undeposited Funds**)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:60 +msgid "Memo: write the Check number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:65 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:74 +msgid "This operation will produce the following journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:68 +#: ../../accounting/receivables/customer_payments/check.rst:81 +#: ../../accounting/receivables/customer_payments/check.rst:131 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:77 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:91 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:141 +msgid "Statement Match" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:70 +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +#: ../../accounting/receivables/customer_payments/check.rst:85 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/check.rst:135 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:79 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:95 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:145 +msgid "100.00" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:72 +#: ../../accounting/receivables/customer_payments/check.rst:83 +msgid "Undeposited Funds" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:75 +#: ../../accounting/receivables/customer_payments/check.rst:121 +msgid "The invoice is marked as paid as soon as you record the check." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:77 +msgid "" +"Then, once you get the bank statements, you will match this statement with " +"the check that is in Undeposited Funds." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:83 +#: ../../accounting/receivables/customer_payments/check.rst:133 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:143 +msgid "X" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:89 +msgid "" +"If you use this approach to manage received checks, you get the list of " +"checks that have not been cashed in the **Undeposit Funds** account " +"(accessible, for example, from the general ledger)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:94 +msgid "" +"Both methods will produce the same data in your accounting at the end of the" +" process. But, if you have checks that have not been cashed, this one is " +"cleaner because those checks have not been reported yet on your bank " +"account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:100 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:110 +msgid "Option 2: One journal entry only" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:105 +msgid "" +"These is nothing to configure if you plan to manage your checks using this " +"method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:114 +msgid "**Payment method:** the bank that will be used for the deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:116 +msgid "Memo: write the check number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:123 +msgid "" +"Once you will receive the bank statements, you will do the matching with the" +" statement and this actual payment. (technically: point this payment and " +"relate it to the statement line)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:127 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:137 +msgid "" +"With this approach, you will get the following journal entry in your books:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:139 +msgid "" +"You may also record the payment directly without going on the customer " +"invoice, using the menu :menuselection:`Sales --> Payments`. This method may" +" be more convenient if you have a lot of checks to record in a batch but you" +" will have to reconcile entries afterwards (matching payments with invoices)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/check.rst:145 +msgid "" +"If you use this approach to manage received checks, you can use the report " +"**Bank Reconciliation Report** to verify which checks have been received or " +"paid by the bank. (this report is available from the **More** option from " +"the Accounting dashboard on the related bank account)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:3 +msgid "How to register credit card payments on invoices?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:5 +msgid "" +"There are two ways to handle payments received by credit cards. Odoo support" +" both approaches so that you can use the one that better fits your habits." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:9 +msgid "" +"**Undeposited Funds** (mostly used in european countries): once you receive " +"the credit card payment authorization, you record a payment by credit card " +"on the invoice (using a Credit card journal and posted on the Undeposited " +"Fund account). Then, once the credit card payments arrives in your bank " +"account, move money from Undeposited Funds to your bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:16 +msgid "" +"**One journal entry only** (mostly used in the U.S.): once your receive the " +"credit card payment, you record a payment on your bank, paid by credit card," +" without going through the Undeposited Funds. Once you process your bank " +"statement, you do the matching with your bank feed and the credit card " +"payment, without creating a dedicated journal entry ." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:23 +msgid "" +"We recommend the first approach as it is more accurate (your bank account " +"balance is accurate, taking into accounts credit cards that have not been " +"cashed yet). Both approaches require the same effort." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:27 +msgid "" +"If you use eCommerce and an automated payment gateway, you will only need to" +" take care of the bank reconciliation part as paid invoice will be " +"automatically recorded in the right journal. You will use the second " +"approach." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:32 +msgid "" +"Even if the first method is cleaner, Odoo support the second approach " +"because some accountants are used to it (*QuickBooks* and *Peachtree* " +"users)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:42 +msgid "" +"On the Accounting module, go to :menuselection:`Configuration --> Journals " +"--> Create`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:44 +msgid "" +"Create a Journal called 'Credit card payments' with the following data:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:46 +msgid "**Journal Name**: Credit card" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:47 +msgid "**Default debit account**: Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:48 +msgid "**Default credit account**: Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:50 +msgid "" +"Once it's done, don't forget to set the \"Credit cards\" account as \"Allow " +"Reconciliation\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:57 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:119 +msgid "From credit card payments to bank statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:59 +msgid "" +"The first way to handle credit cards is to create a credit card journal. " +"Thus, credit cards become a payment method in itself and you will record two" +" transactions." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:63 +#: ../../accounting/receivables/customer_payments/credit_cards.rst:121 +msgid "" +"Once you receive a customer credit card payment, go to the related invoice " +"and click on Register Payment. Fill in the information about the payment:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:67 +msgid "**Payment method**: Credit card" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:69 +msgid "**Memo**: write the invoice reference" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:81 +msgid "Credit Cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:84 +msgid "" +"The invoice is marked as paid as soon as you record the credit card payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:87 +msgid "" +"Then, once you get the bank statements, you will match this statement with " +"the credit card that is in the 'Credit card' account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:93 +msgid "Credit cards" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:98 +msgid "" +"If you use this approach to manage credit cards payments, you get the list " +"of credit cards payments that have not been cashed in the \"Credit card\" " +"account (accessible, for example, from the general ledger)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:104 +msgid "" +"Both methods will produce the same data in your accounting at the end of the" +" process. But, if you have credit cards that have not been cashed, this one " +"is cleaner because those credit cards have not been reported yet on your " +"bank account." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:115 +msgid "" +"There is nothing to configure if you plan to manage your credit cards using " +"this method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:125 +msgid "**Payment method**: the bank that will be used for the deposit" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:127 +msgid "**Memo**: write the credit card transaction number" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:132 +msgid "" +"The invoice is marked as paid as soon as the credit card payment has been " +"recorded. Once you receive the bank statements, you will do the matching " +"with the statement and this actual payment (technically: point this payment " +"and relate it to the statement line)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:150 +msgid "" +"You may also record the payment directly without going on the customer " +"invoice, using the top menu :menuselection:`Sales --> Payments`. This method" +" may be more convenient if you have a lot of credit cards to record in a " +"batch but you will have to reconcile entries afterwards (matching payments " +"with invoices)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:155 +msgid "" +"If you use this approach to manage received credit cards, you can use the " +"report \"Bank Reconciliation Report\" to verify which credit cards have been" +" received or paid by the bank (this report is available from the \"More\" " +"option from the Accounting dashboard on the related bank account)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:166 +#: ../../accounting/receivables/customer_payments/followup.rst:167 +msgid ":doc:`recording`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:167 +#: ../../accounting/receivables/customer_payments/recording.rst:128 +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/credit_cards.rst:169 +#: ../../accounting/receivables/customer_payments/recording.rst:130 +msgid ":doc:`followup`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:3 +msgid "How to get paid and organize customer follow-ups?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:5 +msgid "" +"Getting paid and organizing customer reminders is always a difficult task, " +"however it is critical for the health of the company to stay diligent about " +"outstanding receivables. Fortunately, Odoo provides the right tools to track" +" receivables, automate customer statements, and measure your performance." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:12 +msgid "Customer follow-ups: A step by step guide" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:15 +msgid "Cleaning up outstanding payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:17 +msgid "" +"If you have any unreconciled transactions in your bank account, you will " +"need to process them first before you begin analyzing your customers " +"statements. This ensures that you have recorded all of the latest customer " +"payments before sending out reminders to any customers with outstanding " +"balances." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:27 +msgid "Checking the Aged Receivables report" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:29 +msgid "" +"After you have reconciled all of your bank accounts, you can then generate " +"an accurate Aged Receivables Report from the Reports menu. This report will " +"display all of the customers and their outstanding balances on open " +"invoices." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:37 +msgid "" +"The report displays this information in time increments to better paint a " +"picture of the outstanding balances your customers hold and for how long " +"they have held these outstanding balances. You can then appropriately focus " +"your efforts on the appropriate customers." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:42 +msgid "" +"You can then select any of the customers on this list and Odoo will open up " +"their invoice details in the form of the Customer Follow-Up letter, also " +"known as the **Customer Statement**." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:49 +msgid "From the customer statement, you can:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:51 +msgid "Change and customize the message that is sent to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:53 +msgid "Send a reminder email to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:55 +msgid "Send a printed reminder letter to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:57 +msgid "Send automated printed reminders by utilizing our Docsaway integration" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:60 +msgid "Zoom in on the different open invoices or payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:62 +msgid "Remove an invoice or payment from the report (in case of conflict)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:64 +msgid "Log any call notes made to the customer" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:66 +msgid "" +"Schedule your next follow up task to stay on top of customer payments (e.g. " +"call back in 15 days if not payments are made)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:69 +msgid "" +"You can set reminders for when you would like to next contact the particular" +" customer. Selecting **Manual** will open up the follow up scheduling tool, " +"while selecting **Auto** will automatically recommend that you contact the " +"customer 15 days from then if the customer has not yet paid for the invoice." +" Installing the **Follow-Up Plans** module will allow you to define " +"automated actions and intervals to send reminders." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:79 +msgid "" +"If you have already sent out a reminder to a customer a few days ago, a " +"warning message will appear at the top of the screen, reminding you that you" +" should not send another reminder so soon since one was already sent " +"recently. Every time you log a note, Odoo will automatically set the next " +"reminder date, unless you choose to manually set it by selecting the next " +"reminder button at the top right of the screen." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:88 +msgid "" +"You can also specify the expected payment date on an invoice line directly, " +"therefore defining the next reminder in case the invoice has not been paid." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:92 +msgid "Sending customer statements" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:94 +msgid "" +"Send your customers reminders in batches in the menu :menuselection:`Sales " +"--> Customer Statements`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:97 +msgid "" +"Here Odoo will open all the statements awaiting to be processed, which is " +"determined by the last reminder they received. You can choose to process " +"them one by one, send multiple letters or emails in batches, or set a next " +"action date for the next time they'll be contacted." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:104 +msgid "" +"If an invoice has not yet been paid, Odoo will remind you to contact at " +"particular customer based after their next action date." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:107 +msgid "" +"You can access the customer statement report daily and Odoo will only " +"display the customers you need to contact on any given day. This is based " +"on:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:111 +msgid "Customers you have not yet received a payment from" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:113 +msgid "" +"Customers that have not been reminded over the last X days (\"X\" being " +"defined as the overdue date of the invoice after the first reminder, then " +"the next action date set at every reminder)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:118 +msgid "Setting up your dunning process" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:120 +msgid "" +"The **Payment Follow-up Management** module allows you to define reminder " +"plans. After installing it from the **Apps** menu, go to the **Follow-up " +"Levels** menu in the accounting configuration to set up your dunning " +"process." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:125 +msgid "Some Examples are:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:127 +msgid "**Email**: 3 days before overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:129 +msgid "**Email+Letter**: at the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:131 +msgid "**Email+Call**: 15 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:133 +msgid "**Email+Letter**: 60 days after the overdue date" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:138 +msgid "" +"Thanks to this module, you can send every email and letters in batches for " +"all your customers at once. The next reminder will automatically be computed" +" based on your configured follow-up plan." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:142 +msgid "" +"The module will also add a red/green dot on each customer, this will allow " +"you to easily mark customer status's with the following options: \"Good " +"Debtor, Normal Debtor, or bad debtors." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:150 +msgid "DSO: Measuring your performance" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:152 +msgid "" +"The DSO (Days of Outstanding Sales) is a measure of the average number of " +"days that a company takes to collect revenue after a sale has been made. DSO" +" is calculated by dividing the amount of accounts receivable during a given " +"period by the total value of credit sales during the same period, and " +"multiplying the result by the number of days in the period measured." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:159 +msgid "" +"You can get the DSO of your company from the Executive Summary report under " +"Reporting (check the KPI average debtors days)." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:3 +msgid "What are the different ways to record a payment?" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:5 +msgid "" +"In Odoo, a payment can either be linked directly to an invoice or be a stand" +" alone record for use on a later date:" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:8 +msgid "" +"If a payment is linked to an invoice, it reduces the amount due of the " +"invoice. You can have multiple payments linked to the same invoice." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:12 +msgid "" +"If a payment is not linked to an invoice, the customer has an outstanding " +"credit with your company, or your company as an outstanding balance with a " +"vendor. You can use this outstanding credit/debit to pay future invoices or " +"bills." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:18 +msgid "Paying an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:20 +msgid "" +"If you register a payment on a customer invoice or a vendor bill, the " +"payment is automatically reconciled with the invoice reducing the amount " +"due." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:27 +msgid "" +"The green icon near the payment line will display more information about the" +" payment. From there you can choose to open the journal entry or reconcile " +"the payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:33 +msgid "" +"If you unreconcile a payment, it is still registered in your books but not " +"linked to the specific invoice any longer. If you unreconcile a payment in a" +" different currency, Odoo will create a journal entry to reverse the " +"Currency Exchange Loss/Gain posted at the time of reconciliation." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:39 +msgid "Payments not tied to an invoice" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:42 +msgid "Registering a payment" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:44 +msgid "" +"In the Accounting application, you can create a new payment from the Sales " +"menu (register a customer payment) or the Purchases menu (pay a vendor). If " +"you use these menus, the payment is not linked to an invoice, but can easily" +" be reconciled on an invoice later on." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:52 +msgid "" +"When registering a new payment, you must select a customer or vendor, the " +"payment method, and the amount of the payment. The currency of the " +"transaction is defined by the payment method. If the payment refers to a " +"document (sale order, purchase order or invoice), set the reference of this " +"document in the memo field." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:58 +msgid "" +"Once confirmed, a journal entry will be posted reflecting the transaction " +"just made in the accounting application." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:62 +msgid "Reconciling invoice payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:64 +msgid "" +"The easiest way of reconciling a payment with an invoice is to do so on the " +"invoice directly." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:67 +msgid "" +"When validating a new invoice, Odoo will warn you that an outstanding " +"payment for this customer or vendor is available. In this case, you can " +"reconcile this payment to the invoice near the totals at the bottom, under " +"\"Outstanding Payments\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:76 +msgid "Reconciling all your outstanding payments and invoices" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:78 +msgid "" +"If you want to reconcile all outstanding payments and invoices at once " +"(instead of doing so one by one), you can use the batch reconciliation " +"feature within Odoo." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:82 +msgid "" +"The batch reconciliation feature is available from the dashboard on the " +"Customer Invoices card and the Vendor Bills card for reconciling Accounts " +"Receivable and Payable, respectively." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:89 +msgid "" +"The payments matching tool will open all unreconciled customers or vendors " +"and will give you the opportunity to process them all one by one, doing the " +"matching of all their payments and invoices at once." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:96 +msgid "" +"During the reconciliation, if the sum of the debits and credits do not " +"match, it means there is still a remaining balance that either needs to be " +"reconciled at a later date, or needs to be written off directly." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:101 +msgid "Transferring money from one bank account to another" +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:103 +msgid "" +"Just like making a customer or vendor payment, you transfer cash internally " +"between your bank accounts from the dashboard or from the menus up top." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:110 +msgid "" +"This will take you to the same screen you have for receiving and making " +"payments." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:118 +msgid "" +"When making an internal transfer from one bank account to another, select " +"the bank you want to apply the transfer from in the dashboard, and in the " +"register payments screen, you select the transfer to account. Do not go " +"through this process again in the other bank account or else you will end up" +" with two journal entries for the same transaction." +msgstr "" + +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr "" + +#: ../../accounting/receivables/getting_paid.rst:3 +msgid "How to get paid?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:3 +msgid "How to automate customer follow-ups with plans?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:5 +msgid "" +"With the Odoo Accounting application, you get a dynamic aged receivable " +"report, customer statements and you can easily send them to customers." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:8 +msgid "" +"If you want to go further in the automation of the credit collection " +"process, you can use follow-up plans. They will help you automate all the " +"steps to get paid, by triggering them at the right time: send customer " +"statements by emails, send regular letter (through the Docsaway " +"integration), create a task to manually call the customer, etc..." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:14 +msgid "Here is an example of a plan:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "When?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "What?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:17 +msgid "Who?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "3 days before due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +msgid "Email" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:19 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "automated" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "1 day after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:21 +msgid "Email + Regular Letter" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "15 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +msgid "Call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:23 +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "John Mac Gregor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "35 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:25 +msgid "Email + Letter + Call" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "60 days after due date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Formal notice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:27 +msgid "Bailiff" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:34 +msgid "Install Reminder Module" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:36 +msgid "" +"You must start by activating the feature, using the menu " +":menuselection:`Configuration --> Settings` of the Accounting application. " +"From the settings screen, activate the feature **Enable payment follow-up " +"management**." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:44 +msgid "Define Payment Follow-ups Levels" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:46 +msgid "" +"To automate customer follow ups, you must configure your follow–up levels " +"using the menu :menuselection:`Accounting --> Configuration --> Payment " +"Follow-ups`. You should define one and only one follow-up plan per company." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:50 +msgid "" +"The levels of follow-up are relative to the due date; when no payment term " +"is specified, the invoice date will be considered as the due date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:53 +msgid "" +"For each level, you should define the number of days and create a note which" +" will automatically be added into the reminder letter." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:59 +msgid "Odoo defines several actions for every reminder:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:61 +msgid "" +"**Manual Action:** assign a responsible that will have to call the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:62 +msgid "**Send an Email:** send an email to customer using the provided text" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:63 +msgid "" +"**Send a Letter:** send a letter by regular mail, using the provided note" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:69 +msgid "" +"As you need to provide a number of days relative to the due date, you can " +"use a negative number. As an example, if an invoice is issued the January " +"1st but the due date is January 20, if you set a reminder 3 days before the " +"due date, the customer may receive an email in January 17." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:76 +msgid "Doing your weekly follow-ups" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:78 +msgid "" +"Once everything is setup, Odoo will prepare follow-up letters and emails " +"automatically for you. All you have to do is to the menu " +":menuselection:`Sales --> Customers Statement` in the accounting " +"application." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:85 +msgid "" +"Odoo will automatically propose you actions based on the follow-up plan you " +"defined, invoices to pay and payment received." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:88 +msgid "" +"You can use this menu every day, once a week or once a month. You do not " +"risk to send two times the same reminder to your customer. Odoo only " +"proposes you the action you have to do. If you do it every day, you will " +"have a few calls to do per day. If you do it once a month, you will have " +"much more work once you do it." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:94 +msgid "" +"It's up to you to organize the way you want to work. But it's a good " +"practice to reconcile your bank statements before launching the follow-ups. " +"That way, all paid invoices will be reconciled and you will not send a " +"follow-up letter to a customer that already paid his invoice." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:99 +msgid "From a customer follow-up proposition, you can:" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:101 +msgid "Get the customer information to contact him" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:103 +msgid "Drill down to the customer information form by clicking on its name" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:105 +msgid "Change the text (or the email or letter) and adapt to the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:107 +msgid "" +"Change the colored dot to mark the customer as being a good, normal or bad " +"debtor" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:110 +msgid "Log a note is you called the customer" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:112 +msgid "Exclude some invoices from the statement table (litigation)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:114 +msgid "Send an email with the statement" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:116 +msgid "" +"Print a letter, or send a regular mail (if you installed the Docsaway " +"integration)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:119 +msgid "" +"Plan the next reminder (but it's better to keep in automatic mode so that " +"Odoo will stick to the follow-up plan of the company)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:122 +msgid "Drill down to an invoice" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:124 +msgid "" +"Change the expected payment date of an invoice (thus, impacting the next " +"time Odoo will propose you to send a reminder)" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:128 +msgid "" +"You can force a customer statement, even if Odoo do not proposes you to do " +"it, because it's not the right date yet. To do this, you should go to the " +"Aged Receivable report (in the report menu of the Accounting application). " +"From this report, you can click on a customer to get to his customer " +"statement." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:135 +msgid "How to exclude an invoice from auto follow up?" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:137 +msgid "To see all **overdue invoices** or **on need of action**," +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:139 +msgid "Go to :menuselection:`Accounting --> Sales --> Customers Statement`" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:145 +msgid "Exclude a specific invoice for a specific date" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:147 +msgid "" +"Odoo can exclude an invoice from follow-ups actions for specific date by " +"clicking on **Log a Note**, then choose one of the ready options (*one " +"week*, *two weeks*, *one month*, *two months*), So Odoo will calculate the " +"required date according to the current date." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:155 +msgid "" +"Another way to achieve it is the following: click on the required invoice, " +"then choose **Change expected payment date/note**, then enter a new payment " +"date and note." +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:162 +msgid "Exclude a specific invoice forever" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:164 +msgid "" +"Odoo can exclude an invoice for a specific customer by clicking on the " +"checkbox **Excluded**" +msgstr "" + +#: ../../accounting/receivables/getting_paid/automated_followups.rst:168 +msgid "If you click on **History**, you can see all follow ups actions." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/applications.po b/locale/tr/LC_MESSAGES/applications.po new file mode 100644 index 000000000..2b91ef614 --- /dev/null +++ b/locale/tr/LC_MESSAGES/applications.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../applications.rst:3 +msgid "Applications" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/crm.po b/locale/tr/LC_MESSAGES/crm.po new file mode 100644 index 000000000..8d8e13e04 --- /dev/null +++ b/locale/tr/LC_MESSAGES/crm.po @@ -0,0 +1,2488 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Murat Kaplan <muratk@projetgrup.com>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../crm.rst:5 +msgid "CRM" +msgstr "" + +#: ../../crm/calendar.rst:3 +msgid "Calendar" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:3 +msgid "How to synchronize your calendar with Google Calendar" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:5 +msgid "" +"Connect on your google account and go to " +"`https://console.developers.google.com/ " +"<https://console.developers.google.com/>`_." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:7 +msgid "" +"Click on **Create a project...** and enter a project name and change your id" +" if you want. Don't forget to accept the Terms of Services" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:13 +msgid "" +"In the menu on left side, select the sub menu APIs (from menu APIs and auth)" +" and click on 'Calendar API'. Activate the Calendar API by clicking on the " +"blue button 'Enable API'. When it's done, the Calendar API overview will be " +"available" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:26 +msgid "" +"In the menu on left side, select the sub menu 'Credentials' (from menu APIs " +"and auth) and click on button 'Create new Client ID'" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:32 +msgid "" +"Check that the Application type is set on 'Web Application', then click on " +"'Configure consent screen'. Specify an email address and a product name, " +"then save." +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:41 +msgid "" +"You should now configure the allowed pages on which you will be redirected. " +"To do it, you need to complete the field \"Authorized redirect URI\" and set" +" as value (your own domain followed by '/google_account/authentication'): " +"==> http://mydomain.odoo.com/google_account/authentication You can now click" +" on 'Create Client ID'" +msgstr "" + +#: ../../crm/calendar/google_calendar_credentials.rst:48 +msgid "" +"Once done, you will have the both informations (Client ID and Client Secret)" +" that you need to insert in the 2 fields below!" +msgstr "" + +#: ../../crm/leads.rst:3 +msgid "Leads" +msgstr "" + +#: ../../crm/leads/generate.rst:3 +msgid "Generate leads" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:3 +msgid "How to generate leads from incoming emails?" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:5 +msgid "" +"There are several ways for your company to :doc:`generate leads with Odoo " +"CRM <manual>`. One of them is using your company's generic email address as " +"a trigger to create a new lead in the system. In Odoo, each one of your " +"sales teams is linked to its own email address from which prospects can " +"reach them. For example, if the personal email address of your Direct team " +"is **direct@mycompany.example.com**, every email sent will automatically " +"create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:14 +#: ../../crm/leads/generate/website.rst:73 +#: ../../crm/leads/manage/automatic_assignation.rst:30 +#: ../../crm/leads/manage/lead_scoring.rst:19 +#: ../../crm/overview/started/setup.rst:10 ../../crm/reporting/review.rst:23 +#: ../../crm/salesteam/manage/reward.rst:12 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../crm/leads/generate/emails.rst:16 +msgid "" +"The first thing you need to do is to configure your **outgoing email " +"servers** and **incoming email gateway** from the :menuselection:`Settings " +"module --> General Settings`." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:19 +msgid "" +"Then set up your alias domain from the field shown here below and click on " +"**Apply**." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:26 +msgid "Set up team alias" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:28 +msgid "" +"Go on the Sales module and click on **Dashboard**. You will see that the " +"activation of your domain alias has generated a default email alias for your" +" existing sales teams." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:35 +msgid "" +"You can easily personalize your sales teams aliases. Click on the More " +"button from the sales team of your choice, then on **Settings** to access " +"the sales team form. Into the **Email Alias** field, enter your email alias " +"and click on **Save**. Make sure to allow receiving emails from everyone." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:41 +msgid "" +"From there, each email sent to this email address will generate a new lead " +"into the related sales team." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:48 +msgid "Set up catch-all email domain" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:50 +msgid "" +"Additionally to your sales team aliases, you can also create a generic email" +" alias (e.g. *contact@* or *info@* ) that will also generate a new contact " +"in Odoo CRM. Still from the Sales module, go to " +":menuselection:`Configuration --> Settings` and set up your catch-all email " +"domain." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:57 +msgid "" +"You can choose whether the contacts generated from your catch-all email " +"become leads or opportunities using the radio buttons that you see on the " +"screenshot here below. Note that, by default, the lead stage is not " +"activated in Odoo CRM." +msgstr "" + +#: ../../crm/leads/generate/emails.rst:67 +#: ../../crm/leads/generate/import.rst:89 +#: ../../crm/leads/generate/website.rst:194 +msgid ":doc:`manual`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:68 +#: ../../crm/leads/generate/manual.rst:69 +#: ../../crm/leads/generate/website.rst:195 +msgid ":doc:`import`" +msgstr "" + +#: ../../crm/leads/generate/emails.rst:69 +#: ../../crm/leads/generate/import.rst:91 +#: ../../crm/leads/generate/manual.rst:73 +msgid ":doc:`website`" +msgstr "" + +#: ../../crm/leads/generate/import.rst:3 +msgid "How to import contacts to the CRM?" +msgstr "" + +#: ../../crm/leads/generate/import.rst:5 +msgid "" +"In Odoo CRM, you can import a database of potential customers, for instance " +"for a cold emailing or cold calling campaign, through a CSV file. You may be" +" wondering if the best option is to import your contacts as leads or " +"opportunities. It depends on your business specificities and workflow:" +msgstr "" + +#: ../../crm/leads/generate/import.rst:11 +msgid "" +"Some companies may decide to not use leads, but instead to keep all " +"information directly in an opportunity. For some companies, leads are merely" +" an extra step in the sales process. You could call this extended (start " +"from lead) versus simplified (start from opportunity) customer relationship " +"management." +msgstr "" + +#: ../../crm/leads/generate/import.rst:17 +msgid "" +"Odoo perfectly allows for either one of these approaches to be chosen. If " +"your company handles its sales from a pre qualification step, feel free to " +"activate first the lead stage as described below in order to import your " +"database as leads" +msgstr "" + +#: ../../crm/leads/generate/import.rst:23 +#: ../../crm/leads/generate/manual.rst:9 +#: ../../crm/leads/generate/website.rst:38 +#: ../../crm/salesteam/setup/organize_pipeline.rst:62 +msgid "Activate the lead stage" +msgstr "" + +#: ../../crm/leads/generate/import.rst:25 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. If you want to " +"import your contacts as leads rather than opportunities, go to " +":menuselection:`Configuration --> Settings`, select the option **use leads " +"if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/import.rst:33 +msgid "" +"This activation will create a new submenu :menuselection:`Sales --> Leads` " +"from which you will be able to import your contacts from the **Import** " +"button (if you want to create a lead manually, :doc:`click here <manual>`)" +msgstr "" + +#: ../../crm/leads/generate/import.rst:41 +msgid "Import your CSV file" +msgstr "" + +#: ../../crm/leads/generate/import.rst:43 +msgid "" +"On the new submenu :menuselection:`Sales --> Leads`, click on **Import** and" +" select your Excel file to import from the **Choose File** button. Make sure" +" its extension is **.csv** and don't forget to set up the correct File " +"format options (**Encoding** and **Separator**) to match your local settings" +" and display your columns properly." +msgstr "" + +#: ../../crm/leads/generate/import.rst:50 +msgid "" +"If your prospects database is provided in another format than CSV, you can " +"easily convert it to the CSV format using Microsoft Excel, OpenOffice / " +"LibreOffice Calc, Google Docs, etc." +msgstr "" + +#: ../../crm/leads/generate/import.rst:58 +msgid "Select rows to import" +msgstr "" + +#: ../../crm/leads/generate/import.rst:60 +msgid "" +"Odoo will automatically map the column headers from your CSV file to the " +"corresponding fields if you tick *The first row of the file contains the " +"label of the column* option. This makes imports easier especially when the " +"file has many columns. Of course, you can remap the column headers to " +"describe the property you are importing data into (First Name, Last Name, " +"Email, etc.)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:72 +msgid "" +"If you want to import your contacts as opportunities rather than leads, make" +" sure to add the *Type* column to your csv. This column is used to indicate " +"whether your import will be flagged as a Lead (type = Lead) or as an " +"opportunity (type = Opportunity)." +msgstr "" + +#: ../../crm/leads/generate/import.rst:77 +msgid "" +"Click the **Validate** button if you want to let Odoo verify that everything" +" seems okay before importing. Otherwise, you can directly click the Import " +"button: the same validations will be done." +msgstr "" + +#: ../../crm/leads/generate/import.rst:83 +msgid "" +"For additional technical information on how to import contacts into Odoo " +"CRM, read the **Frequently Asked Questions** section located below the " +"Import tool on the same window." +msgstr "" + +#: ../../crm/leads/generate/import.rst:90 +#: ../../crm/leads/generate/manual.rst:71 +#: ../../crm/leads/generate/website.rst:196 +msgid ":doc:`emails`" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:3 +msgid "How to create a contact into Odoo CRM?" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:5 +msgid "" +"Odoo CRM allows you to manually add contacts into your pipeline. It can be " +"either a lead or an opportunity." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:11 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. To activate it, go " +"to :menuselection:`Sales --> Configuration --> Settings`, select the option " +"\"\"use leads if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:18 +msgid "" +"This activation will create a new submenu **Leads** under **Sales** that " +"gives you access to a list of all your leads from which you will be able to " +"create a new contact." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:26 +msgid "Create a new lead" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:28 +msgid "" +"Go to :menuselection:`Sales --> Leads` and click the **Create** button." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:33 +msgid "" +"From the contact form, provide all the details in your possession (contact " +"name, email, phone, address, etc.) as well as some additional information in" +" the **Internal notes** field. You can also link the lead to an existing " +"company by editing the**Customer** field. Click on save and the contact will" +" be visible as a lead in your pipeline ." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:41 +msgid "" +"your lead can be directly handed over to specific sales team and salesperson" +" by clicking on **Convert to Opportunity** on the upper left corner of the " +"screen." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:45 +msgid "Create a new opportunity" +msgstr "" + +#: ../../crm/leads/generate/manual.rst:47 +msgid "" +"You can also directly add a contact into a specific sales team without " +"having to convert the lead first. On the Sales module, go to your dashboard " +"and click on the **Pipeline** button of the desired sales team. If you don't" +" have any sales team yet, :doc:`you need to create one first " +"<../../salesteam/setup/create_team>`. Then, click on **Create** and fill in " +"the contact details as shown here above. By default, the newly created " +"opportunity will appear on the first stage of your sales pipeline." +msgstr "" + +#: ../../crm/leads/generate/manual.rst:55 +msgid "" +"Another way to create an opportunity is by adding it directly on a specific " +"stage. For example, if you have have spoken to Mr. Smith at a meeting and " +"you want to send him a quotation right away, you can add his contact details" +" on the fly directly into the **Proposition** stage. From the Kanban view of" +" your sales team, just click on the **+** icon at the right of your stage to" +" create the contact. The new opportunity will then pop up into the " +"corresponding stage and you can then fill in the contact details by clicking" +" on it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:3 +msgid "How to generate leads from my website?" +msgstr "" + +#: ../../crm/leads/generate/website.rst:5 +msgid "" +"Your website should be your company's first lead generation tool. With your " +"website being the central hub of your online marketing campaigns, you will " +"naturally drive qualified traffic to feed your pipeline. When a prospect " +"lands on your website, your objective is to capture his information in order" +" to be able to stay in touch with him and to push him further down the sales" +" funnel." +msgstr "" + +#: ../../crm/leads/generate/website.rst:12 +msgid "This is how a typical online lead generation process work :" +msgstr "" + +#: ../../crm/leads/generate/website.rst:14 +msgid "" +"Your website visitor clicks on a call-to action (CTA) from one of your " +"marketing materials (e.g. an email newsletter, a social media message or a " +"blog post)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:18 +msgid "" +"The CTA leads your visitor to a landing page including a form used to " +"collect his personal information (e.g. his name, his email address, his " +"phone number)" +msgstr "" + +#: ../../crm/leads/generate/website.rst:22 +msgid "" +"The visitor submits the form and automatically generates a lead into Odoo " +"CRM" +msgstr "" + +#: ../../crm/leads/generate/website.rst:27 +msgid "" +"Your calls-to-action, landing pages and forms are the key pieces of the lead" +" generation process. With Odoo Website, you can easily create and optimize " +"those critical elements without having to code or to use third-party " +"applications. Learn more `here <https://www.odoo.com/page/website-" +"builder>`__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:32 +msgid "" +"In Odoo, the Website and CRM modules are fully integrated, meaning that you " +"can easily generate leads from various ways through your website. However, " +"even if you are hosting your website on another CMS, it is still possible to" +" fill Odoo CRM with leads generated from your website." +msgstr "" + +#: ../../crm/leads/generate/website.rst:40 +msgid "" +"By default, the lead stage is not activated in Odoo CRM. Therefore, new " +"leads automatically become opportunities. You can easily activate the option" +" of adding the lead step. If you want to import your contacts as leads " +"rather than opportunities, from the Sales module go to " +":menuselection:`Configuration --> Settings`, select the option **use leads " +"if…** as shown below and click on **Apply**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:50 +msgid "" +"Note that even without activating this step, the information that follows is" +" still applicable - the lead generated will land in the opportunities " +"dashboard." +msgstr "" + +#: ../../crm/leads/generate/website.rst:55 +msgid "From an Odoo Website" +msgstr "" + +#: ../../crm/leads/generate/website.rst:57 +msgid "" +"Let's assume that you want to get as much information as possible about your" +" website visitors. But how could you make sure that every person who wants " +"to know more about your company's products and services is actually leaving " +"his information somewhere? Thanks to Odoo's integration between its CRM and " +"Website modules, you can easily automate your lead acquisition process " +"thanks to the **contact form** and the **form builder** modules" +msgstr "" + +#: ../../crm/leads/generate/website.rst:67 +msgid "" +"another great way to generate leads from your Odoo Website is by collecting " +"your visitors email addresses thanks to the Newsletter or Newsletter Popup " +"CTAs. These snippets will create new contacts in your Email Marketing's " +"mailing list. Learn more `here <https://www.odoo.com/page/email-" +"marketing>`__." +msgstr "" + +#: ../../crm/leads/generate/website.rst:75 +msgid "" +"Start by installing the Website builder module. From the main dashboard, " +"click on **Apps**, enter \"**Website**\" in the search bar and click on " +"**Install**. You will be automatically redirected to the web interface." +msgstr "" + +#: ../../crm/leads/generate/website.rst:84 +msgid "" +"A tutorial popup will appear on your screen if this is the first time you " +"use Odoo Website. It will help you get started with the tool and you'll be " +"able to use it in minutes. Therefore, we strongly recommend you to use it." +msgstr "" + +#: ../../crm/leads/generate/website.rst:89 +msgid "Create a lead by using the Contact Form module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:91 +msgid "" +"You can effortlessly generate leads via a contact form on your **Contact " +"us** page. To do so, you first need to install the Contact Form module. It " +"will add a contact form in your **Contact us** page and automatically " +"generate a lead from forms submissions." +msgstr "" + +#: ../../crm/leads/generate/website.rst:96 +msgid "" +"To install it, go back to the backend using the square icon on the upper-" +"left corner of your screen. Then, click on **Apps**, enter \"**Contact " +"Form**\" in the search bar (don't forget to remove the **Apps** tag " +"otherwise you will not see the module appearing) and click on **Install**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:104 +msgid "" +"Once the module is installed, the below contact form will be integrated to " +"your \"Contact us\" page. This form is linked to Odoo CRM, meaning that all " +"data entered through the form will be captured by the CRM and will create a " +"new lead." +msgstr "" + +#: ../../crm/leads/generate/website.rst:112 +msgid "" +"Every lead created through the contact form is accessible in the Sales " +"module, by clicking on :menuselection:`Sales --> Leads`. The name of the " +"lead corresponds to the \"Subject\" field on the contact form and all the " +"other information is stored in the corresponding fields within the CRM. As a" +" salesperson, you can add additional information, convert the lead into an " +"opportunity or even directly mark it as Won or Lost." +msgstr "" + +#: ../../crm/leads/generate/website.rst:123 +msgid "Create a lead using the Form builder module" +msgstr "" + +#: ../../crm/leads/generate/website.rst:125 +msgid "" +"You can create fully-editable custom forms on any landing page on your " +"website with the Form Builder snippet. As for the Contact Form module, the " +"Form Builder will automatically generate a lead after the visitor has " +"completed the form and clicked on the button **Send**." +msgstr "" + +#: ../../crm/leads/generate/website.rst:130 +msgid "" +"From the backend, go to Settings and install the \"**Website Form " +"Builder**\" module (don't forget to remove the **Apps** tag otherwise you " +"will not see the modules appearing). Then, back on the website, go to your " +"desired landing page and click on Edit to access the available snippets. The" +" Form Builder snippet lays under the **Feature** section." +msgstr "" + +#: ../../crm/leads/generate/website.rst:140 +msgid "" +"As soon as you have dropped the snippet where you want the form to appear on" +" your page, a **Form Parameters** window will pop up. From the **Action** " +"drop-down list, select **Create a lead** to automatically create a lead in " +"Odoo CRM. On the **Thank You** field, select the URL of the page you want to" +" redirect your visitor after the form being submitted (if you don't add any " +"URL, the message \"The form has been sent successfully\" will confirm the " +"submission)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:151 +msgid "" +"You can then start creating your custom form. To add new fields, click on " +"**Select container block** and then on the blue **Customize** button. 3 " +"options will appear:" +msgstr "" + +#: ../../crm/leads/generate/website.rst:158 +msgid "" +"**Change Form Parameters**: allows you to go back to the Form Parameters and" +" change the configuration" +msgstr "" + +#: ../../crm/leads/generate/website.rst:161 +msgid "" +"**Add a model field**: allows you to add a field already existing in Odoo " +"CRM from a drop-down list. For example, if you select the Field *Country*, " +"the value entered by the lead will appear under the *Country* field in the " +"CRM - even if you change the name of the field on the form." +msgstr "" + +#: ../../crm/leads/generate/website.rst:167 +msgid "" +"**Add a custom field**: allows you to add extra fields that don't exist by " +"default in Odoo CRM. The values entered will be added under \"Notes\" within" +" the CRM. You can create any field type : checkbox, radio button, text, " +"decimal number, etc." +msgstr "" + +#: ../../crm/leads/generate/website.rst:172 +msgid "Any submitted form will create a lead in the backend." +msgstr "" + +#: ../../crm/leads/generate/website.rst:175 +msgid "From another CMS" +msgstr "" + +#: ../../crm/leads/generate/website.rst:177 +msgid "" +"If you use Odoo CRM but not Odoo Website, you can still automate your online" +" lead generation process using email gateways by editing the \"Submit\" " +"button of any form and replacing the hyperlink by a mailto corresponding to " +"your email alias (learn how to create your sales alias :doc:`here " +"<emails>`)." +msgstr "" + +#: ../../crm/leads/generate/website.rst:183 +msgid "" +"For example if the alias of your company is **salesEMEA@mycompany.com**, add" +" ``mailto:salesEMEA@mycompany.com`` into the regular hyperlink code (CTRL+K)" +" to generate a lead into the related sales team in Odoo CRM." +msgstr "" + +#: ../../crm/leads/manage.rst:3 +msgid "Manage leads" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:3 +msgid "Automate lead assignation to specific sales teams or salespeople" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:5 +msgid "" +"Depending on your business workflow and needs, you may need to dispatch your" +" incoming leads to different sales team or even to specific salespeople. " +"Here are a few example:" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:9 +msgid "" +"Your company has several offices based on different geographical regions. " +"You will want to assign leads based on the region;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:12 +msgid "" +"One of your sales teams is dedicated to treat opportunities from large " +"companies while another one is specialized for SMEs. You will want to assign" +" leads based on the company size;" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:16 +msgid "" +"One of your sales representatives is the only one to speak foreign languages" +" while the rest of the team speaks English only. Therefore you will want to " +"assign to that person all the leads from non-native English-speaking " +"countries." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:21 +msgid "" +"As you can imagine, manually assigning new leads to specific individuals can" +" be tedious and time consuming - especially if your company generates a high" +" volume of leads every day. Fortunately, Odoo CRM allows you to automate the" +" process of lead assignation based on specific criteria such as location, " +"interests, company size, etc. With specific workflows and precise rules, you" +" will be able to distribute all your opportunities automatically to the " +"right sales teams and/or salesman." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:32 +msgid "" +"If you have just started with Odoo CRM and haven't set up your sales team " +"nor registered your salespeople, :doc:`read this documentation first " +"<../../overview/started/setup>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:36 +msgid "" +"You have to install the module **Lead Scoring**. Go to :menuselection:`Apps`" +" and install it if it's not the case already." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:40 +msgid "Define rules for a sales team" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:42 +msgid "" +"From the sales module, go to your dashboard and click on the **More** button" +" of the desired sales team, then on **Settings**. If you don't have any " +"sales team yet, :doc:`you need to create one first " +"<../../salesteam/setup/create_team>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:50 +msgid "" +"On your sales team menu, use in the **Domain** field a specific domain rule " +"(for technical details on the domain refer on the `Building a Module " +"tutorial " +"<https://www.odoo.com/documentation/9.0/howtos/backend.html#domains>`__ or " +"`Syntax reference guide " +"<https://www.odoo.com/documentation/9.0/reference/orm.html#reference-orm-" +"domains>`__) which will allow only the leads matching the team domain." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:56 +msgid "" +"For example, if you want your *Direct Sales* team to only receive leads " +"coming from United States and Canada, your domain will be as following :" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:59 +msgid "``[[country_id, 'in', ['United States', 'Canada']]]``" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:66 +msgid "" +"you can also base your automatic assignment on the score attributed to your " +"leads. For example, we can imagine that you want all the leads with a score " +"under 100 to be assigned to a sales team trained for lighter projects and " +"the leads over 100 to a more experienced sales team. Read more on :doc:`how " +"to score leads here <lead_scoring>`." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:72 +msgid "Define rules for a salesperson" +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:74 +msgid "" +"You can go one step further in your assignment rules and decide to assign " +"leads within a sales team to a specific salesperson. For example, if I want " +"Toni Buchanan from the *Direct Sales* team to receive only leads coming from" +" Canada, I can create a rule that will automatically assign him leads from " +"that country." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:80 +msgid "" +"Still from the sales team menu (see here above), click on the salesperson of" +" your choice under the assignment submenu. Then, enter your rule in the " +"*Domain* field." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:89 +msgid "" +"In Odoo, a lead is always assigned to a sales team before to be assigned to " +"a salesperson. Therefore, you need to make sure that the assignment rule of " +"your salesperson is a child of the assignment rule of the sales team." +msgstr "" + +#: ../../crm/leads/manage/automatic_assignation.rst:95 +#: ../../crm/salesteam/manage/create_salesperson.rst:67 +msgid ":doc:`../../overview/started/setup`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:3 +msgid "How to do efficient Lead Scoring?" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:5 +msgid "" +"Odoo's Lead Scoring module allows you to give a score to your leads based on" +" specific criteria - the higher the value, the more likely the prospect is " +"\"ready for sales\". Therefore, the best leads are automatically assigned to" +" your salespeople so their pipe are not polluted with poor-quality " +"opportunities." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:12 +msgid "" +"Lead scoring is a critical component of an effective lead management " +"strategy. By helping your sales representative determine which leads to " +"engage with in order of priority, you will increase their overall conversion" +" rate and your sales team's efficiency." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:22 +msgid "Install the Lead Scoring module" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:24 +msgid "Start by installing the **Lead Scoring** module." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:26 +msgid "" +"Once the module is installed, you should see a new menu " +":menuselection:`Sales --> Leads Management --> Scoring Rules`" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:33 +msgid "Create scoring rules" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:35 +msgid "" +"Leads scoring allows you to assign a positive or negative score to your " +"prospects based on any demographic or behavioral criteria that you have set " +"(country or origin, pages visited, type of industry, role, etc.). To do so " +"you'll first need to create rules that will assign a score to a given " +"criteria." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:43 +msgid "" +"In order to assign the right score to your various rules, you can use these " +"two methods:" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:45 +msgid "" +"Establish a list of assets that your ideal customer might possess to " +"interest your company. For example, if you run a local business in " +"California, a prospect coming from San Francisco should have a higher score " +"than a prospect coming from New York." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:49 +msgid "" +"Dig into your data to uncover characteristics shared by your closed " +"opportunities and most important clients." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:52 +msgid "" +"Please note that this is not an exact science, so you'll need time and " +"feedback from your sales teams to adapt and fine tune your rules until " +"getting the desired result." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:56 +msgid "" +"In the **Scoring Rules** menu, click on **Create** to write your first rule." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:61 +msgid "" +"First name your rule, then enter a value and a domain (refer on the " +"`official python documentation <https://docs.python.org/2/tutorial/>`__ for " +"more information). For example, if you want to assign 8 points to all the " +"leads coming from **Belgium**, you'll need to give ``8`` as a **value** and " +"``[['country\\_id',=,'Belgium']]`` as a domain." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:68 +msgid "Here are some criteria you can use to build a scoring rule :" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:70 +msgid "country of origin : ``'country_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:72 +msgid "stage in the sales cycle : ``'stage_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:74 +msgid "" +"email address (e.g. if you want to score the professional email addresses) :" +" ``'email_from'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:76 +msgid "page visited : ``'score_pageview_ids.url'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:78 +msgid "name of a marketing campaign : ``'campaign_id'``" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:80 +msgid "" +"After having activated your rules, Odoo will give a value to all your new " +"incoming leads. This value can be found directly on your lead's form view." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:88 +msgid "Assign high scoring leads to your sales teams" +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:90 +msgid "" +"The next step is now to automatically convert your best leads into " +"opportunities. In order to do so, you need to decide what is the minimum " +"score a lead should have to be handed over to a given sales team. Go to your" +" **sales dashboard** and click on the **More** button of your desired sales " +"team, then on **Settings**. Enter your value under the **Minimum score** " +"field." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:100 +msgid "" +"From the example above, the **Direct Sales** team will only receive " +"opportunities with a minimum score of ``50``. The prospects with a lower " +"score can either stay in the lead stage or be assigned to another sales team" +" which has set up a different minimum score." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:106 +msgid "" +"Organize a meeting between your **Marketing** and **Sales** teams in order " +"to align your objectives and agree on what minimum score makes a sales-ready" +" lead." +msgstr "" + +#: ../../crm/leads/manage/lead_scoring.rst:110 +msgid ":doc:`automatic_assignation`" +msgstr "" + +#: ../../crm/leads/voip.rst:3 +msgid "Odoo VOIP" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:3 +msgid "Installation and Setup" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:9 +msgid "Dependencies" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:13 +msgid "wget" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:14 +msgid "gcc" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:15 +msgid "g++" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"<http://www.pjsip.org/download.htm>`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:37 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:43 +msgid "**run:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:49 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:57 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:63 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:69 +msgid "**The result should be:**" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:86 +msgid "Asterisk" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:88 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there <http://downloads.asterisk.org/pub/telephony/asterisk/old-" +"releases/asterisk-13.7.0.tar.gz>`_." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:90 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:96 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:102 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:108 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:114 +msgid "" +"In the menuselect, go to the resources option and ensure that res_srtp is " +"enabled. If there are 3 x’s next to res_srtp, there is a problem with the " +"srtp library and you must reinstall it. Save the configuration (press x). " +"You should also see stars in front of the res_pjsip lines." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:116 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:122 +msgid "" +"If you need the sample configs you can run 'make samples' to install the " +"sample configs. If you need to install the Asterisk startup script you can " +"run 'make config'." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:125 +msgid "DTLS Certificates" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:127 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:133 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:139 +msgid "" +"Create the DTLS certificates (replace pbx.mycompany.com with your ip address" +" or dns name, replace My Super Company with your company name):" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:146 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:148 +msgid "" +"For WebRTC, a lot of the settings that are needed MUST be in the peer " +"settings. The global settings do not flow down into the peer settings very " +"well. By default, Asterisk config files are located in /etc/asterisk/. Start" +" by editing http.conf and make sure that the following lines are " +"uncommented:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:158 +msgid "" +"Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and " +"icesupport to be enabled. In most cases, directmedia should be disabled. " +"Also under the WebRTC client, the transport needs to be listed as ‘ws’ to " +"allow websocket connections. All of these config lines should be under the " +"peer itself; setting these config lines globally might not work:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:186 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:193 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:202 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../crm/leads/voip/setup.rst:204 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:206 +msgid "" +"The SIP Login/Browser's Extension is the number you configured previously in" +" the sip.conf file. In our example, 1060. The SIP Password is the secret you" +" chose in the sip.conf file. The extension of your office's phone is not a " +"required field but it is used if you want to transfer your call from Odoo to" +" an external phone also configured in the sip.conf file." +msgstr "" + +#: ../../crm/leads/voip/setup.rst:212 +msgid "" +"The configuration should also be done in the sale settings under the title " +"\"PBX Configuration\". You need to put the IP you define in the http.conf " +"file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part " +"\"127.0.0.1\" needs to be the same as the IP defined previously and the " +"\"8088\" is the port you defined in the http.conf file." +msgstr "" + +#: ../../crm/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../crm/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo CRM" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:13 +msgid "" +"Hi, my name is Nicholas, I'm a business manager in the textile industry. I " +"sell accessories to retailers. Do you know the difference between a good " +"salesperson and an excellent salesperson? The key is to be productive and " +"organized to do the job. That's where Odoo comes in. Thanks to a well " +"structured organization you'll change a good team into an exceptional team." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:21 +msgid "" +"With Odoo CRM, the job is much easier for me and my entire team. When I log " +"in into Odoo CRM, I have a direct overview of my ongoing performance. But " +"also the activity of the next 7 days and the performance of the last month. " +"I see that I overachieved last month when compared to my invoicing target of" +" $200,000. I have a structured approach of my performance." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:28 +msgid "" +"If I want to have a deeper look into the details, I click on next actions " +"and I can see that today I have planned a call with Think Big Systems. Once " +"I have done my daily review, I usually go to my pipeline. The process is the" +" same for everyone in the team. Our job is to find resellers and before " +"closing any deal we have to go through different stages. We usually have a " +"first contact to qualify the opportunity, then move into offer & negotiation" +" stage, and closing by a 'won'..Well, that's if all goes well." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:38 +msgid "" +"The user interface is really smooth, I can drag and drop any business " +"opportunity from one stage to another in just a few clicks." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:42 +msgid "" +"Now I'd like to go further with an interesting contact: a department store. " +"I highlighted their file by changing the color. For each contact, I have a " +"form view where I can access to all necessary information about the contact." +" I see here my opportunity Macy's has an estimated revenue of $50,000 and a " +"success rate of 10%. I need to discuss about this partnership, so I will " +"schedule a meeting straight from the contact form: Macy's partnership " +"meeting. It's super easy to create a new meeting with any contact. I can as " +"well send an email straight from the opportunity form and the answer from " +"the prospect will simply pop up in the system too. Now, let's assume that " +"the meeting took place, therefore I can mark it as done. And the system " +"automatically suggests a next activity. Actually, we configured Odoo with a " +"set of typical activities we follow for every opportunity, and it's great to" +" have a thorough followup. The next activity will be a follow-up email. " +"Browsing from one screen to the other is really simple and adapting to the " +"view too! I can see my opportunitities as a to-do list of next activities " +"for example." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:62 +msgid "" +"With Odoo CRM I have a sales management tool that is really efficient and me" +" and my team can be well organized. I have a clear overview of my sales " +"pipeline, meetings, revenues, and more." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:67 +msgid "" +"I go back to my pipeline. Macy's got qualified successfully, which mean I " +"can move their file to the next step and I will dapt the expected revenue as" +" discussed. Once I have performed the qualification process, I will create a" +" new quotation based on the feedback I received from my contact. For my " +"existing customers, I can as well quickly discover the activity around them " +"for any Odoo module I use, and continue to discuss about them. It's that " +"simple." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:76 +msgid "" +"We have seen how I can manage my daily job as business manager or " +"salesperson. At the end of the journey I would like to have a concrete view " +"of my customer relationships and expected revenues. If I go into the reports" +" in Odoo CRM, I have the possibility to know exactly what's the evolution of" +" the leads over the past months, or have a look at the potential revenues " +"and the performance of the different teams in terms of conversions from " +"leads to opportunities for instance. So with Odoo I can have a clear " +"reporting of every activity based on predefined metrics or favorites. I can " +"search for other filters too and adapt the view. If I want to go in the " +"details, I choose the list view and can click on any item" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:90 +msgid "" +"Odoo CRM is not only a powerful tool to achieve our sales goals with " +"structured activities, performance dashboard, next acitivities and more, but" +" also allows me to:" +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:94 +msgid "" +"Use leads to get in the system unqualified but targeted contacts I may have " +"gathered in a conference or through a contact form on my website. Those " +"leads can then be converted into opportunities." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:99 +msgid "" +"Manage phone calls from Odoo CRM by using the VoIP app. Call customers, " +"manage a call queue, log calls, schedule calls and next actions to perform." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:103 +msgid "" +"Integrate with Odoo Sales to create beautiful online or PDF quotations and " +"turn them into sales orders." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:106 +msgid "" +"Use email marketing for marketing campaigns to my customers and prospects." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:109 +msgid "" +"Manage my business seamlessly, even on the go. Indeed, Odoo offers a mobile " +"app that lets every business organize key sales activities from leads to " +"quotes." +msgstr "" + +#: ../../crm/overview/main_concepts/introduction.rst:113 +msgid "" +"Odoo CRM is a powerful, yet easy-to-use app. I firstly used the sales " +"planner to clearly state my objectives and set up our CRM. It will help you " +"getting started quickly too." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:3 +msgid "Odoo CRM Terminologies" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:10 +msgid "**CRM (Customer relationship management)**:" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:6 +msgid "" +"System for managing a company's interactions with current and future " +"customers. It often involves using technology to organize, automate, and " +"synchronize sales, marketing, customer service, and technical support." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:14 +msgid "**Sales cycle** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:13 +msgid "" +"Sequence of phases used by a company to convert a prospect into a customer." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:20 +msgid "**Pipeline :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:17 +msgid "" +"Visual representation of your sales process, from the first contact to the " +"final sale. It refers to the process by which you generate, qualify and " +"close leads through your sales cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:24 +msgid "**Sales stage** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:23 +msgid "" +"In Odoo CRM, a stage defines where an opportunity is in your sales cycle and" +" its probability to close a sale." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:29 +msgid "**Lead :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:27 +msgid "" +"Someone who becomes aware of your company or someone who you decide to " +"pursue for a sale, even if they don't know about your company yet." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:34 +msgid "**Opportunity :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:32 +msgid "" +"A lead that has shown an interest in knowing more about your " +"products/services and therefore has been handed over to a sales " +"representative" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:39 +msgid "**Customer :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:37 +msgid "" +"In Odoo CRM, a customer refers to any contact within your database, whether " +"it is a lead, an opportunity, a client or a company." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:45 +msgid "**Key Performance Indicator (KPI)** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:42 +msgid "" +"A KPI is a measurable value that demonstrates how effectively a company is " +"achieving key business objectives. Organizations use KPIs to evaluate their " +"success at reaching targets." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:51 +msgid "**Lead scoring** :" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:48 +msgid "" +"System assigning a positive or negative score to prospects according to " +"their web activity and personal informations in order to determine whether " +"they are \"ready for sales\" or not." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:62 +msgid "**Kanban view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:54 +msgid "" +"In Odoo, the Kanban view is a workflow visualisation tool halfway between a " +"`list view <https://www.odoo.com/documentation/8.0/reference/views.html" +"#reference-views-list>`__ and a non-editable `form view " +"<https://www.odoo.com/documentation/8.0/reference/views.html#reference-" +"views-form>`__ and displaying records as \"cards\". Records may be grouped " +"in columns for use in workflow visualisation or manipulation (e.g. tasks or " +"work-progress management), or ungrouped (used simply to visualize records)." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:66 +msgid "**List view :**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:65 +msgid "" +"View allowing you to see your objects (contacts, companies, tasks, etc.) " +"listed in a table." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:71 +msgid "**Lead generation:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:69 +msgid "" +"Process by which a company collects relevant datas about potential customers" +" in order to enable a relationship and to push them further down the sales " +"cycle." +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:76 +msgid "**Campaign:**" +msgstr "" + +#: ../../crm/overview/main_concepts/terminologies.rst:74 +msgid "" +"Coordinated set of actions sent via various channels to a target audience " +"and whose goal is to generate leads. In Odoo CRM, you can link a lead to the" +" campaign which he comes from in order to measure its efficiency." +msgstr "" + +#: ../../crm/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:3 +msgid "Generating leads with Odoo CRM" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:6 +msgid "What is lead generation?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:8 +msgid "" +"Lead generation is the process by which a company acquires leads and " +"collects relevant datas about potential customers in order to enable a " +"relationship and to turn them into customers." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:12 +msgid "" +"For example, a website visitor who fills in your contact form to know more " +"about your products and services becomes a lead for your company. Typically," +" a Customer Relationship Management tool such as Odoo CRM is used to " +"centralize, track and manage leads." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:18 +msgid "Why is lead generation important for my business?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:20 +msgid "" +"Generating a constant flow of high-quality leads is one of the most " +"important responsibility of a marketing team. Actually, a well-managed lead " +"generation process is like the fuel that will allow your company to deliver " +"great performances - leads bring meetings, meetings bring sales, sales bring" +" revenue and more work." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:27 +msgid "How to generate leads with Odoo CRM?" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:29 +msgid "" +"Leads can be captured through many sources - marketing campaigns, " +"exhibitions and trade shows, external databases, etc. The most common " +"challenge is to successfully gather all the data and to track any lead " +"activity. Storing leads information in a central place such as Odoo CRM will" +" release you of these worries and will help you to better automate your lead" +" generation process, share information with your teams and analyze your " +"sales processes easily." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:37 +msgid "Odoo CRM provides you with several methods to generate leads:" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:39 +msgid ":doc:`../../leads/generate/emails`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:41 +msgid "" +"An inquiry email sent to one of your company's generic email addresses can " +"automatically generate a lead or an opportunity." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:44 +msgid ":doc:`../../leads/generate/manual`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:46 +msgid "" +"You may want to follow up with a prospective customer met briefly at an " +"exhibition who gave you his business card. You can manually create a new " +"lead and enter all the needed information." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:50 +msgid ":doc:`../../leads/generate/website`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:52 +msgid "" +"A website visitor who fills in a form automatically generates a lead or an " +"opportunity in Odoo CRM." +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:55 +msgid ":doc:`../../leads/generate/import`" +msgstr "" + +#: ../../crm/overview/process/generate_leads.rst:57 +msgid "" +"You can provide your salespeople lists of prospects - for example for a cold" +" emailing or a cold calling campaign - by importing them from any CSV file." +msgstr "" + +#: ../../crm/overview/started.rst:3 +msgid "Getting started" +msgstr "" + +#: ../../crm/overview/started/setup.rst:3 +msgid "How to setup your teams, sales process and objectives?" +msgstr "" + +#: ../../crm/overview/started/setup.rst:5 +msgid "" +"This quick step-by-step guide will lead you through Odoo CRM and help you " +"handle your sales funnel easily and constantly manage your sales funnel from" +" lead to customer." +msgstr "" + +#: ../../crm/overview/started/setup.rst:12 +msgid "" +"Create your database from `www.odoo.com/start " +"<http://www.odoo.com/start>`__, select the CRM icon as first app to install," +" fill in the form and click on *Create now*. You will automatically be " +"directed to the module when the database is ready." +msgstr "" + +#: ../../crm/overview/started/setup.rst:22 +msgid "" +"You will notice that the installation of the CRM module has created the " +"submodules Chat, Calendar and Contacts. They are mandatory so that every " +"feature of the app is running smoothly." +msgstr "" + +#: ../../crm/overview/started/setup.rst:27 +msgid "Introduction to the Sales Planner" +msgstr "" + +#: ../../crm/overview/started/setup.rst:29 +msgid "" +"The Sales Planner is a useful step-by-step guide created to help you " +"implement your sales funnel and define your sales objectives easier. We " +"strongly recommend you to go through every step of the tool the first time " +"you use Odoo CRM and to follow the requirements. Your input are strictly " +"personal and intended as a personal guide and mentor into your work. As it " +"does not interact with the backend, you are free to adapt any detail " +"whenever you feel it is needed." +msgstr "" + +#: ../../crm/overview/started/setup.rst:37 +msgid "" +"You can reach the Sales Planner from anywhere within the CRM module by " +"clicking on the progress bar located on the upper-right side of your screen." +" It will show you how far you are in the use of the Sales Planner." +msgstr "" + +#: ../../crm/overview/started/setup.rst:46 +msgid "Set up your first sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:49 +msgid "Create a new team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:51 +msgid "" +"A Direct Sales team is created by default on your instance. You can either " +"use it or create a new one. Refer to the page " +":doc:`../../salesteam/setup/create_team` for more information." +msgstr "" + +#: ../../crm/overview/started/setup.rst:56 +msgid "Assign salespeople to your sales team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:58 +msgid "" +"When your sales teams are created, the next step is to link your salespeople" +" to their team so they will be able to work on the opportunities they are " +"supposed to receive. For example, if within your company Tim is selling " +"products and John is selling maintenance contracts, they will be assigned to" +" different teams and will only receive opportunities that make sense to " +"them." +msgstr "" + +#: ../../crm/overview/started/setup.rst:65 +msgid "" +"In Odoo CRM, you can create a new user on the fly and assign it directly to " +"a sales team. From the **Dashboard**, click on the button **More** of your " +"selected sales team, then on **Settings**. Then, under the **Assignation** " +"section, click on **Create** to add a new salesperson to the team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:71 +msgid "" +"From the **Create: salesman** pop up window (see screenshot below), you can " +"assign someone on your team:" +msgstr "" + +#: ../../crm/overview/started/setup.rst:74 +msgid "" +"Either your salesperson already exists in the system and you will just need " +"to click on it from the drop-down list and it will be assigned to the team" +msgstr "" + +#: ../../crm/overview/started/setup.rst:77 +msgid "" +"Or you want to assign a new salesperson that doesn't exist into the system " +"yet - you can do it by creating a new user on the fly from the sales team. " +"Just enter the name of your new salesperson and click on Create (see below) " +"to create a new user into the system and directly assign it to your team. " +"The new user will receive an invite email to set his password and log into " +"the system. Refer to :doc:`../../salesteam/manage/create_salesperson` for " +"more information about that process" +msgstr "" + +#: ../../crm/overview/started/setup.rst:90 +msgid "Set up your pipeline" +msgstr "" + +#: ../../crm/overview/started/setup.rst:92 +msgid "" +"Now that your sales team is created and your salespeople are linked to it, " +"you will need to set up your pipeline -create the process by which your team" +" will generate, qualify and close opportunities through your sales cycle. " +"Refer to the document :doc:`../../salesteam/setup/organize_pipeline` to " +"define the stages of your pipeline." +msgstr "" + +#: ../../crm/overview/started/setup.rst:99 +msgid "Set up incoming email to generate opportunities" +msgstr "" + +#: ../../crm/overview/started/setup.rst:101 +msgid "" +"In Odoo CRM, one way to generate opportunities into your sales team is to " +"create a generic email address as a trigger. For example, if the personal " +"email address of your Direct team is `direct@mycompany.example.com " +"<mailto:direct@mycompany.example.com>`__\\, every email sent will " +"automatically create a new opportunity into the sales team." +msgstr "" + +#: ../../crm/overview/started/setup.rst:108 +msgid "Refer to the page :doc:`../../leads/generate/emails` to set it up." +msgstr "" + +#: ../../crm/overview/started/setup.rst:111 +msgid "Automate lead assignation" +msgstr "" + +#: ../../crm/overview/started/setup.rst:113 +msgid "" +"If your company generates a high volume of leads every day, it could be " +"useful to automate the assignation so the system will distribute all your " +"opportunities automatically to the right department." +msgstr "" + +#: ../../crm/overview/started/setup.rst:117 +msgid "" +"Refer to the document :doc:`../../leads/manage/automatic_assignation` for " +"more information." +msgstr "" + +#: ../../crm/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../crm/reporting/analysis.rst:3 +msgid "" +"How to analyze the sales performance of your team and get customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:5 +msgid "" +"As a manager, you need to constantly monitor your team's performance in " +"order to help you take accurate and relevant decisions for the company. " +"Therefore, the **Reporting** section of **Odoo Sales** represents a very " +"important tool that helps you get a better understanding of where your " +"company's strengths, weaknesses and opportunities are, showing you trends " +"and forecasts for key metrics such as the number of opportunities and their " +"expected revenue over time , the close rate by team or the length of sales " +"cycle for a given product or service." +msgstr "" + +#: ../../crm/reporting/analysis.rst:14 +msgid "" +"Beyond these obvious tracking sales funnel metrics, there are some other " +"KPIs that can be very valuable to your company when it comes to judging " +"sales funnel success." +msgstr "" + +#: ../../crm/reporting/analysis.rst:19 +msgid "Review pipelines" +msgstr "" + +#: ../../crm/reporting/analysis.rst:21 +msgid "" +"You will have access to your sales funnel performance from the **Sales** " +"module, by clicking on :menuselection:`Sales --> Reports --> Pipeline " +"analysis`. By default, the report groups all your opportunities by stage " +"(learn more on how to create and customize stage by reading " +":doc:`../salesteam/setup/organize_pipeline`) and expected revenues for the " +"current month. This report is perfect for the **Sales Manager** to " +"periodically review the sales pipeline with the relevant sales teams. Simply" +" by accessing this basic report, you can get a quick overview of your actual" +" sales performance." +msgstr "" + +#: ../../crm/reporting/analysis.rst:30 +msgid "" +"You can add a lot of extra data to your report by clicking on the " +"**measures** icon, such as :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:33 +msgid "Expected revenue." +msgstr "" + +#: ../../crm/reporting/analysis.rst:35 +msgid "overpassed deadline." +msgstr "" + +#: ../../crm/reporting/analysis.rst:37 +msgid "" +"Delay to assign (the average time between lead creation and lead " +"assignment)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:40 +msgid "Delay to close (average time between lead assignment and close)." +msgstr "" + +#: ../../crm/reporting/analysis.rst:42 +msgid "the number of interactions per opportunity." +msgstr "" + +#: ../../crm/reporting/analysis.rst:44 +msgid "etc." +msgstr "" + +#: ../../crm/reporting/analysis.rst:50 +msgid "" +"By clicking on the **+** and **-** icons, you can drill up and down your " +"report in order to change the way your information is displayed. For " +"example, if I want to see the expected revenues of my **Direct Sales** team," +" I need to click on the **+** icon on the vertical axis then on **Sales " +"Team**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:55 +msgid "" +"Depending on the data you want to highlight, you may need to display your " +"reports in a more visual view. Odoo **CRM** allows you to transform your " +"report in just a click thanks to 3 graph views : **Pie Chart**, **Bar " +"Chart** and **Line Chart**. These views are accessible through the icons " +"highlighted on the screenshot below." +msgstr "" + +#: ../../crm/reporting/analysis.rst:65 +msgid "Customize reports" +msgstr "" + +#: ../../crm/reporting/analysis.rst:67 +msgid "" +"You can easily customize your analysis reports depending on the **KPIs** " +"(see :doc:`../overview/main_concepts/terminologies`) you want to access. To " +"do so, use the **Advanced search view** located in the right hand side of " +"your screen, by clicking on the magnifying glass icon at the end of the " +"search bar button. This function allows you to highlight only selected data " +"on your report. The **filters** option is very useful in order to display " +"some categories of opportunities, while the **Group by** option improves the" +" readability of your reports according to your needs. Note that you can " +"filter and group by any existing field from your CRM, making your " +"customization very flexible and powerful." +msgstr "" + +#: ../../crm/reporting/analysis.rst:82 +msgid "" +"You can save and reuse any customized filter by clicking on **Favorites** " +"from the **Advanced search view** and then on **Save current search**. The " +"saved filter will then be accessible from the **Favorites** menu." +msgstr "" + +#: ../../crm/reporting/analysis.rst:87 +msgid "" +"Here are a few examples of customized reports that you can use to monitor " +"your sales' performances :" +msgstr "" + +#: ../../crm/reporting/analysis.rst:91 +msgid "Evaluate the current pipeline of each of your salespeople" +msgstr "" + +#: ../../crm/reporting/analysis.rst:93 +msgid "" +"From your pipeline analysis report, make sure first that the **Expected " +"revenue** option is selected under the **Measures** drop-down list. Then, " +"use the **+** and **-** icons and add **Salesperson** and **Stage** to your " +"vertical axis, and filter your desired salesperson. Then click on the " +"**graph view** icon to display a visual representation of your salespeople " +"by stage. This custom report allows you to easily overview the sales " +"activities of your salespeople." +msgstr "" + +#: ../../crm/reporting/analysis.rst:105 +msgid "Forecast monthly revenue by sales team" +msgstr "" + +#: ../../crm/reporting/analysis.rst:107 +msgid "" +"In order to predict monthly revenue and to estimate the short-term " +"performances of your teams, you need to play with two important metrics : " +"the **expected revenue** and the **expected closing**." +msgstr "" + +#: ../../crm/reporting/analysis.rst:111 +msgid "" +"From your pipeline analysis report, make sure first that the **Expected " +"revenue** option is selected under the **Measures** drop-down list. Then " +"click on the **+** icon from the vertical axis and select **Sales team**. " +"Then, on the horizontal axis, click on the **+** icon and select **Expected " +"closing.**" +msgstr "" + +#: ../../crm/reporting/analysis.rst:121 +msgid "" +"In order to keep your forecasts accurate and relevant, make sure your " +"salespeople correctly set up the expected closing and the expected revenue " +"for each one of their opportunities" +msgstr "" + +#: ../../crm/reporting/analysis.rst:126 +msgid ":doc:`../salesteam/setup/organize_pipeline`" +msgstr "" + +#: ../../crm/reporting/review.rst:3 +msgid "How to review my personal sales activities (new sales dashboard)" +msgstr "" + +#: ../../crm/reporting/review.rst:5 +msgid "" +"Sales professionals are struggling everyday to hit their target and follow " +"up on sales activities. They need to access anytime some important metrics " +"in order to know how they are performing and better organize their daily " +"work." +msgstr "" + +#: ../../crm/reporting/review.rst:10 +msgid "" +"Within the Odoo CRM module, every team member has access to a personalized " +"and individual dashboard with a real-time overview of:" +msgstr "" + +#: ../../crm/reporting/review.rst:13 +msgid "" +"Top priorities: they instantly see their scheduled meetings and next actions" +msgstr "" + +#: ../../crm/reporting/review.rst:16 +msgid "" +"Sales performances : they know exactly how they perform compared to their " +"monthly targets and last month activities." +msgstr "" + +#: ../../crm/reporting/review.rst:26 +msgid "Install the CRM application" +msgstr "" + +#: ../../crm/reporting/review.rst:28 +msgid "" +"In order to manage your sales funnel and track your opportunities, you need " +"to install the CRM module, from the **Apps** icon." +msgstr "" + +#: ../../crm/reporting/review.rst:35 +msgid "Create opportunities" +msgstr "" + +#: ../../crm/reporting/review.rst:37 +msgid "" +"If your pipeline is empty, your sales dashboard will look like the " +"screenshot below. You will need to create a few opportunities to activate " +"your dashboard (read the related documentation " +":doc:`../leads/generate/manual` to learn more)." +msgstr "" + +#: ../../crm/reporting/review.rst:45 +msgid "" +"Your dashboard will update in real-time based on the informations you will " +"log into the CRM." +msgstr "" + +#: ../../crm/reporting/review.rst:49 +msgid "" +"you can click anywhere on the dashboard to get a detailed analysis of your " +"activities. Then, you can easily create favourite reports and export to " +"excel." +msgstr "" + +#: ../../crm/reporting/review.rst:54 +msgid "Daily tasks to process" +msgstr "" + +#: ../../crm/reporting/review.rst:56 +msgid "" +"The left part of the sales dashboard (labelled **To Do**) displays the " +"number of meetings and next actions (for example if you need to call a " +"prospect or to follow-up by email) scheduled for the next 7 days." +msgstr "" + +#: ../../crm/reporting/review.rst:64 +msgid "Meetings" +msgstr "" + +#: ../../crm/reporting/review.rst:66 +msgid "" +"In the example here above, I see that I have no meeting scheduled for today " +"and 3 meeting scheduled for the next 7 days. I just have to click on the " +"**meeting** button to access my calendar and have a view on my upcoming " +"appointments." +msgstr "" + +#: ../../crm/reporting/review.rst:75 +msgid "Next actions" +msgstr "" + +#: ../../crm/reporting/review.rst:77 +msgid "" +"Back on the above example, I have 1 activity requiring an action from me. If" +" I click on the **Next action** green button, I will be redirected to the " +"contact form of the corresponding opportunity." +msgstr "" + +#: ../../crm/reporting/review.rst:84 +msgid "" +"Under the **next activity** field, I see that I had planned to send a " +"brochure by email today. As soon as the activity is completed, I can click " +"on **done** (or **cancel**) in order to remove this opportunity from my next" +" actions." +msgstr "" + +#: ../../crm/reporting/review.rst:90 +msgid "" +"When one of your next activities is overdue, it will appear in orange in " +"your dashboard." +msgstr "" + +#: ../../crm/reporting/review.rst:94 +msgid "Performances" +msgstr "" + +#: ../../crm/reporting/review.rst:96 +msgid "" +"The right part of your sales dashboard is about my sales performances. I " +"will be able to evaluate how I am performing compared to my targets (which " +"have been set up by my sales manager) and my activities of the last month." +msgstr "" + +#: ../../crm/reporting/review.rst:105 +msgid "Activities done" +msgstr "" + +#: ../../crm/reporting/review.rst:107 +msgid "" +"The **activities done** correspond to the next actions that have been " +"completed (meaning that you have clicked on **done** under the **next " +"activity** field). When I click on it, I will access a detailed reporting " +"regarding the activities that I have completed." +msgstr "" + +#: ../../crm/reporting/review.rst:116 +msgid "Won in opportunities" +msgstr "" + +#: ../../crm/reporting/review.rst:118 +msgid "" +"This section will sum up the expected revenue of all the opportunities " +"within my pipeline with a stage **Won**." +msgstr "" + +#: ../../crm/reporting/review.rst:125 +msgid "Quantity invoiced" +msgstr "" + +#: ../../crm/reporting/review.rst:127 +msgid "" +"This section will sum up the amount invoiced to my opportunities. For more " +"information about the invoicing process, refer to the related documentation:" +" :doc:`../../accounting/receivables/customer_invoices/overview`" +msgstr "" + +#: ../../crm/reporting/review.rst:132 +msgid ":doc:`analysis`" +msgstr "" + +#: ../../crm/salesteam.rst:3 ../../crm/salesteam/setup.rst:3 +msgid "Sales Team" +msgstr "" + +#: ../../crm/salesteam/manage.rst:3 +msgid "Manage salespeople" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:3 +msgid "How to create a new salesperson?" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:6 +msgid "Create a new user" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:8 +msgid "" +"From the Settings module, go to the submenu :menuselection:`Users --> Users`" +" and click on **Create**. Add first the name of your new salesperson and his" +" professional email address - the one he will use to log in to his Odoo " +"instance - and a picture." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:16 +msgid "" +"Under \"Access Rights\", you can choose which applications your user can " +"access and use. Different levels of rights are available depending on the " +"app. For the Sales application, you can choose between three levels:" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:20 +msgid "**See own leads**: the user will be able to access his own data only" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:22 +msgid "" +"**See all leads**: the user will be able to access all records of every " +"salesman in the sales module" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:25 +msgid "" +"**Manager**: the user will be able to access the sales configuration as well" +" as the statistics reports" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:28 +msgid "" +"When you're done editing the page and have clicked on **Save**, an " +"invitation email will automatically be sent to the user, from which he will " +"be able to log into his personal account." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:36 +msgid "Register your user into his sales team" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:38 +msgid "" +"Your user is now registered in Odoo and can log in to his own session. You " +"can also add him to the sales team of your choice. From the sales module, go" +" to your dashboard and click on the **More** button of the desired sales " +"team, then on **Settings**." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:49 +msgid "" +"If you need to create a new sales team first, refer to the page " +":doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:51 +msgid "" +"Then, under \"Team Members\", click on **Add** and select the name of your " +"salesman from the list. The salesperson is now successfully added to your " +"sales team." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:60 +msgid "" +"You can also add a new salesperson on the fly from your sales team even " +"before he is registered as an Odoo user. From the above screenshot, click on" +" \"Create\" to add your salesperson and enter his name and email address. " +"After saving, the salesperson will receive an invite containing a link to " +"set his password. You will then be able to define his accesses rights under " +"the :menuselection:`Settings --> Users` menu." +msgstr "" + +#: ../../crm/salesteam/manage/create_salesperson.rst:69 +msgid ":doc:`../setup/create_team`" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:5 +msgid "" +"Challenging your employees to reach specific targets with goals and rewards " +"is an excellent way to reinforce good habits and improve your salespeople " +"productivity. The **Gamification** app of Odoo gives you simple and creative" +" ways to motivate and evaluate your employees with real-time recognition and" +" badges inspired by game mechanics." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:14 +msgid "" +"From the **Apps** menu, search and install the **Gamification** module. You " +"can also install the **CRM gamification** app, which will add some useful " +"data (goals and challenges) that can be used related to the usage of the " +"**CRM/Sale** modules." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:23 +msgid "Create a challenge" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:25 +msgid "" +"You will now be able to create your first challenge from the menu " +":menuselection:`Settings --> Gamification Tools --> Challenges`." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:29 +msgid "" +"As the gamification tool is a one-time technical setup, you will need to " +"activate the technical features in order to access the configuration. In " +"order to do so, click on the interrogation mark available from any app " +"(upper-right) and click on **About** and then **Activate the developer " +"mode**." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:38 +msgid "" +"A challenge is a mission that you will send to your salespeople. It can " +"include one or several goals and is set up for a specific period of time. " +"Configure your challenge as follows:" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:42 +msgid "Assign the salespeople to be challenged" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:44 +msgid "Assign a responsible" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:46 +msgid "Set up the periodicity along with the start and the end date" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:48 +msgid "Select your goals" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:50 +msgid "Set up your rewards (badges)" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:53 +msgid "" +"Badges are granted when a challenge is finished. This is either at the end " +"of a running period (eg: end of the month for a monthly challenge), at the " +"end date of a challenge (if no periodicity is set) or when the challenge is " +"manually closed." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:58 +msgid "" +"For example, on the screenshot below, I have challenged 2 employees with a " +"**Monthly Sales Target**. The challenge will be based on 2 goals: the total " +"amount invoiced and the number of new leads generated. At the end of the " +"month, the winner will be granted with a badge." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:67 +msgid "Set up goals" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:69 +msgid "" +"The users can be evaluated using goals and numerical objectives to reach. " +"**Goals** are assigned through **challenges** to evaluate (see here above) " +"and compare members of a team with each others and through time." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:74 +msgid "" +"You can create a new goal on the fly from a **Challenge**, by clicking on " +"**Add new item** under **Goals**. You can select any business object as a " +"goal, according to your company's needs, such as :" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:78 +msgid "number of new leads," +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:80 +msgid "time to qualify a lead or" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:82 +msgid "" +"total amount invoiced in a specific week, month or any other time frame " +"based on your management preferences." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:89 +msgid "" +"Goals may include your database setup as well (e.g. set your company data " +"and a timezone, create new users, etc.)." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:93 +msgid "Set up rewards" +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:95 +msgid "" +"For non-numerical achievements, **badges** can be granted to users. From a " +"simple *thank you* to an exceptional achievement, a badge is an easy way to " +"exprimate gratitude to a user for their good work." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:99 +msgid "" +"You can easily create a grant badges to your employees based on their " +"performance under :menuselection:`Gamification Tools --> Badges`." +msgstr "" + +#: ../../crm/salesteam/manage/reward.rst:106 +msgid ":doc:`../../reporting/analysis`" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:3 +msgid "How to create a new team?" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:5 +msgid "" +"In the Sales module, your sales teams are accessible from the **Dashboard** " +"menu. If you start from a new instance, you will find a sales team installed" +" by default : Direct sales. You can either start using that default sales " +"team and edit it (refer to the section *Create and Organize your stages* " +"from the page :doc:`organize_pipeline`) or create a new one from scratch." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:12 +msgid "" +"To create a new team, go to :menuselection:`Configuration --> Sales Teams` " +"and click on **Create**." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:18 +msgid "Fill in the fields :" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:20 +msgid "Enter the name of your team" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:22 +msgid "Select your team leader" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:24 +msgid "Select your team members" +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:26 +msgid "" +"Don't forget to tick the \"Opportunities\" box if you want to manage " +"opportunities from it and to click on SAVE when you're done. Your can now " +"access your new team from your Dashboard." +msgstr "" + +#: ../../crm/salesteam/setup/create_team.rst:35 +msgid "" +"If you started to work on an empty database and didn't create new users, " +"refer to the page :doc:`../manage/create_salesperson`." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:3 +msgid "Set up and organize your sales pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:5 +msgid "" +"A well structured sales pipeline is crucial in order to keep control of your" +" sales process and to have a 360-degrees view of your leads, opportunities " +"and customers." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:9 +msgid "" +"The sales pipeline is a visual representation of your sales process, from " +"the first contact to the final sale. It refers to the process by which you " +"generate, qualify and close leads through your sales cycle. In Odoo CRM, " +"leads are brought in at the left end of the sales pipeline in the Kanban " +"view and then moved along to the right from one stage to another." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:16 +msgid "" +"Each stage refers to a specific step in the sale cycle and specifically the " +"sale-readiness of your potential customer. The number of stages in the sales" +" funnel varies from one company to another. An example of a sales funnel " +"will contain the following stages: *Territory, Qualified, Qualified Sponsor," +" Proposition, Negotiation, Won, Lost*." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:26 +msgid "" +"Of course, each organization defines the sales funnel depending on their " +"processes and workflow, so more or fewer stages may exist." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:30 +msgid "Create and organize your stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:33 +msgid "Add/ rearrange stages" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:35 +msgid "" +"From the sales module, go to your dashboard and click on the **PIPELINE** " +"button of the desired sales team. If you don't have any sales team yet, you " +"need to create one first." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:46 +msgid "" +"From the Kanban view of your pipeline, you can add stages by clicking on " +"**Add new column.** When a column is created, Odoo will then automatically " +"propose you to add another column in order to complete your process. If you " +"want to rearrange the order of your stages, you can easily do so by dragging" +" and dropping the column you want to move to the desired location." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:58 +msgid "" +"You can add as many stages as you wish, even if we advise you not having " +"more than 6 in order to keep a clear pipeline" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:64 +msgid "" +"Some companies use a pre qualification step to manage their leads before to " +"convert them into opportunities. To activate the lead stage, go to " +":menuselection:`Configuration --> Settings` and select the radio button as " +"shown below. It will create a new submenu **Leads** under **Sales** that " +"gives you access to a listview of all your leads." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:74 +msgid "Set up stage probabilities" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:77 +msgid "What is a stage probability?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:79 +msgid "" +"To better understand what are the chances of closing a deal for a given " +"opportunity in your pipe, you have to set up a probability percentage for " +"each of your stages. That percentage refers to the success rate of closing " +"the deal." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:84 +msgid "" +"Setting up stage probabilities is essential if you want to estimate the " +"expected revenues of your sales cycle" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:88 +msgid "" +"For example, if your sales cycle contains the stages *Territory, Qualified, " +"Qualified Sponsor, Proposition, Negotiation, Won and Lost,* then your " +"workflow could look like this :" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:92 +msgid "" +"**Territory** : opportunity just received from Leads Management or created " +"from a cold call campaign. Customer's Interest is not yet confirmed." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:96 +msgid "*Success rate : 5%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:98 +msgid "" +"**Qualified** : prospect's business and workflow are understood, pains are " +"identified and confirmed, budget and timing are known" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:101 +msgid "*Success rate : 15%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:103 +msgid "" +"**Qualified sponsor**: direct contact with decision maker has been done" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:106 +msgid "*Success rate : 25%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:108 +msgid "**Proposition** : the prospect received a quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:110 +msgid "*Success rate : 50%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:112 +msgid "**Negotiation**: the prospect negotiates his quotation" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:114 +msgid "*Success rate : 75%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:116 +msgid "" +"**Won** : the prospect confirmed his quotation and received a sales order. " +"He is now a customer" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:119 +msgid "*Success rate : 100%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:121 +msgid "**Lost** : the prospect is no longer interested" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:123 +msgid "*Success rate : 0%*" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:127 +msgid "" +"Within your pipeline, each stage should correspond to a defined goal with a " +"corresponding probability. Every time you move your opportunity to the next " +"stage, your probability of closing the sale will automatically adapt." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:131 +msgid "" +"You should consider using probability value as **100** when the deal is " +"closed-won and **0** for deal closed-lost." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:135 +msgid "How to set up stage probabilities?" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:137 +msgid "" +"To edit a stage, click on the **Settings** icon at the right of the desired " +"stage then on EDIT" +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:143 +msgid "" +"Select the Change probability automatically checkbox to let Odoo adapt the " +"probability of the opportunity to the probability defined in the stage. For " +"example, if you set a probability of 0% (Lost) or 100% (Won), Odoo will " +"assign the corresponding stage when the opportunity is marked as Lost or " +"Won." +msgstr "" + +#: ../../crm/salesteam/setup/organize_pipeline.rst:151 +msgid "" +"Under the requirements field you can enter the internal requirements for " +"this stage. It will appear as a tooltip when you place your mouse over the " +"name of a stage." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/db_management.po b/locale/tr/LC_MESSAGES/db_management.po new file mode 100644 index 000000000..6133aaa34 --- /dev/null +++ b/locale/tr/LC_MESSAGES/db_management.po @@ -0,0 +1,521 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../db_management/db_online.rst:8 +msgid "Online Database management" +msgstr "" + +#: ../../db_management/db_online.rst:13 +msgid "Duplicating a database" +msgstr "" + +#: ../../db_management/db_online.rst:15 +msgid "" +"Database duplication, renaming, custom DNS, etc. is not available to free " +"customers of our Online platform." +msgstr "" + +#: ../../db_management/db_online.rst:18 +msgid "" +"Access the `database management page <https://www.odoo.com/my/databases>`__ " +"(you will have to sign in). Next, make sure you are connected as the " +"administrator of the database you want to duplicate. After that, click on " +"the **Manage Your Databases** button." +msgstr "" + +#: ../../db_management/db_online.rst:26 +msgid "" +"In the line of the database you want to duplicate, you will have a few " +"buttons. To duplicate your database, just click **Duplicate**. You will have" +" to give a name to your duplicate, then click **Duplicate Database**." +msgstr "" + +#: ../../db_management/db_online.rst:36 +msgid "A duplicated database has the same behaviour as a real one:" +msgstr "" + +#: ../../db_management/db_online.rst:38 +msgid "Emails are sent" +msgstr "" + +#: ../../db_management/db_online.rst:40 +msgid "Payments are processed (in the e-commerce, for example)" +msgstr "" + +#: ../../db_management/db_online.rst:42 +msgid "Delivery orders (shipping providers) are sent" +msgstr "" + +#: ../../db_management/db_online.rst:44 +msgid "Etc." +msgstr "" + +#: ../../db_management/db_online.rst:46 +msgid "" +"It is **strongly** advised to test behaviour using sample customers/products" +" (with a `disposable e-mail <http://www.mailinator.com>`__ address, for " +"example)" +msgstr "" + +#: ../../db_management/db_online.rst:50 +msgid "" +"After a few seconds, you will be logged in your duplicated database. Notice " +"that the url uses the name you chose for your duplicated database." +msgstr "" + +#: ../../db_management/db_online.rst:54 +msgid "Duplicate databases expire automatically after 15 days." +msgstr "" + +#: ../../db_management/db_premise.rst:7 +msgid "On-premise Database management" +msgstr "" + +#: ../../db_management/db_premise.rst:10 +msgid "Register a database" +msgstr "" + +#: ../../db_management/db_premise.rst:12 +msgid "" +"To register your database, you just need to enter your Subscription Code in " +"the banner in the App Switcher. Make sure you do not add extra spaces before" +" or after your subscription code. If the registration is successful, it will" +" turn green and will provide you with the Expiration Date of your freshly-" +"registered database. You can check this Epiration Date in the About menu " +"(Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../db_management/db_premise.rst:20 +msgid "Registration Error Message" +msgstr "" + +#: ../../db_management/db_premise.rst:22 +msgid "" +"If you are unable to register your database, you will likely encounter this " +"message:" +msgstr "" + +#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97 +#: ../../db_management/db_premise.rst:130 +msgid "Solutions" +msgstr "" + +#: ../../db_management/db_premise.rst:33 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../db_management/db_premise.rst:35 +msgid "" +"Check if your subscription details get the tag \"In Progress\" on your `Odoo" +" Account <https://accounts.odoo.com/my/contract>`__ or with your Account " +"Manager" +msgstr "" + +#: ../../db_management/db_premise.rst:39 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../db_management/db_premise.rst:41 +msgid "" +"You can link only one database per subscription. (Need a test or a " +"development database? `Find a partner <https://www.odoo.com/partners>`__)" +msgstr "" + +#: ../../db_management/db_premise.rst:45 +msgid "" +"You can unlink the old database yourself on your `Odoo Contract " +"<https://accounts.odoo.com/my/contract>`__ with the button \"Unlink " +"database\"" +msgstr "" + +#: ../../db_management/db_premise.rst:52 +msgid "" +"A confirmation message will appear; make sure this is the correct database " +"as it will be deactivated shortly:" +msgstr "" + +#: ../../db_management/db_premise.rst:59 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../db_management/db_premise.rst:61 +#: ../../db_management/db_premise.rst:190 +msgid "" +"From July 2016 onward, Odoo 9 now automatically change the uuid of a " +"duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../db_management/db_premise.rst:64 +msgid "" +"If it's not the case, you may have multiple databases sharing the same UUID." +" Please check on your `Odoo Contract " +"<https://accounts.odoo.com/my/contract>`__, a short message will appear " +"specifying which database is problematic:" +msgstr "" + +#: ../../db_management/db_premise.rst:73 +msgid "" +"In this case, you need to change the UUID on your test databases to solve " +"this issue. You will find more information about this in :ref:`this section " +"<duplicate_premise>`." +msgstr "" + +#: ../../db_management/db_premise.rst:76 +msgid "" +"For your information, we identify database with UUID. Therefore, each " +"database should have a distinct UUID to ensure that registration and " +"invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../db_management/db_premise.rst:82 +msgid "Too much users error message" +msgstr "" + +#: ../../db_management/db_premise.rst:84 +msgid "" +"If you have more users in your local database than provisionned in your Odoo" +" Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../db_management/db_premise.rst:93 +msgid "" +"When the message appears you have 30 days before the expiration. The " +"countdown is updated everyday." +msgstr "" + +#: ../../db_management/db_premise.rst:99 +msgid "" +"**Add more users** on your subscription: follow the link and Validate the " +"upsell quotation and pay for the extra users." +msgstr "" + +#: ../../db_management/db_premise.rst:102 +msgid "or" +msgstr "" + +#: ../../db_management/db_premise.rst:104 +msgid "" +"**Deactivate users** as explained in this `Documentation " +"<https://www.odoo.com " +"/documentation/user/10.0/db_management/documentation.html#deactivating-" +"users>`__ and **Reject** the upsell quotation." +msgstr "" + +#: ../../db_management/db_premise.rst:109 +msgid "" +"Once your database has the correct number of users, the expiration message " +"will disappear automatically after a few days, when the next verification " +"occurs. We understand that it can be a bit frightening to see the countdown," +" so you can :ref:`force an Update Notification <force_ping>` to make the " +"message disappear right away." +msgstr "" + +#: ../../db_management/db_premise.rst:116 +msgid "Database expired error message" +msgstr "" + +#: ../../db_management/db_premise.rst:118 +msgid "" +"If your database reaches its expiration date before your renew your " +"subscription, you will encounter this message:" +msgstr "" + +#: ../../db_management/db_premise.rst:126 +msgid "" +"This **blocking** message appears after a non-blocking message that lasts 30" +" days. If you fail to take action before the end of the countdown, the " +"database is expired." +msgstr "" + +#: ../../db_management/db_premise.rst:134 +msgid "" +"Renew your subscription: follow the link and renew your subscription - note " +"that" +msgstr "" + +#: ../../db_management/db_premise.rst:133 +msgid "" +"if you wish to pay by Wire Transfer, your subscription will effectively be " +"renewed only when the payment arrives, which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../db_management/db_premise.rst:136 +msgid "Contact our `Support <https://www.odoo.com/help>`__" +msgstr "" + +#: ../../db_management/db_premise.rst:138 +msgid "" +"None of those solutions worked for you? Please contact our `Support " +"<https://www.odoo.com/help>`__" +msgstr "" + +#: ../../db_management/db_premise.rst:145 +msgid "Force an Update Notification" +msgstr "" + +#: ../../db_management/db_premise.rst:147 +msgid "" +"Update Notifications happen once every 7 days and keep your database up-to-" +"date with your Odoo Enterprise subscription. If you modify your subscription" +" (i.e. add more users, renew it for a year, etc.), your local database will " +"only be made aware of the change once every 7 days - this can cause " +"discrepancies between the state of your subscription and some notifications " +"in your App Switcher. When doing such an operation on your subscription, you" +" can force an Update using the following procedure:" +msgstr "" + +#: ../../db_management/db_premise.rst:154 +msgid "Connect to the database with the **Administrator** account" +msgstr "" + +#: ../../db_management/db_premise.rst:155 +msgid "" +"Switch to the Developer mode by using the **About** option in the top-right " +"menu (in V9) / in **Settings** (in V10): click on **Activate the developer" +" mode**" +msgstr "" + +#: ../../db_management/db_premise.rst:158 +msgid "" +"Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > " +"\"Scheduled Actions\"" +msgstr "" + +#: ../../db_management/db_premise.rst:160 +msgid "" +"Find \"Update Notification\" in the list, click on it, and finally click on " +"the button \"**RUN MANUALLY**\"" +msgstr "" + +#: ../../db_management/db_premise.rst:162 +msgid "Refresh the page, the \"Expiration\" notification should be gone" +msgstr "" + +#: ../../db_management/db_premise.rst:165 +msgid "" +"You may have kept the same UUID on different databases and we receive " +"information from those databases too. So please read :ref:`this " +"documentation <duplicate_premise>` to know how to change the UUID. After the" +" change you can force a ping to speed up the verification, your production " +"database will then be correctly identified." +msgstr "" + +#: ../../db_management/db_premise.rst:174 +msgid "Duplicate a database" +msgstr "" + +#: ../../db_management/db_premise.rst:176 +msgid "" +"You can duplicate your database by accessing the database manager on your " +"server (<odoo-server>/web/database/manager). In this page, you can easily " +"duplicate your database (among other things)." +msgstr "" + +#: ../../db_management/db_premise.rst:184 +msgid "" +"When you duplicate a local database, it is **strongly** advised to change " +"the duplicated database's uuid (Unniversally Unique Identifier), since this " +"uuid is how your database identifies itself with our servers. Having two " +"databases with the same uuid could result in invoicing problems or " +"registration problems down the line." +msgstr "" + +#: ../../db_management/db_premise.rst:193 +msgid "" +"The database uuid is currently accessible from the menu **Settings > " +"Technical > System Parameters**, we advise you to use a `uuid generator " +"<https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to" +" generate a new uuid. You can then simply replace it like any other record " +"by clicking on it and using the edit button." +msgstr "" + +#: ../../db_management/documentation.rst:7 +msgid "Users and Features" +msgstr "" + +#: ../../db_management/documentation.rst:9 +msgid "" +"As the administrator of your database, you are responsible for its usage. " +"This includes the Apps you install as well as the number of users currently " +"in use." +msgstr "" + +#: ../../db_management/documentation.rst:13 +msgid "" +"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) " +"but it is *not* a smartphone. You should apply caution when adding/removing " +"features (especially Apps) on your database since this may impact your " +"subscription amount significantly (or switch you from a free account to a " +"paying one on our online platform)." +msgstr "" + +#: ../../db_management/documentation.rst:19 +msgid "" +"This page contains some information as to how you can manage your Odoo " +"instances. Before carrying any of these procedures, we **strongly** advise " +"to test them on a duplicate of your database first. That way, if something " +"goes wrong, your day-to-day business is not impacted." +msgstr "" + +#: ../../db_management/documentation.rst:24 +msgid "" +"You can find guides on how to duplicate your databases both for :ref:`online" +" <duplicate_online>` and :ref:`on premise <duplicate_premise>` " +"installations." +msgstr "" + +#: ../../db_management/documentation.rst:28 +msgid "" +"If you have questions about the content of this page or if you encounter an " +"issue while carrying out these procedures, please contact us through our " +"`support form <https://www.odoo.com/help>`__." +msgstr "" + +#: ../../db_management/documentation.rst:34 +msgid "Deactivating Users" +msgstr "" + +#: ../../db_management/documentation.rst:36 +msgid "" +"Make sure you have sufficient **administrative rights** if you want to " +"change the status of any of your users." +msgstr "" + +#: ../../db_management/documentation.rst:39 +msgid "" +"In your Odoo instance, click on **Settings**. You will have a section " +"showing you the active users on your database. Click on **Manage access " +"rights.**" +msgstr "" + +#: ../../db_management/documentation.rst:44 +#: ../../db_management/documentation.rst:82 +msgid "|settings|" +msgstr "" + +#: ../../db_management/documentation.rst:44 +msgid "|browse_users|" +msgstr "" + +#: ../../db_management/documentation.rst:47 +msgid "You'll then see the list of your users." +msgstr "" + +#: ../../db_management/documentation.rst:52 +msgid "" +"The pre-selected filter *Internal Users* shows your paying users (different " +"from the *Portal Users* which are free). If you remove this filter, you'll " +"get all your users (the ones you pay for and the portal ones)" +msgstr "" + +#: ../../db_management/documentation.rst:57 +msgid "" +"In your list of users, click on the user you want to deactivate. As soon as " +"you are on the userform, go with your mouse cursor on the status **Active** " +"(top right). Click on Active and you will notice that the status will change" +" to **Inactive** immediately." +msgstr "" + +#: ../../db_management/documentation.rst:66 +msgid "The user is now deactivated." +msgstr "" + +#: ../../db_management/documentation.rst:68 +msgid "**Never** deactivate the main user (*admin*)" +msgstr "" + +#: ../../db_management/documentation.rst:71 +msgid "Uninstalling Apps" +msgstr "" + +#: ../../db_management/documentation.rst:73 +msgid "" +"Make sure you first test what you are about to do on a :ref:`duplicate " +"<duplicate>` of your database before making any changes (*especially* " +"installing/uninstalling apps)." +msgstr "" + +#: ../../db_management/documentation.rst:77 +msgid "" +"In your Odoo instance click on **Settings**; in this app, you will be able " +"to see how many applications you have installed. Click on **Browse Apps** to" +" access the list of your installed applications." +msgstr "" + +#: ../../db_management/documentation.rst:82 +msgid "|browse_apps|" +msgstr "" + +#: ../../db_management/documentation.rst:85 +msgid "" +"In your applications' dashboard, you will see all the icons of your " +"applications. Click on the application you want to uninstall. Then, on the " +"form of the application, click on **Uninstall**." +msgstr "" + +#: ../../db_management/documentation.rst:92 +msgid "" +"Some applications have dependencies, like Invoicing, eCommerce, etc. " +"Therefore, the system will give you a warning message to advise you of what " +"is about to be removed. If you uninstall your application, all its " +"dependencies will be uninstalled as well (and the data in them will " +"permanently disappear). If you are sure you still want to uninstall it, then" +" click **Confirm**." +msgstr "" + +#: ../../db_management/documentation.rst:99 +msgid "" +"Last, after having checked the warning message (if any), click **Confirm**." +msgstr "" + +#: ../../db_management/documentation.rst:104 +msgid "You have finished uninstalling your application." +msgstr "" + +#: ../../db_management/documentation.rst:107 +msgid "Good to know" +msgstr "" + +#: ../../db_management/documentation.rst:109 +msgid "" +"**Uninstalling apps, managing users, etc. is up to you**: no one else can " +"know if your business flow is broken better than you. If we were to " +"uninstall applications for you, we would never be able to tell if relevant " +"data had been removed or if one of your business flow was broken because we " +"*do not know how you work* and therefore cannot validate these kinds of " +"operations." +msgstr "" + +#: ../../db_management/documentation.rst:115 +msgid "" +"**Odoo Apps have dependencies**: this means that you may need to install " +"modules that you do not actively use to access some features of Odoo you " +"might need. For example, the Website Builder app is needed to be able to " +"show your customer their Quotes in a web page. Even though you might not " +"need or use the Website itself, it is needed for the Online Quotes feature " +"to work properly." +msgstr "" + +#: ../../db_management/documentation.rst:122 +msgid "" +"**Always test app installation/removal on a duplicate** (or on a free trial " +"database): that way you can know what other apps may be required, etc. This " +"will avoid surprises when uninstalling or when receiving your invoices." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/discuss.po b/locale/tr/LC_MESSAGES/discuss.po new file mode 100644 index 000000000..7a3811ed4 --- /dev/null +++ b/locale/tr/LC_MESSAGES/discuss.po @@ -0,0 +1,563 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Güven YILMAZ <guvenyilmaz@outlook.com.tr>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../discuss.rst:5 +msgid "Discuss" +msgstr "Mesajlaşma" + +#: ../../discuss/email_servers.rst:3 +msgid "How to use my own email servers to send and receive email in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:6 +msgid "When is it needed" +msgstr "" + +#: ../../discuss/email_servers.rst:7 +msgid "" +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." +msgstr "" + +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" +msgstr "" + +#: ../../discuss/email_servers.rst:15 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." +msgstr "" + +#: ../../discuss/email_servers.rst:21 +msgid "" +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:26 +msgid "Set an outgoing email server for outbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:27 +msgid "" +"You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " +"etc.) as well as your admin credentials. Once all the information has been " +"filled out, click on *Test Connection*." +msgstr "" + +#: ../../discuss/email_servers.rst:35 +msgid "Set an incoming email server for inbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:36 +msgid "" +"Fill out the form according to your email provider’s settings. Leave the " +"*Actions to Perform on Incoming Mails* blank. Once all the information has " +"been filled out, click on *TEST & CONFIRM*." +msgstr "" + +#: ../../discuss/email_servers.rst:43 +msgid "" +"By default inbound messages are fetched every 5 minutes. You can change this" +" value in developer mode. Go to :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." +msgstr "" + +#: ../../discuss/email_servers.rst:49 +msgid "Set the domain name" +msgstr "" + +#: ../../discuss/email_servers.rst:50 +msgid "" +"Enter the domain name of your email servers (e.g. mycompany.com) in General " +"Settings." +msgstr "" + +#: ../../discuss/email_servers.rst:57 +msgid "Create a catchall address" +msgstr "" + +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 +msgid "" +"Create a catchall address in your email server settings. We advise you to " +"use \"catchall@\" so that everything works out straight away. If you want to" +" use another alias, you have extra steps in Odoo:" +msgstr "" + +#: ../../discuss/email_servers.rst:67 +msgid "Activate the developer mode from your Settings Dashboard." +msgstr "" + +#: ../../discuss/email_servers.rst:72 +msgid "" +"Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` and enter your custom catchall alias in " +"*mail.catchall.alias*." +msgstr "" + +#: ../../discuss/email_servers.rst:79 +msgid "You can edit the email alias used for bounced messages the same way." +msgstr "" + +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" +msgstr "" + +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 +msgid "" +"Odoo Discuss is a perfect tool to send and read messages related to business" +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +"both systems without mingling them: What is related to Odoo business objects" +" or applications goes into Odoo; What is not can be managed into your " +"external email box." +msgstr "" + +#: ../../discuss/email_servers.rst:150 +msgid "" +"To do so, create specific email aliases to use in Odoo (to generate leads or" +" opportunities, helpdesk tickets, etc.). If you take an email alias already " +"used for messaging outside of Odoo, incoming messages will land into both " +"systems. This will negatively impact your productivity." +msgstr "" + +#: ../../discuss/mail_twitter.rst:3 +msgid "How to follow Twitter feed from Odoo" +msgstr "" + +#: ../../discuss/mail_twitter.rst:8 +msgid "" +"You can follow specific hashtags on Twitter and see the tweets within the " +"Odoo Discuss channels of your choice. The tweets are retrieved periodically " +"from Twitter. An authenticated user can retweet the messages." +msgstr "" + +#: ../../discuss/mail_twitter.rst:13 +msgid "Setting up the App on Twitter's side" +msgstr "" + +#: ../../discuss/mail_twitter.rst:15 +msgid "" +"Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks" +" for tweets, and through which a user can retweet. To set up this app, go to" +" http://apps.twitter.com/app/new and put in the values:" +msgstr "" + +#: ../../discuss/mail_twitter.rst:19 +msgid "Name: this is the name of the application on Twitter" +msgstr "" + +#: ../../discuss/mail_twitter.rst:21 +msgid "" +"Website: this is the external url of your Odoo database, with \"/web\" " +"added. For example, if your Odoo instance is hosted at " +"\"http://www.example.com\", you should put \"http://www.example.com/web\" in" +" this field." +msgstr "" + +#: ../../discuss/mail_twitter.rst:25 +msgid "" +"Callback URL: this is the address on which Twitter will respond. Following " +"the previous example you should write " +"\"http://www.example.com/web/twitter/callback\"." +msgstr "" + +#: ../../discuss/mail_twitter.rst:28 +msgid "" +"Do not forget to accept the terms **Developer agreement** of use and click " +"on **Create your Twitter application** at the bottom of the page." +msgstr "" + +#: ../../discuss/mail_twitter.rst:33 +msgid "Getting the API key and secret" +msgstr "" + +#: ../../discuss/mail_twitter.rst:35 +msgid "" +"When on the App dashboard, switch to the **Keys and Access Tokens** tab." +msgstr "" + +#: ../../discuss/mail_twitter.rst:40 +msgid "" +"And copy those values in Odoo in :menuselection:`Settings--> General " +"Settings--> Twitter discuss integration` and click on **Save** to save the " +"settings." +msgstr "" + +#: ../../discuss/mentions.rst:3 +msgid "How to grab attention of other users in my messages" +msgstr "" + +#: ../../discuss/mentions.rst:5 +msgid "" +"You can **mention** a user in a channel or chatter by typing **@user-name**." +" Mentioning a user in the chatter will set them as a follower of the item " +"(if they are not already) and send a message to their inbox. The item " +"containing the mention will also be bolded in the list view. Mentioning a " +"user in a channel will send a message to their inbox. You cannot mention a " +"user in a channel who is not subscribed to the channel. Typing **#channel-" +"name** will provide a link to the mentioned channel in either a chatter or " +"another channel." +msgstr "" + +#: ../../discuss/mentions.rst:15 +msgid "Direct messaging a user" +msgstr "" + +#: ../../discuss/mentions.rst:17 +msgid "" +"**Direct messages** are private messages viewable only by the sender and " +"recipient. You can send direct messages to other users from within the " +"Discuss module by creating a new conversation or selecting an existing one " +"from the sidebar. Direct messages can be sent from anywhere in Odoo using " +"the speech bubble icon in the top bar. The online status of other users is " +"displayed to the left of their name. A **green dot** indicates that a user " +"is Online, an **orange dot** that they are Idle, and a **grey dot** that " +"they are offline." +msgstr "" + +#: ../../discuss/mentions.rst:28 +msgid "Desktop notifications from Discuss" +msgstr "" + +#: ../../discuss/mentions.rst:30 +msgid "" +"You can choose to see **desktop notifications** when you receive a new " +"direct message. The notification shows you the sender and a brief preview of" +" the message contents. These can be configured or disabled by clicking on " +"the gear icon in the corner of the notification.." +msgstr "" + +#: ../../discuss/monitoring.rst:3 +msgid "How to be responsive at work thanks to my Odoo inbox" +msgstr "" + +#: ../../discuss/monitoring.rst:5 +msgid "" +"Use the **Inbox** in Discuss app to monitor updates and progress on " +"everything you do in Odoo. Notifications and messages from everything you " +"follow or in which you are mentioned appear in your inbox." +msgstr "" + +#: ../../discuss/monitoring.rst:13 +msgid "You can keep an eye on your **Inbox** from any screen." +msgstr "" + +#: ../../discuss/monitoring.rst:18 +msgid "" +"Marking an item with a check marks the message as **read** and removes it " +"from your inbox. If you would like to save an item for future reference or " +"action, mark it with a star to add it to the **Starred** box. You can star " +"any message or notification in Discuss or any of the item-specific chatters " +"throughout Odoo to keep tabs on it here." +msgstr "" + +#: ../../discuss/overview.rst:3 +msgid "Why to use Odoo Discuss" +msgstr "" + +#: ../../discuss/overview.rst:5 +msgid "" +"Odoo Discuss is an easy to use messaging app for teams that brings all your " +"organization's communication into one place and seamlessly integrates with " +"the Odoo platform. Discuss lets you send and receive messages from wherever " +"you are in Odoo as well as manage your messages and notifications easily " +"from within the app. Discuss allows you to create **channels** for team " +"chats, conversations about projects, meeting coordination, and more in one " +"simple and searchable interface." +msgstr "" + +#: ../../discuss/team_communication.rst:3 +msgid "How to efficiently communicate in team using channels" +msgstr "" + +#: ../../discuss/team_communication.rst:5 +msgid "" +"You can use **channels** to organize discussions between individual teams, " +"departments, projects, or any other group that requires regular " +"communication. By having conversations that everyone in the channel can see," +" it's easy to keep the whole team in the loop with the latest developments." +msgstr "" + +#: ../../discuss/team_communication.rst:12 +msgid "Creating a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:14 +msgid "" +"In Discuss there are two types of channels - **public** and **private**." +msgstr "" + +#: ../../discuss/team_communication.rst:17 +msgid "" +"A **public channel** can only be created by an administrator with write " +"privileges and can be seen by everyone in the organization. By contrast, a " +"**private channel** can be created by any user and by default is only " +"visible to users who have been invited to this channel." +msgstr "" + +#: ../../discuss/team_communication.rst:24 +msgid "" +"A public channel is best used when many employees need to access information" +" (such as interdepartmental communication or company announcements), whereas" +" a private channel should be used whenever information should be limited to " +"specific users/employees (such as department specific or sensitive " +"information)." +msgstr "" + +#: ../../discuss/team_communication.rst:31 +msgid "Configuring a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:33 +msgid "" +"You can configure a channel's name, description, access rights, automatic " +"subscription, and emailing from :menuselection:`#channel-name --> Settings`." +" Changing channel access rights allows you to control which groups can view " +"each channel. You can make a channel visible by all users, invited users, or" +" users within a selected user group. Note that allowing \"Everyone\" to " +"follow a private channel will let other users view and join it as they would" +" a public channel." +msgstr "" + +#: ../../discuss/team_communication.rst:47 +msgid "How to set up a mailing list" +msgstr "" + +#: ../../discuss/team_communication.rst:49 +msgid "" +"A channel can be configured to behave as a mailing list. From within " +":menuselection:`#channel-name --> Settings`, define the email you would like" +" to use. Users can then post to the channel and choose to receive " +"notifications using the defined email address. An envelope icon will appear " +"next to the channel name in the list to indicate that a channel will send " +"messages by email." +msgstr "" + +#: ../../discuss/team_communication.rst:57 +msgid "Locating a channel" +msgstr "" + +#: ../../discuss/team_communication.rst:59 +msgid "" +"If you do not see a channel on your dashboard, you can search the list of " +"**public channels** to locate the correct channel or create a new channel by" +" clicking the plus icon." +msgstr "" + +#: ../../discuss/team_communication.rst:66 +msgid "" +"You can also click the **CHANNELS** heading to browse a list of all public " +"channels. This allows the user to manually **join** and **leave** public " +"channels from a single screen." +msgstr "" + +#: ../../discuss/team_communication.rst:71 +msgid "" +"It is always wise to search for a channel before creating a new one to " +"ensure that duplicate entries are not created for the same topic." +msgstr "" + +#: ../../discuss/team_communication.rst:76 +msgid "Using filters to navigate within Discuss" +msgstr "" + +#: ../../discuss/team_communication.rst:78 +msgid "" +"The topbar search provides access to the same comprehensive search function " +"present in the rest of Odoo. You can apply multiple **filter criteria** and " +"**save filters** for later use. The search function accepts wildcards by " +"using the underscore character \"\\ **\\_**\\ \" to represent a **single " +"character wildcard.**" +msgstr "" + +#: ../../discuss/tracking.rst:3 +msgid "How to follow a discussion thread and define what I want to hear about" +msgstr "" + +#: ../../discuss/tracking.rst:6 +msgid "How to follow a discussion thread" +msgstr "" + +#: ../../discuss/tracking.rst:7 +msgid "" +"You can keep track of virtually any business object in Odoo (an opportunity," +" a quotation, a task, etc.), by **following** it." +msgstr "" + +#: ../../discuss/tracking.rst:14 +msgid "How to choose the events to follow" +msgstr "" + +#: ../../discuss/tracking.rst:15 +msgid "" +"You can choose which types of events you want to be notified about. The " +"example below shows the options available when following a **task** in the " +"**Project** app." +msgstr "" + +#: ../../discuss/tracking.rst:23 +msgid "How to add other followers" +msgstr "" + +#: ../../discuss/tracking.rst:24 +msgid "" +"You can invite other users and add channels as followers. Adding a channel " +"as a follower will send messages posted in the chatter to the channel with a" +" link back to the original document." +msgstr "" + +#: ../../discuss/tracking.rst:34 +msgid "How to be a default follower" +msgstr "" + +#: ../../discuss/tracking.rst:35 +msgid "" +"You are automatically set as a default follower of any item you create. In " +"some applications like CRM and Project, you can be a default follower of any" +" new record created to get notified of specific events (e.g. a new task " +"created, an opportunity won)." +msgstr "" + +#: ../../discuss/tracking.rst:40 +msgid "" +"To do so, start following the parent business object (e.g. the sales channel" +" in CRM, the project in Project). Then, choose the events you want to hear " +"about." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/ecommerce.po b/locale/tr/LC_MESSAGES/ecommerce.po new file mode 100644 index 000000000..0d6ca9578 --- /dev/null +++ b/locale/tr/LC_MESSAGES/ecommerce.po @@ -0,0 +1,1240 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../ecommerce.rst:5 +msgid "eCommerce" +msgstr "" + +#: ../../ecommerce/getting_started.rst:3 +msgid "Get started" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:3 +msgid "How to customize my catalog page" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:6 +msgid "Product Catalog" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:8 +msgid "" +"All your published items show up in your catalog page (or *Shop* page)." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:13 +msgid "" +"Most options are available in the *Customize* menu: display attributes, " +"website categories, etc." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:20 +msgid "Highlight a product" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:22 +msgid "" +"Boost the visibility of your star/promoted products: push them to top, make " +"them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop" +" page, switch to Edit mode and click any item to start customizing the grid." +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:26 +msgid "" +"See how to do it: " +"https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:29 +msgid "Quick add to cart" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:31 +msgid "" +"If your customers buy a lot of items at once, make their process shorter by " +"enabling purchases from the catalog page. To do so, add product description " +"and add to cart button. Turn on the following options in *Customize* menu: " +"Product Description, Add to Cart, List View (to display product description " +"better)." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:3 +msgid "How to build a product page" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:5 +msgid "On the website click *New Page* in the top-right corner." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:7 +msgid "Then click *New Product* and follow the blinking tips." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:12 +msgid "Here are the main elements of the Product page:" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:17 +msgid "Many elements can be made visible from the *Customize* menu." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:22 +msgid "See how to configure your products from links here below." +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:26 +msgid ":doc:`../managing_products/variants`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:27 +msgid ":doc:`../../sales/products_prices/taxes`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:28 +msgid ":doc:`../managing_products/stock`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:29 +msgid ":doc:`../maximizing_revenue/cross_selling`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:30 +msgid ":doc:`../maximizing_revenue/reviews`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:31 +msgid ":doc:`../maximizing_revenue/pricing`" +msgstr "" + +#: ../../ecommerce/getting_started/product_page.rst:32 +msgid ":doc:`../../website/optimize/seo`" +msgstr "" + +#: ../../ecommerce/managing_products.rst:3 +msgid "Manage my products" +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:3 +msgid "How to display several images per product" +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:5 +msgid "" +"By default your product web page displays the main image of your product " +"only. If you like to show your products under several angles, you can turn " +"the image into a carrousel." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:11 +msgid "" +"Check *Several images per product* in :menuselection:`Website Admin --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:13 +msgid "" +"Open a product detail form and upload images from *Images* tab. Hit *Create*" +" in Edit mode to get the upload wizard." +msgstr "" + +#: ../../ecommerce/managing_products/multi_images.rst:19 +msgid "Such extra image are common to all the product variants (if any)." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:3 +msgid "How to show product availability" +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:5 +msgid "" +"The availability of your products can be shown on the website to reassure " +"your customers." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:10 +msgid "" +"To display this, open the *Sales* tab in the product detail form and select " +"an option in *Availability*." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:16 +msgid "" +"A custom warning message can be anything related to a stock out, delivery " +"delay, etc." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:22 +msgid "This tool does not require the Inventory app to be installed." +msgstr "" + +#: ../../ecommerce/managing_products/stock.rst:25 +msgid "" +"If one item is no longer sellable, unpublish it from your website. If it " +"comes to one particular product variant, deactivate the variant in the " +"backend (see :doc:`../maximizing_revenue/pricing`)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:3 +msgid "How to manage product variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:5 +msgid "" +"Product variants are used to offer variations of the same product to your " +"customers on the products page. For example, the customer chooses a T-shirt " +"and then selects its size and color." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:13 +msgid "How to create attributes & variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:15 +msgid "" +"Turn on *Products can have several attributes, defining variants (Example: " +"size, color,...)* in :menuselection:`Sales --> Settings`." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:18 +msgid "Select a product from the Products list, go to the *Variants* tab." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:20 +msgid "" +"Add as many attributes as you need from 3 different types: radio buttons, " +"drop-down menu or color buttons. You get several variants as soon as there " +"are 2 values for 1 attribute." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:28 +msgid "How to edit variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:30 +msgid "See all the variants from the product template detail form." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:38 +msgid "You can edit following data:" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:40 +msgid "Picture (will update in real time on the website)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:41 +msgid "Barcode," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:42 +msgid "Internal Reference (SKU #)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:43 +msgid "Volume," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:44 +msgid "Weight," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:45 +msgid "Active (available in quotes & website)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:48 +msgid "" +"Both the Barcode and the Internal Reference are variant-specific. You need " +"to populate them once the variants generated." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:52 +msgid "" +"See and edit all the variants from :menuselection:`Sales --> Sales --> " +"Product Variants` as well. This might be quicker if you manage lots of " +"variants." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:56 +msgid "How to set specific prices per variant" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:58 +msgid "" +"You can also set a specific public price per variant by clicking *Variant " +"Prices* in the product detail form (action in top-left corner)." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:64 +msgid "" +"The Price Extra is added to the product price whenever the corresponding " +"attribute value is selected." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:74 +msgid "" +"Pricelist formulas let you set advanced price computation methods for " +"product variants. See :doc:`../maximizing_revenue/pricing`." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:78 +msgid "How to disable/archive variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:80 +msgid "" +"You can disable/archive specific variants so that they are no longer " +"available in quotes & website (not existing in your stock, deprecated, " +"etc.). Simply uncheck *Active* in their detail form." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:86 +msgid "" +"To retrieve such archived items, hit *Archived* on searching the variants " +"list. You can reactivate them the same way." +msgstr "" + +#: ../../ecommerce/maximizing_revenue.rst:3 +msgid "Maximize my revenue" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:3 +msgid "How to sell accessories and optional products (cross-selling)" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:5 +msgid "" +"You sell computers. Why not stimulating your customers to buy a top-notch " +"screen or an extra-warranty? That's the goal of cross-selling " +"functionalities:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:8 +msgid "Accessory products on checkout page," +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:9 +msgid "" +"Optional products on a new *Add to Cart* screen (not installed by default)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:12 +msgid "Accessory products when checking out" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:14 +msgid "" +"Accessories (e.g. for computers: mouse, keyboard) show up when the customer " +"reviews the cart before paying." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:20 +msgid "Select accessories in the *Sales* tab of the product detail page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:26 +msgid "" +"There is an algorithm to figure out the best accessories to display in case " +"several items are added to cart. If any item is the accessory of several " +"products added to cart, it is most likely that it will be atop the list of " +"suggested accessories." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:31 +msgid "Optional products when adding to cart" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:33 +msgid "" +"Optional products are directly related to the item added to cart (e.g. for " +"computers: warranty, OS software, extra components). Whenever the main " +"product is added to cart, such a new screen pops up as an extra step." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:40 +msgid "To publish optional products:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:42 +msgid "" +"Install *eCommerce Optional Products* addon in *Apps* menu. Remove the " +"default filter to search on addons as well, otherwise only main apps show " +"up." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:48 +msgid "Select optional items from the *Sales* tab of the product detail form." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/cross_selling.rst:54 +msgid "" +"The quantity of optional items added to cart is the same than the main item." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:3 +msgid "How to adapt the prices to my website visitors" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:5 +msgid "This section sheds some light on pricing features of eCommerce app:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:7 +msgid "force a price by geo-localization," +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:9 +msgid "let the customer choose the currency." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:11 +msgid "" +"As a pre-requisite, check out how to managing produt pricing: " +":doc:`../../sales/products_prices/prices/pricing`)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:15 +msgid "Geo-IP to automatically apply the right price" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:17 +msgid "" +"Assign country groups to your pricelists. That way, your visitors not yet " +"logged in will get their own currency when landing on your website." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:20 +msgid "Once logged in, they get the pricelist matching their country." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:23 +msgid "Currency selector" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:25 +msgid "" +"In case you sell in several currencies, you can let your customers choose " +"their own currency. Check *Selectable* to add the pricelist to the website " +"drop-down menu." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:34 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:35 +msgid ":doc:`../../sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/pricing.rst:36 +msgid ":doc:`promo_code`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:3 +msgid "How to create & share promotional codes" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:5 +msgid "" +"Want to boost your sales for Xmas? Share promocodes through your marketing " +"campaigns and apply any kind of discounts." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:9 +#: ../../ecommerce/maximizing_revenue/reviews.rst:13 +msgid "Setup" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:11 +msgid "" +"Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based" +" on formula* for *Sale Price*." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:14 +msgid "" +"Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a" +" new pricelist with the discount rule (see :doc:`pricing`). Then enter a " +"code." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:21 +msgid "" +"Make the promocode field available on your *Shopping Cart* page (option in " +"*Customize* menu). Add a product to cart to reach it." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:27 +msgid "" +"Once turned on you see a new section on the right side. On clicking *Apply* " +"prices get automatically updated in the cart." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:33 +msgid "" +"The promocode used by the customer is stored in the system so you can " +"analyze the performance of your marketing campaigns." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:39 +msgid "Show sales per pricelists..." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/promo_code.rst:43 +msgid ":doc:`pricing`" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:3 +msgid "How to enable comments & rating" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:5 +msgid "" +"Publishing and monitoring customer experience will help you gain the trust " +"of new customers and better engage with your community. In 2 clicks, allow " +"your customer to share their feedback!" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:15 +msgid "" +"Activate comments & rating from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:21 +msgid "" +"Visitors must log in to share their comments. Make sure they are able to do " +"so (see Portal documentation)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:25 +msgid "Review the posts in real time" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:27 +msgid "" +"Whenever a post is published, the product manager and all the product " +"followers get notified in their Inbox (*Discuss* menu)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:34 +msgid "" +"By default the user who created the product is automatically set as " +"follower." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:36 +msgid "" +"Click the product name to open the detail form and review the comment (in " +"the product discussion thread)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:43 +msgid "Moderate & unpublish" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:45 +msgid "" +"You can easily moderate by using the chatter, either in the product detail " +"form or on the web page." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:48 +msgid "" +"To unpublish the post, open the product web page and click the *Published* " +"button to turn it red (*Unpublished*)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:56 +msgid "..tip::" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/reviews.rst:55 +msgid "" +"You can access the web page from the detail form by clicking the *Published*" +" smart button (and vice versa)." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:3 +msgid "How to sell pricier product alternatives (upselling)" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:5 +msgid "" +"In order to maximize your revenue, suggesting pricier alternative products " +"is strongly advised for basic items. That way, your customer will spend more" +" time browsing your catalog." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:12 +msgid "To do so:" +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:14 +msgid "" +"Select such *Alternative Products* in the *Sales* tab of the product detail " +"form. 3 alternatives are fine! Don't publish too many otherwise your " +"customers will be confused." +msgstr "" + +#: ../../ecommerce/maximizing_revenue/upselling.rst:20 +msgid "" +"Turn on *Alternative Products* from the *Customize* menu of the product web " +"page." +msgstr "" + +#: ../../ecommerce/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:3 +msgid "Introduction to Odoo eCommerce" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your eCommerce website in no " +"time. The topics follow the buying process:" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:13 +msgid "Product Page" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:14 +msgid "Shop Page" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:15 +msgid "Pricing" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:16 +msgid "Taxes" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:17 +msgid "Checkout process" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:18 +msgid "Upselling & cross-selling" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:19 +msgid "Payment" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:20 +msgid "Shipping & Tracking" +msgstr "" + +#: ../../ecommerce/overview/introduction.rst:24 +msgid ":doc:`../../website/publish/domain_name`" +msgstr "" + +#: ../../ecommerce/publish.rst:3 +msgid "Launch my website" +msgstr "" + +#: ../../ecommerce/shopper_experience.rst:3 +msgid "Get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:3 +msgid "How to get paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:5 +msgid "" +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:10 +msgid "What are the payment methods available" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:13 +msgid "Wire transfer" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:15 +msgid "" +"Wire Transfer is the default payment method available. The aim is providing " +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:21 +msgid "Payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:27 +msgid "`Paypal <paypal.html>`__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:33 +msgid "Sips" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:38 +msgid "How to go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:40 +msgid "" +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 +msgid "" +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:61 +msgid "How to debit credit cards to pay subscriptions" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:62 +msgid "" +"`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 +msgid "" +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 +msgid "" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:85 +msgid "How to:" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:87 +msgid "Switch to developer mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:89 +msgid "Take the **Custom** payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:91 +msgid "" +"Set up the payment form (S2S Form Template) as instructed by your payment " +"acquirer. You can start from *default_acquirer_button* that you can " +"duplicate." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:98 +msgid "" +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"<https://developer.paypal.com/docs/classic/paypal-payments-standard" +"/integration-guide/installment_buttons>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:102 +msgid "" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. <https://www.odoo.com/page/contactus>`__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:109 +msgid ":doc:`paypal`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:3 +msgid "How to get paid with Paypal" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:5 +msgid "" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:11 +msgid "Set up your Paypal account" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:13 +msgid "" +"Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade " +"your account to *Business account* if you have a basic account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "" +"Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your " +"**Profile**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:22 +msgid "Now enter the menu **My selling tools**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:29 +msgid "" +"Turn on **Auto Return** and enter the **Return URL**: " +"<odoo_instance_url>/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:36 +msgid "" +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:43 +msgid "" +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 +msgid "Transaction fees" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:114 +msgid "" +"You can charge an extra to the customer to cover the transaction fees Paypal" +" charges you. Once redirected to Paypal, your customer sees an extra applied" +" to the order amount." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:117 +msgid "" +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"<https://www.paypal.com/webapps/mpp/paypal-fees>`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:3 +msgid "How customers can access their customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:5 +msgid "" +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:14 +msgid "Sign up" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:16 +msgid "" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 +msgid "" +"Once logged in the customer will access the account by clicking *My Account*" +" in the login dropdown menu." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:31 +msgid "" +"THere they find all their history. The main address (billing) can also be " +"modified." +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:37 +msgid "" +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." +msgstr "" + +#: ../../ecommerce/taxes.rst:3 +msgid "Collect taxes" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/expenses.po b/locale/tr/LC_MESSAGES/expenses.po new file mode 100644 index 000000000..df7b00e8d --- /dev/null +++ b/locale/tr/LC_MESSAGES/expenses.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2016-11-22 13:16+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../expenses.rst:5 +msgid "Expenses" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/general.po b/locale/tr/LC_MESSAGES/general.po new file mode 100644 index 000000000..b3a1fa64e --- /dev/null +++ b/locale/tr/LC_MESSAGES/general.po @@ -0,0 +1,831 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../general.rst:5 +msgid "General" +msgstr "" + +#: ../../general/auth.rst:3 +msgid "Authentication" +msgstr "" + +#: ../../general/auth/google.rst:3 +msgid "How to allow users to sign in with their Google account" +msgstr "" + +#: ../../general/auth/google.rst:5 +msgid "" +"Connect to your Google account and go to " +"`https://console.developers.google.com/ " +"<https://console.developers.google.com/>`_." +msgstr "" + +#: ../../general/auth/google.rst:7 +msgid "" +"Click on **Create Project** and enter the project name and other details." +msgstr "" + +#: ../../general/auth/google.rst:15 +msgid "Click on **Use Google APIs**" +msgstr "" + +#: ../../general/auth/google.rst:20 +msgid "" +"On the left side menu, select the sub menu **Credentials** (from **API " +"Manager**) then select **OAuth consent screen**." +msgstr "" + +#: ../../general/auth/google.rst:25 +msgid "" +"Fill in your address, email and the product name (for example odoo) and then" +" save." +msgstr "" + +#: ../../general/auth/google.rst:30 +msgid "" +"Then click on **Add Credentials** and select the second option (OAuth 2.0 " +"Client ID)." +msgstr "" + +#: ../../general/auth/google.rst:38 +msgid "" +"Check that the application type is set on **Web Application**. Now configure" +" the allowed pages on which you will be redirected." +msgstr "" + +#: ../../general/auth/google.rst:40 +msgid "" +"To achieve this, complete the field **Authorized redirect URIs**. Copy paste" +" the following link in the box: http://mydomain.odoo.com/auth_oauth/signin. " +"Then click on **Create**" +msgstr "" + +#: ../../general/auth/google.rst:48 +msgid "" +"Once done, you receive two information (your Client ID and Client Secret). " +"You have to insert your Client ID in the **General Settings**." +msgstr "" + +#: ../../general/base_import.rst:3 +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" + +#: ../../general/base_import/import_faq.rst:3 +msgid "How to import data into Odoo" +msgstr "" + +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "" + +#: ../../general/base_import/import_faq.rst:7 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." +msgstr "" + +#: ../../general/base_import/import_faq.rst:16 +msgid "" +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." +msgstr "" + +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" +msgstr "" + +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../general/base_import/import_faq.rst:25 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:31 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:81 +msgid "" +"Odoo can automatically detect if a column is a date and it will try to guess" +" the date format from a set of most used date format. While this process can" +" work for a lot of simple date format, some exotic date format will not be " +"recognize and it is also possible to have some confusion (day and month " +"inverted as example) as it is difficult to guess correctly which part is the" +" day and which one is the month in a date like '01-03-2016'." +msgstr "" + +#: ../../general/base_import/import_faq.rst:83 +msgid "" +"To view which date format Odoo has found from your file you can check the " +"**Date Format** that is shown when clicking on **Options** under the file " +"selector. If this format is incorrect you can change it to your liking using" +" the *ISO 8601* to define the format." +msgstr "" + +#: ../../general/base_import/import_faq.rst:86 +msgid "" +"If you are importing an excel (.xls, .xlsx) file, you can use date cells to " +"store dates as the display of dates in excel is different from the way it is" +" stored. That way you will be sure that the date format is correct in Odoo " +"whatever your locale date format is." +msgstr "" + +#: ../../general/base_import/import_faq.rst:91 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:93 +msgid "" +"Yes, we fully support numbers with parenthesis to represent negative sign as" +" well as numbers with currency sign attached to them. Odoo also " +"automatically detect which thousand/decimal separator you use (you can " +"change those under **options**). If you use a currency symbol that is not " +"known to Odoo, it might not be recognized as a number though and it will " +"crash." +msgstr "" + +#: ../../general/base_import/import_faq.rst:95 +msgid "" +"Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../general/base_import/import_faq.rst:97 +msgid "32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:98 +msgid "32000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:99 +msgid "32,000.00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:100 +msgid "-32000.00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:101 +msgid "(32000.00)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:102 +msgid "$ 32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:103 +msgid "(32000.00 €)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:105 +msgid "Example that will not work:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:107 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../general/base_import/import_faq.rst:108 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:113 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:115 +msgid "" +"By default the Import preview is set on commas as field separators and " +"quotation marks as text delimiters. If your csv file does not have these " +"settings, you can modify the File Format Options (displayed under the Browse" +" CSV file bar after you select your file)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:117 +msgid "" +"Note that if your CSV file has a tabulation as separator, Odoo will not " +"detect the separations. You will need to change the file format options in " +"your spreadsheet application. See the following question." +msgstr "" + +#: ../../general/base_import/import_faq.rst:122 +msgid "" +"How can I change the CSV file format options when saving in my spreadsheet " +"application?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:124 +msgid "" +"If you edit and save CSV files in speadsheet applications, your computer's " +"regional settings will be applied for the separator and delimiter. We " +"suggest you use OpenOffice or LibreOffice Calc as they will allow you to " +"modify all three options (in 'Save As' dialog box > Check the box 'Edit " +"filter settings' > Save)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:126 +msgid "" +"Microsoft Excel will allow you to modify only the encoding when saving (in " +"'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:131 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:133 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When you" +" want to import such fields, Odoo will have to recreate links between the " +"different records. To help you import such fields, Odoo provides 3 " +"mechanisms. You must use one and only one mechanism per field you want to " +"import." +msgstr "" + +#: ../../general/base_import/import_faq.rst:135 +msgid "" +"For example, to reference the country of a contact, Odoo proposes you 3 " +"different fields to import:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:137 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../general/base_import/import_faq.rst:138 +msgid "" +"Country/Database ID: the unique Odoo ID for a record, defined by the ID " +"postgresql column" +msgstr "" + +#: ../../general/base_import/import_faq.rst:139 +msgid "" +"Country/External ID: the ID of this record referenced in another application" +" (or the .XML file that imported it)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:141 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:143 +msgid "Country: Belgium" +msgstr "" + +#: ../../general/base_import/import_faq.rst:144 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../general/base_import/import_faq.rst:145 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../general/base_import/import_faq.rst:147 +msgid "" +"According to your need, you should use one of these 3 ways to reference " +"records in relations. Here is when you should use one or the other, " +"according to your need:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:149 +msgid "" +"Use Country: This is the easiest way when your data come from CSV files that" +" have been created manually." +msgstr "" + +#: ../../general/base_import/import_faq.rst:150 +msgid "" +"Use Country/Database ID: You should rarely use this notation. It's mostly " +"used by developers as it's main advantage is to never have conflicts (you " +"may have several records with the same name, but they always have a unique " +"Database ID)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:151 +msgid "" +"Use Country/External ID: Use External ID when you import data from a third " +"party application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:153 +msgid "" +"When you use External IDs, you can import CSV files with the \"External ID\"" +" column to define the External ID of each record you import. Then, you will " +"be able to make a reference to that record with columns like " +"\"Field/External ID\". The following two CSV files give you an example for " +"Products and their Categories." +msgstr "" + +#: ../../general/base_import/import_faq.rst:155 +msgid "" +"`CSV file for categories " +"<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:157 +msgid "" +"`CSV file for Products " +"<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:161 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:163 +msgid "" +"If for example you have two product categories with the child name " +"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " +"Products/Sellable\"), your validation is halted but you may still import " +"your data. However, we recommend you do not import the data because they " +"will all be linked to the first 'Sellable' category found in the Product " +"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of " +"the duplicates' values or your product category hierarchy." +msgstr "" + +#: ../../general/base_import/import_faq.rst:165 +msgid "" +"However if you do not wish to change your configuration of product " +"categories, we recommend you use make use of the external ID for this field " +"'Category'." +msgstr "" + +#: ../../general/base_import/import_faq.rst:170 +msgid "" +"How can I import a many2many relationship field (e.g. a customer that has " +"multiple tags)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:172 +msgid "" +"The tags should be separated by a comma without any spacing. For example, if" +" you want your customer to be linked to both tags 'Manufacturer' and " +"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column" +" of your CSV file." +msgstr "" + +#: ../../general/base_import/import_faq.rst:174 +msgid "" +"`CSV file for Manufacturer, Retailer " +"<../../_static/example_files/m2m_customers_tags.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:179 +msgid "" +"How can I import a one2many relationship (e.g. several Order Lines of a " +"Sales Order)?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:181 +msgid "" +"If you want to import sales order having several order lines; for each order" +" line, you need to reserve a specific row in the CSV file. The first order " +"line will be imported on the same row as the information relative to order. " +"Any additional lines will need an addtional row that does not have any " +"information in the fields relative to the order. As an example, here is " +"purchase.order_functional_error_line_cant_adpat.CSV file of some quotations " +"you can import, based on demo data." +msgstr "" + +#: ../../general/base_import/import_faq.rst:184 +msgid "" +"`File for some Quotations " +"<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:186 +msgid "" +"The following CSV file shows how to import purchase orders with their " +"respective purchase order lines:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:188 +msgid "" +"`Purchase orders with their respective purchase order lines " +"<../../_static/example_files/o2m_purchase_order_lines.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:190 +msgid "" +"The following CSV file shows how to import customers and their respective " +"contacts:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:192 +msgid "" +"`Customers and their respective contacts " +"<../../_static/example_files/o2m_customers_contacts.csv>`_." +msgstr "" + +#: ../../general/base_import/import_faq.rst:197 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:199 +msgid "" +"If you import a file that contains one of the column \"External ID\" or " +"\"Database ID\", records that have already been imported will be modified " +"instead of being created. This is very usefull as it allows you to import " +"several times the same CSV file while having made some changes in between " +"two imports. Odoo will take care of creating or modifying each record " +"depending if it's new or not." +msgstr "" + +#: ../../general/base_import/import_faq.rst:201 +msgid "" +"This feature allows you to use the Import/Export tool of Odoo to modify a " +"batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../general/base_import/import_faq.rst:206 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:208 +msgid "" +"If you do not set all fields in your CSV file, Odoo will assign the default " +"value for every non defined fields. But if you set fields with empty values " +"in your CSV file, Odoo will set the EMPTY value in the field, instead of " +"assigning the default value." +msgstr "" + +#: ../../general/base_import/import_faq.rst:213 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../general/base_import/import_faq.rst:215 +msgid "" +"If you need to import data from different tables, you will have to recreate " +"relations between records belonging to different tables. (e.g. if you import" +" companies and persons, you will have to recreate the link between each " +"person and the company they work for)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:217 +msgid "" +"To manage relations between tables, you can use the \"External ID\" " +"facilities of Odoo. The \"External ID\" of a record is the unique identifier" +" of this record in another application. This \"External ID\" must be unique " +"accoss all the records of all objects, so it's a good practice to prefix " +"this \"External ID\" with the name of the application or table. (like " +"'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../general/base_import/import_faq.rst:219 +msgid "" +"As an example, suppose you have a SQL database with two tables you want to " +"import: companies and persons. Each person belong to one company, so you " +"will have to recreate the link between a person and the company he work for." +" (If you want to test this example, here is a <a " +"href=\"/base_import/static/csv/database_import_test.sql\">dump of such a " +"PostgreSQL database</a>)" +msgstr "" + +#: ../../general/base_import/import_faq.rst:221 +msgid "" +"We will first export all companies and their \"External ID\". In PSQL, write" +" the following command:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:227 +msgid "This SQL command will create the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:234 +msgid "" +"To create the CSV file for persons, linked to companies, we will use the " +"following SQL command in PSQL:" +msgstr "" + +#: ../../general/base_import/import_faq.rst:240 +msgid "It will produce the following CSV file::" +msgstr "" + +#: ../../general/base_import/import_faq.rst:248 +msgid "" +"As you can see in this file, Fabien and Laurence are working for the Bigees " +"company (company_1) and Eric is working for the Organi company. The relation" +" between persons and companies is done using the External ID of the " +"companies. We had to prefix the \"External ID\" by the name of the table to " +"avoid a conflict of ID between persons and companies (person_1 and company_1" +" who shared the same ID 1 in the orignial database)." +msgstr "" + +#: ../../general/base_import/import_faq.rst:250 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two CSV files, you will have 4 " +"contacts and 3 companies. (the firsts two contacts are linked to the first " +"company). You must first import the companies and then the persons." +msgstr "" + +#: ../../general/odoo_basics.rst:3 +msgid "BASICS" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:3 +msgid "How to add a user" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:5 +msgid "" +"Odoo provides you with the option to add additional users at any given " +"point." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:9 +msgid "Add individual users" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:11 +msgid "" +"From the Settings module, go to the submenu :menuselection:`Users --> Users`" +" and click on **CREATE.** First add the name of your new user and the " +"professional email address - the one he will use to log into Odoo instance -" +" and a picture." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:19 +msgid "" +"Under Access Rights, you can choose which applications your user can access " +"and use. Different levels of rights are available depending on the app." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:23 +msgid "" +"When you’re done editing the page and have clicked on **SAVE**, an " +"invitation email will automatically be sent to the user. The user must click" +" on it to accept the invitation to your instance and create a log-in." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:32 +msgid "" +"Remember that each additional user will increase your subscription fees. " +"Refer to our `*Pricing page* <https://www.odoo.com/pricing>`__ for more " +"information." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:39 +msgid "" +"You can also add a new user on the fly from your dashboard. From the above " +"screenshot, enter the email address of the user you would like to add and " +"click on **INVITE**. The user will receive an email invite containing a link" +" to set his password. You will then be able to define his accesses rights " +"under the :menuselection:`Settings --> Users menu`." +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:45 +msgid "" +"`Deactivating Users <../../db_management/documentation.html#deactivating-" +"users>`_" +msgstr "" + +#: ../../general/odoo_basics/add_user.rst:46 +msgid ":doc:`../../crm/salesteam/setup/create_team`" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:3 +msgid "Manage Odoo in your own language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:5 +msgid "" +"Odoo provides you with the option to manage Odoo in different languages, and" +" each user can use Odoo in his own language ." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:9 +msgid "Load your desired language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:11 +msgid "" +"The first thing to do is to load your desired language on your Odoo " +"instance." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:14 +msgid "" +"From the general dashboard click on the **Settings** app; on the top left of" +" the page select :menuselection:`Translations --> Load a Translation`, " +"select a language to install and click on **LOAD.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:23 +msgid "" +"If you check the \"Websites to translate\" checkbox you will have the option" +" to change the navigation language on your website." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:27 +msgid "Change your language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:29 +msgid "" +"You can change the language to the installed language by going to the drop-" +"down menu at the top right side of the screen, choose **Preferences**." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:36 +msgid "" +"Then change the Language setting to your installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:42 +msgid "Open a new menu to view the changes." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:45 +msgid "Change another user's language" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:47 +msgid "" +"Odoo also gives you the possibility for each user to choose his preferred " +"language." +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:50 +msgid "" +"To change the language for a different user, choose :menuselection:`Users " +"--> Users` from the Settings app. Here you have a list of all users and you " +"can choose the user who you'd like to change the language for. Select the " +"user and click on **Edit** in the top left corner. Under Preferences you can" +" change the Language to any previously installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../general/odoo_basics/choose_language.rst:61 +msgid ":doc:`../../website/publish/translate`" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/getting_started.po b/locale/tr/LC_MESSAGES/getting_started.po new file mode 100644 index 000000000..2814b333b --- /dev/null +++ b/locale/tr/LC_MESSAGES/getting_started.po @@ -0,0 +1,635 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../getting_started/documentation.rst:5 +msgid "Odoo Online Implementation" +msgstr "" + +#: ../../getting_started/documentation.rst:7 +msgid "" +"This document summarizes **Odoo's Online services**, our Success Pack " +"**implementation methodology**, and *best practices* to **get started** with" +" our product." +msgstr "" + +#: ../../getting_started/documentation.rst:11 +msgid "" +"*We recommend that new Odoo Online customers read this document before the " +"kick-off call with our project manager. This way, we save time and don't " +"have to use your hours from the success pack discussing the basics.*" +msgstr "" + +#: ../../getting_started/documentation.rst:16 +msgid "" +"*If you have not read this document, our project manager will review this " +"with you at the time of the kick-off call.*" +msgstr "" + +#: ../../getting_started/documentation.rst:20 +msgid "Getting Started" +msgstr "" + +#: ../../getting_started/documentation.rst:22 +msgid "" +"Do not wait for the kick-off meeting to begin playing with the software. The" +" more exposure you have with Odoo, the more time you will save later during " +"the implementation." +msgstr "" + +#: ../../getting_started/documentation.rst:26 +msgid "" +"Once you purchase an Odoo Online subscription, you will receive instructions" +" by e-mail on how to activate or create your database. From this email, you " +"can activate your existing Odoo database or create a new one from scratch." +msgstr "" + +#: ../../getting_started/documentation.rst:31 +msgid "" +"If you did not receive this email, e.g. because the payment was made by " +"someone else in your company, contact our support using our `online support " +"form <https://www.odoo.com/help>`__." +msgstr "" + +#: ../../getting_started/documentation.rst:38 +msgid "" +"Fill in the sign-in or sign-up screens and you will get your first Odoo " +"database ready to be used." +msgstr "" + +#: ../../getting_started/documentation.rst:41 +msgid "" +"In order to familiarize yourself with the user interface, take a few minutes" +" to create records: *products, customers, opportunities or projects / " +"tasks*. Follow the blinking dots, they give you tips about the user " +"interface as shown in the picture below." +msgstr "" + +#: ../../getting_started/documentation.rst:47 +msgid "|left_pic|" +msgstr "" + +#: ../../getting_started/documentation.rst:47 +msgid "|right_pic|" +msgstr "" + +#: ../../getting_started/documentation.rst:50 +msgid "" +"Once you get used to the user interface, have a look at the implementation " +"planners. These are accessible from the Settings app, or from the top " +"progress bar on the right hand side of the main applications." +msgstr "" + +#: ../../getting_started/documentation.rst:58 +msgid "These implementation planners will:" +msgstr "" + +#: ../../getting_started/documentation.rst:60 +msgid "help you define your goals and KPIs for each application," +msgstr "" + +#: ../../getting_started/documentation.rst:62 +msgid "guide you through the different configuration steps," +msgstr "" + +#: ../../getting_started/documentation.rst:64 +msgid "and provide you with tips and tricks to getting the most out of Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:66 +msgid "" +"Fill in the first steps of the implementation planner (goals, expectations " +"and KPIs). Our project manager will review them with you during the " +"implementation process." +msgstr "" + +#: ../../getting_started/documentation.rst:73 +msgid "" +"If you have questions or need support, our project manager will guide you " +"through all the steps. But you can also:" +msgstr "" + +#: ../../getting_started/documentation.rst:76 +msgid "" +"Read the documentation on our website: " +"`https://www.odoo.com/documentation/user " +"<https://www.odoo.com/documentation/user>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:79 +msgid "" +"Watch the videos on our eLearning platform (Free with your first Success " +"Pack): `https://odoo.thinkific.com/courses/odoo-functional " +"<https://odoo.thinkific.com/courses/odoo-functional>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:82 +msgid "" +"Watch the webinars on our `Youtube channel " +"<https://www.youtube.com/user/OpenERPonline>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:85 +msgid "" +"Or send your questions to our online support through our `online support " +"form <https://www.odoo.com/help>`__." +msgstr "" + +#: ../../getting_started/documentation.rst:89 +msgid "What do we expect from you?" +msgstr "" + +#: ../../getting_started/documentation.rst:91 +msgid "" +"We are used to deploying fully featured projects within 25 to 250 hours of " +"services, which is much faster than any other ERP vendor on the market. Most" +" projects are completed between 1 to 9 calendar months." +msgstr "" + +#: ../../getting_started/documentation.rst:95 +msgid "" +"But what really **differentiates between a successful implementation and a " +"slow one, is you, the customer!** From our experience, when our customer is " +"engaged and proactive the implementation is smooth." +msgstr "" + +#: ../../getting_started/documentation.rst:100 +msgid "Your internal implementation manager" +msgstr "" + +#: ../../getting_started/documentation.rst:102 +msgid "" +"We ask that you maintain a single point of contact within your company to " +"work with our project manager on your Odoo Implementation. This is to ensure" +" efficiency and a single knowledge base in your company. Additionally, this " +"person must:" +msgstr "" + +#: ../../getting_started/documentation.rst:107 +msgid "" +"**be available at least 2 full days a week** for the project, otherwise you " +"risk slowing down your implementation. More is better with the fastest " +"implementations having a full time project manager." +msgstr "" + +#: ../../getting_started/documentation.rst:111 +msgid "" +"**have authority to take decisions** on their own. Odoo usually transforms " +"all departments within a company for the better. There can be many small " +"details that need quick turn arounds for answers and if there is too much " +"back and forth between several internal decision makers within your company " +"it could potentially seriously slow everything down." +msgstr "" + +#: ../../getting_started/documentation.rst:117 +msgid "" +"**have the leadership** to train and enforce policies internally with full " +"support from all departments and top management, or be part of top " +"management." +msgstr "" + +#: ../../getting_started/documentation.rst:121 +msgid "Integrate 90% of your business, not 100%" +msgstr "" + +#: ../../getting_started/documentation.rst:123 +msgid "" +"You probably chose Odoo because no other software allows for such a high " +"level of automation, feature coverage, and integration. But **don't be an " +"extremist.**" +msgstr "" + +#: ../../getting_started/documentation.rst:127 +msgid "" +"Customizations cost you time, money, are more complex to maintain, add risks" +" to the implementation, and can cause issues with upgrades." +msgstr "" + +#: ../../getting_started/documentation.rst:130 +msgid "" +"Standard Odoo can probably cover 90% of your business processes and " +"requirements. Be flexible on the remaining 10%, otherwise that 10% will cost" +" you twice the original project price. One always underestimates the hidden " +"costs of customization." +msgstr "" + +#: ../../getting_started/documentation.rst:134 +msgid "" +"**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was " +"designed. Learn how it works and don't try to replicate the way your old " +"system(s) works." +msgstr "" + +#: ../../getting_started/documentation.rst:138 +msgid "" +"**The project first, customizations second.** If you really want to " +"customize Odoo, phase it towards the end of the project, ideally after " +"having been in production for several months. Once a customer starts using " +"Odoo, they usually drop about 60% of their customization requests as they " +"learn to perform their work flows out of the box, or the Odoo way. It is " +"more important to have all your business processes working than customizing " +"a screen to add a few fields here and there or automating a few e-mails." +msgstr "" + +#: ../../getting_started/documentation.rst:147 +msgid "" +"Our project managers are trained to help you make the right decisions and " +"measure the tradeoffs involved but it is much easier if you are aligned with" +" them on the objectives. Some processes may take more time than your " +"previous system(s), however you need to weigh that increase in time with " +"other decreases in time for other processes. If the net time spent is " +"decreased with your move to Odoo than you are already ahead." +msgstr "" + +#: ../../getting_started/documentation.rst:155 +msgid "Invest time in learning Odoo" +msgstr "" + +#: ../../getting_started/documentation.rst:157 +msgid "" +"Start your free trial and play with the system. The more comfortable you are" +" with navigating Odoo, the better your decisions will be and the quicker and" +" easier your training phases will be." +msgstr "" + +#: ../../getting_started/documentation.rst:161 +msgid "" +"Nothing replaces playing with the software, but here are some extra " +"resources:" +msgstr "" + +#: ../../getting_started/documentation.rst:164 +msgid "" +"Documentation: `https://www.odoo.com/documentation/user " +"<https://www.odoo.com/documentation/user>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:167 +msgid "" +"Introduction Videos: `https://www.odoo.com/r/videos " +"<https://www.odoo.com/r/videos>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:170 +msgid "" +"Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 " +"<https://www.odoo.com/blog/customer-reviews-6>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:174 +msgid "Get things done" +msgstr "" + +#: ../../getting_started/documentation.rst:176 +msgid "" +"Want an easy way to start using Odoo? Install Odoo Notes to manage your to-" +"do list for the implementation: `https://www.odoo.com/page/notes " +"<https://www.odoo.com/page/notes>`__. From your Odoo home, go to Apps and " +"install the Notes application." +msgstr "" + +#: ../../getting_started/documentation.rst:184 +msgid "This module allows you to:" +msgstr "" + +#: ../../getting_started/documentation.rst:186 +msgid "Manage to-do lists for better interactions with your consultant;" +msgstr "" + +#: ../../getting_started/documentation.rst:188 +msgid "Share Odoo knowledge & good practices with your employees;" +msgstr "" + +#: ../../getting_started/documentation.rst:190 +msgid "" +"Get acquainted with all the generic tools of Odoo: Messaging, Discussion " +"Groups, Kanban Dashboard, etc." +msgstr "" + +#: ../../getting_started/documentation.rst:197 +msgid "" +"This application is even compatible with the Etherpad platform " +"(http://etherpad.org). To use these collaborative pads rather than standard " +"Odoo Notes, install the following add-on: Memos Pad." +msgstr "" + +#: ../../getting_started/documentation.rst:202 +msgid "What should you expect from us?" +msgstr "" + +#: ../../getting_started/documentation.rst:205 +msgid "Subscription Services" +msgstr "" + +#: ../../getting_started/documentation.rst:208 +msgid "Cloud Hosting" +msgstr "" + +#: ../../getting_started/documentation.rst:210 +msgid "" +"Odoo provides a top notch cloud infrastructure including backups in three " +"different data centers, database replication, the ability to duplicate your " +"instance in 10 minutes, and more!" +msgstr "" + +#: ../../getting_started/documentation.rst:214 +msgid "" +"Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla " +"<https://www.odoo.com/page/odoo-online-sla>`__\\" +msgstr "" + +#: ../../getting_started/documentation.rst:217 +msgid "" +"Odoo Online Security: `https://www.odoo.com/page/security " +"<https://www.odoo.com/fr_FR/page/security>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:220 +msgid "" +"Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy " +"<https://www.odoo.com/page/odoo-privacy-policy>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:224 +msgid "Support" +msgstr "" + +#: ../../getting_started/documentation.rst:226 +msgid "" +"Your Odoo Online subscription includes an **unlimited support service at no " +"extra cost, 24/5, Monday to Friday**. To cover 24 hours, our teams are in " +"San Francisco, Belgium and India. Questions could be about anything and " +"everything from: how to use or configure, bugfix requests, payments or " +"subscription issues." +msgstr "" + +#: ../../getting_started/documentation.rst:232 +msgid "" +"Our support can be contacted through our `online support form " +"<https://www.odoo.com/help>`__." +msgstr "" + +#: ../../getting_started/documentation.rst:235 +msgid "" +"Note: The support team cannot develop new features, customize, import data " +"or train your users. These services are provided by your dedicated project " +"manager, as part of the Success Pack." +msgstr "" + +#: ../../getting_started/documentation.rst:240 +msgid "Upgrades" +msgstr "" + +#: ../../getting_started/documentation.rst:242 +msgid "" +"Once every two months, Odoo releases a new version. You will get an upgrade " +"button within the **Manage Your Databases** screen. Upgrading your database " +"is at your own discretion, but allows you to benefit from new features." +msgstr "" + +#: ../../getting_started/documentation.rst:247 +msgid "" +"We provide the option to upgrade in a test environment so that you can " +"evaluate a new version or train your team before the roll out. Simply fill " +"our `online support form <https://www.odoo.com/help>`__ to make this " +"request." +msgstr "" + +#: ../../getting_started/documentation.rst:252 +msgid "Success Pack Services" +msgstr "" + +#: ../../getting_started/documentation.rst:254 +msgid "" +"The Success Pack is a package of premium hour-based services performed by a " +"dedicated project manager and business analyst. The list of services " +"according to your success pack is detailed online: `https://www.odoo.com" +"/pricing-packs <https://www.odoo.com/pricing-packs>`__" +msgstr "" + +#: ../../getting_started/documentation.rst:259 +msgid "" +"The goal of the project manager is to help you get to production within the " +"defined time frame and budget, i.e. the initial number of hours defined in " +"your success pack." +msgstr "" + +#: ../../getting_started/documentation.rst:263 +msgid "His/her role includes:" +msgstr "" + +#: ../../getting_started/documentation.rst:265 +msgid "" +"**Project Management:** review of your objectives & expectations, phasing of" +" the implementation (road map), mapping of your business needs and the Odoo " +"features." +msgstr "" + +#: ../../getting_started/documentation.rst:269 +msgid "**Customized Support:** by phone, e-mail or webinar." +msgstr "" + +#: ../../getting_started/documentation.rst:271 +msgid "" +"**Training, Coaching, and Onsite Consulting:** remote trainings via screen " +"sharing or training on premises. For on premise training sessions, you will " +"be expected to pay extra for travel expenses and accommodations for your " +"consultant." +msgstr "" + +#: ../../getting_started/documentation.rst:276 +msgid "" +"**Configuration:** decisions about how to implement specific needs in Odoo " +"and advanced configuration. (e.g. logistic routes, advanced pricing " +"structures, etc.)" +msgstr "" + +#: ../../getting_started/documentation.rst:280 +msgid "" +"**Data Import**: we can do it or assist you on how to do it with a template " +"prepared by the project manager." +msgstr "" + +#: ../../getting_started/documentation.rst:283 +msgid "" +"If you have subscribed to a **Custom App**, you benefit from following extra" +" services:" +msgstr "" + +#: ../../getting_started/documentation.rst:286 +msgid "**Customization of screens**" +msgstr "" + +#: ../../getting_started/documentation.rst:288 +msgid "" +"**Customization of reports (PDF):** our project managers have access to " +"developers for advanced customizations." +msgstr "" + +#: ../../getting_started/documentation.rst:291 +msgid "" +"**Website Design:** standard themes are provided to get started at no extra " +"cost. However, our project manager can coach you on how to utilize the " +"building blocks of the website designer. The time spent will consume hours " +"of your success pack." +msgstr "" + +#: ../../getting_started/documentation.rst:296 +msgid "" +"**Workflow automations:** e.g. setting values in fields based on triggers, " +"sending reminders by emails, automating actions, etc. For very advanced " +"automations, our project managers have access to Odoo developers." +msgstr "" + +#: ../../getting_started/documentation.rst:302 +msgid "Implementation Methodology" +msgstr "" + +#: ../../getting_started/documentation.rst:304 +msgid "" +"We follow a **lean and hands-on methodology**, that is used to put customers" +" in production in a short period of time and at a low cost." +msgstr "" + +#: ../../getting_started/documentation.rst:307 +msgid "" +"After the kick-off meeting, we define a phasing plan to deploy Odoo " +"progressively, by groups of apps." +msgstr "" + +#: ../../getting_started/documentation.rst:313 +msgid "" +"The goal of the **Kick-off call** is for our project manager to come to an " +"understanding of your business in order to propose an implementation plan " +"(phasing). Each phase is the deployment of a set applications that you will " +"fully use in production at the end of the phase." +msgstr "" + +#: ../../getting_started/documentation.rst:319 +msgid "For every phase, the steps are the following:" +msgstr "" + +#: ../../getting_started/documentation.rst:321 +msgid "" +"**On Boarding:** Odoo's project manager will review Odoo's business flows " +"with you, according to your business. The goal is to train you, validate the" +" business process and configure according to your specific needs." +msgstr "" + +#: ../../getting_started/documentation.rst:326 +msgid "" +"**Data:** created manually or imported from your existing system. You are " +"responsible to export the data from your existing system and Odoo's project " +"manager will import them in Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:330 +msgid "" +"**Training:** once your applications are set up, your data imported, and the" +" system is working smoothly, you will train your users. There will be some " +"back and forth with your Odoo project manager to answer questions and " +"process your feedback." +msgstr "" + +#: ../../getting_started/documentation.rst:335 +msgid "**Production**: Once everyone is trained, your users start using Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:338 +msgid "" +"Once you are comfortable using Odoo, we will fine-tune the process and " +"**automate** some tasks and do the remaining customizations (**extra screens" +" and reports**)." +msgstr "" + +#: ../../getting_started/documentation.rst:342 +msgid "" +"Once all applications are deployed and users are comfortable on Odoo, our " +"project manager will not work on your project anymore (unless you have new " +"needs) and you will use the support service if you have further questions." +msgstr "" + +#: ../../getting_started/documentation.rst:348 +msgid "Managing your databases" +msgstr "" + +#: ../../getting_started/documentation.rst:350 +msgid "" +"To access your databases, go to Odoo.com, sign in and click **My Databases**" +" in the drop-down menu at the top right corner." +msgstr "" + +#: ../../getting_started/documentation.rst:356 +msgid "" +"Odoo gives you the opportunity to test the system before going live or " +"before upgrading to a newer version. Do not mess up your working environment" +" with test data!" +msgstr "" + +#: ../../getting_started/documentation.rst:360 +msgid "" +"In that purpose, you can create as many free trials as you want (available " +"for 15 days). Those instances can be instant copies of your working " +"environment. To do so, go to the Odoo.com account in **My Organizations** " +"page and click **Duplicate**." +msgstr "" + +#: ../../getting_started/documentation.rst:371 +msgid "" +"You can find more information on how to manage your databases :ref:`here " +"<db_management/documentation>`." +msgstr "" + +#: ../../getting_started/documentation.rst:375 +msgid "Customer Success" +msgstr "" + +#: ../../getting_started/documentation.rst:377 +msgid "" +"Odoo is passionate about delighting our customers and ensuring that they " +"have all the resources needed to complete their project." +msgstr "" + +#: ../../getting_started/documentation.rst:380 +msgid "" +"During the implementation phase, your point of contact is the project " +"manager and eventually the support team." +msgstr "" + +#: ../../getting_started/documentation.rst:383 +msgid "" +"Once you are in production, you will probably have less interaction with " +"your project manager. At that time, we will assign a member of our Client " +"Success Team to you. They are specialized in the long-term relationship with" +" our customers. They will contact you to showcase new versions, improve the " +"way you work with Odoo, assess your new needs, etc..." +msgstr "" + +#: ../../getting_started/documentation.rst:390 +msgid "" +"Our internal goal is to keep customers for at least 10 years and offer them " +"a solution that grows with their needs!" +msgstr "" + +#: ../../getting_started/documentation.rst:393 +msgid "Welcome aboard and enjoy your Odoo experience!" +msgstr "" + +#: ../../getting_started/documentation.rst:396 +msgid ":doc:`../../db_management/documentation`" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/index.po b/locale/tr/LC_MESSAGES/index.po new file mode 100644 index 000000000..0c0419743 --- /dev/null +++ b/locale/tr/LC_MESSAGES/index.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../index.rst:3 +msgid "Odoo User Documentation" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/inventory.po b/locale/tr/LC_MESSAGES/inventory.po new file mode 100644 index 000000000..a115e209a --- /dev/null +++ b/locale/tr/LC_MESSAGES/inventory.po @@ -0,0 +1,7666 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Güven YILMAZ <guvenyilmaz@outlook.com.tr>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../inventory.rst:5 ../../inventory/overview/concepts/double-entry.rst:64 +msgid "Inventory" +msgstr "Stok" + +#: ../../inventory/barcode.rst:3 +msgid "Barcodes" +msgstr "" + +#: ../../inventory/barcode/operations.rst:3 +msgid "Daily Operations" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:3 +msgid "How to do an inventory adjustment with barcodes?" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:5 +msgid "From the Barcode application:" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:7 +msgid "Click on **Inventory**" +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:12 +msgid "" +"Scan all the products (if you have 5 identical articles, scan it 5 times, or" +" use the keyboard to set the quantity)." +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:16 +msgid "" +"If you manage multiple locations, scan the location before scanning the " +"products. Eg. scan a shelf's barcode ; scan each product on the shelf ; " +"repeat for each shelf in the wharehouse." +msgstr "" + +#: ../../inventory/barcode/operations/adjustments.rst:20 +msgid "" +"When you've scanned all the items of the location, validate the inventory " +"manually or by scanning the **Validate** barcode." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:3 +msgid "How to process delivery orders?" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:5 +msgid "" +"There are two approaches to process delivery orders: you can either work on " +"printed documents (and scan lines on the documents), or on a screen (and " +"scan products directly)." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:10 +msgid "Process printed delivery orders:" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:12 +msgid "" +"Print delivery orders of the day by selecting all documents from the **To " +"Do** list and print **Picking Operations** from the top menu." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:15 +msgid "" +"Once you start processing your delivery orders, **scan the barcode** on the " +"top-right corner of the document to load the right record on the screen." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:19 +msgid "" +"Then, **scan the barcode** of every product, or scan the barcode of the " +"product on the picking line if the barcode on the product is not easily " +"accessible, visible or is missing." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:23 +#: ../../inventory/barcode/operations/receipts.rst:24 +msgid "" +"Once you scanned all products, scan the **Validate** barcode action to " +"finish the operation." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:30 +msgid "Process delivery orders from a computer or mobile device:" +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:32 +msgid "" +"Load all the delivery orders marked as **To Do**, and open the first one." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:35 +#: ../../inventory/barcode/operations/receipts.rst:33 +msgid "Pick up and scan each listed product." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:37 +msgid "" +"When you've picked all the items, click the **Validate** button or scan the " +"**Validate barcode** action to finish the Operation." +msgstr "" + +#: ../../inventory/barcode/operations/delivery.rst:40 +msgid "" +"Move to the next delivery order to process by clicking on the top-right " +"right **arrow** or scanning the **Pager-Next** barcode action." +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:3 +msgid "How to do an internal transfer?" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:5 +msgid "In Odoo, there are two types of internal transfers:" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:7 +msgid "" +"Those initiated automatically by the system (for example, a quality control)" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:10 +msgid "" +"Those created by a worker (for example, through the internal transfer area " +"of the dashboard)." +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:13 +msgid "To make an Internal Transfer:" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:15 +msgid "From the home of the barcode application, scan the **source location**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:17 +msgid "Pick up and **scan the products**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:19 +msgid "Scan the **destination location**" +msgstr "" + +#: ../../inventory/barcode/operations/internal.rst:21 +msgid "**Validate** the transfer to finish it" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:3 +msgid "How to handle lots and serial numbers with barcodes?" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:5 +msgid "" +"Lots Numbers can be encoded from incoming shipments, internal moves and " +"outgoing deliveries:" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:8 +msgid "" +"In the barcode interface, **scan** the products you want create a lot from" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:10 +msgid "" +"If this product should be manage by lots, a window opens to help you scan " +"the lots/serial numbers" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:13 +msgid "" +"**Scan** a lot barcode, **type** one manually or **leave empty** to generate" +" one automatically" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:16 +msgid "Click or scan **Validate** once you are done" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:18 +msgid "What is the difference between **Lots** and **Serial Numbers**?" +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:20 +msgid "" +"**Lot** numbers are attributed to several identical products, so each time " +"you scan a lot number, Odoo will add one on the product count." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:24 +msgid "" +"On the opposite, a **serial number** is unique, and represented by only one " +"barcode, sticked on only one item. This means that Odoo won't accept " +"scanning the same serial number more than once per operation." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:32 +msgid "Here, we configured **Lu - Petit Beukelaer** tracking by lots." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:37 +msgid "" +"Scan a product from this incoming shipment, then scan the lot number of each" +" product (you can also use the keyboard)." +msgstr "" + +#: ../../inventory/barcode/operations/lots_serial_numbers.rst:43 +msgid "Click save/scan **Validate** and you are done." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:3 +msgid "How to process incoming receipts?" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:5 +msgid "" +"There are two approaches to process incoming receipts: you can either work " +"on printed documents (and scan lines on the documents), or on a screen (and " +"scan products directly)." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:10 +msgid "Process printed incoming receipts:" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:12 +msgid "" +"Print incoming receipts of the day by selecting all documents from the **To " +"Receive** list and print **Picking Operations** from the top menu." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:16 +msgid "" +"Once you start processing your incoming receipts, scan the barcode on the " +"top-right corner of the document to load the right record on the screen." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:20 +msgid "" +"Then, scan the barcode of every product, or scan the barcode of the product " +"on the picking line if the barcode on the product is not easily accessible, " +"visible or is missing." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:28 +msgid "Process incoming receipts from a computer or mobile device:" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:30 +msgid "" +"Load all the incoming receipts marked as **To Receive**, and open the first " +"one." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:35 +msgid "" +"When you've picked all the items, click the **Validate** button or scan the " +"**Validate** barcode action to finish the Operation." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:38 +msgid "" +"Move to the next incoming receipt to process by clicking on the top-right " +"right **arrow** or scanning the **Pager-Next** barcode action." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:42 +#: ../../inventory/management/delivery/scheduled_dates.rst:137 +msgid "Example" +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:44 +msgid "Open operation interface." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:49 +msgid "Scan." +msgstr "" + +#: ../../inventory/barcode/operations/receipts.rst:54 +msgid "" +"The picking appears. Scan items and/or fill in informations using the mouse " +"and keyboard." +msgstr "" + +#: ../../inventory/barcode/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:3 +msgid "Set up your barcode scanner" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:5 +msgid "" +"Getting started with barcode scanning in Odoo is fairly easy. Yet, a good " +"user experience relies on an appropriate hardware setup. This guide will " +"help you through the task of choosing and configuring the barcode scanner." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:11 +msgid "Find the barcode scanner that suits your needs" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:13 +msgid "" +"The 3 recommended type of barcode scanners to work with the Odoo " +"**Inventory** and **Barcode Scanning** apps are the **USB scanner**, **the " +"bluetooth scanner** and the **mobile computer scanner**." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:20 +msgid "" +"If you scan products at a computer location, the **USB scanner** is the way " +"to go. Simply plug it in the computer to start scanning. Just make sure when" +" you buy it that the scanner is compatible with your keyboard layout or can " +"be configured to be so." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:25 +msgid "" +"The **bluetooth scanner** can be paired with a smartphone or a tablet and is" +" a good choice if you want to be mobile but don't need a big investment. An " +"approach is to log in Odoo on you smartphone, pair the bluetooth scanner " +"with the smartphone and work in the warehouse with always the possibility to" +" check your smartphone from time to time and use the software 'manually'." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:32 +msgid "" +"For heavy use, the **mobile computer scanner** is the handiest solution. It " +"consists in a small computer with a built-in barcode scanner. This one can " +"turn out to be a very productive solution, however you need to make sure " +"that is is capable of running Odoo smoothy. The most recent models using " +"Android + Google Chrome or Windows + Internet Explorer Mobile should do the " +"job. However, due to the variety of models and configurations on the market," +" it is essential to test it first." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:42 +msgid "Configure your barcode scanner" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:45 +msgid "Keyboard layout" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:50 +msgid "" +"An USB barcode scanner needs to be configured to use the same keyboard " +"layout as your operating system. Otherwise, your scanner won't translate " +"characters correctly (replacing a 'A' with a 'Q' for example). Most scanners" +" are configured by scanning the appropriate barcode in the user manual." +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:57 +msgid "Automatic carriage return" +msgstr "" + +#: ../../inventory/barcode/setup/hardware.rst:59 +msgid "" +"By default, Odoo has a 50 milliseconds delay between each successive scan " +"(it helps avoid accidental double scanning). If you want to suppress this " +"delay, you can configure your scanner to insert a carriage return at the end" +" of each barcode. This is usually the default configuration and can be " +"explicitly configured by scanning a specific barcode in the user manual ('CR" +" suffix ON', 'Apply Enter for suffix', etc.)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:3 +msgid "How to activate the barcodes in Odoo?" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:5 +msgid "" +"The barcode scanning features can save you a lot of the time usually lost " +"switching between the keyboard, the mouse and the scanner. Properly " +"attributing barcodes to products, pickings locations, etc. allows you to " +"work more efficiently by controlling the software almost exclusively with " +"the barcode scanner." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:17 +msgid "" +"Print this document to be able to use your barcode scanner to perform more " +"actions." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:19 +msgid ":ref:`Document:` |download_barcode|" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:23 +msgid "Set products barcodes" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:28 +msgid "" +"In order to fill a picking or to perform an inventory, you need to make sure" +" that your products are encoded in Odoo along with their barcodes. If this " +"is not already done, you can fill in the products barcodes through a handy " +"interface. Go to :menuselection:`Inventory --> Configuration --> Settings` " +"and click the **Configure Product Barcodes** button. This interface can also" +" be accessed via the planner." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:37 +msgid "" +"Product variants: be careful to add barcodes directly on the variant, and " +"not the template product (otherwise you won't be able to differentiate " +"them)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:42 +msgid "Set locations barcodes" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:47 +msgid "" +"If you manage multiple locations, you will find useful to attribute a " +"barcode to each location and stick it on the location. You can configure the" +" locations barcodes in :menuselection:`Inventory --> Configuration --> " +"Warehouse Management --> Locations`. There is button in the **Print** menu " +"that you can use to print the locations names and barcodes. There are 4 " +"barcodes per page, arranged in a way that is convenient to print on sticker " +"paper." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:56 +msgid "" +"Example of location naming: **warehouse short name** - **location short " +"name** - (**Corridor X** - **Shelf Y** - **Height Z**) Example: A032-025-133" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:63 +msgid "Barcode formats" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:65 +msgid "" +"Most retail products use EAN-13 barcodes. They cannot be made up without " +"proper authorization: you must pay the International Article Numbering " +"Association a fee in exchange for an EAN code sequence (that's why no two " +"products in a store will ever have the same EAN code)." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:70 +msgid "" +"Still, as Odoo supports any string as a barcode, so you can always define " +"your own barcode format for internal use." +msgstr "" + +#: ../../inventory/management.rst:3 +msgid "Warehouse Management" +msgstr "" + +#: ../../inventory/management/adjustment.rst:3 +msgid "Inventory Adjustment" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:3 +msgid "How to make the initial inventory?" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:5 +msgid "" +"One of the most important feature in an warehouse management software is to " +"keep the inventory right." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:8 +msgid "" +"Once your products have been defined, it is time to make your initial " +"inventory. You will reflect reality by inventorying the right quantities in " +"the right locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:13 +#: ../../inventory/management/lots_serial_numbers/lots.rst:55 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:34 +msgid "Product Configuration" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:15 +msgid "" +"In the Inventory module, open the :menuselection:`Inventory Control --> " +"Products`, then click on **Create** to create a new product. Configure the " +"product type so that it is **Stockable** and not a consumable." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:23 +msgid "Start the initial inventory" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:26 +msgid "Update the product quantity for one product" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:28 +msgid "" +"In the product you just created, you can see in the upper tiles that we have" +" 0 product On Hand. Click on the **Update qty on Hand** button." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:31 +msgid "" +"A new window opens. In the **New Quantity on Hand** field, type the quantity" +" of product you currently hold in stock, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:39 +msgid "" +"if you are using multiple locations for your warehouse, you will be able to " +"set the location of your product from this screen." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:42 +msgid "" +"You can now see from the On Hand tab that the quantity has been updated." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:47 +msgid "" +"Now, if you check the **Inventory Adjustments** in the **Inventory Control**" +" menu, you will see that a new line named \"INV: (name of your product)\" " +"has automatically been created and validated by the system." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:55 +msgid "Multiple products at once" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:57 +msgid "" +"Create all the products for which you want to follow the stock (as stockable" +" products). Once the required products in stock have been defined, use an " +"initial inventory operation to put the current quantities into the system by" +" location. Go to :menuselection:`Inventory Control --> Inventory " +"Adjustments` to start your initial inventory." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:63 +msgid "" +"Give it a name (for example Initial Inventory) and select the stock location" +" of your inventory. Note that when you select a parent location (such as " +"Stock, which might be split into sub locations), you can also select the sub" +" (or child) locations." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:71 +msgid "" +"You can choose between making an inventory for all products, for a few or " +"only for one. In this case, we choose the **All products** option." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:79 +msgid "" +"If you need your stock valuation to be done in a different period than the " +"one that will be selected by default according to the inventory end date, " +"enter the corresponding accounting period in the Force Valuation Period " +"field. The accounting module needs to be installed." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:84 +msgid "" +"Click the **Start Inventory** button. Depending on the type of inventory you" +" have chosen (all products or selected ones) you might have to add products " +"manually by clicking on **Add an item**." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:88 +msgid "" +"Add the **Real Quantity** that you have in your stock for each product." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:92 +msgid "" +"additional information will be available according to the options you " +"activated (multi-locations, serial number, consignee stocks)." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:98 +msgid "" +"Click the **Validate Inventory** button to confirm the inventory and post " +"it." +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:102 +msgid "Reporting" +msgstr "" + +#: ../../inventory/management/adjustment/initial_inventory.rst:104 +msgid "" +"To check the current stock, go to :menuselection:`Inventory Control --> " +"Products`, and click on the **list button**:" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:3 +msgid "How to choose between minimum stock rule and make to order?" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:5 +msgid "" +"**Minimum Stock rules** and **Make to Order** have similar consequences but " +"different rules. They should be used depending on your manufacturing and " +"delivery strategies." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:15 +msgid "" +"**Minimum Stock** rules are used to ensure that you always have the minimum " +"amount of a product in stock in order to manufacture your products and/or " +"answer to your customer needs. When the stock level of a product reaches its" +" minimum the system will automatically generate a procurement with the " +"quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:22 +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:56 +msgid "Make to Order" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:24 +msgid "" +"The **Make to Order** function will trigger a **Purchase Order** of the " +"amount of the **Sales Order** related to the product. The system will " +"**not** check the current stock valuation. This means that a draft purchase " +"order will be generated regardless of the quantity on hand of the product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:30 +#: ../../inventory/management/delivery/delivery_countries.rst:12 +#: ../../inventory/management/delivery/inventory_flow.rst:37 +#: ../../inventory/management/delivery/label_type.rst:13 +#: ../../inventory/management/delivery/one_step.rst:13 +#: ../../inventory/management/delivery/packaging_type.rst:13 +#: ../../inventory/management/delivery/three_steps.rst:34 +#: ../../inventory/management/delivery/two_steps.rst:29 +#: ../../inventory/management/incoming/handle_receipts.rst:50 +#: ../../inventory/management/incoming/three_steps.rst:28 +#: ../../inventory/management/incoming/two_steps.rst:21 +#: ../../inventory/management/misc/owned_stock.rst:22 +#: ../../inventory/management/misc/scrap.rst:25 +#: ../../inventory/overview/concepts/double-entry.rst:159 +#: ../../inventory/overview/concepts/double-entry.rst:164 +#: ../../inventory/routes/concepts/cross_dock.rst:21 +#: ../../inventory/routes/concepts/inter_warehouse.rst:10 +#: ../../inventory/routes/concepts/procurement_rule.rst:25 +#: ../../inventory/routes/concepts/push_rule.rst:29 +#: ../../inventory/routes/concepts/use_routes.rst:22 +#: ../../inventory/routes/costing/landed_costs.rst:18 +#: ../../inventory/routes/strategies/putaway.rst:23 +#: ../../inventory/routes/strategies/removal.rst:18 +#: ../../inventory/settings/products/packages.rst:17 +#: ../../inventory/settings/products/packages.rst:66 +#: ../../inventory/settings/products/uom.rst:17 +#: ../../inventory/settings/products/variants.rst:114 +#: ../../inventory/settings/warehouses/location_creation.rst:6 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:6 +#: ../../inventory/shipping/operation/invoicing.rst:16 +#: ../../inventory/shipping/operation/labels.rst:15 +#: ../../inventory/shipping/operation/multipack.rst:13 +#: ../../inventory/shipping/setup/delivery_method.rst:17 +#: ../../inventory/shipping/setup/third_party_shipper.rst:14 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:35 +msgid "" +"The Minimum Stock Rules configuration is available through the menu " +":menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the " +"drop down menu. There, click on **Create** to set minimum and maximum stock " +"values for a given product." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"If the active field is set to False, it will allow you to hide the " +"orderpoint without removing it." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Default Unit of Measure used for all stock operation." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"Moves created through this orderpoint will be put in this procurement group." +" If none is given, the moves generated by procurement rules will be grouped " +"into one big picking." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"When the virtual stock goes below the Min Quantity specified for this field," +" Odoo generates a procurement to bring the forecasted quantity to the Max " +"Quantity." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"When the virtual stock goes below the Min Quantity, Odoo generates a " +"procurement to bring the forecasted quantity to the Quantity specified as " +"Max Quantity." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"The procurement quantity will be rounded up to this multiple. If it is 0, " +"the exact quantity will be used." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "" +"Number of days after the orderpoint is triggered to receive the products or " +"to order to the vendor" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:45 +msgid "" +"Then, click on your product to access the related product form and, on the " +"**Inventory submenu**, do not forget to select a supplier." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:52 +msgid "" +"Don't forget to select the right product type in the product form. A " +"consumable can not be stocked and will thus not be accounted for in the " +"stock valuation." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:58 +msgid "" +"The Make to Order configuration is available on your product form through " +"your :menuselection:`Inventory module --> Inventory control --> Products` " +"(or any other module where products are available)." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:62 +msgid "On the product form, under **Inventory**, click on **Make To Order**." +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:68 +msgid "Choice between the two options" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:70 +msgid "" +"The choice between the two options is thus dependent of your inventory " +"strategy. If you prefer to have a buffer and always have at least a minimum " +"amount, the minimum stock rule should be used. If you want to reorder your " +"stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../inventory/management/delivery.rst:3 +msgid "Delivery Orders" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:3 +msgid "How do I cancel a delivery order?" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:6 +#: ../../inventory/management/delivery/delivery_countries.rst:6 +#: ../../inventory/management/delivery/label_type.rst:6 +#: ../../inventory/management/delivery/one_step.rst:6 +#: ../../inventory/management/delivery/packaging_type.rst:6 +#: ../../inventory/management/delivery/three_steps.rst:6 +#: ../../inventory/management/delivery/two_steps.rst:6 +#: ../../inventory/management/incoming/handle_receipts.rst:6 +#: ../../inventory/management/incoming/three_steps.rst:6 +#: ../../inventory/management/incoming/two_steps.rst:6 +#: ../../inventory/management/lots_serial_numbers/lots.rst:6 +#: ../../inventory/management/misc/scrap.rst:6 ../../inventory/overview.rst:3 +#: ../../inventory/overview/process/sale_to_delivery.rst:6 +#: ../../inventory/routes/concepts/procurement_rule.rst:6 +#: ../../inventory/routes/concepts/push_rule.rst:6 +#: ../../inventory/routes/concepts/use_routes.rst:6 +#: ../../inventory/routes/costing/landed_costs.rst:6 +#: ../../inventory/routes/strategies/putaway.rst:6 +#: ../../inventory/routes/strategies/removal.rst:6 +#: ../../inventory/settings/products/packages.rst:6 +#: ../../inventory/settings/products/uom.rst:6 +#: ../../inventory/shipping/operation/cancel.rst:6 +#: ../../inventory/shipping/operation/invoicing.rst:6 +#: ../../inventory/shipping/operation/labels.rst:6 +#: ../../inventory/shipping/operation/multipack.rst:6 +#: ../../inventory/shipping/setup/delivery_method.rst:6 +#: ../../inventory/shipping/setup/third_party_shipper.rst:6 +msgid "Overview" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:8 +msgid "" +"Odoo gives you the possibility to cancel a delivery method whether it has " +"been validated to fast, it needs to be modified or for any other reason." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:12 +msgid "" +"Some carriers are more flexible than others, so make sure to cancel your " +"delivery order as fast as possible if it needs to be done so you don't have " +"any bad surprise." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:17 +#: ../../inventory/shipping/operation/multipack.rst:26 +#: ../../inventory/shipping/setup/third_party_shipper.rst:107 +msgid "Sale process" +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:19 +msgid "" +"Go to the **Sales** module, click on **Sales** and then on **Sales Order**. " +"Then click on the sale order you want to cancel." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:25 +msgid "" +"Click on the **Delivery** button, in the upper right corner of the sale " +"order." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:31 +msgid "" +"Now, click on the **Additional info** tab and you will see that next to the " +"**Carrier Tracking Reference**, there is a **Cancel** button. Click on it to" +" cancel the delivery." +msgstr "" + +#: ../../inventory/management/delivery/cancel_order.rst:38 +msgid "" +"To make sure that your delivery is cancelled, check in the history, you will" +" receive the confirmation of the cancellation." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:3 +msgid "How can I limit a delivery method to a certain number of countries?" +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:8 +msgid "" +"With Odoo, you can have different types of delivery methods, and you can " +"limit them to a certain number of countries." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:14 +msgid "" +"Go to the **Inventory** module, click on **Configuration** and then on " +"**Delivery Methods**." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:20 +msgid "" +"Select the delivery method that you want to change, or create a new one." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:25 +msgid "" +"In the **Destination** tab, choose the countries to which you want to apply " +"this delivery method." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:28 +msgid "Now, that this is done, Let's see the result." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:30 +msgid "" +"If you go to the website, and you try to buy something, once you've entered " +"your details and you proceed to the payment, the website will propose you " +"only the delivery methods that apply to your shipping address." +msgstr "" + +#: ../../inventory/management/delivery/delivery_countries.rst:39 +msgid "" +"This process doesn't work in backend. We assume that when you create a Sale " +"Order, you know which delivery method you can use since you created them." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:3 +msgid "" +"How to send products to customers directly from suppliers (drop-shipping)?" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:6 +msgid "What is drop-shipping?" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:8 +msgid "" +"Drop-Shipping is a system that allows orders taken from your store to be " +"shipped straight from your supplier to your customer. On a usual delivery " +"system, products are sent from your supplier to your warehouse to be put in " +"stock, and then shipped to your customers after ordering. With drop-" +"shipping, no item is stocked. When a customer places an order in your shop, " +"the item is delivered straight from the supplier to the customer. Therefore," +" the product doesn't need to get through your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:18 +msgid "Points to be considered while implementing drop-shipping" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:20 +msgid "" +"Use drop-shipping only for the products you can't or don't want to keep in " +"stock. One reason is that you'll always make smaller margins on items that " +"are drop-shipped, so you should keep it only for items that take up a lot of" +" space in your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:25 +msgid "" +"Drop-shipping is best for niche products. Chances are that products that are" +" in high demand are being offered by large suppliers at a fraction of the " +"price you'll be able to charge, so using a more costly shipping method won't" +" be financially rewarding. But if your product is unique, then it makes " +"sense!" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:31 +msgid "" +"To protect your customers from bad experiences, test drop-shipping companies" +" for yourself beforehand and list the best ones." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:34 +msgid "" +"Make sure time is not against you. Drop-shipping should take a reasonable " +"amount of time and surely not more than it would have taken you to handle it" +" all by yourself. It's also nice to be able to provide your customers with a" +" tracking number." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:39 +msgid "" +"Items have to be available from your supplier. It's good to know if the " +"product you're selling is available upstream. If you don't have that " +"information, inform your customers that you don't hold the item in stock and" +" that it's subject to availability from a third party." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:46 +msgid "" +"For more information and insights on Drop-shipping, read our blog on `What " +"is drop-shipping and how to use it <https://www.odoo.com/blog/business-" +"hacks-1/post/what-is-drop-shipping-and-how-to-use-it-250>`__." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:50 +msgid "Configuring drop-shipping" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:52 +msgid "" +"Open the menu :menuselection:`Inventory --> Configuration --> Settings`. Go " +"to **Location & Warehouse**, locate the **Dropshipping** option and tick the" +" box **Allow suppliers to deliver directly to your customers**. Then, click " +"on **Apply**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:60 +msgid "" +"Then go to the menu :menuselection:`Sales --> Configuration --> Settings`. " +"Locate **Order Routing** and tick the box **Choose specific routes on sales " +"order lines (advanced)**. Click on **Apply**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:67 +msgid "" +"Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a " +"supplier to the products you want to dropship." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:74 +msgid "How to send products from the customers directly to the suppliers" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:76 +msgid "" +"Create a **Sales Order** and specify on a sales order line for your products" +" that the route is **Dropshipping**." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:82 +msgid "" +"Open the menu :menuselection:`Purchases --> Purchases --> Requests for " +"Quotation`. The draft purchase order is automatically created from the " +"procurement with the drop-shipping route. Once the order is confirmed, you " +"will see that one shipment has been created." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:90 +msgid "" +"To confirm the sending from the vendor to the customer, go back to " +"**Inventory** app. On the dashboard, click on **# TO RECEIVE** on the " +"dropship card." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:97 +msgid "" +"It will open the list of drop-shipping transfers. Validate the transfer once" +" it has been done. The items will be directly delivered from the partner to " +"the customer without transiting to your warehouse." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:103 +msgid ":doc:`inventory_flow`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:3 +msgid "How to choose the right inventory flow to handle delivery orders?" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:5 +msgid "" +"Depending on factors such as the type of items you sell, the size of your " +"warehouse, the number of orders you register everyday... the way you handle " +"deliveries to your customers can vary a lot." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:9 +msgid "" +"Odoo allows you to handle shipping from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:12 +msgid "**One step (shipping)**: Ship directly from stock" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:14 +msgid "" +"**Two steps (pick + ship)**: Bring goods to output location before shipping" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:17 +msgid "" +"**Three steps (pick + pack + ship)**: Make packages into a dedicated " +"location, then bring them to the output location for shipping" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:20 +msgid "" +"For companies having a rather small warehouse and that do not require high " +"stock of items or don't sell perishable items, a one step shipping is the " +"simplest solution, as it does not require a lot of configuration and allows " +"to handle orders very quickly." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:25 +msgid "" +"Using inventory methods such as FIFO, LIFO and FEFO require to have at least" +" two steps to handle a shipment. The picking method will be determined by " +"the removal strategy, and the items removed will then be shipped to the " +"customer. This method is also interesting if you hold larger stocks and " +"especially when the items you stock are big in size." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:31 +msgid "" +"The three steps system becomes useful in more specific situations, the main " +"one being for handling very large stocks. The items are transferred to a " +"packing area, where they will be assembled by area of destination, and then " +"set to outbound trucks for final delivery to the customers." +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:40 +#: ../../inventory/management/incoming/handle_receipts.rst:53 +msgid "One step flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:42 +msgid "Please read documentation on :doc:`one_step`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:45 +#: ../../inventory/management/incoming/handle_receipts.rst:58 +msgid "Two steps flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:47 +#: ../../inventory/management/incoming/handle_receipts.rst:60 +msgid "Please read documentation on :doc:`two_steps`" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:50 +#: ../../inventory/management/incoming/handle_receipts.rst:63 +msgid "Three steps flow" +msgstr "" + +#: ../../inventory/management/delivery/inventory_flow.rst:52 +#: ../../inventory/management/incoming/handle_receipts.rst:65 +msgid "Please read documentation on :doc:`three_steps`" +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:3 +msgid "How can I change the label type?" +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:8 +msgid "" +"With Odoo, you can choose among different types of labels for your delivery " +"orders. Follow the steps below and give an appropriate label type to your " +"delivery." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:15 +msgid "" +"In the **Inventory** module, Go to **Configuration** and click on **Delivery" +" methods**." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:18 +msgid "Choose a delivery method and then click on **Edit**." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:23 +msgid "" +"In the **Pricing** tab, under **Fedex label stock type**, you can choose one" +" of the label types available. The availability will vary depending on the " +"carrier." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:30 +msgid "" +"Once this is done, you can see the result if you go to the Sales module and " +"you create a new sale order." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:33 +msgid "" +"As you confirm the sale and validate the delivery with the carrier for which" +" you have modified the label type, The label will appear in your history." +msgstr "" + +#: ../../inventory/management/delivery/label_type.rst:46 +msgid "" +"The default label type is paper letter, and if you choose the label type " +"bottom half for example, here is the difference :" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:3 +msgid "How to process delivery orders in one step (shipping)?" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default to utilize a one-step operation: once all goods are " +"available, they are able to be shipped in a single delivery order." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:15 +msgid "" +"There is no configuration needed. The default outgoing shipments are " +"configured to be directly delivered from the stock." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:18 +msgid "" +"However, if **advance routes** is activated and you set another shipping " +"configuration on your warehouse, you can set it back to the one-step " +"delivery configuration. Go to :menuselection:`Configuration --> Warehouses` " +"and edit the concerned warehouse." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:23 +msgid "" +"Set the outgoing shippings the option to **Ship directly from stock (Ship " +"Only)**" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:30 +#: ../../inventory/management/delivery/two_steps.rst:68 +msgid "Create a Sales Order" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:32 +msgid "" +"Create a sales order (From quotation to sales order) with some products to " +"deliver." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:35 +msgid "" +"Notice that we now see ``1`` delivery associated with this sales order in " +"the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:41 +msgid "" +"If you click on the **1 Delivery** stat button, you should now see your " +"picking." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:45 +#: ../../inventory/management/delivery/three_steps.rst:99 +#: ../../inventory/management/delivery/two_steps.rst:88 +msgid "Process a Delivery" +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:47 +#: ../../inventory/management/delivery/three_steps.rst:143 +#: ../../inventory/management/delivery/two_steps.rst:113 +msgid "" +"Go to **Inventory** and click on the **# TO DO** link under the **Delivery " +"Orders** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:53 +#: ../../inventory/management/delivery/three_steps.rst:110 +#: ../../inventory/management/delivery/three_steps.rst:130 +#: ../../inventory/management/delivery/three_steps.rst:149 +#: ../../inventory/management/delivery/two_steps.rst:99 +#: ../../inventory/management/delivery/two_steps.rst:119 +#: ../../inventory/management/incoming/three_steps.rst:99 +msgid "Click on the picking that you want to process." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:55 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"**customer**." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:58 +msgid "" +"This has completed the **Shipping Step** and the WH/OUT should now show " +"**Done** in the status column at the top of the page, which means the " +"product has been shipped to the customer." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:3 +msgid "How can you change the packaging type for your sale order?" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:8 +msgid "" +"Odoo gives you the possibility to change the default packaging type and " +"adapt the packaging the way you want it, depending on the weight of the " +"order." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:15 +msgid "" +"In the **Inventory** module, Go to **Configuration** and then click on " +"**Settings**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:18 +msgid "" +"In :menuselection:`Traceability --> Packages`, flag **Record packages used " +"on packing : pallets, boxes,...**" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:24 +msgid "*Sale process*" +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:26 +msgid "In the **Sales** module, go to **Sales** and click on **Sale Order**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:28 +msgid "Create your new Sale Order, and **Confirm the Sale**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:33 +msgid "" +"Once you've confirmed the Sale, you need to click on **Delivery**, to be " +"redirected to the Delivery order." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:36 +msgid "Click on **Edit**, and you can now change the packaging." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:41 +msgid "" +"In the **Operations** tab, in the last column, change the **0** and put the " +"number of products that you want to pack together. Then click on **Put in " +"Pack**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:48 +msgid "" +"Choose the type of packaging that you want. You can also see that the weight" +" has been adapted to your package, and you can change it manually if you " +"want it to be more precise. Then click on **Save**." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:52 +msgid "Repeat the operation until all the products are put in pack." +msgstr "" + +#: ../../inventory/management/delivery/packaging_type.rst:54 +msgid "Finally, click on **Validate** to confirm the delivery." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:3 +msgid "How is the scheduled delivery date computed?" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:5 +msgid "" +"Scheduled dates are computed in order to be able to plan deliveries, " +"receptions and so on. Depending on the habits of your company Odoo " +"automatically generates scheduled dates via the scheduler. The Odoo " +"scheduler computes everything per line, whether it's a manufacturing order, " +"a delivery order, a sale order, etc. The dates that are computed are " +"dependent on the different leads times configured in Odoo." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:13 +msgid "Configuring lead times" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:15 +msgid "" +"Configuring **lead times** is a first essentiel move in order to compute " +"scheduled dates. Lead times are the delays (in term of delivery, " +"manufacturing, ...) promised to your different partners and/or clients." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:19 +msgid "Configuration of the different lead times are made as follows:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:22 +msgid "At a product level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:24 +msgid "**Supplier lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:26 +msgid "" +"Is the time needed for the supplier to deliver your purchased product. To " +"configure the supplier lead time select a product, and go in the " +"**Inventory** tab. You will have to add a vendor to your product in order to" +" select a supplier lead time." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:35 +msgid "" +"Do not forget that it is possible to add different vendors and thus " +"different delivery lead times depending on the vendor." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:38 +msgid "" +"Once a vendor is selected, just open its form and fill its **Delivery lead " +"time**. In this case security days have no influence, the scheduled delivery" +" days will be equal to: **Date** of the purchase order + **Delivery Lead " +"Time**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:46 +msgid "**Customer lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:48 +msgid "" +"Customer lead time is the time needed to get your product from your store / " +"warehouse to your customer. It can be configured for any product. Simply " +"select a product, go into the sales tab and indicate your **Customer lead " +"time**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:56 +msgid "**Manufacturing lead time**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:58 +msgid "" +"At the same page it is possible to configure the **Manufacturing Lead Time**" +" as well. Manufacturing lead time is the time needed to manufacture the " +"product." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:63 +msgid "" +"Don't forget to tick the manufacturing box in inventory if you want to " +"create manufacturing routes." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:67 +msgid "At the company level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:69 +msgid "" +"At company level, it is possible to configure **security days** in order to " +"cope with eventual delays and to be sure to meet your engagements. The idea " +"is to subtract **backup** days from the **computed scheduled date** in case " +"of delays." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:74 +msgid "**Sales Safety days**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:76 +msgid "" +"Sales safety days are **back-up** days to ensure you will be able to deliver" +" your clients engagements in times. They are margins of errors for delivery " +"lead times. Security days are the same logic as the early wristwatch, in " +"order to arrive on time. The idea is to subtract the numbers of security " +"days from the calculation and thus to compute a scheduled date earlier than " +"the one you promised to your client. In that way you are sure to be able to " +"keep your commitment." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:84 +msgid "" +"To set ut your security dates, go to :menuselection:`Settings --> General " +"settings` and click on **Configure your company data**." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:90 +msgid "" +"Once the menu is open, go in the configuration tab and indicate the number " +"of safety days." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:93 +msgid "**Purchase Safety days**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:95 +msgid "Purchase days follow to the same logic than sales security days." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:97 +msgid "" +"They are margins of error for vendor lead times. When the system generates " +"purchase orders for procuring products, they will be scheduled that many " +"days earlier to cope with unexpected vendor delays. Purchase lead time can " +"be found in the same menu as the sales safety days" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:106 +msgid "" +"Note that you can also configure a default Manufacturing lead time from " +"here." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:110 +msgid "At route level" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:112 +msgid "" +"The internal transfers that a product might do due to the movement of stocks" +" can also influence the computed date." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:115 +msgid "" +"The delays due to internal transfers can be specified in the **inventory** " +"app when creating a new push rule in a route." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:118 +msgid "Go to the push rules section on a route form to set a delay." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:124 +msgid "At sale order level:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:126 +msgid "**Requested date**:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:128 +msgid "" +"Odoo offers the possibility to select a requested date by the client by " +"indicating the date in the other information tab of the sales order. If this" +" date is earlier than the theoreticaly computed date odoo will automatically" +" display a warning." +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:139 +msgid "" +"As an example, you may sell a car today (January 1st), that is purchased on " +"order, and you promise to deliver your customer within 20 days (January 20)." +" In such a scenario, the scheduler may trigger the following events, based " +"on your configuration:" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:144 +msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:146 +msgid "" +"January 18: receive the product from your supplier (1 day of Purchase days)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:149 +msgid "" +"January 10: deadline to order at your supplier (9 days of supplier delivery " +"lead time)" +msgstr "" + +#: ../../inventory/management/delivery/scheduled_dates.rst:152 +msgid "" +"January 8: trigger a purchase request to your purchase team, since the team " +"need on average 2 days to find the right supplier and order." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:3 +msgid "How to process delivery orders in three steps (pick + pack + ship)?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default on a **one-step** operation: once all goods are available," +" they can be shipped in bulk in a single delivery order. However, that " +"process may not reflect the reality and your company may require more steps " +"before shipping." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:14 +msgid "" +"With the **three steps** process (**Pick + Pack + Ship**), the items are " +"transferred to a packing area, where they will be assembled by area of " +"destination, and then set to outbound trucks for final delivery to the " +"customers." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:19 +msgid "" +"A few configuration steps are necessary in order to accomplish **Pick + Pack" +" + Ship** in Odoo. These steps create some additional locations, which by " +"default are called **Output** and **Packing Zone**. So, if your warehouse's " +"code is ``WH``, this configuration will create a location called " +"``WH/Output`` and another one called ``WH/Packing Zone``." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:25 +msgid "" +"Goods will move from **WH/Stock** to **WH/Packing Zone** in the first step. " +"Then move from **WH/Packing Zone** to **WH/Output**. Then finally it will be" +" delivered from **WH/Output** to its **final destination**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:30 +#: ../../inventory/management/delivery/two_steps.rst:25 +msgid "" +"Check out :doc:`inventory_flow` to determine if this inventory flow is the " +"correct method for your needs." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:37 +msgid "Install the Inventory module" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:39 +msgid "From the **App** menu, search and install the **Inventory** module." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:44 +msgid "" +"You will also need to install the **Sales** module to be able to issue sales" +" orders." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:48 +msgid "Allow managing routes" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:50 +msgid "" +"Odoo configures movement of delivery orders via **routes**. Routes provide a" +" mechanism to link different actions together. In this case, we will link " +"the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:54 +msgid "" +"To allow management of routes, go to :menuselection:`Configuration --> " +"Settings`" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:56 +msgid "" +"Under :menuselection:`Location & Warehouse --> Routes`, activate the radio " +"button **Advanced routing of products using rules**. Make sure that the " +"option **Manage several locations per warehouse** is activated as well." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:64 +msgid "Configure the warehouse for Pick + Pack + Ship" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:66 +msgid "" +"Go to :menuselection:`Configuration --> Warehouses` and edit the warehouse " +"that will be used." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:69 +msgid "" +"For outgoing shippings, set the option to **Make packages into a dedicated " +"location, bring them to the output location for shipping (Pick + Pack + " +"Ship).**" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:77 +msgid "Create a Sale Order" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:79 +msgid "" +"From the **Sale** module, create a sales order with some products to " +"deliver." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:81 +msgid "" +"Notice that we now see ``3`` transfers associated with this sales order in " +"the **stat button** above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:87 +msgid "If you click the button, you should now see three different pickings:" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:89 +msgid "The first with a reference **PICK** to designate the picking process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:91 +msgid "" +"The second one with the reference **PACK** that is the packing process," +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:93 +msgid "The last with a reference **OUT** to designate the shipping process." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:102 +#: ../../inventory/management/delivery/two_steps.rst:91 +msgid "How to Process the Picking Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:104 +msgid "" +"Ensure that you have enough product in stock and Go to **Inventory** and " +"click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:112 +#: ../../inventory/management/delivery/two_steps.rst:101 +msgid "Click on **Reserve** to reserve the products if they are available." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:114 +msgid "" +"Click on **Validate** to complete the move from **WH/Stock** to **WH/Packing" +" Zone**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:116 +msgid "" +"This has completed the picking Step and the **WH/PICK** should now show " +"**Done** in the status column at the top of the page. The product has been " +"moved from **WH/Stock** to **WH/Packing Zone** location, which makes the " +"product available for the next step (Packing)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:122 +msgid "How to Process the Packing Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:124 +msgid "" +"Go to **Inventory** and click on the **# TRANSFERS** link under the **Pack**" +" kanban card." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:132 +msgid "" +"Click on **Validate** to complete the move from **WH/Packing Zone** to " +"**WH/Output**." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:135 +msgid "" +"This has completed the packing step and the **WH/PACK** should now show " +"**Done** in the status column at the top of the page. The product has been " +"moved from **WH/Packing Zone** to **WH/Output location**, which makes the " +"product available for the next step (Shipping)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:141 +#: ../../inventory/management/delivery/two_steps.rst:111 +msgid "How to Process the Shipping Step?" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:151 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"**customer** (Click **Apply** to assign the quantities based on the " +"quantities listed in the **To Do** column)." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:155 +msgid "" +"This has completed the shipping step and the **WH/OUT** should now show " +"**Done** in the status column at the top of the page. The product has been " +"shipped to the customer." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:3 +msgid "How to process delivery orders in two steps (pick + ship)?" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:8 +msgid "" +"When an order goes to the shipping department for final delivery, Odoo is " +"set up by default to utilize a **one-step** operation: once all goods are " +"available, they are able to be shipped in a single delivery order. However, " +"your company's business process may have one or more steps that happen " +"before shipping. In the **two steps** process, the items in a delivery order" +" are **picked** in the warehouse and brought to an **output location** for " +"**shipping**. The goods are then shipped." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:16 +msgid "" +"In order to accomplish a **Pick + Ship** delivery in Odoo, there are a few " +"necessary configuration steps. These steps create an additional location, " +"which by default is called **Output**. So, if your warehouse's code is " +"``WH``, this configuration will create a location called ``WH/Output``. " +"Goods will move from ``WH/Stock`` to ``WH/Output`` in the first step " +"(picking). Then, they move from ``WH/Output`` to ``WH/Customers`` (in the " +"case of sales orders) in the second step (shipping)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:32 +msgid "Allow management of routes" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:34 +msgid "" +"Odoo configures movement of delivery orders via the **routes**. Routes " +"provide a mechanism to chain different actions together. In this case, we " +"will chain the picking step to the shipping step." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:38 +msgid "" +"To allow management of routes, go to :menuselection:`Configuration --> " +"Settings`." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:40 +msgid "" +"Ensure that the radio button **Advanced routing of products using rules** is" +" checked." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:46 +msgid "" +"Click on **Apply** at the top of the page to save changes (if you needed to " +"check the radio button above)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:50 +msgid "" +"If you checked option **Advanced routing of products using rules** you may " +"need to activate **Manage several locations per warehouse** if it wasn't " +"activated beforehand." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:55 +msgid "Configure warehouse for Pick + Ship" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:57 +msgid "" +"To configure a **Pick + Ship** move, go to :menuselection:`Configuration -->" +" Warehouses` and edit the warehouse that will be used." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:61 +msgid "" +"For outgoing shippings, set the option to **Bring goods to output location " +"before shipping (Pick + Ship)**" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:70 +msgid "" +"Install the **Sale** if it is not the case, and create a sales order with " +"some products to deliver." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:73 +msgid "" +"Notice that we now see ``2`` transfers associated with this sales order in " +"the **Delivery** stat button above the sales order." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:79 +msgid "" +"If you click on the **2 Transfers** stat button, you should now see two " +"different pickings, one with a reference **PICK** to designate the picking " +"process and another with a reference **OUT** to designate the shipping " +"process." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:93 +msgid "" +"Ensure that you have enough product in stock, and go to **Inventory** and " +"click on the **Waiting** link under the **Pick** kanban card." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:103 +msgid "" +"Click on **Validate** to complete the move from **WH/Stock** to " +"**WH/Output**." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:105 +msgid "" +"This has completed the picking step and the **WH/PICK** move should now show" +" **Done** in the status column at the top of the page. The product has been " +"moved from **WH/Stock** to **WH/Output** location, which makes the product " +"**available for the next step** (Shipping)." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:121 +msgid "" +"Click on **Validate** to complete the move from **WH/Output** to the " +"customer (Click **Apply** to assign the quantities based on the quantities " +"listed in the **To Do** column)" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:125 +msgid "" +"This has completed the shipping step and the **WH/OUT** move should now show" +" **Done** in the status column at the top of the page. The product has been " +"shipped to the customer." +msgstr "" + +#: ../../inventory/management/incoming.rst:3 +msgid "Incoming Shipments" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:3 +msgid "How to choose the right flow to handle receipts?" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:8 +msgid "" +"Depending on factors such as the type of items you receive, the size of your" +" warehouse, the number of receipt you register everyday... the way you " +"handle receipts to your customers can vary a lot." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:12 +msgid "" +"Odoo allows you to handle receipts from your warehouse in 3 different ways:" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:15 +msgid "**One step**: Receive goods directly in stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:17 +msgid "**Two steps**: Unload in input location then go to stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:19 +msgid "" +"**Three steps**: Unload in input location, go through a quality control " +"before being admitted in stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:22 +msgid "" +"Odoo uses **routes** to define exactly how you will handle the different " +"receipt steps. The configuration is done at the level of the warehouse. In " +"standard, the reception is a one step process, but changing the " +"configuration can allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:27 +msgid "The principles are the following:" +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:29 +msgid "**One step**: You receive the goods directly in your stock." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:31 +msgid "" +"**Two steps**: You receive the goods in an input area then transfer them " +"from input area to your stock. As long as the goods are not transferred in " +"your stock, they will not be available for further processing." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:36 +msgid "" +"**Three steps**: In many companies, it is necessary to assess the received " +"good. The goal is to check that the products correspond to the quality " +"requirements agreed with the suppliers. Adding a quality control step in the" +" goods receipt process can become essential." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:42 +msgid "" +"You receive the goods in an input area, then transfer them into quality area" +" for quality control. When your quality check process finishes then you can " +"move the goods from QC to stock. Of course, you may change the quantity and " +"only transfer to Stock the quantity that is valid and decide that you will " +"return the quantity that is not good." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:55 +msgid "This is the default configuration in Odoo." +msgstr "" + +#: ../../inventory/management/incoming/handle_receipts.rst:68 +#: ../../inventory/management/incoming/three_steps.rst:126 +#: ../../inventory/management/incoming/two_steps.rst:97 +msgid ":doc:`../delivery/inventory_flow`" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:3 +msgid "How to add a quality control step in goods receipt? (3 steps)" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:8 +msgid "" +"In many companies, it is necessary to assess the received good. The goal is " +"to check that the products correspond to the quality requirements agreed " +"with the suppliers. Therefore, adding a quality control step in the goods " +"receipt process can become essential." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:13 +#: ../../inventory/management/incoming/two_steps.rst:8 +msgid "" +"Odoo uses routes to define exactly how you will handle the different receipt" +" steps. The configuration is done at the level of the warehouse. By default," +" the reception is a one step process, but changing the configuration can " +"allow to have 2 or even 3 steps." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:18 +msgid "" +"The 3 steps flow is as follows: You receive the goods in an input area, then" +" transfer them into quality area for quality control. When the quality check" +" has been processed, you can move the goods from QC to stock. Of course, you" +" may change the quantity and only transfer to stock the quantity that is " +"valid and decide that you will return the quantity that is not good." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:25 +#: ../../inventory/management/incoming/two_steps.rst:18 +msgid "This is the case that will be explained in this document." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:31 +#: ../../inventory/management/incoming/two_steps.rst:24 +msgid "Use advanced routes" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:33 +msgid "" +"To allow management of routes, go to the menu :menuselection:`Inventory --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:39 +#: ../../inventory/management/incoming/two_steps.rst:32 +msgid "" +"Ensure that the routes option **Advance routing of product using rules** is " +"checked, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:42 +msgid "" +"Make sure that **Manage several locations per warehouse** is also ticked." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:46 +msgid "How to add a quality control step in goods receipt?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:48 +msgid "" +"Go to the menu :menuselection:`Inventory --> Configuration --> Warehouse` " +"and choose the warehouse where you want to change reception methods." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:51 +msgid "" +"By default, warehouses are configured with one step reception (**Receive " +"goods directly into stock**)." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:54 +msgid "" +"To add quality control before transfer goods into stock location, tick " +"**Unload in input location, go through a quality control before being " +"admitted in stock (3 steps)**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:62 +msgid "How to control a receipt?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:65 +msgid "How to process the receipt step ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:67 +msgid "" +"In the **Purchase** app, create a **Request for Quotation**. Click on the " +"**Confirm order** button. You can see that there is one **Shipment** related" +" to purchase order in the stat button above the purchase order form view. " +"This is the receipt step." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:75 +msgid "" +"Go to **Inventory** and click on the link **# TO RECEIVE** in the " +"**Receipts** card." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:80 +msgid "" +"Click on the receipt that you want to process. Click on **Validate** to " +"complete the move from the **Vendor** location to **WH/Input**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:83 +msgid "" +"This has completed the receipt step and the status column at the top of the " +"page for **WH/IN** should now show **Done**. The product has been moved from" +" the **Vendor** to the **WH/Input** location, which makes the product " +"available for the next step (Move to the quality control zone)" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:89 +msgid "" +"How to move your product from the receipt zone to the quality control zone ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:91 +msgid "" +"Go to the **Inventory** dashboard. You will see that there is one transfer " +"ready (the move to the quality control zone) and one waiting (the move to " +"the stock after the control). Click on the link **# TRANSFERS** in the " +"**Internal Transfers** to process the quality control." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:101 +msgid "" +"Click on **Validate** to complete the move from **WH/Input** to **WH/Quality" +" Control**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:104 +msgid "" +"This has completed the internal transfer step and the status column at the " +"top of the page for **WH/INT** should now show **Done**. The receipt is now " +"ready to be controlled." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:109 +msgid "How to to process the quality control ?" +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:111 +msgid "" +"Go back to the **Inventory** dashboard. The waiting transfer is now ready. " +"Click on the link **# TRANSFERS** in the **Internal Transfers** card to " +"process the quality control." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:118 +msgid "" +"Click on the last picking to process. Click on **Validate** to complete the " +"move from **WH/Quality Control** to **WH/Stock**." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:121 +msgid "" +"This has completed the quality control step and the status column at the top" +" of the page for **WH/INT** should now show **Done**. The receipt has been " +"controlled and has moved to your stock." +msgstr "" + +#: ../../inventory/management/incoming/three_steps.rst:127 +msgid ":doc:`two_steps`" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:3 +msgid "How to unload your shipment to an input location? (2 steps)" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:13 +msgid "" +"The 2 steps flow is the following : You receive the goods in an input area " +"then transfer them from input area to your stock. As long as the goods are " +"not transferred in your stock, they will not be available for further " +"processing." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:26 +msgid "" +"To allow management of routes, go to the menu :menuselection:`Inventory --> " +"Configuration --> Settings`" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:35 +msgid "" +"Make sure that **\"Manage several locations per warehouse\"** is also " +"ticked." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:39 +msgid "How to configure your warehouse ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:41 +msgid "" +"Go to the the menu :menuselection:`Inventory --> Configuration --> " +"Warehouse` and choose the warehouse where you want to change reception " +"methods." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:44 +msgid "" +"By default, warehouses are configured with one step reception (option " +"**Receive goods directly into stock**)." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:47 +msgid "" +"To add the control step, tick **Unload in input location then go to stock (2" +" steps)**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:54 +msgid "How to receipt a shipment in 2 steps?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:57 +msgid "How to process the Receipt step ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:59 +msgid "" +"In the purchase module, create a **Request for Quotation**, then click on " +"the **Confirm order** button. You can see that there is one **Shipment** " +"related to purchase order in the **stat button** above the purchase order " +"form view. This is the receipt step." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:67 +msgid "" +"Go to **Inventory** and click on the **# TO RECEIVE** link on the " +"**Receipts** card." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:73 +msgid "" +"Click on the receipt that you want to process, then click on **Validate** to" +" complete the move from the **Vendor** to **WH/Input**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:76 +msgid "" +"This has completed the Receipt Step and the move refered with **WH/IN**. The" +" product has been moved from the **Vendor** to the **WH/Input** location, " +"which makes the product available for the next step." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:81 +msgid "How to to transfer the receipt to your stock ?" +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:83 +msgid "" +"Go back to the **Inventory** dashboard. The waiting transfer is now ready. " +"Click on the **# TRANSFERS** in the **Internal Transfers** to process the " +"quality control." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:90 +msgid "" +"Click on the picking you want to process. Click on **Validate** to complete " +"the move from **WH/Input** to **WH/Stock**." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:93 +msgid "" +"This has completed the internal transfer step and the move refered with " +"**WH/INT**. The receipt has been moved to your stock." +msgstr "" + +#: ../../inventory/management/incoming/two_steps.rst:98 +msgid ":doc:`three_steps`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers.rst:3 +msgid "Lots and Serial Numbers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:3 +msgid "What's the difference between lots and serial numbers?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:6 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:6 +#: ../../inventory/management/misc/owned_stock.rst:6 +#: ../../inventory/settings/products/variants.rst:170 +msgid "Introduction" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:8 +msgid "" +"In Odoo, lots and serial numbers have similarities in their functional " +"system but are different in their behavior. They are both managed within the" +" **Inventory**, **Purchases** and **Sales** app." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:12 +msgid "" +"**Lots** correspond to a certain number of products you received and store " +"altogether in one single pack." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:15 +msgid "" +"**Serial numbers** are identification numbers given to one product in " +"particular, to allow to track the history of the item from reception to " +"delivery and after-sales." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:20 +msgid "When to use" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:22 +msgid "" +"**Lots** are interesting for products you receive in great quantity and for " +"which a lot number can help in reportings, quality controls, or any other " +"info. Lots will help identify a number of pieces having for instance a " +"production fault. It can be useful for a batch production of clothes or " +"food." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:28 +msgid "" +"**Serial numbers** are interesting for items that could require after-sales " +"service, such as smartphones, laptops, fridges, and any electronic devices. " +"You could use the manufacturer's serial number or your own, depending on the" +" way you manage these products" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:34 +msgid "When not to use" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:36 +msgid "" +"Storing consumable products such as kitchen roll, toilet paper, pens and " +"paper blocks in lots would make no sense at all, as there are very few " +"chances that you can return them for production fault." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:40 +msgid "" +"On the other hand, giving a serial number to every product is a time-" +"consuming task that will have a purpose only in the case of items that have " +"a warranty and/or after-sales services. Putting a serial number on bread, " +"for instance, makes no sense at all." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:46 +#: ../../inventory/management/lots_serial_numbers/lots.rst:135 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/differences.rst:47 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:129 +msgid ":doc:`lots`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:3 +msgid "How to manage lots of identical products?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:8 +msgid "" +"Lots are useful for products you receive in great quantity and for which a " +"lot number can help in reportings, quality controls, or any other info. Lots" +" will help identify a number of pieces having for instance a production " +"fault. It can be useful for a batch production of clothes or food." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:14 +msgid "" +"Odoo has the capacity to manage lots ensuring compliance with the " +"traceability requirements imposed by the majority of industries." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:17 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:15 +msgid "" +"The double-entry management in Odoo enables you to run very advanced " +"traceability." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:21 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:19 +msgid "Setting up" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:24 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:22 +msgid "Application configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:26 +msgid "" +"You need activate the tracking of lots in the settings. In the **Inventory**" +" application, go to :menuselection:`Configuration --> Settings`, select " +"**Track lots or serial numbers**" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:33 +msgid "" +"In order to have an advanced management of the lots, you should also select " +"**Manage several locations per warehouse**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:39 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:31 +#: ../../inventory/shipping/operation/labels.rst:27 +#: ../../inventory/shipping/setup/third_party_shipper.rst:26 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:42 +msgid "Operation types configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:44 +msgid "" +"You also need to set up how you will manage lots for each operations. In the" +" **Inventory** application, go to :menuselection:`Configuration --> " +"Operation Types`." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:48 +msgid "" +"For each type (receipts, internal transfers, deliveries,...), you can set if" +" you can create new lot numbers or only use existing lot numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:57 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:36 +msgid "" +"Finally, you have to configure which products you want to track in lots." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:59 +msgid "" +"Go into :menuselection:`Inventory Control --> Products`, and open the " +"product of your choice. Click on **Edit**, and in the **Inventory** tab, " +"select **Tracking by Lots**, then click on **Save**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:67 +msgid "Manage lots" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:70 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:49 +msgid "Transfers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:72 +msgid "" +"In order to process a transfer of a product tracked by lot, you have to " +"input the lot number(s)." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:75 +msgid "Click on the lot icon :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:80 +msgid "" +"A window will pop-up. Click on **Add an item** and fill in the lot number " +"and the quantity." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:86 +msgid "" +"Depending on your operation type configuration, you will be able to fill in " +"new lot numbers, or only use existing ones." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:90 +msgid "In the scanner interface, you just have to scan the lot numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:93 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:79 +msgid "Inventory adjustment" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:95 +msgid "Inventory of a product tracked by lot can be done in 2 ways:" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:97 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:83 +msgid "Classic inventory by products" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:99 +msgid "Inventory of a lot" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:101 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:87 +msgid "" +"When doing a classic inventory, there is a **Serial Number** column. If the " +"product has already been assigned with a number, it is already pre-filled." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:105 +msgid "" +"Click on **Add an item** if the product has not been inventoried yet. You " +"can easily create lots, just type in a new lot number in the column." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:111 +msgid "" +"You can also just do the inventory of a lot. In this case, you will have to " +"fill in the **Lot number**. You can also create a new lot from here. Just " +"type in the number, a window will pop out to link the number to a product." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:120 +msgid "Lots traceability" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:122 +msgid "" +"You can check the lot traceability from :menuselection:`Inventory --> " +"Inventory Control --> Serial Numbers/Lots`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:128 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:122 +msgid "You can have more details by clicking on the **Traceability** button :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:134 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:128 +msgid ":doc:`differences`" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:3 +msgid "How to work with serial numbers?" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:8 +msgid "" +"Serial Number Tracking is used to track products with serial numbers on " +"every transactions. You can track the current location of the product with " +"serial numbers. When the products are moved from one location to another " +"location, the system will automatically identify the current location of the" +" product based on last movement of the product. So you can get the last " +"location where the products are moved." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:24 +msgid "" +"You need activate the tracking of serial numbers in the settings. In the " +"**Inventory** application, go to :menuselection:`Configuration --> " +"Settings`, select **Track lots or serial numbers**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:38 +msgid "" +"Go into :menuselection:`Inventory Control --> Products`, and open the " +"product of your choice. Click on **Edit**, and in the **Inventory** tab, " +"select **By Unique Serial Number**, then click on **Save**." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:46 +msgid "Manage Serial Numbers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:51 +msgid "" +"In order to process a transfer of a product tracked by serial number, you " +"have to input the number(s). In order to be able to assign serial numbers to" +" products with tracking features enabled you will first need to mark your " +"transfer as to do. Click on the **Mark as TODO** button to display the Lot " +"Split icon." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:57 +msgid "Click on the serial number icon :" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:62 +msgid "" +"A window will pop-up. Click on **Add an item** and fill in the serial " +"numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:68 +msgid "" +"If you move products that already have serial numbers assigned, those will " +"appear in the list. Just click on the **+** icon to to confirm that you are " +"moving those serial numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:76 +msgid "In the scanner interface, you just have to scan the serial numbers." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:81 +msgid "" +"Inventory of a product tracked by serial numbers can be done in 2 ways:" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:85 +msgid "Inventory of a serial number" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:91 +msgid "" +"Click on **Add an item** if the product has not been inventoried yet. You " +"can easily create serial numbers, just type in a new number in the column." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:98 +msgid "The quantity should be 1 for each line." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:100 +msgid "" +"You can also just do the inventory of a serial number. In this case, you " +"will have to fill in the serial number. You can also create a new one from " +"here. Just type in the number, a window will pop out to link it to a " +"product." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:109 +msgid "Serial Number traceability" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:111 +msgid "" +"The serial number given to these items allow you to keep track of where they" +" were received, put in stock, to whom they were sold and where they were " +"shipped to." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:115 +msgid "" +"To track an item, open the **Inventory** module, and in " +":menuselection:`Inventory Control --> Serial Numbers/lots`, click on the " +"serial number corresponding to your search." +msgstr "" + +#: ../../inventory/management/misc.rst:3 +msgid "Miscellaneous Operations" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:3 +msgid "How to manage stock that you don't own?" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:8 +msgid "" +"Some suppliers can sometimes offer you to store and sell products without " +"having to buy those items: this technique is called **consignee stock**." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:12 +msgid "" +"Consignee stock is a great way for manufacturers and suppliers to launch new" +" products. As resellers may be reluctant to buying a product that they are " +"not sure to be able to sell, consignee stock will allow them to propose an " +"item to check its market without having to pay for it in the first place." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:18 +msgid "" +"Odoo has the ability to manage consignee stocks through the advanced " +"settings." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:24 +msgid "" +"Open the menu :menuselection:`Inventory --> Configuration --> Settings`, and" +" in the **Product Owners** section, select **Manage consignee stocks " +"(advanced)**, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:32 +msgid "Reception of Consignee Stock" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:34 +msgid "" +"In the Inventory's Dashboard, open the **Receipts** and create a new " +"reception. You can see that in the right side of the page, a new **Owner** " +"line has appeared. You can specify the partner which owns the stock or leave" +" it blank if you are the owner." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:3 +msgid "How to configure and run schedulers?" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:6 +msgid "What is a scheduler" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:8 +msgid "" +"The scheduler is the calculation engine which plans and prioritises " +"production and purchasing automatically according to the rules defined on " +"products. By default, the scheduler is set to run once a day (Odoo " +"automatically creates a **Scheduled Action** for this)." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:14 +msgid "Calculating Requirements / Scheduling" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:16 +msgid "" +"Scheduling only validates procurements that are confirmed but not yet " +"started. These procurement reservations will themselves start production, " +"tasks or purchases depending on the configuration of the requested product." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:21 +msgid "" +"You take into account the priority of operations when starting reservations " +"and procurements. Urgent requests, those with a date in the past, or " +"requests with a date earlier than the others will be started first. In case " +"there are not enough products in stock to satisfy all the requests, you can " +"be sure that the most urgent requests will be produced first." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:29 +msgid "Configure and run the scheduler" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:32 +msgid "Run the scheduler manually" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:34 +msgid "" +"This feature is not visible by default. You have to enable **debug mode** to" +" see this. To enable debug mode, go to :menuselection:`Help --> About` and " +"click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:38 +msgid "" +"You can also start the scheduler manually from the menu " +":menuselection:`Inventory --> Schedulers --> Run Schedulers`. The scheduler " +"uses all the relevant parameters defined for products, suppliers and the " +"company to determine the priorities between the different production orders," +" deliveries and supplier purchases." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:48 +msgid "Configure and run the scheduler (only for advanced users)" +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:50 +msgid "" +"This feature is not visible by default. You have to enable **debug mode** to" +" see this. To enable debug mode, go to :menuselection:`Help -> About` and " +"click on **Activate the developer mode**." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:54 +msgid "" +"You can set the starting time of the scheduler by modifying the " +"corresponding action in the menu :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`. Modify the Run mrp Scheduler " +"configuration." +msgstr "" + +#: ../../inventory/management/misc/schedulers.rst:63 +msgid ":doc:`../delivery/scheduled_dates`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:3 +msgid "How to scrap products?" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:8 +msgid "" +"Scrap means waste that either has no economic value or only the value of its" +" basic material" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:11 +msgid "content recoverable through recycling." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:13 +msgid "" +"In your warehouse you sometimes find products that are damaged or that are " +"unusable due to expiry or for some other reason. You often notice this " +"during picking or physical inventory." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:17 +msgid "" +"Since you cannot normally sell or store these products, you have to scrap " +"product." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:20 +msgid "" +"When goods are scrapped they are not reflected in the system as a part of " +"the inventory. The scrapped material will be physically moved to scrap area." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:27 +msgid "" +"When you install inventory management, odoo automatically creates one " +"default scrap location, namely **Virtual location/Scrapped**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:30 +msgid "" +"To create an extra scrap location, Go to :menuselection:`Inventory --> " +"Configuration --> Setting` and check **Manage several locations per " +"warehouse**, then click on **Apply**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:38 +msgid "" +"After applying **Manage several location per warehouse**, you can create a " +"new scrap location in :menuselection:`Configuration --> Warehouse Management" +" --> Locations.`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:43 +msgid "" +"To define a scrap location, you have to check **Is a Scrap Location?** on " +"location form view." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:47 +msgid "Different ways to scrap product" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:49 +msgid "Odoo provides several ways to scrap products." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:52 +msgid "1) Scrap from Receipt (Initial Demand tab)." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:54 +msgid "" +"To scrap product from incoming shipment, Go to :menuselection:`Inventory -->" +" Dashboard --> Receipts`." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:60 +msgid "" +"Open the incoming shipment, and in the **Initial demand** tab, click on the " +"scrap products button." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:67 +msgid "2) Scrap from delivery order (Initial Demand tab) ." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:69 +msgid "" +"To scrap product from outgoing shipment, Go to :menuselection:`Inventory -->" +" Dashboard --> Delivery Orders`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:75 +msgid "" +"Open the outgoing shipment, and in the **Initial demand** tab, click on the " +"scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:82 +msgid "3) Scrap from internal transfer (Initial Demand tab)." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:84 +msgid "" +"To scrap product from internal transfer, Go to :menuselection:`Inventory -->" +" Dashboard --> Receipts`" +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:90 +msgid "" +"Open the internal transfer, and in the **Initial demand** tab, click on the " +"scrap products button on stock move in initial demand tab." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:96 +msgid "" +"When you click on scrap button, a popup will open. You can enter the " +"quantity of products, and specify the scrap location, then click on " +"**Scrap**." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:104 +msgid "" +"To allow change scrap location on wizard, you have to select **Manage " +"several location per warehouse** in the settings at " +":menuselection:`Inventory --> Configuration --> Setting`" +msgstr "" + +#: ../../inventory/management/reporting.rst:3 +msgid "Valuation Methods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:5 +msgid "How to do an inventory valuation? (Anglo-Saxon Accounting)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:7 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:7 +msgid "" +"Every year your inventory valuation has to be recorded in your balance " +"sheet. This implies two main choices:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:10 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:10 +msgid "" +"the way you compute the cost of your stored items (Standard vs. Average vs. " +"Real Price);" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:13 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:13 +msgid "" +"the way you record the inventory value into your books (periodic vs. " +"Perpetual)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:17 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:17 +msgid "Costing Method" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:63 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:64 +msgid "Standard Price" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:28 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:73 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:128 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:181 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:29 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:74 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:129 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:182 +msgid "Operation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:29 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:74 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:129 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:182 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:30 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:75 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:130 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:183 +msgid "Unit Cost" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:30 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:75 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:130 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:183 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:31 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:76 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:131 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:184 +msgid "Qty On Hand" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:31 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:76 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:131 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:184 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:32 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:77 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:132 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:185 +msgid "Delta Value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:32 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:77 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:132 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:185 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:33 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:78 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:133 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:186 +msgid "Inventory Value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:34 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:39 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:44 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:49 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:55 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:84 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:139 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:192 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:202 +msgid "$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:35 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:80 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:135 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:188 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:36 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:81 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:136 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:189 +msgid "0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:37 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:79 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:82 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:134 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:137 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:187 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:190 +msgid "$0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:38 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:83 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:138 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:191 +msgid "Receive 8 Products at $10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:40 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:85 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:140 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:193 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:41 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:86 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:141 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:194 +msgid "8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:41 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:86 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:141 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:194 +msgid "+8*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:42 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:87 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:142 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:195 +msgid "$80" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:43 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:88 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:143 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:196 +msgid "Receive 4 Products at $16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:45 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:90 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:145 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:198 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:46 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:91 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:146 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:199 +msgid "12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:46 +msgid "+4*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:47 +msgid "$120" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:48 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:93 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:148 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:201 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:49 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:94 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:149 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:202 +msgid "Deliver 10 Products" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:50 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:95 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:150 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:203 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:51 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:96 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:151 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:204 +msgid "2" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-10*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:53 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:206 +msgid "$20" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:54 +msgid "Receive 2 Products at $9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:56 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:101 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:156 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:209 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:57 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:102 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:157 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:210 +msgid "4" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:57 +msgid "+2*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:58 +msgid "$40" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:60 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:61 +msgid "" +"**Standard Price** means you estimate the cost price based on direct " +"materials, direct labor and manufacturing overhead at the end of a specific " +"period (usually once a year). You enter this cost price in the product form." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:118 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:119 +msgid "Average Price" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:89 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:94 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:144 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:197 +msgid "$12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:91 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:146 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:199 +msgid "+4*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:92 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:147 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:200 +msgid "$144" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-10*$12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:98 +msgid "$24" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:99 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:154 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:207 +msgid "Receive 2 Products at $6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:100 +msgid "$9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:102 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:157 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:210 +msgid "+2*$6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:103 +msgid "$36" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:105 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:106 +msgid "" +"The **Average Price** method recomputes the cost price as a receipt order " +"has been processed, based on prices defined in tied purchase orders: FORMULA" +" (see here attached)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:109 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:110 +msgid "The average cost does not change when products leave the warehouse." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:111 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:112 +msgid "" +"From an accounting point of view, this method is mainly justified in case of" +" huge purchase price variations and is quite unusual due to its operational " +"complexity. Your actually need a software like Odoo to easily keep this cost" +" up-to-date." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:116 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:117 +msgid "" +"This method is dedicated to advanced users. It requires well established " +"business processes because the order in which you process receipt orders " +"matters in the cost computation." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:171 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:172 +msgid "FIFO" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:149 +msgid "$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-8*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-2*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:153 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:211 +msgid "$32" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:155 +msgid "$11" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:158 +msgid "$44" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:160 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:213 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:161 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:214 +msgid "" +"For **Real Price** (FIFO, LIFO, FEFO, etc), the costing is further refined " +"by the removal strategy set on the warehouse location or product's internal " +"category. The default strategy is FIFO. With such method, your inventory " +"value is computed from the real cost of your stored products (cfr. " +"Quantitative Valuation) and not from the cost price shown in the product " +"form. Whenever you ship items, the cost price is reset to the cost of the " +"last item(s) shipped. This cost price is used to value any product not " +"received from a purchase order (e.g. inventory adjustments)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:170 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:171 +msgid "" +"FIFO is advised if you manage all your workflow into Odoo (Sales, Purchases," +" Inventory). It suits any kind of users." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 +msgid "LIFO (not accepted in IFRS)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-4*$16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:0 +msgid "-6*$10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:208 +msgid "$8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:223 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:224 +msgid "LIFO is not permitted outside the United States." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:225 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:226 +msgid "" +"Odoo allows any method. The default one is **Standard Price**. To change it," +" check **Use a 'Fixed', 'Real' or 'Average' price costing method** in " +"Purchase settings. Then set the costing method from products' internal " +"categories. Categories show up in the Inventory tab of the product form." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:231 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:232 +msgid "" +"Whatever the method is, Odoo provides a full inventory valuation in " +":menuselection:`Inventory --> Reports --> Inventory Valuation` (i.e. current" +" quantity in stock * cost price)." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:236 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:237 +msgid "Periodic Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:238 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:239 +msgid "" +"In a periodic inventory valuation, goods reception and outgoing shipments " +"have no direct impact in the accounting. At the end of the month or year, " +"the accountant posts one journal entry representing the value of the " +"physical inventory." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:243 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:244 +msgid "" +"This is the default configuration in Odoo and it works out-of-the-box. Check" +" following operations and find out how Odoo is managing the accounting " +"postings." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +msgid "Vendor Bill" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "\\" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "Debit" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:253 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:271 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:310 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:254 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:271 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:305 +msgid "Credit" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 +msgid "Assets: Inventory" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:255 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:256 +msgid "50" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 +msgid "Assets: Deferred Tax Assets" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:256 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:257 +msgid "4.68" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 +msgid "Liabilities: Accounts Payable" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:257 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:258 +msgid "54.68" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 +#: ../../inventory/overview/concepts/double-entry.rst:30 +#: ../../inventory/overview/concepts/double-entry.rst:45 +#: ../../inventory/overview/concepts/double-entry.rst:52 +#: ../../inventory/overview/concepts/double-entry.rst:57 +#: ../../inventory/overview/concepts/double-entry.rst:64 +#: ../../inventory/overview/concepts/double-entry.rst:72 +msgid "Configuration:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:261 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:262 +msgid "" +"Purchased Goods: defined on the product or on the internal category of " +"related product (Expense Account field)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:263 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:263 +msgid "" +"Deferred Tax Assets: defined on the tax used on the purchase order line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:264 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:264 +msgid "Accounts Payable: defined on the vendor related to the bill" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:265 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:265 +msgid "Goods Receptions" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:266 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:287 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:266 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:286 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 +msgid "No Journal Entry" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 +msgid "Customer Invoice" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 +msgid "Revenues: Sold Goods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:273 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:273 +msgid "100" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 +msgid "Liabilities: Deferred Tax Liabilities" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:274 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:274 +msgid "9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 +msgid "Assets: Accounts Receivable" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:275 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:275 +msgid "109" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:279 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:279 +msgid "" +"Revenues: defined on the product or on the internal category of related " +"product (Income Account field)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:281 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:280 +msgid "Deferred Tax Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:281 +msgid "Accounts Receivable: defined on the customer (Receivable Account)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:284 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:283 +msgid "" +"The fiscal position used on the invoice may have a rule that replaces the " +"Income Account or the tax defined on the product by another one." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:286 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:285 +msgid "Customer Shipping" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:289 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:288 +msgid "Manufacturing Orders" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:295 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:294 +msgid "" +"At the end of the month/year, your company does a physical inventory or just" +" relies on the inventory in Odoo to value the stock into your books." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:298 +msgid "" +"Then you need to break down the purchase balance into both the inventory and" +" the cost of goods sold using the following formula:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:301 +msgid "" +"Cost of goods sold (COGS) = Starting inventory value + Purchases – Closing " +"inventory value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:303 +msgid "To update the stock valuation in your books, record such an entry:" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 +msgid "Assets: Inventory (closing value)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:312 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:307 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 +msgid "X" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:313 +msgid "Expenses: Cost of Good Sold" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:314 +msgid "Expenses: Purchased Goods" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:315 +msgid "Assets: Inventory (starting value)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:319 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:319 +msgid "Perpetual Inventory Valuation" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:321 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:321 +msgid "" +"In a perpetual inventory valuation, goods receptions and outgoing shipments " +"are posted in your books in real time. The books are therefore always up-to-" +"date. This mode is dedicated to expert accountants and advanced users only. " +"As opposed to periodic valuation, it requires some extra configuration & " +"testing." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:328 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:328 +msgid "Let's take the case of a reseller." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:340 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:340 +msgid "**Configuration:**" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:342 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:342 +msgid "Accounts Receivable/Payable: defined on the partner (Accounting tab)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:344 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:344 +msgid "" +"Deferred Tax Assets/Liabilities: defined on the tax used on the invoice line" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:347 +msgid "" +"Revenues/Expenses: defined by default on product's internal category and can" +" be set in product form (Accounting tab) as a specific replacement value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:351 +msgid "" +"Goods Received Not Purchased: to set as Stock Input Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:354 +msgid "" +"Goods Issued Not Invoiced: to set as Stock Output Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:357 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:352 +msgid "" +"Inventory: to set as Stock Valuation Account in product's internal category" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:359 +msgid "" +"Price Difference: to set in product's internal category or in product form " +"as a specific replacement value" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:364 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:356 +msgid ":doc:`../../routes/strategies/removal`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:365 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:357 +msgid ":doc:`../../../accounting/others/inventory/avg_price_valuation`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:366 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:358 +msgid ":doc:`../../routes/costing/landed_costs`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:5 +msgid "How to do an inventory valuation? (Continental Accounting)" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:35 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:40 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:45 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:50 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:56 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:85 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:140 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:193 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:203 +msgid "€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:38 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:80 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:83 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:135 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:138 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:188 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:191 +msgid "€0" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:39 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:84 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:139 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:192 +msgid "Receive 8 Products at €10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:42 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:87 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:142 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:195 +msgid "+8*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:43 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:88 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:143 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:196 +msgid "€80" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:44 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:89 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:144 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:197 +msgid "Receive 4 Products at €16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:47 +msgid "+4*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:48 +msgid "€120" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-10*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:54 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:207 +msgid "€20" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:55 +msgid "Receive 2 Products at €9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:58 +msgid "+2*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:59 +msgid "€40" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:90 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:95 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:145 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:198 +msgid "€12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:92 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:147 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:200 +msgid "+4*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:93 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:148 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:201 +msgid "€144" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-10*€12" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:99 +msgid "€24" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:100 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:155 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:208 +msgid "Receive 2 Products at €6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:101 +msgid "€9" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:103 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:158 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:211 +msgid "+2*€6" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:104 +msgid "€36" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:150 +msgid "€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-8*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-2*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:154 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:212 +msgid "€32" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:156 +msgid "€11" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:159 +msgid "€44" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-4*€16" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:0 +msgid "-6*€10" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:209 +msgid "€8" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:297 +msgid "" +"Create a journal entry to move the stock variation value from your " +"Profit&Loss section to your assets." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:308 +msgid "Expenses: Inventory Variations" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:311 +msgid "" +"If the stock value decreased, the **Inventory** account is credited and te " +"**Inventory Variations** debited." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:346 +msgid "" +"Revenues/Expenses: defined by default on product's internal category; can be" +" also set in product form (Accounting tab) as a replacement value." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_continental.rst:349 +msgid "" +"Inventory Variations: to set as Stock Input/Output Account in product's " +"internal category" +msgstr "" + +#: ../../inventory/overview/concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:5 +msgid "Double-Entry Inventory Management" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:7 +msgid "" +"A double-entry inventory has no stock input, output (disparition of " +"products) or transformation. Instead, all operations are stock moves between" +" locations (possibly virtual)." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:16 +msgid "Operations" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:18 +msgid "" +"Stock moves represent the transit of goods and materials between locations." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:30 +msgid "Production Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:24 +msgid "Consume:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "2 Wheels: Stock → Production" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bike Frame: Stock → Production" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:26 +msgid "Produce:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:27 +msgid "1 Bicycle: Production → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Stock: the location the Manufacturing Order is initiated from" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Production: on the product form, field \"Production Location\"" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:36 +msgid "Drop-shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:33 +msgid "1 Bicycle: Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:36 +msgid "Configurarion:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Supplier: on the product form" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Customer: on the sale order itself" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:45 +msgid "Client Delivery" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:39 +msgid "Pick" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:40 +msgid "1 Bicycle: Stock → Packing Zone" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:41 +msgid "Pack" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:42 +msgid "1 Bicycle: Packing Zone → Output" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:43 +#: ../../inventory/shipping.rst:3 +msgid "Shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:44 +msgid "1 Bicycle: Output → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "on the pick+pack+ship route for the warehouse" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:52 +msgid "Inter-Warehouse transfer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:49 +msgid "Transfer:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Warehouse 1 → Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Warehouse 2: the location the transfer is initiated from" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Warehouse 1: on the transit route" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:57 +msgid "Broken Product (scrapped)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:55 +msgid "1 Bicycle: Warehouse → Scrap" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:58 +msgid "Scrap: Scrap Location when creating the scrapping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:60 +msgid "Missing products in inventory" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:61 +msgid "1 Bicycle: Warehouse → Inventory Loss" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:62 +msgid "Extra products in inventory" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:63 +msgid "1 Bicycle: Inventory Loss → Warehouse" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:65 +msgid "Inventory Loss: \"Inventory Location\" field on the product" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:72 +msgid "Reception" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Supplier → Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "1 Bicycle: Input → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Supplier: purchase order supplier" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:0 +msgid "Input: \"destination\" field on the purchase order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:75 +msgid "Analysis" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:77 +msgid "" +"Inventory analysis can use products count or products value (= number of " +"products * product cost)." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:80 +msgid "For each inventory location, multiple data points can be analysed:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:148 +msgid "Procurements & Procurement Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:150 +msgid "" +"A procurement is a request for a specific quantity of products to a specific" +" location. They can be created manually or automatically triggered by:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:159 +msgid "New sale orders" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:157 +#: ../../inventory/overview/concepts/double-entry.rst:162 +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "Effect" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:157 +msgid "" +"A procurement is created at the customer location for every product ordered " +"by the customer (you have to deliver the customer)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:160 +msgid "" +"Procurement Location: on the customer, field \"Customer Location\" " +"(property)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:164 +msgid "Minimum Stock Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:163 +msgid "A procurement is created at the rule's location." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:165 +msgid "Procurement location: on the rule, field \"Location\"" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "Procurement rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:168 +msgid "A new procurement is created on the rule's source location" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:170 +msgid "" +"*Procurement rules* describe how procurements on specific locations should " +"be fulfilled e.g.:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:173 +msgid "where the product should come from (source location)" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:174 +msgid "" +"whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made " +"To Stock)`" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:182 +msgid "Routes" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:184 +msgid "" +"Procurement rules are grouped in routes. Routes define paths the product " +"must follow. Routes may be applicable or not, depending on the products, " +"sales order lines, warehouse,..." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:188 +msgid "" +"To fulfill a procurement, the system will search for rules belonging to " +"routes that are defined in (by order of priority):" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:202 +#: ../../inventory/settings/warehouses.rst:3 +msgid "Warehouses" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:194 +msgid "Warehouse Route Example: Pick → Pack → Ship" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:196 +msgid "Picking List:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:197 +msgid "Pick Zone → Pack Zone" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:198 +msgid "Pack List:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:199 +msgid "Pack Zone → Gate A" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:201 +msgid "Delivery Order:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:201 +msgid "Gate A → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:203 +msgid "" +"Routes that describe how you organize your warehouse should be defined on " +"the warehouse." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "A Product" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:205 +msgid "Product Route Example: Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:207 +#: ../../inventory/overview/concepts/double-entry.rst:217 +msgid "Reception:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:208 +#: ../../inventory/overview/concepts/double-entry.rst:218 +msgid "Supplier → Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:209 +msgid "Confirmation:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:210 +msgid "Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "Storage:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:212 +msgid "Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:221 +msgid "Product Category" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:215 +msgid "Product Category Route Example: cross-dock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:219 +msgid "Cross-Docks:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:220 +msgid "Input → Output" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:221 +msgid "Delivery:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:222 +msgid "Output → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Sale Order Line" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:224 +msgid "Sale Order Line Example: Drop-shipping" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Order:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Supplier → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:230 +msgid "Push Rules" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:232 +msgid "" +"Push rules trigger when products enter a specific location. They " +"automatically move the product to a new location. Whether a push rule can be" +" used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:240 +#: ../../inventory/settings/products/uom.rst:88 +msgid "Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:239 +msgid "Product lands in Input" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:240 +msgid "Push 1: Input → Quality Control" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:241 +msgid "Push 2: Quality Control → Stock" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:244 +msgid "Warehouse Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:243 +msgid "Product lands in Transit" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:244 +msgid "Push: Transit → Warehouse 2" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:247 +msgid "Procurement Groups" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:249 +msgid "" +"Routes and rules define inventory moves. For every rule, a document type is " +"provided:" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:252 +msgid "Picking" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:253 +msgid "Packing" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:254 +msgid "Delivery Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:255 +msgid "Purchase Order" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:256 +msgid "..." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:258 +msgid "" +"Moves are grouped within the same document type if their procurement group " +"and locations are the same." +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:261 +msgid "" +"A sale order creates a procurement group so that pickings and delivery " +"orders of the same order are grouped. But you can define specific groups on " +"reordering rules too. (e.g. to group purchases of specific products " +"together)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:3 +msgid "Terminologies" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:5 +msgid "" +"**Warehouse**: A warehouse in Odoo is a location where you store products. " +"It is either a physical or a virtual warehouse. It could be a store or a " +"repository." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:9 +msgid "" +"**Location**: Locations are used to structure storage zones within a " +"warehouse. In addition to internal locations (your warehouse), Odoo has " +"locations for suppliers, customers, inventory loss counter-parts, etc." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:14 +msgid "" +"**Lots**: Lots are a batch of products identified with a unique barcode or " +"serial number. All items of a lot are from the same product. (e.g. a set of " +"24 bottle) Usually, lots come from manufacturing order batches or " +"procurements." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:19 +msgid "" +"**Serial Number**: A serial number is a unique identifier of a specific " +"product. Technically, serial numbers are similar to having a lot of 1 unique" +" item." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:23 +msgid "" +"**Unit of Measure**: Define how the quantity of products is expressed. " +"Meters, Pounds, Pack of 24, Kilograms,… Unit of measure of the same category" +" (ex: size) can be converted to each others (m, cm, mm) using a fixed ratio." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:28 +msgid "" +"**Consumable**: A product for which you do not want to manage the inventory " +"level (no quantity on hand or forecasted) but that you can receive and " +"deliver. When this product is needed Odoo suppose that you always have " +"enough stock." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:33 +msgid "" +"**Stockable**: A product for which you want to manage the inventory level." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:36 +msgid "" +"**Package:** A package contains several products (identified by their serial" +" number/lots or not). Example: a box containing knives and forks." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:40 +msgid "" +"**Procurement**: A procurement is a request for a specific quantity of " +"products to a specific location. Procurement are automatically triggered by " +"other documents: Sale orders, Minimum Stock Rules, and Procurement rules. " +"You can trigger the procurement manually. When procurements are triggered " +"automatically, you should always pay attention for the exceptions (e.g. a " +"product should be purchased from a vendor, but no supplier is defined)." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:48 +msgid "" +"**Routes**: Routes define paths the product must follow. Routes may be " +"applicable or not, depending on the products, sales order lines, warehouse,…" +" To fulfill a procurement, the system will search for rules belonging to " +"routes that are defined in the related product/sale order." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:54 +msgid "" +"**Push Rules**: Push rules trigger when products enter a specific location. " +"They automatically move the product to a new location. Whether a push rule " +"can be used depends on applicable routes." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:58 +msgid "" +"**Procurement Rules** or **Pull Rules**: Procurement rules describe how " +"procurements on specific locations should be fulfilled e.g.: where the " +"product should come from (source location), whether the procurement is MTO " +"or MTS,..." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:63 +msgid "" +"**Procurement Group**: Routes and rules define inventory moves. For every " +"rule, a document type is provided: Picking, Packing, Delivery Order, " +"Purchase Order,… Moves are grouped within the same document type if their " +"procurement group and locations are the same." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:69 +msgid "" +"**Stock Moves**: Stock moves represent the transit of goods and materials " +"between locations." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:72 +msgid "" +"**Quantity On Hand**: The quantity of a specific product that is currently " +"in a warehouse or location." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:75 +msgid "" +"**Forecasted Quantity**: The quantity of products you can sell for a " +"specific warehouse or location. It is defined as the Quantity on Hand - " +"Future Delivery Orders + Future incoming shipments + Future manufactured " +"units." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:80 +msgid "" +"**Reordering Rules**: It defines the conditions for Odoo to automatically " +"trigger a request for procurement (buying at a supplier or launching a " +"manufacturing order). It is triggered when the forecasted quantity meets the" +" minimum stock rule." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:85 +msgid "" +"**Cross-Dock**: Cross-docking is a practice in the logistics of unloading " +"materials from an incoming semi-trailer truck or railroad car and loading " +"these materials directly into outbound trucks, trailers, or rail cars, with " +"no storage in between. (does not go to the stock, directly from incoming to " +"packing zone)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:91 +msgid "" +"**Drop-Shipping**: move products from the vendor/manufacturer directly to " +"the customer (could be retailer or consumer) without going through the usual" +" distribution channels. Products are sent directly from the vendor to the " +"customer, without passing through your own warehouse." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:97 +msgid "" +"**Removal Strategies**: the strategy to use to select which product to pick " +"for a specific operation. Example: FIFO, LIFO, FEFO." +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:100 +msgid "" +"**Putaway Strategies**: the strategy to use to decide in which location a " +"specific product should be set when arriving somewhere. (example: cables " +"goes in rack 3, storage A)" +msgstr "" + +#: ../../inventory/overview/concepts/terminologies.rst:104 +msgid "" +"**Scrap**: A product that is broken or outdated. Scrapping a product removes" +" it from the stock." +msgstr "" + +#: ../../inventory/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:3 +msgid "From procurement to delivery" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:8 +msgid "" +"Inventory is the heart of your business. It can be really complicated, but " +"with Odoo, doing a receipt or a delivery has never been easier. We will show" +" you in this document how easy to do a full process, from the receipt to the" +" delivery." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:13 +msgid "" +"Odoo inventory is fully integrated with other applications, such as " +"**Purchase**, **Sales** or **Inventory**. But is not limited to those " +"processes, it is also fully integrated with our **e-Commerce**, " +"**Manufacturing** and **Repairs** applications." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:19 +msgid "How to process a receipt ?" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:22 +msgid "Install Purchase application" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:24 +msgid "" +"First, you will need to install the **Purchase Management** application. Go " +"to :menuselection:`Apps` and install it." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:31 +msgid "Make a purchase order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:33 +msgid "" +"Go to the **Purchases** applications. The first screen is the **Request for " +"Quotation** list. Click on the **Create** button." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:36 +msgid "" +"Fill in the **Vendor** information and click on **Add an Item** to add some " +"products to your request for quotation." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:42 +msgid "" +"Click on **Confirm order** when you are sure about the products, prices and " +"quantity." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:46 +msgid "Retrieve the Receipt" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:48 +msgid "You can retrieve the receipt order in 2 ways:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:51 +msgid "From the purchase order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:53 +msgid "" +"On the top right of your purchase order, you will see a button with the " +"related **Receipt**:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:59 +#: ../../inventory/overview/process/sale_to_delivery.rst:136 +msgid "Click on it to see the **Transfer order**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:62 +#: ../../inventory/overview/process/sale_to_delivery.rst:139 +msgid "From the Inventory Dashboard" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:64 +msgid "" +"When opening the **Inventory** application, click on **# to receive** to see" +" the list of your deliveries to process." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:70 +msgid "In the list, click on the one related to the purchase order:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:76 +msgid "Process the Receipt" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:81 +#: ../../inventory/overview/process/sale_to_delivery.rst:162 +msgid "" +"To process the stock transfer. Simply click on **Validate** to complete the " +"transfer. A message will appear asking if you want to process the whole " +"order, accept it by clicking on **Apply**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:86 +msgid "" +"Procurements can be automated. Please read our document " +":doc:`../../management/adjustment/min_stock_rule_vs_mto` for more " +"information." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:91 +msgid "How to process a delivery order ?" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:94 +msgid "Install Sales application" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:96 +msgid "" +"First, you will need to install the **Sales Management** application. Go to " +":menuselection:`Apps` and install it." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:103 +msgid "Place a sale order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:105 +msgid "" +"Go to the **Sales** applications. Click on the **Quotations** button of your" +" team." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:111 +msgid "" +"You will get the list of all your quotations. Click on the **Create** " +"button." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:114 +msgid "" +"Fill in the **Customer informations** and click on **Add an Item** to add " +"some products to your quotation." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:120 +msgid "Click on **Confirm sale** to place the order." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:123 +msgid "Retrieve the Delivery order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:125 +msgid "You can retrieve the delivery order in 2 ways:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:128 +msgid "From the sale order" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:130 +msgid "" +"On the top right of your sale order, you will see a button with the related " +"**Delivery**:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:141 +msgid "" +"When opening the **Inventory** application, click on **# to do** to see the " +"list of your receipts to process." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:147 +msgid "In the list, click on the one related to the sale order:" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:153 +msgid "" +"If the product is not in stock, the sale order will be listed as **Waiting**" +" on your dashboard." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:157 +msgid "Process the delivery" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:167 +msgid "E-Commerce orders are processed the same way." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:170 +msgid "" +"You can easily integrate your delivery orders with different delivery " +"methods. Please read the document " +":doc:`../../shipping/setup/delivery_method`." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:175 +msgid "Advanced flows" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:177 +msgid "" +"In this document, the flows that are explained are the most simple ones. " +"Odoo also suit for companies having advanced warehouse management." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:180 +msgid "" +"By default, only **receipts** and **deliveries** are configured but you can " +"activate the use of multi-locations and multi-warehouses to do **internal " +"transfers**." +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:184 +msgid "**Routes**: you can automate flows with push and pull rules" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:186 +msgid "" +"**Multi-step** receipts and deliveries can be easily configured for each " +"warehouse" +msgstr "" + +#: ../../inventory/overview/process/sale_to_delivery.rst:189 +msgid "" +"Much more: **Barcode scanning**, **serial numbers**, **lots**, **cross-" +"docking**, **dropshipping**, integration with a **third-party** shipper, " +"**putaway** and **removal** strategies.... All of it is possible with Odoo." +msgstr "" + +#: ../../inventory/overview/start.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:3 +msgid "How to setup Odoo inventory?" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:5 +msgid "" +"The Odoo Inventory application has an implementation guide that you should " +"follow to configure it. It's a step-by-step manual with links to the " +"different screens you need." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:9 +msgid "" +"Once you have installed the **Inventory** application, click on the top-" +"right progress bar to get access to the implementation guide." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:15 +msgid "The implementation guide helps you through the following steps:" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:17 +msgid "Set up your warehouse" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:19 +msgid "Import your vendors" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:21 +msgid "Import your products" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:23 +msgid "Set up the initial inventory" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:25 +msgid "Configure your sales and purchase flows" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:27 +msgid "Set up replenishment mechanisms" +msgstr "" + +#: ../../inventory/overview/start/setup.rst:29 +msgid "" +"Configure advanced features like package, traceability, routes and inventory" +" valuation." +msgstr "" + +#: ../../inventory/overview/start/setup.rst:37 +msgid "" +"If you want to set up operations with barcode scanner in your warehouse, you" +" should install the **Barcode** application that adds features on top of the" +" inventory application. The barcode application will guide you to configure " +"and use your scanner optimally." +msgstr "" + +#: ../../inventory/routes.rst:3 +msgid "Advanced Routes" +msgstr "" + +#: ../../inventory/routes/concepts.rst:3 +msgid "Concepts" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:3 +msgid "How to organize a cross-dock in your warehouse?" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:5 +msgid "" +"Cross dock area is temporarily area where we are not storing any product " +"instead just managing place according to delivery for further customer. This" +" will save lot of time for inter warehouse transfer and storing process. We " +"are managing our products with docking area where product directly place " +"from supplier location and transfer this to gate pass for customer delivery." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:17 +msgid "" +"For more information on how to organise your warehouse, read `What is cross " +"docking and is it for me? <https://www.odoo.com/blog/business-hacks-1/post" +"/what-is-cross-docking-and-is-it-for-me-270>`_" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:24 +msgid "Warehouse and routes" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:26 +msgid "" +"In the **Inventory** module, open :menuselection:`Configuration --> Settings" +" --> Location & Warehouse`, then in **Routes**, select **Advanced routing of" +" products using rules**, then click on **Apply**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:33 +msgid "" +"Open :menuselection:`Configuration --> Warehouse Management --> Warehouses`," +" then open the warehouse you want to cross-dock from and click on **Edit**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:36 +msgid "In the **Warehouse Configuration** tab, select:" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:38 +msgid "" +"**Incoming Shipments**: Unload in input location then go to stock (2 steps)" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:41 +msgid "**Outgoing Shipments**: Ship directly from stock (Ship only)" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:43 +msgid "then click on **Save**." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:48 +msgid "" +"This steps has generated a cross-docking route that you can see in " +":menuselection:`Inventory --> Configurations --> Routes --> Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:52 +msgid "Cross Docking Route" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:54 +msgid "" +"We will use the route **Buy** for first part of the flow and create a route " +"for the remaining part:" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:60 +msgid "" +"Each of the procurement rule will now be configured. Cross Dock location is " +"created as an internal physical location." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:67 +msgid ":menuselection:`Input --> Cross Dock`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:73 +msgid ":menuselection:`Cross Dock --> Output`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:79 +msgid ":menuselection:`Output --> Customer`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:82 +msgid "Product with cross dock" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:84 +msgid "" +"We have created the Vegetable Fennel product and assigned the routes created" +" above as well as the **Buy** route." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:87 +msgid "" +"We have also specified a supplier and a minimum order rule which is needed " +"for replenishment of a stockable product." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:95 +msgid ":doc:`use_routes`" +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:96 +msgid ":doc:`../../management/incoming/two_steps`" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:3 +msgid "How to do inter-warehouses transfers?" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:5 +msgid "" +"If you own different warehouses you might want to transfer goods from one " +"warehouse to the other. This is very easy thanks to the inventory " +"application in Odoo." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:12 +msgid "" +"First of all you have to select the multi locations option. Go to " +":menuselection:`Configuration --> Settings` in the **Inventory " +"application**. Then tick the **Manage several locations per warehouse** " +"option. Please don't forget to **apply** your changes." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:22 +msgid "" +"This option should also be ticked if you wish to manage different locations " +"and routes in your warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:26 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:9 +msgid "Creating a new warehouse" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:28 +msgid "" +"The next step is to create your new warehouse. In the Inventory application " +"click on :menuselection:`Configuration --> Warehouse Management --> " +"Warehouses`. You are now able to create your warehouse by clicking on " +"**Create**." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:33 +msgid "" +"Fill in a **Warehouse Name** and a **Short Name**. The short name is 5 " +"characters maximum." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:41 +msgid "" +"please note that the **Short Name** is very important as it will appear on " +"your transfer orders and other warehouse documents. It might be smart to use" +" an understandable one (e.g.: WH/[first letters of location])." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:46 +msgid "" +"If you go back to your dashboard, new operations will automatically have " +"been generated for your new warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:53 +msgid "Creating a new inventory" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:55 +msgid "" +"If you create a new warehouse you might already have an existing physical " +"inventory in it. In that case you should create an inventory in Odoo, if not" +" you can skip this step." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:59 +msgid "" +"Go into the inventory application, select :menuselection:`Inventory Control " +"--> Inventory Adjustment`. You can then create a new inventory by clicking " +"on **Create**. Fill in the **Inventory Reference**, **Date** and be sure to " +"select the right warehouse and location." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:67 +msgid "" +"Next, click on **Start Inventory**. A new window will open where you will be" +" able to input your existing products. Select add an item and indicate the " +"**Real Quantity** available in the warehouse. The theoretical quantity can " +"not be changed as it represents a computed quantity from purchase and sales " +"orders." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:76 +msgid "" +"Don't forget to validate your inventory once you have recorder the state of " +"all yours product." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:80 +msgid "Create an internal transfer" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:82 +msgid "" +"The final step is to create your internal transfer. If you want to tranfer 2" +" units of a product from your first warehouse to another one in Brussels, " +"proceed as follows:" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:86 +msgid "" +"From your dashboard, select a internal movement of one of the two " +"warehouses. To do so, click on :menuselection:`More --> Transfer`." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:92 +msgid "" +"A new window will open where you will be able to select the source location " +"zone (in this case our \"old warehouse\") and the destination location zone " +"(in this case our \"new\" warehouse located in Brussels)." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:96 +msgid "" +"Add the products you want to transfer by clicking on **Add an Item** and " +"don't forget to **Validate** or **Mark as TODO** once you are done." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:102 +msgid "" +"If you select **Validate**, Odoo will process all quantities to transfer." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:104 +msgid "" +"If you select **Mark as TODO**, Odoo will put the transfer in **Waiting " +"Availability** status. Click on **Reserve** to reserve the amount of " +"products in your source warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:108 +msgid "It is also possible to manually transfer each product:" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:110 +msgid "Via your dashboard, select the transfer order in the source location." +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:115 +msgid "Select the right transfer order" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:120 +msgid "" +"3. Click on the little pencil logo in the lower right corner in order to " +"open the operation details window. In this new window you can manually " +"indicate how much products you process" +msgstr "" + +#: ../../inventory/routes/concepts/inter_warehouse.rst:129 +msgid "" +"If you decide to partially process the transfer order (e.g. a part of the " +"products can't be shipped yet due to an unexpected event), Odoo will " +"automatically ask if you wish to create a **backorder**. Create a backorder " +"if you expect to process the remaining products later, do not create a " +"backorder if you will not supply/receive the remaining products." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:3 +msgid "What is a procurement rule?" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:8 +msgid "" +"The procurement inventory control system begins with a customer's order. " +"With this strategy, companies only make enough product to fulfill customer's" +" orders. One advantage to the system is that there will be no excess of " +"inventory that needs to be stored, thus reducing inventory levels and the " +"cost of carrying and storing goods. However, one major disadvantage to the " +"pull system is that it is highly possible to run into ordering dilemmas, " +"such as a supplier not being able to get a shipment out on time. This leaves" +" the company unable to fulfill the order and contributes to customer " +"dissatisfaction." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:18 +msgid "" +"An example of a pull inventory control system is the make-to-order. The goal" +" is to keep inventory levels to a minimum by only having enough inventory, " +"not more or less, to meet customer demand. The MTO system eliminates waste " +"by reducing the amount of storage space needed for inventory and the costs " +"of storing goods." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:27 +msgid "" +"Procurement rules are part of the routes. Go to the Inventory " +"application>Configuration>Settings and tick \"Advance routing of products " +"using rules\"." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:35 +msgid "Procurement rules settings" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:37 +msgid "" +"The procurement rules are set on the routes. In the inventory application, " +"go to Configuration > Routes." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:40 +msgid "In the Procurement rules section, click on Add an item." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:45 +msgid "" +"Here you can set the conditions of your rule. There are 3 types of action " +"possibles :" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:48 +msgid "Move from another location rules" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:50 +msgid "" +"Manufacturing rules that will trigger the creation of manufacturing orders." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:53 +msgid "Buy rules that will trigger the creation of purchase orders." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:56 +msgid "" +"The Manufacturing application has to be installed in order to trigger " +"manufacturing rules." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:60 +msgid "" +"The Purchase application has to be installed in order to trigger **buy** " +"rules." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:68 +msgid "Try to create a procurement rule in our demo instance." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:71 +msgid "" +"Some Warehouse Configuration creates routes with procurement rules already " +"defined." +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:75 +#: ../../inventory/routes/concepts/use_routes.rst:130 +#: ../../inventory/routes/concepts/use_routes.rst:152 +msgid ":doc:`push_rule`" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:76 +#: ../../inventory/routes/concepts/push_rule.rst:84 +#: ../../inventory/routes/concepts/use_routes.rst:153 +msgid ":doc:`inter_warehouse`" +msgstr "" + +#: ../../inventory/routes/concepts/procurement_rule.rst:77 +#: ../../inventory/routes/concepts/push_rule.rst:85 +#: ../../inventory/routes/concepts/use_routes.rst:154 +msgid ":doc:`cross_dock`" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:3 +msgid "What is a push rule?" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:8 +msgid "" +"The push system of inventory control involves forecasting inventory needs to" +" meet customer demand. Companies must predict which products customers will " +"purchase along with determining what quantity of goods will be purchased. " +"The company will in turn produce enough product to meet the forecast demand " +"and sell, or push, the goods to the consumer. Disadvantages of the push " +"inventory control system are that forecasts are often inaccurate as sales " +"can be unpredictable and vary from one year to the next. Another problem " +"with push inventory control systems is that if too much product is left in " +"inventory. This increases the company's costs for storing these goods. An " +"advantage to the push system is that the company is fairly assured it will " +"have enough product on hand to complete customer orders, preventing the " +"inability to meet customer demand for the product." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:22 +msgid "" +"A push flow indicates how locations are chained with the other ones. As soon" +" as a given quantity of products is moved in the source location, a chained " +"move is automatically foreseen according to the parameters set on the flow " +"specification (destination location, delay, type of move, journal). It can " +"be triggered automatically or manually." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:31 +msgid "" +"Push rules are part of the routes. Go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings` and tick **Advance routing of products using" +" rules**." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:39 +msgid "Push rules settings" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:41 +msgid "" +"The push rules are set on the routes. Go to :menuselection:`Configuration " +"--> Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:44 +msgid "In the push rule section, click on **Add an item**." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:49 +msgid "" +"Here you can set the conditions of your rule. In this example, when a good " +"is in **Input location**, it needs to be moved to the quality control. In " +"the 3 steps receipts, another push rule will make the goods that are in the " +"quality control location move to the stock." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:59 +msgid "Try to create a push rule in our demo instance." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:62 +msgid "" +"Some warehouse configuration creates routes with push rules already defined." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:66 +msgid "Stock transfers" +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:68 +msgid "" +"The push rule will trigger stock transfer. According to the rule set on your" +" route, you will see that some transfers might be ready and other are " +"waiting." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:72 +msgid "" +"The push rule that was set above will create moves from **WH/Input** " +"location to the **WH/Quality Control** location." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:78 +msgid "" +"In this example, another move is waiting according to the second push rule, " +"it defines that when the quality control is done, the goods will be moved to" +" the main stock." +msgstr "" + +#: ../../inventory/routes/concepts/push_rule.rst:83 +#: ../../inventory/routes/concepts/use_routes.rst:128 +msgid ":doc:`procurement_rule`" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:3 +msgid "How to use routes?" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:8 +msgid "" +"A route is a collection of procurement rules and push rules. Odoo can manage" +" advanced push/pull routes configuration, for example:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:11 +msgid "Manage product manufacturing chains" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:13 +msgid "Manage default locations per product" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:15 +msgid "" +"Define routes within your warehouse according to business needs, such as " +"quality control, after sales services or supplier returns" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:18 +msgid "" +"Help rental management, by generating automated return moves for rented " +"products" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:24 +msgid "" +"Procurement rules are part of the routes. Go to the **Inventory** " +"application, :menuselection:`Configuration --> Settings` and tick **Advance " +"routing of products using rules**." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:32 +msgid "Pre-configured routes" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:34 +msgid "Odoo has some pre-configured routes for your warehouses." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:36 +msgid "" +"In the Inventory application, go to :menuselection:`Configuration --> " +"Warehouses`." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:39 +msgid "" +"In the **Warehouse Configuration** tab, **Incoming Shipments** and " +"**Outgoing Shippings** options set some routes according to your choices." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:46 +msgid "Custom Routes" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:48 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Routes`." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:54 +msgid "" +"First, you have to select the places where this route can be selected. You " +"can combine several choices." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:58 +msgid "Routes applied on warehouses" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:60 +msgid "" +"If you tick **Warehouses**, you have to choose on which warehouse it will be" +" applied. The route will be set for all transfer in that warehouse that " +"would meet the conditions of the procurement and push rules." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:68 +msgid "Routes applied on products" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:70 +msgid "" +"If you tick **Products**, you have to manually set on which product it will " +"be applied." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:76 +msgid "" +"Open the product on which you want to apply the routes " +"(:menuselection:`Inventory --> Control --> Products`). In the Inventory Tab," +" select the route(s):" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:84 +msgid "Routes applied on Product Category" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:86 +msgid "" +"If you tick **Product Categories**, you have to manually set on which " +"categories it will be applied." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:92 +msgid "" +"Open the product on which you want to apply the routes " +"(:menuselection:`Configuration --> Product Categories`). Select the route(s)" +" under the **Logistics** section :" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:100 +msgid "Routes applied on Sales Order lines" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:102 +msgid "" +"If you tick **Sales order lines**, you have to manually set the route every " +"time you make a sale order." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:108 +msgid "" +"In order to make it work, you also have to activate the use of the routes on" +" the sales order." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:111 +msgid "" +"In the Sales application, go to :menuselection:`Configuration --> Settings` " +"and tick **Choose specific routes on sales order lines (advanced)**." +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:118 +msgid "You can now choose the routes for each lines of your sales orders:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:124 +msgid "Procurement and push rules" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:126 +msgid "Please refer to the documents:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:133 +msgid "Procurement configuration" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:135 +msgid "" +"When doing a procurement request, you can force the route you want to use. " +"On the product (:menuselection:`Inventory Control --> Products`), click on " +"**Procurement Request**. Choose the route you want to use next to " +"**Preferred Routes**:" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:144 +msgid "Make-to-Order Route" +msgstr "" + +#: ../../inventory/routes/concepts/use_routes.rst:146 +msgid "" +"If you work with no stock, or with minimum stock rules, it is better to use " +"the **Make To Order** route. Combine it with the route **Buy** or " +"**Manufacture** and it will trigger automatically the purchase order or the " +"Manufacturing Order when your products are out-of-stock." +msgstr "" + +#: ../../inventory/routes/costing.rst:3 +msgid "Product Costing" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:3 +msgid "How to integrate landed costs in the cost of the product?" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:8 +msgid "Landed costs include all charges associated to a good transfer." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:10 +msgid "Landed cost includes = Cost of product + Shipping + Customs + Risk" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:12 +msgid "" +"All of these components might not be applicable in every shipment, but " +"relevant components must be considered as a part of the landed cost. We have" +" to identify landed cost to decide sale price of product because it will " +"impact on company profits." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:21 +msgid "Applications configuration" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:23 +msgid "" +"First, you need to activate the use of the landed costs. Go to " +":menuselection:`Inventory application --> Configuration --> Setting`. Check " +"accounting option **Include landed costs in product costing computation** & " +"**Perpetual inventory valuation**, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:32 +msgid "" +"Then go to the :menuselection:`Purchase application --> Configuration --> " +"Setting`. Choose costing method **Use a 'Fixed', 'Real' or 'Average' price " +"costing method**, then click on **Apply** to save changes." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:40 +msgid "Landed Cost Types" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:42 +msgid "" +"Start by creating specific products to indicate your various **Landed " +"Costs**, such as freight, insurance or custom duties. Go to " +":menuselection:`Inventory --> Configuration --> Landed Cost types`." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:52 +msgid "" +"Landed costs are only possible for products configured in real time " +"valuation with real price costing method. The costing method is configured " +"on the product category." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:57 +msgid "Link landed costs to a transfer" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:59 +msgid "" +"To calculate landed costs, go to :menuselection:`Inventory --> Inventory " +"Control --> Landed Costs`." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:62 +msgid "" +"Click on the **Create** button and select the picking(s) you want to " +"attribute landed costs." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:68 +msgid "" +"Select the account journal in which to post the landed costs. We recommend " +"you to create a specific journal for landed costs. Therefore it will be " +"easier to keep track of your postings." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:75 +msgid "" +"Click the **Compute** button to see how the landed costs will be split " +"across the picking lines." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:81 +msgid "" +"To confirm the landed costs attribution, click on the **Validate** button." +msgstr "" + +#: ../../inventory/routes/strategies.rst:3 +msgid "Putaway & Removal Strategies" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:3 +msgid "What is a putaway strategy?" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:8 +msgid "" +"A good warehouse implementation takes care that products automatically move " +"to their appropriate destination location. Putaway is the process of taking " +"products off the receiving shipment and putting them into the most " +"appropriate location." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:13 +msgid "" +"If for instance a warehouse contains volatile substances, it is important to" +" make sure that certain products are not stored close to each other because " +"of a potential chemical reaction." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:17 +msgid "" +"A putaway strategy follows the same principle as removal strategies but " +"affects the destination location. Putaway strategies are defined at the " +"location level (unlike removal strategies which are defined at the product " +"level)." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:25 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Settings` and check " +"option **Manage several location per warehouse & Advance routing of products" +" using rules**, then click on **Apply**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:33 +msgid "Setting up a strategy" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:35 +msgid "" +"Let's take as an example a retail shop where we store vegetables and fruits." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:38 +msgid "" +"We have to store this type of product in different locations to maintain " +"product quality." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:41 +msgid "" +"Suppose there is one warehouse location **WH/Stock** and there is sub " +"location **WH/Stock/Vegetables** & **WH/Stock/Fruits**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:44 +msgid "" +"You can create a putaway strategy from :menuselection:`Inventory --> " +"Configuration --> Locations`. Open any location where you want to set a " +"putaway strategy, click on **Edit** and locate the option **Put Away " +"Strategy**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:52 +msgid "" +"Open the roll-down menu and click on **Create and Edit**. This will open a " +"form view of put away strategy on which you have to set a name for the " +"strategy, and set the method and fixed location for each category." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:59 +msgid "" +"When you have entered all the necessary information, click on **Save**." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:61 +msgid "" +"Now, when you purchase products with those categories, they will " +"automatically be transferred to the correct location." +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:64 +msgid "" +"To check current inventory, Go to :menuselection:`Inventory --> Inventory " +"Control --> Current Inventory`" +msgstr "" + +#: ../../inventory/routes/strategies/putaway.rst:67 +msgid "There you can see current inventory by location." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:3 +msgid "What is a removal strategy (FIFO, LIFO, and FEFO)?" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:8 +msgid "" +"Removal strategies are usually in picking operations to select the best " +"products in order to optimize the distance for the worker, for quality " +"control purpose or due to reason of product expiration." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:12 +msgid "" +"When a product movement needs to be done, Odoo will find available products " +"that can be assigned to shipping. The way Odoo assign these products depend " +"on the **removal strategy** that is defined on the **product category** or " +"on the **location**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:20 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Settings`:" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:29 +msgid "" +"Check **Track lots or serial numbers**, **Manage several location per " +"warehouse** and **Advanced routing of products using rules**, then click on " +"**Apply**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:33 +msgid "" +"Then, open :menuselection:`Configuration --> Locations` and open the " +"location on which you want to apply a removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:40 +msgid "Types of removal strategy" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:43 +msgid "FIFO ( First In First Out )" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:45 +msgid "" +"A **First In First Out** strategy implies that the products that were " +"stocked first will move out first. Companies should use FIFO method if they " +"are selling perishable goods. Companies selling products with relatively " +"short demand cycles, such as clothes, also may have to pick FIFO to ensure " +"they are not stuck with outdated styles in inventory." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:51 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Locations`, open the " +"stock location and set **FIFO** removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:54 +msgid "Let's take one example of FIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:56 +msgid "" +"In your warehouse stock (``WH/Stock``) location, there are ``3`` lots of " +"``iPod 32 Gb`` available." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:59 +msgid "" +"You can find details of available inventory in inventory valuation report." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:65 +msgid "Create one sales order ``25`` unit of ``iPod 32 GB`` and confirm it." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:67 +msgid "" +"You can see in the outgoing shipment product that the ``Ipod 32 Gb`` are " +"assigned with the **oldest** lots, using the FIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:75 +msgid "LIFO (Last In First Out)" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:77 +msgid "" +"In this warehouse management, the products which are brought in the last, " +"moves out the first. LIFO is used in case of products which do not have a " +"shelf life." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:81 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Locations`, open the " +"stock location and set **LIFO** removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:84 +msgid "" +"In our example, let's check the current available stock of ``Ipod 32 Gb`` on" +" ``WH/Stock`` location." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:90 +msgid "Create a sale order with ``10`` units of ``Ipod 32 Gb``." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:92 +msgid "" +"You can see in the outgoing shipment product that the ``Ipod 32 Gb`` are " +"assigned with the **newest** lots, using the LIFO removal strategy." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:100 +msgid "FEFO ( First Expiry First Out )" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:102 +msgid "" +"In FEFO warehouse management, the products are dispatched from the warehouse" +" according to their expiration date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:105 +msgid "" +"Go to :menuselection:`Inventory --> Configuration --> Setting`. Check the " +"option **Define Expiration date on serial numbers**. Then click on **Apply**" +" to save changes." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:112 +msgid "" +"This will allow you to set four expiration fields for each lot or serial " +"number: **best before date**, **end of life date**, **alert date** and " +"**removal date**. These dates can be set from :menuselection:`Inventory " +"Control --> Serial Numbers/Lots`." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:119 +msgid "" +"**Best Before Date**: This is the date on which the goods with this " +"serial/lot number start deteriorating, without being dangerous yet." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:122 +msgid "" +"**End of Life Date:** This is the date on which the goods with this " +"serial/lot number may become dangerous and must not be consumed." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:125 +msgid "" +"**Removal Date:** This is the date on which the goods with this serial/lot " +"number should be removed from the stock. Using the FEFO removal strategym " +"goods are picked for delivery orders using this date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:129 +msgid "" +"**Alert Date:** This is the date on which an alert should be sent about the " +"goods with this serial/lot number." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:132 +msgid "" +"Lots will be picked based on their **removal date**, from earliest to " +"latest. Lots without a removal date defined will be picked after lots with " +"removal dates." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:136 +msgid "" +"All dates except **removal date** are for informational and reporting " +"purposes only. Lots that are past any or all of the above expiration dates " +"may still be picked for delivery orders, and no alerts will be sent when " +"lots pass their **alert date**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:140 +msgid "" +"Expiration dates on lots can also be set automatically when goods are " +"received into stock. After enabling expiration dates on serial numbers, four" +" new fields will become available in the inventory tab of the product form: " +"**product life time**, **product use time**, **product removal time**, and " +"**product alert time**. When an integer is entered into one of these fields," +" the expiration date of a lot/serial of the product in question will be set " +"to the creation date of the lot/serial number plus the number of days " +"entered in the time increment field. If the time increment field is set to " +"zero, then the expiration date of a lot/serial must be defined manually " +"after the lot has been created." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:149 +msgid "" +"Each of these time increment fields is used to generate one of the lot " +"expiration date fields as follows:" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:151 +msgid "Product Use Time --> Best Before Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:153 +msgid "Product Removal Time --> Removal Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:155 +msgid "Product Life Time --> End of Life Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:157 +msgid "Product Alert Time --> Alert Date" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:159 +msgid "" +"To set the removal strategy on location, go to :menuselection:`Configuration" +" --> Locations` and choose FEFO." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:165 +msgid "" +"Let's take an example, there are ``3`` lots of ``ice cream`` available in " +"``WH/Stock`` location: ``LOT0001``, ``LOT0002``, ``LOT0003`` with different " +"expiration date." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Lot / Serial No**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Product**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:170 +msgid "**Expiration Date**" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +msgid "LOT0001" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +#: ../../inventory/routes/strategies/removal.rst:174 +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "Ice Cream" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:172 +msgid "08/20/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:174 +msgid "LOT0002" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:174 +msgid "08/10/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "LOT0003" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:176 +msgid "08/15/2015" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:179 +msgid "" +"We will create a sale order with ``15kg`` of ``ice cream`` and confirm it." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:181 +msgid "" +"The outgoing shipment related to sale order will make the move based on " +"removal strategy **FEFO**." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:184 +msgid "" +"It will take ``10kg`` from ``LOT0002`` and ``5kg`` from ``LOT0003`` based on" +" the removal dates." +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:192 +msgid ":doc:`../../management/reporting/valuation_methods_continental`" +msgstr "" + +#: ../../inventory/routes/strategies/removal.rst:193 +msgid ":doc:`../../management/reporting/valuation_methods_anglo_saxon`" +msgstr "" + +#: ../../inventory/settings.rst:3 +msgid "Settings" +msgstr "" + +#: ../../inventory/settings/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:3 +msgid "How to use packages?" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:8 +#: ../../inventory/settings/products/usage.rst:31 +msgid "" +"The package is the physical container in which you put one or several " +"product." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:11 +msgid "By default, Odoo does not take into account the use of it." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:13 +msgid "" +"Once you activate the option, you will be able to manage one or several " +"packages when doing your transfers." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:19 +msgid "" +"To configure the use of packages, go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings`. µ Locate the **Packages** section and tick " +"**Record packages used on packing: pallets, boxes,...**" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:27 +#: ../../inventory/shipping/operation/multipack.rst:23 +msgid "Click on **Apply** when you are done." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:30 +msgid "Pack products" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:32 +msgid "" +"Putting products in packs is usually done when processing warehouses " +"transfers (receipt, internals or deliveries)." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:35 +msgid "" +"To be able to put products in pack, the status of your transfer has to be " +"**Available**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:41 +msgid "" +"In the operation tab, you can put your products into one or multiple " +"packages." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:44 +#: ../../inventory/shipping/operation/multipack.rst:50 +msgid "" +"Choose the quantity you want to put in the first pack in the **Done** " +"column, then click on the link **Put in Pack**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:50 +#: ../../inventory/shipping/operation/multipack.rst:56 +msgid "It will automatically create a pack with the requested quantity." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:52 +#: ../../inventory/shipping/operation/multipack.rst:58 +msgid "Do the same steps for the other pieces you want to pack in." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:57 +#: ../../inventory/shipping/operation/multipack.rst:63 +msgid "Click on **Validate** when you are done." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:60 +msgid "Whole packages transfers" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:62 +msgid "" +"If you are using several locations and/or warehouses, it is possible to " +"transfer packages with its contents." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:68 +msgid "" +"You need to configure the **Operation Type** to allow moving packages. Go to" +" :menuselection:`Configuration --> Operations Types`. Tick **Allow moving " +"packs**:" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:75 +msgid "Transfer packages" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:77 +msgid "" +"Create a transfer order. Choose the source and the destination locations, " +"then click on **Mark as todo**. Do not put anything under the **Initial " +"Demand** tab." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:84 +msgid "" +"In the Operation tab, click on **Add an item** under the **Package To Move**" +" section." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:87 +msgid "Tick the **Done** checkbox to confirm the move of the package :" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:92 +msgid "When it is finished, click on **Validate**." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:95 +msgid "Packages traceability" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:97 +msgid "" +"To trace a package or check its content, go to :menuselection:`Inventory " +"Control --> Packages`." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:103 +msgid "Click on **Package Transfers** to see all its moves." +msgstr "" + +#: ../../inventory/settings/products/packages.rst:106 +#: ../../inventory/settings/products/usage.rst:70 +msgid ":doc:`../../overview/start/setup`" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:107 +msgid ":doc:`usage`" +msgstr "" + +#: ../../inventory/settings/products/packages.rst:108 +#: ../../inventory/settings/products/usage.rst:71 +msgid ":doc:`uom`" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:3 +msgid "How to use different units of measure?" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:8 +msgid "" +"In some cases, handling products in different unit of measures is necessary." +" For example, if you buy products in a country where the metric system is of" +" application and sell the in a country where the imperial system is used, " +"you will need to convert the units." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:13 +msgid "" +"You can set up Odoo to work with different units of measure for one product." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:19 +msgid "" +"In the **Inventory** application, go to :menuselection:`Configuration --> " +"Settings`. In the **Products** section, select **Some products may be " +"sold/purchased in different units of measure (advanced)**, then click on " +"**Apply**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:27 +msgid "Setting up units on your products" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:29 +msgid "" +"In :menuselection:`Inventory Control --> Products`, open the product which " +"you would like to change the purchase/sale unit of measure, and click on " +"**Edit**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:32 +msgid "" +"In the **Unit of Measure** section, select the unit in which the product " +"will be sold and in which internal transfers will be done." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:35 +msgid "" +"In the **Purchase Unit of Measure** section, select the unit in which you " +"purchase the product. When you're done, click on **Save**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:42 +msgid "Click on the edit button |edit| to create new unit of measures." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:46 +msgid "Transfer from one unit to another" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:48 +msgid "" +"When doing inter-unit transfers, the rounding is automatically done by Odoo." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:51 +msgid "" +"The unit of measure can be changed throughout the whole process. The only " +"condition is that the unit of measure is part of the same category." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:54 +msgid "In this example, we are in the egg business :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:56 +msgid "We buy eggs by trays (30 eggs)" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:58 +msgid "We check all eggs individually when receiving it (quality control)" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:60 +msgid "We sell eggs by the dozen to the customers" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:66 +msgid "" +"The **Sale price** is expressed in the **Product unit of measure**. The " +"**Cost price** is expressed in the **Purchase Unit of Measure**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:70 +msgid "" +"All internal transfers are expressed in the **Product Unit of Measure**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:74 +msgid "Procurement" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:76 +msgid "" +"When doing your procurement request, you can still change the unit of " +"measure." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:82 +msgid "The unit of measure can also be changed in the purchase order :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:90 +msgid "The quality control is done by unit." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:92 +msgid "" +"The basic unit of measure of our product is **Unit**. Therefore the quality " +"check is done by unit." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:99 +msgid "" +"The unit of measure can only be changed when the transfer status is " +"**Draft**." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:103 +#: ../../inventory/shipping/setup/delivery_method.rst:74 +msgid "Delivery process" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:105 +msgid "" +"The eggs are sold by the dozen. You can choose the unit of measure on the " +"sale order document. When doing it, the price is automatically computed from" +" the unit to the dozen." +msgstr "" + +#: ../../inventory/settings/products/uom.rst:112 +msgid "" +"In the delivery order, the initial demand is done in the sales order unit of" +" measure :" +msgstr "" + +#: ../../inventory/settings/products/uom.rst:118 +msgid "" +"But the transfer is done in the product unit of measure. Everything is " +"converted automatically :" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:3 +msgid "When should you use packages, units of measure or kits?" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:6 +msgid "Unit of measures" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:8 +msgid "" +"Units of measures are an indication about the unit used to handle a product." +" Products can be expressed in multiple units of measure at once." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:11 +msgid "" +"Activate this option if you are working with several ones in your warehouse." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:14 +msgid "" +"The purchase unit of measure might be different that the one you use in your" +" warehouse." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:17 +msgid "" +"The selling unit of measure is set on the sale order and can be different." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:24 +msgid "" +"The conversion between the different units of measures is done " +"automatically. The only condition is that all the units have to be in the " +"same category (Unit, Weight, Volume, Length,...)" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:29 +msgid "Packages" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:38 +msgid "Packaging" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:40 +msgid "Packaging is the physical container that protects your product." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:42 +msgid "" +"If you are selling computers, the packaging contains the computer with the " +"notice and the power plug." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:45 +msgid "In Odoo, packagings are just used for indicative purpose." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:51 +msgid "" +"You can define on the **Packages** which **Packaging** it uses. But it is " +"only for indicative purpose." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:55 +msgid "When to use packages, packagings or unit of measures ?" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:57 +msgid "" +"For example, you are sellings eggs. In your warehouse, you manage the eggs " +"individually. Lots of eggs are scrapped and you do it egg by egg. The **unit" +" of measure** is ``Unit(s)``." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:61 +msgid "" +"If you are selling eggs by the dozen, the selling **unit of measure** is the" +" ``Dozen``. You will set it on your sale order." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:64 +msgid "" +"The ``cardboard trays`` that contains the dozen of eggs is the " +"**packaging**." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:66 +msgid "" +"When you are selling several trays, you might wrap all the trays into a " +"``box`` or in a ``plastic`` wrapping. It is the **package**." +msgstr "" + +#: ../../inventory/settings/products/usage.rst:72 +msgid ":doc:`packages`" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:3 +msgid "Using product variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:10 +msgid "" +"As an example, a company selling t-shirts may have the following product:" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:13 +msgid "B&C T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:15 +msgid "Sizes: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:16 +msgid "Colors: Blue, Red, White, Black" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:26 +msgid "Impact of variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:50 +msgid "Should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:53 +msgid "When should you use variants?" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:55 +msgid "Using variants has the following impacts:" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:77 +msgid "When should you avoid using variants?" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:91 +msgid "Quality: T-Shirts, Polos, Shirts" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:93 +#: ../../inventory/settings/products/variants.rst:105 +#: ../../inventory/settings/products/variants.rst:110 +msgid "Color: Red, Blue" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:95 +#: ../../inventory/settings/products/variants.rst:106 +#: ../../inventory/settings/products/variants.rst:111 +msgid "Size: S, M, L, XL" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:103 +msgid "Product Template: T-shirt" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:108 +msgid "Product Template: Polos" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:117 +msgid "Activate the variant feature" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:129 +msgid "Creating products with variants" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:135 +msgid "Now, click on the product you wish to add variants to." +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:160 +msgid "" +"You can also add a different barcode and internal reference to the variant." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:163 +msgid "" +"When you have entered all the specifications of the variant, click on " +"**Save**." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:167 +msgid "Managing Product Variants" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:172 +msgid "" +"The examples below are all based on this product template that has two " +"variant attributes :" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:175 +msgid "T-Shirt B&C" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:177 +msgid "Color: Red, Blue, White" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:179 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:182 +msgid "Managing combination possibilities" +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:197 +msgid "" +"That deactivating a product is different than having an inventory of 0." +msgstr "" + +#: ../../inventory/settings/products/variants.rst:200 +msgid "Setting a price per variant" +msgstr "" + +#: ../../inventory/settings/products/variants.rst:202 +msgid "" +"You can add a cost over the main price for some of the variants of a " +"product." +msgstr "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/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 "" + +#: ../../inventory/settings/products/variants.rst:220 +msgid "When you have entered all the extra values, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3 +msgid "What is the difference between warehouses and locations?" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:5 +msgid "" +"In Odoo, a **Warehouse** is the actual building/place in which your items " +"are stocked. You can setup multiple warehouses and create moves between " +"warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:9 +msgid "" +"A **Location**, is a specific space within your warehouse. It can be " +"considered as a sublocation of your warehouse, as a shelf, a floor, an " +"aisle, etc. Therefore, a location is part of one warehouse only and it is " +"not possible to link one location to multiple warehouses. You can configure " +"as much locations as you need under one warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:15 +msgid "There are 3 types of locations:" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:17 +msgid "" +"The **Physical Locations** are internal locations that are part of the " +"warehouses for which you are the owner. They can be the loading and " +"unloading area of your warehouse, a shelf or a department, etc." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:21 +msgid "" +"The **Partner Locations** are spaces within a customer and/or vendor's " +"warehouse. They work the same way as Physical Locations with the only " +"difference being that you are not the owner of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:25 +msgid "" +"The **Virtual Locations** are places that do not exist, but in which " +"products can be placed when they are not physically in an inventory yet (or " +"anymore). They come in handy when you want to place lost products out of " +"your stock (in the **Inventory loss**), or when you want to take into " +"account products that are on their way to your warehouse (**Procurements**)." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:31 +msgid "" +"In Odoo, locations are structured hierarchically. You can structure your " +"locations as a tree, dependent on a parent-child relationship. This gives " +"you more detailed levels of analysis of your stock operations and the " +"organization of your warehouses." +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:37 +#: ../../inventory/settings/warehouses/location_creation.rst:44 +msgid ":doc:`warehouse_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:38 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:48 +msgid ":doc:`location_creation`" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:3 +msgid "How to create a new location?" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:9 +msgid "Creating a new location" +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:11 +msgid "" +"In order to be able to create new locations, you must allow the system to " +"manage multiple locations. In the **Inventory** module, open the menu " +":menuselection:`Configuration --> Settings`. In the **Location & Warehouse**" +" section, tick the **Manage several locations per warehouse** box, then " +"click on **Apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:20 +msgid "" +"In the **Inventory** module, open :menuselection:`Configuration --> " +"Warehouse Management --> Locations` In the Locations window, click on " +"**Create**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:24 +msgid "" +"Type the name of the location in the **Location Name** field, and select the" +" **Parent Location** in the list. The parent location can be a physical, " +"partner or virtual location, and you can add as many sub-locations as needed" +" to a location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:29 +msgid "" +"You can also fill in the **Additional Information** fields and add a note to" +" describe your location." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:35 +msgid "When you are finished, click on **Save**." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:38 +msgid "" +"A warehouse also corresponds to a location. As the locations are " +"hierarchical, Odoo will create the parent location of the warehouse, " +"containing all the sublocations in it." +msgstr "" + +#: ../../inventory/settings/warehouses/location_creation.rst:43 +#: ../../inventory/settings/warehouses/warehouse_creation.rst:47 +msgid ":doc:`difference_warehouse_location`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:3 +msgid "How to create a new warehouse?" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:11 +msgid "" +"In order to be able to create a new warehouse, you must allow the system to " +"manage multiple locations. In the **Inventory** module, open the menu " +":menuselection:`Settings --> Configuration`. In the **Location & Warehouse**" +" section, tick the **Manage several locations per warehouse** box, then " +"click on **apply**." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:20 +msgid "" +"Open the menu :menuselection:`Configuration --> Warehouse Management --> " +"Warehouses`" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:22 +msgid "" +"In the warehouses screen, click on **Create**. A new screen appears, with 3 " +"fields :" +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:25 +msgid "In **Warehouse Name**, insert the full name of the warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:27 +msgid "" +"In the **Short Name** field, insert a 5-characters code for your warehouse. " +"Keep in mind that this code is the one that will appear in the lists, so " +"make sure you choose a name that is easy to understand and easy to enter." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:32 +msgid "" +"In the **Address** field, you can select an existing company or create one " +"on-the-go. Therefore, the address of your warehouse will be the same as the " +"one of the company you selected. You can also leave this field empty and " +"edit it afterwards." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:40 +msgid "Click on **Save** to finish configuring your new warehouse." +msgstr "" + +#: ../../inventory/settings/warehouses/warehouse_creation.rst:43 +msgid "" +"When you create a warehouse, the system will create the necessary picking " +"types and main child locations for this main location in the background." +msgstr "" + +#: ../../inventory/shipping/operation.rst:3 +msgid "Shipping Operations" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:12 +msgid "" +"It will allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:20 +msgid "" +"If the delivery order is not **Validated**, then the request hasn't been " +"made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:24 +msgid "" +"If you have clicked on **Validate**, the request has been made and you " +"should have received the tracking number and the label. You can still cancel" +" the request. Simply click on the **Cancel** button next to the **Carrier " +"Tracking Ref**:" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:42 +msgid "" +"After cancelling the shipping request, you can change the carrier you want " +"to use. Confirm it by clicking on the **Send to shipper** button. You will " +"get a new tracking number and a new label." +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:50 +#: ../../inventory/shipping/operation/labels.rst:115 +#: ../../inventory/shipping/operation/multipack.rst:83 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../inventory/shipping/operation/cancel.rst:51 +#: ../../inventory/shipping/operation/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:8 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:10 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:13 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:18 +msgid "" +"To configure the price of your delivery methods, go to the **Inventory** " +"app, click on :menuselection:`Configuration --> Delivery --> Delivery " +"Methods`." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:21 +msgid "" +"You can manually set a price for the shipping: It can be fixed or based on " +"rules." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:24 +msgid "" +"Or you can use the transportation company computation system. Read the " +"document :doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:28 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:31 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:33 +#: ../../inventory/shipping/operation/invoicing.rst:55 +msgid "" +"On your sale order, choose the carrier that will be used. Click on " +"**Delivery Method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:39 +#: ../../inventory/shipping/operation/multipack.rst:36 +msgid "" +"The price is computed when you **save** the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:42 +msgid "" +"To invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product. It may vary from the real price." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:46 +msgid "" +"When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:53 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:61 +msgid "" +"The price is computed when you **save** the sale order. Confirm the sale " +"order and proceed to deliver the product." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:64 +msgid "" +"The real shipping cost are computed when the delivery order is validated." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:70 +msgid "" +"Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:76 +msgid "" +"When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:83 +msgid "" +"If you split the delivery and make several ones, each delivery order will " +"add a line to the sale order." +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:87 +msgid ":doc:`../setup/third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/operation/invoicing.rst:88 +#: ../../inventory/shipping/operation/multipack.rst:84 +msgid ":doc:`labels`" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:3 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers " +"linked with the transportation company tracking system. It allows you to " +"manage the transport company, the real prices and the destination. And " +"finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:18 +#: ../../inventory/shipping/setup/third_party_shipper.rst:17 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:20 +msgid "" +"In the **Inventory** module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:30 +#: ../../inventory/shipping/setup/delivery_method.rst:34 +#: ../../inventory/shipping/setup/third_party_shipper.rst:33 +msgid "Configure the delivery method" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:32 +#: ../../inventory/shipping/setup/delivery_method.rst:36 +#: ../../inventory/shipping/setup/third_party_shipper.rst:35 +msgid "" +"To configure your delivery methods, go to the **Inventory** module, click on" +" :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:35 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:41 +msgid "" +"In the **Pricing** tab, the name of the provider means that the delivery " +"will be handled and computed by the shipper system." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:46 +msgid "" +"The first one is linked to **your account** (develop key, password,...). For" +" more information, please refer to the provider website." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:49 +#: ../../inventory/shipping/setup/third_party_shipper.rst:62 +msgid "" +"The second column varies according to the **provider**. You can choose the " +"packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:52 +#: ../../inventory/shipping/setup/third_party_shipper.rst:65 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:55 +#: ../../inventory/shipping/setup/third_party_shipper.rst:77 +msgid "Company configuration" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:57 +#: ../../inventory/shipping/setup/third_party_shipper.rst:79 +msgid "" +"In order to compute the right price, the provider needs your company " +"information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:64 +#: ../../inventory/shipping/setup/third_party_shipper.rst:86 +msgid "" +"To check your information, go to the **Settings** application and click on " +"**General Settings**. Click on the first link **Configure your company " +"data**." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:68 +#: ../../inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:70 +#: ../../inventory/shipping/setup/third_party_shipper.rst:92 +msgid "" +"The shipper companies need the weight of your product, otherwise the price " +"computation cannot be done." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:73 +msgid "" +"Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open " +"the products you want to ship and set a weight on it." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:80 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to do" +" the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:85 +msgid "How to print shipping labels ?" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:87 +msgid "" +"The delivery order created from the sale order will take the shipping " +"information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:90 +#: ../../inventory/shipping/setup/third_party_shipper.rst:135 +msgid "" +"If you create a delivery transfer from the inventory module, you can add the" +" third party shipper in the additional info tab." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:96 +msgid "" +"Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:98 +#: ../../inventory/shipping/setup/third_party_shipper.rst:151 +msgid "" +"The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../inventory/shipping/operation/labels.rst:110 +msgid "" +"If you are doing multi-packages shippings, most of the time, there will be " +"one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:3 +msgid "How to manage multiple packs for the same delivery order?" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:8 +msgid "" +"By default, Odoo considers that your delivery is composed of one package. " +"But you can easily ship your deliveries with more than one package. It is " +"fully integrated with the third-party shippers." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:15 +msgid "" +"To configure the use of packages, go to the menu :menuselection:`Inventory " +"--> Configuration --> Settings`. Locate the **Packages** section and tick " +"**Record packages used on packing: pallets, boxes,...**" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:29 +#: ../../inventory/shipping/setup/delivery_method.rst:77 +#: ../../inventory/shipping/setup/third_party_shipper.rst:110 +msgid "Sale order" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:34 +msgid "Click on a **Delivery Method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:40 +msgid "Multi-packages Delivery" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:42 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:48 +msgid "From here, you can split your delivery into multiple packages." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:66 +msgid "Multi-packages with a 3rd party-shipper" +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:68 +msgid "" +"Once the delivery order is validated, you will receive the tracking number. " +"The **carrier Tracking ref** field will automatically be filled. Click on " +"the **Tracking** button to check your delivery on the provider website." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:76 +msgid "" +"The **labels** to stick on your packages are available in the history " +"underneath:" +msgstr "" + +#: ../../inventory/shipping/setup.rst:3 +msgid "Shipping Setup" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:3 +msgid "How to setup a delivery method?" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:8 +msgid "" +"Odoo can handle various delivery methods, but it is not activated by " +"default. Delivery methods can be used for your sale orders, your deliveries " +"but also on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:12 +msgid "" +"Delivery methods allow you to manage the transport company, the price and " +"the destination. You can even integrate Odoo with external shippers to " +"compute the real price and the packagings." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:20 +msgid "Install the inventory module" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:22 +msgid "" +"Delivery methods are handled by the **Delivery costs** module. Go to " +"**Apps** and search for the module. You should remove the **Apps** filter in" +" order to see it :" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:30 +#: ../../inventory/shipping/setup/third_party_shipper.rst:29 +msgid "" +"If you want to integrate delivery methods in your e-commerce, you'll have to" +" install the **eCommerce Delivery** module." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:39 +msgid "First set a name and a transporter company." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:44 +msgid "" +"Then you'll have to set the pricing. It can be fixed or based on rules." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:46 +msgid "" +"If the price is fixed, tick **Fixed price**. You'll just have to define the " +"price. If you want the delivery to be free above a certain amount, tick the " +"option **Free if Order total is more than** and set a price." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:54 +msgid "" +"If the price varies according to rules, tick **Based on Rules**. Click on " +"**add an item to a pricing rule**. Choose a condition based on either the " +"weight, the volume, the price or the quantity." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:61 +msgid "" +"Finally you can limit the delivery method to a few destinations. The limit " +"can be applied to some countries, states or even zip codes. This feature " +"limits the list of countries on your e-commerce." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:69 +msgid "" +"You can integrate Odoo with external shippers in order to compute the real " +"price and packagings, and handle the printing the shipping labels. See " +":doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:82 +msgid "" +"You can now choose the **Delivery Method** on your sale order. If you want " +"to invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:88 +#: ../../inventory/shipping/setup/third_party_shipper.rst:130 +msgid "Delivery" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:90 +msgid "You can add or change the delivery method on the delivery itself." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:95 +msgid "" +"On the delivery, check the **Carrier Information**. The carrier is the " +"chosen delivery method." +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:99 +msgid ":doc:`third_party_shipper`" +msgstr "" + +#: ../../inventory/shipping/setup/delivery_method.rst:100 +#: ../../inventory/shipping/setup/third_party_shipper.rst:158 +msgid ":doc:`../operation/invoicing`" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:9 +msgid "A DHL Password" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:11 +msgid "A DHL Account Number" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:15 +msgid "" +"Getting SiteID and password for countries other than United States (UK and " +"Rest of the world)" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:17 +msgid "" +"You should contact DHL account manager and request integration for XML " +"Express API. The presales should provide you live credentials." +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:22 +msgid "" +"You need to write to xmlrequests@dhl.com along with your full Account " +"details like account number, region, address, etc. to get API Access." +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:24 +msgid "" +"In meantime, for testing the solution, you can use the tests credentials as " +"given in the demo data:" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:26 +msgid "**SiteID**: CustomerTest" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:28 +msgid "**Password**: alkd89nBV" +msgstr "" + +#: ../../inventory/shipping/setup/dhl_credentials.rst:30 +msgid "**DHL Account Number**: 803921577" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo can be linked with the transportation company tracking system. It will " +"allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:19 +msgid "" +"In the inventory module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:38 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created. Most of the time, there will be **2** delivery methods for the same" +" provider: one for **international** shipping and the other for **domestic**" +" shipping." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:43 +msgid "" +"You can create other methods with the same provider with other " +"configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:46 +msgid "" +"You can change the **Name** of the delivery method. This is the name that " +"will appear on your ecommerce." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:49 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:54 +msgid "" +"In the pricing tab, the name of the provider chosen under the **Price " +"computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:57 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:59 +msgid "" +"The first one is linked to **your account** (developer key, password,...). " +"For more information, please refer to the provider website." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:67 +msgid "" +"Finally you can limit the delivery method to a few destinations. You can " +"limit it to some countries, states or even zip codes. This feature limits " +"the list of countries on your e-commerce. It is useful for the domestic " +"providers. For example, USPS US only delivers from the United States to the " +"United States." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:95 +msgid "" +"Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products" +" you want to ship and set a weight on it." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:102 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to " +"make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:115 +msgid "" +"You can now choose the carrier on your sale order. Click on **Delivery " +"method** to choose the right one." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:118 +msgid "" +"The price is computed when you save the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:121 +msgid "" +"If you want to invoice the price of the delivery charge on the sale order, " +"click on **Set price**, it will add a line with the name of the delivery " +"method as a product. It may vary from the real price." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:125 +msgid "" +"Otherwise, the real price (computed when the delivery is validated) will " +"automatically be added to the invoice. For more information, please read the" +" document :doc:`../operation/invoicing`" +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:132 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it. You can change the carrier if you want to." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:141 +msgid "" +"The weight is computed based on the products weights. The shipping cost will" +" be computed once the transfer is validated." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:144 +msgid "" +"Click on **Validate** to receive the tracking number. The **Carrier Tracking" +" ref** field will automatically be filled. Click on the **Tracking** button " +"to check your delivery on the provider website." +msgstr "" + +#: ../../inventory/shipping/setup/third_party_shipper.rst:159 +msgid ":doc:`../operation/labels`" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:13 +msgid "" +"An Access Key is a 16 character alpha-numeric code that allows access to the" +" UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:19 +msgid "" +"Note that only customers located in the US can open a UPS account online. If" +" you are located outside the US, you will need to contact UPS Customer " +"Service in order to to open an account." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:23 +msgid "" +"You can read additional information about opening a UPS account on the their" +" website, on the page, `How to Open a UPS Account Online " +"<https://www.ups.com/content/us/en/resources/sri/openaccountonline.html?srch_pos=2&srch_phr=open+ups+account>`_" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:27 +msgid "" +"If you don't already have a UPS account, you can create one along with your " +"online profile by following these steps:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:30 +msgid "" +"1. Access the UPS.com web site at `www.ups.com <http://www.ups.com/>`__, and" +" click the **New User** link at the top of the page." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:34 +msgid "" +"2. Click the **Register for MyUPS** button, and follow the prompts to " +"complete the registration process." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:37 +msgid "" +"If you already have a UPS account, you can add it to your online profile as " +"follows:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:39 +msgid "" +"1. Log in to the UPS.com site (`http://www.ups.com <http://www.ups.com/>`__)" +" using your UPS.com User ID and Password." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:43 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:45 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:47 +msgid "" +"4. Click the **Add an Existing UPS Account** link in the **UPS Account " +"Details** section of the page." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:50 +msgid "" +"5. In the **Add New Account** screen, enter the **UPS Account Number**, " +"**Account Name**, and **Postal Code** fields. The country defaults to United" +" States.q" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:54 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:57 +msgid "Get an Access Key" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:59 +msgid "" +"After you have added your UPS account number to your user profile you can " +"request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:62 +msgid "" +"1. Go to the **UPS Developer Kit** web page " +"`https://www.ups.com/upsdeveloperkit?loc=en\\_US " +"<https://www.ups.com/upsdeveloperkit?loc=en_US>`__" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:65 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:67 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:69 +msgid "Verify your contact information" +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:71 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../inventory/shipping/setup/ups_credentials.rst:73 +msgid "" +"The **Access Key** will be provided to you on the web page, and an email " +"with the Access Key will be sent to the email address of the primary " +"contact." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/manufacturing.po b/locale/tr/LC_MESSAGES/manufacturing.po new file mode 100644 index 000000000..4940e7340 --- /dev/null +++ b/locale/tr/LC_MESSAGES/manufacturing.po @@ -0,0 +1,729 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Murat Kaplan <muratk@projetgrup.com>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../manufacturing.rst:5 +msgid "Manufacturing" +msgstr "" + +#: ../../manufacturing/operations.rst:3 +msgid "Manufacturing Operations" +msgstr "" + +#: ../../manufacturing/operations/replenishment.rst:3 +msgid "Replenishment Strategies" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:3 +msgid "How to select the right replenishment strategy" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:5 +msgid "" +"Minimum Stock rules and Make to Order have similar consequences but " +"different rules. They should be used depending on your manufacturing and " +"delivery strategies." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:15 +msgid "" +"Minimum Stock rules are used to ensure that you always have the minimum " +"amount of a product in stock in order to manufacture your products and/or " +"answer to your customer needs. When the stock level of a product reaches its" +" minimum the system will automatically generate a procurement order with the" +" quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:22 +#: ../../manufacturing/operations/replenishment/strategies.rst:58 +msgid "Make to Order" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:24 +msgid "" +"The Make to Order function will trigger a Purchase Order of the amount of " +"the Sales Order related to the product. The system will **not** check the " +"current stock. This means that a draft purchase order will be generated " +"regardless of the quantity on hand of the product." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:30 +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:27 +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:62 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../manufacturing/operations/replenishment/strategies.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:35 +msgid "" +"The Minimum Stock Rules configuration is available through your Inventory " +"module. In the Inventory Control menu select \"Reordering Rule\" in the drop" +" down menu. There, click on \"Create\" to set minimum and maximum stock " +"values for a given product." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:44 +msgid "" +"Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity " +"multiple\" fields" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:47 +msgid "" +"Then, click on your product to access the related product form and, on the " +"\"Inventory submenu\", do not forget to select a supplier." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:54 +msgid "" +"Don't forget to select the right product type. A consumable can not be " +"stocked and will thus not be accounted for in the stock valuation." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:60 +msgid "" +"The Make to Order configuration is available on your product form through " +"your :menuselection:`Inventory --> Inventory control --> Products` (or any " +"other module where products are available)." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:64 +msgid "On the product form, under Inventory, click on \"Make To Order\"." +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:70 +msgid "Choice between the two options" +msgstr "" + +#: ../../manufacturing/operations/replenishment/strategies.rst:72 +msgid "" +"The choice between the two options is thus dependent of your inventory " +"strategy. If you prefer to have a buffer and always have at least a minimum " +"amount, the minimum stock rule should be used. If you want to reorder your " +"stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../manufacturing/overview.rst:3 +msgid "Overview" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials.rst:3 +#: ../../manufacturing/overview/main_concepts/terminologies.rst:6 +msgid "Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:3 +msgid "How to Sell a Set of Products as a Kit" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:5 +msgid "" +"A *kit* is a set of components that are delivered without first being " +"assembled or mixed. Kits are described in Odoo using *bills of materials*. " +"There are two basic ways to configure kits, depending on how stock of the " +"kit product is to be managed. In either case, both the Inventory and " +"Manufacturing apps must be installed." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:12 +msgid "Manage Stock of Component Products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:14 +msgid "" +"If you would like to assemble kits as they are ordered, managing stock of " +"the kit *components* only, you will use a Kit BoM without a manufacturing " +"step." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:18 +msgid "" +"A product using a Kit BoM will appear as a single line item on a quotation " +"and sales order, but will generate a delivery order with one line item for " +"each of the components of the kit. In the examples below, the image at left " +"shows a sales order for the kit \"Custom Computer Kit\", while the image at " +"right shows the corresponding delivery order." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:24 +msgid "|image0|\\ |image1|" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:29 +msgid "" +"From the **Products** menu in either the Inventory or Manufacturing app, " +"create each component product as you would any other product, then create " +"the top-level, or kit product. The kit product should have only the route " +"**Manufacture** set. Because you cannot track the stock of kit products, the" +" Product Type should be set to **Consumable**. Because a kit product cannot " +"be purchased, **Can be Purchased** should be unchecked." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:37 +msgid "" +"All other parameters on the kit product may be modified according to your " +"preference. The component products require no special configuration." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:44 +msgid "" +"Once the products are configured, create a bill of materials for the kit " +"product. Add each component and its quantity. Select the BoM Type **Ship " +"this product as a set of components**. All other options may be left with " +"their default values." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:53 +msgid "Manage Stock of Kit Product and Component Products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:55 +msgid "" +"If you would like to manage stock of the top-level kit product, you will use" +" a standard BoM with a manufacturing step instead of a Kit BoM. When using a" +" standard BoM to assemble kits, a manufacturing order will be created. The " +"manufacturing order must be registered as completed before the kit product " +"will appear in your stock." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:64 +msgid "" +"On the kit product, select the route **Manufacture**. You may also select " +"**Make to Order**, which will create a manufacturing order whenever a sales " +"order is confirmed. Select the product type **Stockable Product** to enable " +"stock management." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:72 +msgid "" +"When you create the bill of materials, select the BoM Type **Manufacture " +"this product**. The assembly of the kit will be described by a manufacturing" +" order rather than a packing operation." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:3 +msgid "How to manage BoMs for product variants" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:5 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:125 +msgid "" +"Odoo allows you to use one bill of materials for multiple variants of the " +"same product. Simply enable variants from :menuselection:`Configuration --> " +"Settings`." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:12 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:132 +msgid "" +"You will then be able to specify which component lines are to be used in the" +" manufacture of each product variant. You may specify multiple variants for " +"each line. If no variant is specified, the line will be used for all " +"variants." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:17 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:137 +msgid "" +"When defining variant BoMs on a line-item-basis, the **Product Variant** " +"field in the main section of the BoM should be left blank. This field is " +"used when creating a BoM for one variant of a product only." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:3 +msgid "How to manage semi-finished products" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:5 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:83 +msgid "" +"A subassembly is a manufactured product which is intended to be used as a " +"component of another manufactured product. You may wish to employ sub-" +"assemblies to simplify a complex BoM, to more accurately represent your " +"manufacturing flow, or to use the same subassembly in multiple BoMs. A BoM " +"that employs subassemblies is often referred to as a multi-level BoM." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:12 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:90 +msgid "" +"Multi-level bills of materials in Odoo are accomplished by creating a top-" +"level BoM and subassembly BoMs. Next, the procurement route of the " +"subassembly product is defined. This ensures that every time a manufacturing" +" order for the top-level product is created, a manufacturing order for each " +"subassembly is created as well." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:19 +msgid "Configure the Top -Level Product BoM" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:21 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:99 +msgid "" +"To configure a multi-level BoM, create the top-level product and its BoM. " +"Include any subassemblies in the list of components. Create a BoM for each " +"subassembly as you would for any product." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:29 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:107 +msgid "Configure the Subassembly Product Data" +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:31 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:109 +msgid "" +"On the product form of the subassembly, you must select the routes " +"**Manufacture** and **Make To Order**. The **Manufacture** route takes " +"precedence over the **Buy** route, so selecting the latter will have no " +"effect." +msgstr "" + +#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:39 +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:117 +msgid "" +"If you would like to be able to purchase the subassembly in addition to " +"manufacturing it, select **Can be Purchased**. All other fields on the " +"subassembly product form may be configured according to your preference." +msgstr "" + +#: ../../manufacturing/overview/getting_started.rst:3 +msgid "Getting Started" +msgstr "" + +#: ../../manufacturing/overview/getting_started.rst:5 +msgid "How to consume composents to make a finished product" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:3 +msgid "How to create a Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:5 +msgid "" +"A bill of materials (BoM) is a document that describes the component " +"products, the quantity of each component, and the process required to " +"manufacture a product, including a routing and individual steps." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:9 +msgid "" +"In Odoo, each product may have multiple BoMs associated with it, but a BoM " +"can only be associated with a single product. A single BoM can, however, " +"describe multiple variants of the same product." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:14 +msgid "Setting up a Basic BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:16 +msgid "" +"If you choose to manage your manufacturing operations using manufacturing " +"orders only, you will define basic bills of materials without routings. For " +"more information about which method of management to use, review the " +"**Getting Started** section of the *Manufacturing* chapter of the " +"documentation." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:22 +msgid "" +"Before creating your first bill of materials, you will need to create a " +"product and at least one component (components are considered products in " +"Odoo). You can do so from :menuselection:`Master Data --> Products`, or on " +"the fly from the relevant fields on the BoM form. Review the Inventory " +"chapter for more information about configuring products. Once you have " +"created a product and at least one component, select them from the relevant " +"dropdown menus to add them to your bill of materials. A new bill of " +"materials can be created from :menuselection:`Master Data --> Bills of " +"Materials`, or using the button on the top of the product form." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:32 +msgid "" +"Under the **Miscellaneous** tab, you can fill additional fields. " +"**Sequence** defines the order in which your BoMs will be selected for " +"production orders, with lower numbers having higher priority. **Version** " +"allows you to track changes to your BoM over time." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:38 +msgid "Adding a Routing to a BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:40 +msgid "" +"A routing defines a series of operations required to manufacture a product " +"and the work center at which each operation is performed. A routing may be " +"added to multiple BoMs, though a BoM may only have one routing. For more " +"information about configuring routings, review the chapter on routings." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:46 +msgid "" +"After enabling routings from :menuselection:`Configuration --> Settings`, " +"you will be able to add a routing to a bill of materials by selecting a " +"routing from the dropdown list or creating one on the fly." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:50 +msgid "" +"You may define the work operation or step in which each component is " +"consumed using the field, **Consumed in Operation** under the **Components**" +" tab. Similarly, you can define the operation at which the product will be " +"produced under the **Miscellaneous** tab using the field **Produced at " +"Operation**. If this field is left blank, the products will be " +"consumed/produced at the final operation in the routing." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:61 +msgid "Adding Byproducts to a BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:63 +msgid "" +"In Odoo, a byproduct is any product produced by a BoM in addition to the " +"primary product." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:66 +msgid "" +"To add byproducts to a BoM, you will first need to enable them from " +":menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:72 +msgid "" +"Once byproducts are enabled, you can add them to your bills of materials " +"under the **Byproducts** tab of the bill of materials. You can add any " +"product or products as byproducts. Byproducts are produced in the same step " +"of the routing as the primary product of the BoM." +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:81 +msgid "Setting up a BoM for a Product With Sub-Assemblies" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:97 +msgid "Configure the Top-Level Product BoM" +msgstr "" + +#: ../../manufacturing/overview/getting_started/bill_configuration.rst:123 +msgid "Using a Single BoM to Describe Several Variants of a Single Product" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:3 +msgid "How to process a manufacturing order" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:8 +msgid "" +"There are two basic ways to manage manufacturing in Odoo. The first way " +"manages work with one document only. This document is the **manufacturing " +"order**. The second way uses additional documents to give you more precise " +"control over the manufacturing process. In this way, **Manufacturing " +"orders** are divided into one or more steps defined by **work orders**, " +"performed in an order defined by **routings**." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:17 +msgid "How to manage manufacturing without routings" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:19 +msgid "" +"You will most likely use manufacturing orders without routings if all the " +"work to produce your product is performed in one place, by one person, in " +"one step, and/or you do not need the level of granular control afforded by " +"work orders and routings." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:24 +msgid "" +"Managing your operations in this way is the default behavior in Odoo. There " +"are two basic phases from planning to production:" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:27 +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:52 +msgid "Create manufacturing orders" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:29 +msgid "Record Production" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:32 +msgid "How to manage manufacturing with routings and work orders" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:34 +msgid "" +"To use work orders and routings, you will need to enable the option **Manage" +" production by work orders** From :menuselection:`Configuration --> " +"Settings`. You will then be able to add routings to bills of materials, and " +"configure some additional related fields. You will also be able to create " +"**work centers**, the locations at which work orders are performed." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:41 +msgid "" +"When manufacturing with routings and work orders, each work order is " +"scheduled individually. You will also have access to time and capacity " +"planning, and reports on costing and efficiency on a work center level." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:45 +msgid "" +"Manufacturing using routings can be broken down into several steps. When " +"configuring your BoM, you will need to add a routing defining the component " +"work orders. After planning the manufacturing order, you will have the added" +" step of scheduling work orders." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:50 +msgid "The workflow is thus divided into three basic phases, as follows:" +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:54 +msgid "Schedule the associated work orders." +msgstr "" + +#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:56 +msgid "Perform the scheduled work and record production." +msgstr "" + +#: ../../manufacturing/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:3 +msgid "Introduction to Odoo Manufacturing" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/intro.rst:13 +msgid "Work in progress." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:3 +msgid "Manufacturing Terminologies" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:9 +msgid "" +"A bill of materials (BoM) is a document that describes the materials, the " +"quantity of each material, and the steps required to manufacture a product. " +"Depending on the industry and the nature of the finished product, a " +"different name may be used to describe the same document. For example, in " +"the pharmaceutical industry, the term “recipe” may be used." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:14 +msgid "Cycle" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:17 +msgid "" +"A production cycle is a frame of time during which an entire manufacturing " +"process can be fulfilled." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:19 +msgid "Downtime or Leave" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:22 +msgid "" +"Time during which a resource is unavailable. If the resource is a machine, " +"the unavailability is downtime, while if the resource is human, unavailable " +"time is called a Leave." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:25 +msgid "Finished products" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:28 +msgid "" +"Finished products are the final output of a manufacturing process. They are " +"normally not intended to be used as input into another manufacturing order " +"of the company." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:31 +msgid "Kit" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:34 +msgid "" +"A kit is a set of components that are described by a bill of materials, but " +"which are delivered separately rather than assembled or mixed." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:36 +msgid "Multi-level Bill of Materials" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:39 +msgid "" +"A bill of material can quickly grow very complex. To keep it manageable, it " +"can be broken down into several smaller manufactured parts, each having its " +"own BOM. These parts are typically referred to as sub-assembly of " +"intermediate products." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:44 +msgid "" +"Defining a BOM in multiple levels reduces the complexity of the top-level " +"document and allows components to be reused in other BoMs." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:46 +msgid "Phantom Bill of Material" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:49 +msgid "" +"A phantom bill of material is always used in the context of multi-level " +"BOMs. It allows to add a sub-assembly as part of a bigger end-product while " +"avoiding to trigger a separate manufacturing order for the sub-assembly." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:54 +msgid "" +"As such, when a manufacturing order for the final product is launched, the " +"components of the sub-assembly are reflected in the parent BOM as if they " +"were direct components of the parent BOM." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:58 +msgid "" +"Phantom BOM are thus used for grouping a set of components with the aim of " +"reusing them in many other BOM without the need to launch separate " +"manufacturing orders for the sub-assemblies." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:61 +msgid "Raw Materials" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:64 +msgid "" +"Raw materials and components constitute the input that are transformed to " +"produce semi-finished or finished goods." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:67 +msgid "" +"The transformation here can take many aspects according to the industry. It " +"can be simple assembly, welding, mixing, etc." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:69 +msgid "Routing" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:72 +msgid "" +"A routing is a document that describes a series of Work Orders and the Work " +"Centers at which they will be carried out" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:74 +msgid "Semi-finished products and sub-assemblies" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:77 +msgid "" +"These are products which are manufactured with the purpose to be consumed in" +" another manufacturing order." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:79 +msgid "Work Order Operations" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:82 +msgid "" +"Work Order Operations specify the set of activities necessary to fully " +"process a manufacturing order. Each activity or operation takes some time to" +" be completed and is performed into a determined production unit (also " +"called work center)." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:86 +msgid "Work Order" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:89 +msgid "" +"A work order is a single manufacturing operation that is scheduled for " +"execution on a given date and a given duration." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:91 +msgid "Work Center" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:94 +msgid "" +"Work centers identify production units and their resources. They are used to" +" represent the plant capacity as well as costing information. The capacity " +"is a combination of resources and their availability time." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:97 +msgid "Resources" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:100 +msgid "" +"In manufacturing a resource can be a human being (employee) or machine " +"available in a work center." +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:102 +msgid "Working Time" +msgstr "" + +#: ../../manufacturing/overview/main_concepts/terminologies.rst:105 +msgid "" +"Each resource has its normal working time. For instance, machines can be set" +" up to operate 7 days a week 20 hours out of 24." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/point_of_sale.po b/locale/tr/LC_MESSAGES/point_of_sale.po new file mode 100644 index 000000000..2fac8f4f7 --- /dev/null +++ b/locale/tr/LC_MESSAGES/point_of_sale.po @@ -0,0 +1,2948 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Murat Kaplan <muratk@projetgrup.com>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../point_of_sale.rst:5 +msgid "Point of Sale" +msgstr "" + +#: ../../point_of_sale/advanced.rst:3 +msgid "Advanced topics" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:3 +msgid "How to use discount tags on products?" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:5 +msgid "This tutorial will describe how to use discount tags on products." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:8 +msgid "Barcode Nomenclature" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:10 +msgid "" +"To start using discounts tags, let's first have a look at the **barcode " +"nomenclature** in order to print our correct discounts tags." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:13 +msgid "I want to have a discount for the product with the following barcode." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:18 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Barcode " +"Nomenclatures`. In the default nomenclature, you can see that to set a " +"discount, you have to start you barcode with ``22`` and the add the " +"percentage you want to set for the product." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:26 +msgid "" +"For instance if you want ``50%`` discount on a product you have to start you" +" barcode with ``2250`` and then add the product barcode. In our example, the" +" barcode will be:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:34 +msgid "Scanning your products" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:36 +msgid "If you go back to the **dashboard** and start a **new session**" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:41 +msgid "You have to scan:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:43 +msgid "the product" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:45 +msgid "the discount tag" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:47 +msgid "When the product is scanned, it appears on the ticket" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:52 +msgid "" +"Then when you scan the discount tag, ``50%`` discount is applied on the " +"product." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:58 +msgid "That's it, this how you can use discount tag on products with Odoo." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:61 +#: ../../point_of_sale/advanced/loyalty.rst:114 +#: ../../point_of_sale/advanced/manual_discount.rst:83 +#: ../../point_of_sale/advanced/mercury.rst:94 +#: ../../point_of_sale/advanced/multi_cashiers.rst:171 +#: ../../point_of_sale/advanced/register.rst:57 +#: ../../point_of_sale/advanced/reprint.rst:35 +#: ../../point_of_sale/overview/start.rst:155 +#: ../../point_of_sale/restaurant/print.rst:69 +#: ../../point_of_sale/restaurant/split.rst:81 +#: ../../point_of_sale/restaurant/tips.rst:43 +#: ../../point_of_sale/restaurant/transfer.rst:35 +msgid ":doc:`../shop/cash_control`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:62 +#: ../../point_of_sale/advanced/loyalty.rst:115 +#: ../../point_of_sale/advanced/manual_discount.rst:84 +#: ../../point_of_sale/advanced/mercury.rst:95 +#: ../../point_of_sale/advanced/multi_cashiers.rst:172 +#: ../../point_of_sale/advanced/register.rst:58 +#: ../../point_of_sale/advanced/reprint.rst:36 +#: ../../point_of_sale/overview/start.rst:156 +#: ../../point_of_sale/restaurant/print.rst:70 +#: ../../point_of_sale/restaurant/split.rst:82 +#: ../../point_of_sale/restaurant/tips.rst:44 +#: ../../point_of_sale/restaurant/transfer.rst:36 +msgid ":doc:`../shop/invoice`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:63 +#: ../../point_of_sale/advanced/loyalty.rst:116 +#: ../../point_of_sale/advanced/manual_discount.rst:85 +#: ../../point_of_sale/advanced/mercury.rst:96 +#: ../../point_of_sale/advanced/multi_cashiers.rst:173 +#: ../../point_of_sale/advanced/register.rst:59 +#: ../../point_of_sale/advanced/reprint.rst:37 +#: ../../point_of_sale/overview/start.rst:157 +#: ../../point_of_sale/restaurant/print.rst:71 +#: ../../point_of_sale/restaurant/split.rst:83 +#: ../../point_of_sale/restaurant/tips.rst:45 +#: ../../point_of_sale/restaurant/transfer.rst:37 +msgid ":doc:`../shop/refund`" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:64 +#: ../../point_of_sale/advanced/loyalty.rst:117 +#: ../../point_of_sale/advanced/manual_discount.rst:86 +#: ../../point_of_sale/advanced/mercury.rst:97 +#: ../../point_of_sale/advanced/multi_cashiers.rst:174 +#: ../../point_of_sale/advanced/register.rst:60 +#: ../../point_of_sale/advanced/reprint.rst:38 +#: ../../point_of_sale/overview/start.rst:158 +#: ../../point_of_sale/restaurant/print.rst:72 +#: ../../point_of_sale/restaurant/split.rst:84 +#: ../../point_of_sale/restaurant/tips.rst:46 +#: ../../point_of_sale/restaurant/transfer.rst:38 +msgid ":doc:`../shop/seasonal_discount`" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:3 +msgid "How to create & run a loyalty & reward system" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:6 +#: ../../point_of_sale/advanced/manual_discount.rst:41 +#: ../../point_of_sale/advanced/multi_cashiers.rst:37 +#: ../../point_of_sale/advanced/multi_cashiers.rst:88 +#: ../../point_of_sale/advanced/reprint.rst:6 +#: ../../point_of_sale/overview/start.rst:22 +#: ../../point_of_sale/restaurant/print.rst:6 +#: ../../point_of_sale/restaurant/split.rst:6 +#: ../../point_of_sale/restaurant/tips.rst:6 +#: ../../point_of_sale/shop/seasonal_discount.rst:6 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../point_of_sale/advanced/loyalty.rst:8 +msgid "" +"In the **Point of Sale** application, go to :menuselection:`Configuration " +"--> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:14 +msgid "" +"You can tick **Manage loyalty program with point and reward for customers**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:21 +msgid "Create a loyalty program" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:23 +msgid "" +"After you apply, go to :menuselection:`Configuration --> Loyalty Programs` " +"and click on **Create**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:29 +msgid "" +"Set a **name** and an **amount** of points given **by currency**, **by " +"order** or **by product**. Extra rules can also be added such as **extra " +"points** on a product." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:33 +msgid "To do this click on **Add an item** under **Rules**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:38 +msgid "You can configure any rule by setting some configuration values." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:40 +msgid "**Name**: An internal identification for this loyalty program rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:41 +msgid "**Type**: Does this rule affects products, or a category of products?" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:42 +msgid "**Target Product**: The product affected by the rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:43 +msgid "**Target Category**: The category affected by the rule" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:44 +msgid "" +"**Cumulative**: The points won from this rule will be won in addition to " +"other rules" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:45 +msgid "" +"**Points per product**: How many points the product will earn per product " +"ordered" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:46 +msgid "" +"**Points per currency**: How many points the product will earn per value " +"sold" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:51 +msgid "" +"Your new rule is now created and rewards can be added by clicking on **Add " +"an Item** under **Rewards**." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:57 +msgid "Three types of reward can be given:" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:59 +msgid "" +"**Resale**: convert your points into money. Set a product that represents " +"the value of 1 point." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:64 +msgid "" +"**Discount**: give a discount for an amount of points. Set a product with a " +"price of ``0 €`` and without any taxes." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:69 +msgid "**Gift**: give a gift for an amount of points" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:77 +msgid "Applying your loyalty program to a point of sale" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:79 +msgid "On the **Dashboard**, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:84 +msgid "Next to loyalty program, set the program you want to set." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:90 +msgid "Gathering and consuming points" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:92 +msgid "To start gathering points you need to set a customer on the order." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:94 +msgid "Click on **Customer** and select the right one." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:96 +msgid "Loyalty points will appear on screen." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:101 +msgid "" +"The next time the customer comes to your shop and has enough points to get a" +" reward, the **Rewards** button is highlighted and gifts can be given." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:108 +msgid "" +"The reward is added and of course points are subtracted from the total." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:3 +msgid "How to apply manual discounts?" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:6 +#: ../../point_of_sale/advanced/mercury.rst:6 +#: ../../point_of_sale/overview.rst:3 ../../point_of_sale/overview/start.rst:6 +msgid "Overview" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:8 +msgid "" +"You can apply manual discounts in two different ways. You can directly set a" +" discount on the product or you can set a global discount on the whole cart." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:13 +msgid "Discount on the product" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:15 +#: ../../point_of_sale/advanced/register.rst:8 +msgid "On the dashboard, click on **New Session**:" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:20 +msgid "You will get into the main point of sale interface :" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:25 +#: ../../point_of_sale/advanced/mercury.rst:76 +#: ../../point_of_sale/shop/cash_control.rst:53 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. If you click on a product, it will be added in the cart. You can " +"directly set the correct quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:30 +msgid "" +"The same way you insert a quantity, Click on **Disc** and then type the " +"discount (in percent). This is how you insert a manual discount on a " +"specific product." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:38 +msgid "Global discount" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:43 +msgid "" +"If you want to set a global discount, you need to go to " +":menuselection:`Configuration --> Settings` and tick **Allow global " +"discounts**" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:50 +msgid "Then from the dashboard, click on :menuselection:`More --> Settings`" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:55 +msgid "" +"You have to activate **Order Discounts** and create a product that will be " +"added as a product with a negative price to deduct the discount." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:61 +msgid "" +"On the product used to create the discount, set the price to ``0`` and do " +"not forget to remove all the **taxes**, that can make the calculation wrong." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:68 +msgid "Set a global discount" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:70 +msgid "" +"Now when you come back to the **dashboard** and start a **new session**, a " +"**Discount** button appears and by clicking on it you can set a " +"**discount**." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:76 +msgid "" +"When it's validated, the discount line appears on the order and you can now " +"process to the payment." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:3 +msgid "How to accept credit card payments in Odoo POS using Mercury?" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:8 +msgid "" +"A **MercuryPay** account (see `MercuryPay website " +"<https://www.mercurypay.com>`__.) is required to accept credit card payments" +" in Odoo 9 POS with an integrated card reader. MercuryPay only operates with" +" US and Canadian banks making this procedure only suitable for North " +"American businesses. An alternative to an integrated card reader is to work " +"with a standalone card reader, copy the transaction total from the Odoo POS " +"screen into the card reader, and record the transaction in Odoo POS." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:18 +msgid "Module installation" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:20 +msgid "" +"Go to **Apps** and install the **Mercury Payment Services** application." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:26 +msgid "Mercury Configuration" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:28 +msgid "" +"In the **Point of Sale** application, click on :menuselection:`Configuration" +" --> Mercury Configurations` and then on **Create**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:35 +msgid "Introduce your **credentials** and then save them." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:40 +msgid "" +"Then go to :menuselection:`Configuration --> Payment methods` and click on " +"**Create**. Under the **Point of Sale** tab you can set a **Mercury " +"configuration** to the **Payment method**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:47 +msgid "" +"Finally, go to :menuselection:`Configuration --> Point of Sale` and add a " +"new payment method on the point of sale by editing it." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:54 +msgid "" +"Then select the payment method corresponding to your mercury configuration." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:60 +msgid "Save the modifications." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:63 +#: ../../point_of_sale/shop/cash_control.rst:48 +msgid "Register a sale" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:65 +msgid "" +"On the dashboard, you can see your point(s) of sales, click on **New " +"Session**:" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:71 +#: ../../point_of_sale/overview/start.rst:114 +msgid "You will get the main point of sale interface:" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:82 +msgid "Payment with credit cards" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:84 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the credit" +" card **Payment Method**." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:90 +msgid "" +"Type in the **Amount** to be paid with the credit card. Now you can swipe " +"the card and validate the payment." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:3 +msgid "How to manage multiple cashiers?" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:5 +msgid "" +"This tutorial will describe how to manage multiple cashiers. There are four " +"differents ways to manage several cashiers." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:9 +msgid "Switch cashier without any security" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:11 +msgid "" +"As prerequisite, you just need to have a second user with the **Point of " +"Sale User** rights (Under the :menuselection:`General Settings --> Users` " +"menu). On the **Dashboard** click on **New Session** as the main user." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:18 +#: ../../point_of_sale/advanced/multi_cashiers.rst:64 +#: ../../point_of_sale/advanced/multi_cashiers.rst:123 +msgid "On the top of the screen click on the **user name**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:23 +msgid "And switch to another cashier." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:28 +msgid "" +"The name on the top has changed which means you have changed the cashier." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:34 +msgid "Switch cashier with pin code" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:39 +msgid "" +"If you want your cashiers to need a pin code to be able to use it, you can " +"set it up in by clicking on **Settings**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:45 +msgid "Then click on **Manage access rights**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:50 +msgid "" +"**Edit** the cashier and add a security pin code on the **Point of Sale** " +"tab." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:57 +msgid "Change cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:59 +#: ../../point_of_sale/advanced/multi_cashiers.rst:118 +msgid "On the **Dashboard** click on **New Session**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:69 +msgid "Choose your **cashier**:" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:74 +msgid "" +"You will have to insert the user's **pin code** to be able to continue." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:79 +msgid "Now you can see that the cashier has changed." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:85 +msgid "Switch cashier with cashier barcode badge" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:90 +msgid "" +"If you want your cashiers to scan its badge, you can set it up in by " +"clicking on **Settings**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:96 +msgid "Then click on **Manage access rights**" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:101 +msgid "" +"**Edit** the cashier and add a **security pin code** on the **Point of " +"Sale** tab." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:108 +msgid "" +"Be careful of the barcode nomenclature, the default one forced you to use a " +"barcode starting with ``041`` for cashier barcodes. To change that go to " +":menuselection:`Point of Sale --> Configuration --> Barcode Nomenclatures`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:116 +msgid "Change Cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:128 +msgid "" +"When the cashier scans his own badge, you can see on the top that the " +"cashier has changed." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:132 +msgid "Assign session to a user" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:134 +msgid "" +"Click on the menu :menuselection:`Point of Sale --> Orders --> Sessions`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:139 +msgid "" +"Then, click on **New** and assign as **Responsible** the correct cashier to " +"the point of sale." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:145 +msgid "When the cashier logs in he is able to open the session" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:151 +msgid "Assign a default point of sale to a cashier" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:153 +msgid "" +"If you want your cashiers to be assigned to a point of sale, go to " +":menuselection:`Point of Sales --> Configuration --> Settings`." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:159 +msgid "Then click on **Manage Access Rights**." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:164 +msgid "" +"**Edit** the cashier and add a **Default Point of Sale** under the **Point " +"of Sale** tab." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:3 +msgid "How to register customers?" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:6 +#: ../../point_of_sale/restaurant/split.rst:21 +#: ../../point_of_sale/shop/invoice.rst:6 +#: ../../point_of_sale/shop/seasonal_discount.rst:78 +msgid "Register an order" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:13 +msgid "You arrive now on the main view :" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:18 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. If you click on a product, it will be added in the cart. You can " +"directly set the quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:23 +msgid "Record a customer" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:25 +msgid "On the main view, click on **Customer**:" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:30 +msgid "Register a new customer by clicking on the button." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:35 +msgid "The following form appear. Fill in the relevant information:" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:40 +msgid "When it's done click on the **floppy disk** icon" +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:45 +msgid "" +"You just registered a new customer. To set this customer to the current " +"order, just tap on **Set Customer**." +msgstr "" + +#: ../../point_of_sale/advanced/register.rst:51 +msgid "The customer is now set on the order." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:3 +msgid "How to reprint receipts?" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:8 +msgid "This feature requires a POSBox and a receipt printer." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:10 +msgid "" +"If you want to allow a cashier to reprint a ticket, go to " +":menuselection:`Configuration --> Settings` and tick the option **Allow " +"cashier to reprint receipts**." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:17 +msgid "" +"You also need to allow the reprinting on the point of sale. Go to " +":menuselection:`Configuration --> Point of Sale`, open the one you want to " +"configure and and tick the option **Reprinting**." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:25 +msgid "How to reprint a receipt?" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:27 +msgid "" +"In the Point of Sale interface click on the **Reprint Receipt** button." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:32 +msgid "The last printed receipt will be printed again." +msgstr "" + +#: ../../point_of_sale/analyze.rst:3 +msgid "Analyze sales" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:3 +msgid "Getting daily sales statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:7 +msgid "Point of Sale statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:9 +msgid "" +"On your dashboard, click on the **More** button on the point of sale you " +"want to analyse. Then click on **Orders**." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:15 +msgid "You will get the figures for this particular point of sale." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:21 +msgid "Global statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:23 +msgid "Go to :menuselection:`Reports --> Orders`." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:25 +msgid "You will get the figures of all orders for all point of sales." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:31 +msgid "Cashier statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:33 +msgid "Go to :menuselection:`Reports --> Sales Details`." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:35 +msgid "" +"Choose the dates. Select the cashiers by clicking on **Add an item**. Then " +"click on **Print Report**." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:41 +msgid "You will get a full report in a PDF file. Here is an example :" +msgstr "" + +#: ../../point_of_sale/belgian_fdm.rst:3 +msgid "Belgian Fiscal Data Module" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:3 +msgid "Setting up the Fiscal Data Module with the Odoo POS" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:8 +msgid "" +"The Belgian government requires certain businesses to use a government-" +"certified device called a **Fiscal Data Module** (also known as a " +"**blackbox**). This device works together with the POS application and logs " +"certain transactions. On top of that, the used POS application must also be " +"certified by the government and must adhere to strict standards specified by" +" them. `Odoo 9 (Enterprise Edition) is a certified application " +"<http://www.systemedecaisseenregistreuse.be/systemes-certifies>`_. More " +"information concerning the Fiscal Data Module can be found on `the official " +"website <http://www.systemedecaisseenregistreuse.be/>`_." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:20 +msgid "Required hardware" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:22 +msgid "" +"A government certified `Fiscal Data Module " +"<http://www.systemedecaisseenregistreuse.be/systemes-" +"certifies#FDM%20certifiés>`_ per POS, all of them should work, but the " +"Cleancash SC-B is recommended, you will also need:" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:27 +msgid "" +"Serial null modem cable per FDM (`example <http://www.startech.com/Cables" +"/Serial-Parallel-PS-2/DB9-DB25/10-ft-Cross-Wired-Serial-Null-Modem-Cable-" +"DB9-FM~SCNM9FM>`__)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:29 +msgid "" +"Serial-to-USB adapter per FDM (`example " +"<http://trendnet.com/products/proddetail.asp?prod=265_TU-S9>`__)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:32 +msgid "A registered POSBox per POS configuration" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:35 +msgid "Setup" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:38 +msgid "POSBox" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:40 +msgid "" +"In order to use a Fiscal Data Module, you will need a registered POSBox. " +"These POSBoxes are similar to the regular POSBoxes we sell, but they are " +"registered with the Belgian government. This is required by law. Attempting " +"to use a Fiscal Data Module on a non-registered POSBox will not work. You " +"can verify that the Fiscal Data Module is recognized by the POSBox by going " +"to the *Hardware status page* via the POSBox homepage." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:52 +msgid "Odoo" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:54 +msgid "" +"An Odoo POS app can be given certified POS capabilities by installing the " +"**Belgian Registered Cash Register** app (technical name: " +"``pos_blackbox_be``). Because of government restrictions imposed on us, this" +" installation cannot be undone. After this, you will have to ensure that " +"each POS configuration has a unique registered POSBox associated with it " +"(:menuselection:`Point of Sale --> Configuration --> Point of Sale` and " +"ensure Hardware Proxy / POSBox and the serial number of your POSBox is set)." +" The first time you open the Point of Sale and attempt to do a transaction, " +"you will be asked to input the PIN that you received with your VAT signing " +"card." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:69 +msgid "Certification & On-premise" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:71 +msgid "" +"The certification granted by the government is restricted to the use on " +"odoo.com SaaS instance. The usage of the module from the source or a " +"modified version will **not** be certified. For on-premise users, we also " +"support the Fiscal Data Module in such installations. The main restriction " +"is that this requires an obfuscated version of the ``pos_blackbox_be`` " +"module we will provide on request for Enterprise customers." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:79 +msgid "Restrictions" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:81 +msgid "" +"As mentioned before, in order to get certified the POS application must " +"adhere to strict government guidelines. Because of this, a certified Odoo " +"POS has some limitations not present in the non-certified Odoo POS." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:86 +msgid "Refunding is disabled" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:87 +msgid "Modifying orderline prices" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:88 +msgid "Creating/modifying/deleting POS orders" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:89 +msgid "Selling products without a valid tax" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:90 +msgid "Multiple Odoo POS configurations per POSBox are not allowed" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:91 +msgid "Using the POS without a connection to the POSBox (and thus FDM)" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:92 +msgid "Blacklisted modules: pos_discount, pos_reprint, pos_loyalty" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:3 +msgid "Point of Sale Hardware Setup" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:6 +msgid "POSBox Setup Guide" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:11 +#: ../../point_of_sale/overview/setup.rst:206 +msgid "Prerequisites" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:13 +msgid "" +"Before you start setting up your POSBox make sure you have everything. You " +"will need :" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:16 +msgid "The POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:17 +msgid "A 2A Power adapter" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:18 +msgid "A computer or tablet with an up-to-date web browser" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:19 +msgid "A running SaaS or Odoo instance with the Point of Sale installed" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:20 +msgid "A local network set up with DHCP (this is the default setting)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:21 +msgid "An RJ45 Ethernet Cable or a Linux compatible USB Wi-Fi adapter" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:22 +msgid "" +"An Epson USB TM-T20 Printer or another ESC/POS compatible printer " +"(officially supported printers are listed at the `POS Hardware page " +"<https://www.odoo.com/page/pos-ipad-android-hardware>`_)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:25 +msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:26 +msgid "An Epson compatible cash drawer" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:29 +#: ../../point_of_sale/overview/setup.rst:214 +msgid "Step By Step Setup Guide" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:32 +msgid "Current version of the POSBox (since 2015)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:36 +msgid "Connect peripheral devices" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:38 +msgid "" +"Officially supported hardware is listed on `the POS Hardware page " +"<https://www.odoo.com/page/pos-ipad-android-hardware>`_, but other hardware " +"might work as well." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:42 +msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:45 +msgid "" +"**Cash drawer**: The cash drawer should be connected to the printer with an " +"RJ25 cable." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:48 +msgid "" +"**Barcode scanner**: Connect your barcode scanner. In order for your barcode" +" scanner to be compatible it must behave as a keyboard and must be " +"configured in **US QWERTY**. It also must end barcodes with an Enter " +"character (keycode 28). This is most likely the default configuration of " +"your barcode scanner." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:54 +msgid "**Scale**: Connect your scale and power it on." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:56 +msgid "" +"**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. " +"Make sure this will connect the POSBox to the same network as your POS " +"device." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:60 +msgid "" +"**Wi-Fi**: If you do not wish to use Ethernet, plug in a Linux compatible " +"USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux " +"compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 " +"chipset. Make sure not to plug in an Ethernet cable, because all Wi-Fi " +"functionality will be bypassed when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:68 +msgid "Power the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:70 +msgid "" +"Plug the power adapter into the POSBox, a bright red status led should light" +" up." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:74 +msgid "Make sure the POSBox is ready" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:76 +msgid "" +"Once powered, The POSBox needs a while to boot. Once the POSBox is ready, it" +" should print a status receipt with its IP address. Also the status LED, " +"just next to the red power LED, should be permanently lit green." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:82 +#: ../../point_of_sale/overview/setup.rst:293 +msgid "Setup the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:84 +msgid "" +"To setup the POSBox in the Point of Sale go to :menuselection:`Point of Sale" +" --> Configuration --> Settings` and select your Point of Sale. Scroll down " +"to the ``Hardware Proxy / POSBox`` section and activate the options for the " +"hardware you want to use through the POSBox. Specifying the IP of the POSBox" +" is recommended (it is printed on the receipt that gets printed after " +"booting up the POSBox). When the IP is not specified the Point of Sale will " +"attempt to find it on the local network." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:93 +msgid "" +"If you are running multiple Point of Sales on the same POSBox, make sure " +"that only one of them has Remote Scanning/Barcode Scanner activated." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:96 +msgid "" +"It might be a good idea to make sure the POSBox IP never changes in your " +"network. Refer to your router documentation on how to achieve this." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:101 +msgid "Launch the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:103 +msgid "" +"If you didn't specify the POSBox's IP address in the configuration, the POS " +"will need some time to perform a network scan to find the POSBox. This is " +"only done once." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:107 +msgid "" +"The Point of Sale is now connected to the POSBox and your hardware should be" +" ready to use." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:111 +msgid "Wi-Fi configuration" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:113 +msgid "" +"The POSBox is Wi-Fi-capable. In order to use it you'll need a Linux " +"compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are" +" Linux compatible. Officially supported are Wi-Fi adapters with a Ralink " +"5370 chipset." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:118 +msgid "" +"Make sure not to plug in an Ethernet cable, as all Wi-Fi related " +"functionality will be disabled when a wired network connection is available." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:122 +msgid "" +"When the POSBox boots with a Wi-Fi adapter it will start its own Wi-Fi " +"Access Point called \"Posbox\" you can connect to. The receipt that gets " +"printed when the POSBox starts will reflect this. In order to make the " +"POSBox connect to an already existing Wi-Fi network, go to the homepage of " +"the POSBox (indicated on the receipt) and go to the Wi-Fi configuration " +"page. On there you can choose a network to connect to. Note that we only " +"support open and WPA(2)-PSK networks. When connecting to a WPA-secured " +"network, fill in the password field. The POSBox will attempt to connect to " +"the specified network and will print a new POSBox status receipt after it " +"has connected." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:133 +msgid "" +"If you plan on permanently setting up the POSBox with Wi-Fi, you can use the" +" \"persistent\" checkbox on the Wi-Fi configuration page when connecting to " +"a network. This will make the network choice persist across reboots. This " +"means that instead of starting up its own \"Posbox\" network it will always " +"attempt to connect to the specified network after it boots." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:140 +msgid "" +"When the POSBox fails to connect to a network it will fall back to starting " +"it's own \"Posbox\" Access Point. If connection is lost with a Wi-Fi network" +" after connecting to it, the POSBox will attempt to re-establish connection " +"automatically." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:146 +msgid "Multi-POS Configuration" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:148 +msgid "" +"The advised way to setup a multi Point of Sale shop is to have one POSBox " +"per Point of Sale. In this case it is mandatory to manually specify the IP " +"address of each POSBox in each Point of Sale. You must also configure your " +"network to make sure the POSBox's IP addresses don't change. Please refer to" +" your router documentation." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:155 +msgid "POSBoxless Guide (advanced)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:159 +msgid "" +"If you are running your Point of Sale on a Debian-based Linux distribution, " +"you do not need the POSBox as you can run its software locally. However the " +"installation process is not foolproof. You'll need at least to know how to " +"install and run Odoo. You may also run into issues specific to your " +"distribution or to your particular setup and hardware configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:166 +msgid "" +"Drivers for the various types of supported hardware are provided as Odoo " +"modules. In fact, the POSBox runs an instance of Odoo that the Point of Sale" +" communicates with. The instance of Odoo running on the POSBox is very " +"different from a 'real' Odoo instance however. It does not handle *any* " +"business data (eg. POS orders), but only serves as a gateway between the " +"Point of Sale and the hardware." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:173 +msgid "" +"The goal of this section will be to set up a local Odoo instance that " +"behaves like the Odoo instance running on the POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:177 +msgid "Image building process" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:179 +msgid "" +"We generate the official POSBox images using the scripts in " +"https://github.com/odoo/odoo/tree/8.0/addons/point_of_sale/tools/posbox. " +"More specifically, we run `posbox_create_image.sh " +"<https://github.com/odoo/odoo/blob/8.0/addons/point_of_sale/tools/posbox/posbox_create_image.sh>`_." +" This builds an image called ``posbox.img``, which we zip and upload to " +"`nightly.odoo.com <https://nightly.odoo.com>`_ for users to download." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:187 +msgid "" +"The scripts in this directory might be useful as a reference if you get " +"stuck or want more detail about something." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:191 +msgid "Summary of the image creation process" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:193 +msgid "" +"The image creation process starts by downloading the latest `Raspbian " +"<https://www.raspbian.org/>`_ image. It then locally mounts this Raspbian " +"image and copies over some files and scripts that will make the Raspbian " +"image turn itself into a POSBox when it boots. These scripts will update " +"Raspbian, remove non-essential packages and install required packages. In " +"order to boot Raspbian we use qemu, which is capable of providing ARM " +"emulation. After this, the emulated Raspbian OS will shut itself down. We " +"then once again locally mount the image, remove the scripts that were used " +"to initialize the image at boot and we copy over some extra configuration " +"files. The resulting image is then ready to be tested and used." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:208 +msgid "A Debian-based Linux distribution (Debian, Ubuntu, Mint, etc.)" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:209 +msgid "A running Odoo instance you connect to to load the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:210 +msgid "" +"You must uninstall any ESC/POS printer driver as it will conflict with " +"Odoo's built-in driver" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:217 +msgid "Extra dependencies" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:219 +msgid "" +"Because Odoo runs on Python 2, you need to check which version of pip you " +"need to use." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:222 +msgid "``# pip --version``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:224 +#: ../../point_of_sale/overview/setup.rst:230 +msgid "If it returns something like::" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:228 +msgid "You need to try pip2 instead." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:234 +msgid "You can use pip." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:236 +msgid "The driver modules requires the installation of new python modules:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:238 +msgid "``# pip install pyserial``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:240 +msgid "``# pip install pyusb==1.0.0b1``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:242 +msgid "``# pip install qrcode``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:245 +msgid "Access Rights" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:247 +msgid "" +"The drivers need raw access to the printer and barcode scanner devices. " +"Doing so requires a bit system administration. First we are going to create " +"a group that has access to USB devices" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:251 +msgid "``# groupadd usbusers``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:253 +msgid "Then we add the user who will run the OpenERP server to ``usbusers``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:255 +msgid "``# usermod -a -G usbusers USERNAME``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:257 +msgid "" +"Then we need to create a udev rule that will automatically allow members of " +"``usbusers`` to access raw USB devices. To do so create a file called " +"``99-usbusers.rules`` in the ``/etc/udev/rules.d/`` directory with the " +"following content::" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:265 +msgid "Then you need to reboot your machine." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:268 +msgid "Start the local Odoo instance" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:270 +msgid "We must launch the Odoo server with the correct settings" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:272 +msgid "" +"``$ ./odoo.py " +"--load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale,hw_scanner,hw_escpos``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:275 +msgid "Test the instance" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:277 +msgid "" +"Plug all your hardware to your machine's USB ports, and go to " +"``http://localhost:8069/hw_proxy/status`` refresh the page a few times and " +"see if all your devices are indicated as *Connected*. Possible source of " +"errors are: The paths on the distribution differ from the paths expected by " +"the drivers, another process has grabbed exclusive access to the devices, " +"the udev rules do not apply or a superseded by others." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:285 +msgid "Automatically start Odoo" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:287 +msgid "" +"You must now make sure that this Odoo install is automatically started after" +" boot. There are various ways to do so, and how to do it depends on your " +"particular setup. Using the init system provided by your distribution is " +"probably the easiest way to accomplish this." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:295 +msgid "" +"The IP address field in the POS configuration must be either ``127.0.0.1`` " +"or ``localhost`` if you're running the created Odoo server on the machine " +"that you'll use as the Point of Sale device. You can also leave it empty." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:301 +msgid "POSBox Technical Documentation" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:304 +msgid "Technical Overview" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:307 +msgid "The POSBox Hardware" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:309 +msgid "" +"The POSBox's Hardware is based on a `Raspberry Pi 2 " +"<https://www.raspberrypi.org/products/raspberry-pi-2-model-b/>`_, a popular " +"single-board computer. The Raspberry Pi 2 is powered with a 2A micro-usb " +"power adapter. 2A is needed to give enough power to the barcode scanners. " +"The Software is installed on a 8Gb Class 10 or Higher SD Card. All this " +"hardware is easily available worldwide from independent vendors." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:318 +msgid "Compatible Peripherals" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:320 +msgid "" +"Officially supported hardware is listed on the `POS Hardware page " +"<https://www.odoo.com/page/pos-ipad-android-hardware>`_." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:324 +msgid "The POSBox Software" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:326 +msgid "" +"The POSBox runs a heavily modified Raspbian Linux installation, a Debian " +"derivative for the Raspberry Pi. It also runs a barebones installation of " +"Odoo which provides the webserver and the drivers. The hardware drivers are " +"implemented as Odoo modules. Those modules are all prefixed with ``hw_*`` " +"and they are the only modules that are running on the POSBox. Odoo is only " +"used for the framework it provides. No business data is processed or stored " +"on the POSBox. The Odoo instance is a shallow git clone of the ``8.0`` " +"branch." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:335 +msgid "" +"The root partition on the POSBox is mounted read-only, ensuring that we " +"don't wear out the SD card by writing to it too much. It also ensures that " +"the filesystem cannot be corrupted by cutting the power to the POSBox. Linux" +" applications expect to be able to write to certain directories though. So " +"we provide a ramdisk for /etc and /var (Raspbian automatically provides one " +"for /tmp). These ramdisks are setup by ``setup_ramdisks.sh``, which we run " +"before all other init scripts by running it in ``/etc/init.d/rcS``. The " +"ramdisks are named /etc_ram and /var_ram respectively. Most data from /etc " +"and /var is copied to these tmpfs ramdisks. In order to restrict the size of" +" the ramdisks, we do not copy over certain things to them (eg. apt related " +"data). We then bind mount them over the original directories. So when an " +"application writes to /etc/foo/bar it's actually writing to " +"/etc_ram/foo/bar. We also bind mount / to /root_bypass_ramdisks to be able " +"to get to the real /etc and /var during development." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:351 +msgid "Logs of the running Odoo server can be found at:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:353 +msgid "``/var/log/odoo/odoo.log``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:355 +msgid "" +"Various POSBox related scripts (eg. wifi-related scripts) running on the " +"POSBox will log to /var/log/syslog and those messages are tagged with " +"``posbox_*``." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:360 +msgid "Accessing the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:363 +msgid "Local Access" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:365 +msgid "" +"If you plug a QWERTY USB keyboard into one of the POSBox's USB ports, and if" +" you connect a computer monitor to the *HDMI* port of the POSBox, you can " +"use it as a small GNU/Linux computer and perform various administration " +"tasks, like viewing some logs." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:370 +msgid "The POSBox will automatically log in as root on the default tty." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:373 +msgid "Remote Access" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:375 +msgid "" +"If you have the POSBox's IP address and an SSH client you can access the " +"POSBox's system remotely. The login credentials are ``pi``/``raspberry``." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:380 +msgid "Updating The POSBox Software" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:382 +msgid "" +"Only upgrade the POSBox if you experience problems or want to use newly " +"implemented features." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:385 +msgid "" +"The best way to update the POSBox software is to download a new version of " +"the image and flash the SD-Card with it. This operation is described in " +"detail in `this tutorial <http://elinux.org/RPi_Easy_SD_Card_Setup>`_, just " +"replace the standard Raspberry Pi image with the latest one found at `the " +"official POSBox image page <http://nightly.odoo.com/master/posbox/>`_. This " +"method of upgrading will ensure that you're running the latest version of " +"the POSBox software." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:394 +msgid "" +"The second way of upgrading is through the built in upgrade interface that " +"can be reached through the POSBox homepage. The nice thing about upgrading " +"like this is that you don't have to flash a new image. This upgrade method " +"is limited to what it can do however. It can not eg. update installed " +"configuration files (like eg. /etc/hostapd.conf). It can only upgrade:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:401 +msgid "The internal Odoo application" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:402 +msgid "" +"Scripts in the folder " +"``odoo/addons/point_of_sale/tools/posbox/configuration/``" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:404 +msgid "When in doubt, always use the first method of upgrading." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:407 +msgid "Troubleshoot" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:410 +msgid "The POS cannot connect to the POSBox" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:412 +msgid "" +"The easiest way to make sure the POSBox is properly set-up is to turn it on " +"with the printer plugged in as it will print a receipt indicating any error " +"if encountered or the POSBox's IP address in case of success. If no receipt " +"is printed, check the following steps:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:416 +msgid "" +"Make sure the POSBox is powered on, indicated by a brightly lit red status " +"LED." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:418 +msgid "" +"Make sure the POSBox is ready, this is indicated by a brightly lit green " +"status LED just next to the red power status LED. The POSBox should be ready" +" ~2 minutes after it is started." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:421 +msgid "" +"Make sure the POSBox is connected to the same network as your POS device. " +"Both the device and the POSBox should be visible in the list of connected " +"devices on your network router." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:424 +msgid "" +"Make sure that your LAN is set up with DHCP, and gives IP addresses in the " +"range 192.168.0.X, 192.168.1.X, 10.0.0.X. If you cannot setup your LAN that " +"way, you must manually set up your POSBox's IP address." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:428 +msgid "" +"If you have specified the POSBox's IP address in the configuration, make " +"sure it correspond to the printed on the POSBox's status receipt." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:431 +msgid "Make sure that the POS is not loaded over HTTPS." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:432 +msgid "" +"A bug in Firefox's HTTP implementation prevents the autodiscovery from " +"working reliably. When using Firefox you should manually set up the POSBox's" +" IP address in the POS configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:437 +msgid "The Barcode Scanner is not working" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:439 +msgid "" +"The barcode scanner must be configured in US QWERTY and emit an Enter after " +"each barcode. This is the default configuration of most barcode readers. " +"Refer to the barcode reader documentation for more information." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:443 +msgid "" +"The POSBox needs a 2A power supply to work with some barcode scanners. If " +"you are not using the provided power supply, make sure the one you use has " +"enough power." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:446 +msgid "" +"Some barcode scanners will need more than 2A and will not work, or will work" +" unreliably, even with the provided power supply. In those case you can plug" +" the barcode scanner in a self-powered USB hub." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:449 +msgid "" +"Some poorly built barcode scanners do not advertise themselves as barcode " +"scanners but as a usb keyboard instead, and will not be recognized by the " +"POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:454 +msgid "The Barcode Scanner is not working reliably" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:456 +msgid "" +"Make sure that no more than one device with 'Scan via Proxy'/'Barcode " +"Scanner' enabled are connected to the POSBox at the same time." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:461 +msgid "Printing the receipt takes too much time" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:463 +msgid "" +"A small delay before the first print is expected, as the POSBox will do some" +" preprocessing to speed up the next printings. If you suffer delays " +"afterwards it is most likely due to poor network connection between the POS " +"and the POSBox." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:469 +msgid "Some characters are not correctly printed on the receipt" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:471 +msgid "" +"The POSBox does not support all languages and characters. It currently " +"supports Latin and Cyrillic based scripts, with basic Japanese support." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:476 +msgid "The printer is offline" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:478 +msgid "" +"Make sure the printer is connected, powered, has enough paper and has its " +"lid closed, and is not reporting an error. If the error persists, please " +"contact support." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:483 +msgid "The cashdrawer does not open" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:485 +msgid "" +"The cashdrawer should be connected to the printer and should be activated in" +" the POS configuration." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:489 +msgid "Credits" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:490 +msgid "" +"The POSBox project was developed by Frédéric van der Essen with the kind " +"help of Gary Malherbe, Fabien Meghazi, Nicolas Wisniewsky, Dimitri Del " +"Marmol, Joren Van Onder and Antony Lesuisse." +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:494 +msgid "" +"This development would not have been possible without the Indiegogo campaign" +" and those who contributed to it. Special thanks goes to the partners who " +"backed the campaign with founding partner bundles:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:498 +msgid "Camptocamp" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:499 +msgid "BHC" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:500 +msgid "openBig" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:501 +msgid "Eeezee-IT" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:502 +msgid "Solarsis LDA" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:503 +msgid "ACSONE" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:504 +msgid "Vauxoo" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:505 +msgid "Ekomurz" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:506 +msgid "Datalp" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:507 +msgid "Dao Systems" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:508 +msgid "Eggs Solutions" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:509 +msgid "OpusVL" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:511 +msgid "" +"And also the partners who've backed the development with the Founding POSBox" +" Bundle:" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:514 +msgid "Willow IT" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:515 +msgid "E\\. Akhalwaya & Sons" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:516 +msgid "Multibase" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:517 +msgid "Mindesa" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:518 +msgid "bpso.biz" +msgstr "" + +#: ../../point_of_sale/overview/setup.rst:519 +msgid "Shine IT." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:3 +msgid "Getting started with Odoo Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:8 +msgid "" +"Odoo's online **Point of Sale** application is based on a simple, user " +"friendly interface. The **Point of Sale** application can be used online or " +"offline on iPads, Android tablets or laptops." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:12 +msgid "" +"Odoo **Point of Sale** is fully integrated with the **Inventory** and the " +"**Accounting** applications. Any transaction with your point of sale will " +"automatically be registered in your inventory management and accounting and," +" even in your **CRM** as the customer can be identified from the app." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:17 +msgid "" +"You will be able to run real time statistics and consolidations across all " +"your shops without the hassle of integrating several external applications." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:25 +msgid "Install the Point of Sale Application" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:27 +msgid "" +"Start by installing the **Point of Sale** application. Go to " +":menuselection:`Apps` and install the **Point of Sale** application." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:33 +msgid "" +"Do not forget to install an accounting **chart of account**. If it is not " +"done, go to the **Invoicing/Accounting** application and click on **Browse " +"available countries**:" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:40 +msgid "Then choose the one you want to install." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:42 +msgid "When it is done, you are all set to use the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:45 +msgid "Adding Products" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:47 +msgid "" +"To add products from the point of sale **Dashboard** go to " +":menuselection:`Orders --> Products` and click on **Create**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:50 +msgid "" +"The first example will be oranges with a price of ``3€/kg``. In the " +"**Sales** tab, you can see the point of sale configuration. There, you can " +"set a product category, specify that the product has to be weighted or not " +"and ensure that it will be available in the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:58 +msgid "" +"In same the way, you can add lemons, pumpkins, red onions, bananas... in the" +" database." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:62 +msgid "How to easily manage categories?" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:64 +msgid "" +"If you already have a database with your products, you can easily set a " +"**Point of Sale Category** by using the Kanban view and by grouping the " +"products by **Point of Sale Category**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:72 +msgid "Configuring a payment method" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:74 +msgid "" +"To configure a new payment method go to :menuselection:`Configuration --> " +"Payment methods` and click on **Create**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:81 +msgid "" +"After you set up a name and the type of payment method, you can go to the " +"point of sale tab and ensure that this payment method has been activated for" +" the point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:86 +msgid "Configuring your points of sales" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:88 +msgid "" +"Go to :menuselection:`Configuration --> Point of Sale`, click on the " +"``main`` point of sale. Edit the point of sale and add your custom payment " +"method into the available payment methods." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:95 +msgid "" +"You can configure each point of sale according to your hardware, " +"location,..." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "An internal identification of the point of sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Accounting journal used to post sales entries." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Accounting journal used to create invoices." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"Check this if you want to group the Journal Items by Product while closing a" +" Session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"Defines what kind of barcodes are available and how they are assigned to " +"products, customers and cashiers" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"This sequence is automatically created by Odoo but you can change it to " +"customize the reference numbers of your orders." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "This Point of sale's sales will be related to this Sales Channel." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables an integrated Virtual Keyboard" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables invoice generation from the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The payment input will behave similarily to bank payment input, and will be " +"prefilled with the exact due amount" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The point of sale will display this product category by default. If no " +"category is specified, all available products will be shown" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The product used to encode the customer tip. Leave empty if you do not " +"accept tips." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The displayed prices will always include all taxes, even if the taxes have " +"been setup differently" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "For imprecise industrial touchscreens" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The product categories will be displayed with pictures." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The hostname or ip address of the hardware proxy, Will be autodetected if " +"left empty" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enable barcode scanning with a remotely connected barcode scanner" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables Electronic Scale integration" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatically open the cashdrawer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bypass browser printing and prints via the hardware proxy" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The receipt will automatically be printed at the end of each order" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "" +"The receipt screen will be skipped if the receipt can be printed " +"automatically." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "A short text that will be inserted as a header in the printed receipt" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "A short text that will be inserted as a footer in the printed receipt" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Check the amount of the cashbox at opening and closing." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Enables Bill Splitting in the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Allows to print the Bill before payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Allow custom notes on Orderlines" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:0 +msgid "The restaurant floors served by this point of sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:100 +msgid "Now you are ready to make your first steps with your point of sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:103 +msgid "First Steps in the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:106 +msgid "Your first order" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:108 +msgid "" +"On the dashboard, you can see your points of sales, click on **New " +"session**:" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:119 +msgid "" +"On the right you can see the products list with the categories on the top. " +"If you click on a product, it will be added in the cart. You can directly " +"set the correct quantity or weight by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:125 +#: ../../point_of_sale/shop/cash_control.rst:59 +msgid "Payment" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:127 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84 €`` " +"and pays with a ``20 €`` note. When it's done, click on **Validate**." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:134 +#: ../../point_of_sale/shop/cash_control.rst:68 +msgid "" +"Your ticket is printed and you are now ready to make your second order." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:137 +#: ../../point_of_sale/shop/cash_control.rst:71 +msgid "Closing a session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:139 +msgid "" +"At the end of the day, to close the session, click on the **Close** button " +"on the top right. Click again on the close button of the point of sale. On " +"this page, you will see a summary of the transactions" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:146 +msgid "" +"If you click on a payment method line, the journal of this method appears " +"containing all the transactions performed." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:152 +msgid "Now, you only have to validate and close the session." +msgstr "" + +#: ../../point_of_sale/restaurant.rst:3 +msgid "Advanced Restaurant Features" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:3 +msgid "How to register multiple orders simultaneously?" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:6 +msgid "Register simultaneous orders" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:8 +msgid "" +"On the main screen, just tap on the **+** on the top of the screen to " +"register another order. The current orders remain opened until the payment " +"is done or the order is cancelled." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:16 +msgid "Switch from one order to another" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:18 +msgid "Simply click on the number of the order." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:24 +msgid "Cancel an order" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:26 +msgid "" +"If you made a mistake or if the order is cancelled, just click on the **-** " +"button. A message will appear to confirm the order deletion." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:34 +#: ../../point_of_sale/shop/invoice.rst:115 +msgid ":doc:`../advanced/register`" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:35 +msgid ":doc:`../advanced/reprint`" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:36 +msgid ":doc:`transfer`" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:3 +msgid "How to handle kitchen & bar order printing?" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:8 +#: ../../point_of_sale/restaurant/split.rst:10 +msgid "From the dashboard click on :menuselection:`More --> Settings`:" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:13 +msgid "Under the **Bar & Restaurant** section, tick **Bill Printing**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:18 +msgid "In order printers, click on **add an item** and then **Create**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:23 +msgid "" +"Set a printer **Name**, its **IP address** and the **Category** of product " +"you want to print on this printer. The category of product is useful to " +"print the order for the kitchen." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:30 +msgid "Several printers can be added this way" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:35 +msgid "" +"Now when you register an order, products will be automatically printed on " +"the correct printer." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:39 +msgid "Print a bill before the payment" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:41 +msgid "On the main screen, click on the **Bill** button." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:46 +msgid "Finally click on **Print**." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:51 +msgid "Click on **Ok** once it is done." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:54 +msgid "Print the order (kitchen printing)" +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:56 +msgid "" +"This is different than printing the bill. It only prints the list of the " +"items." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:59 +msgid "Click on **Order**, it will automatically be printed." +msgstr "" + +#: ../../point_of_sale/restaurant/print.rst:65 +msgid "" +"The printer is automatically chosen according to the products categories set" +" on it." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:3 +msgid "How to setup Point of Sale Restaurant?" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:5 +msgid "" +"Go to the **Point of Sale** application, :menuselection:`Configuration --> " +"Settings`" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:11 +msgid "" +"Enable the option **Restaurant: activate table management** and click on " +"**Apply**." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:17 +msgid "" +"Then go back to the **Dashboard**, on the point of sale you want to use in " +"restaurant mode, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:23 +msgid "" +"Under the **Restaurant Floors** section, click on **add an item** to insert " +"a floor and to set your PoS in restaurant mode." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:29 +msgid "Insert a floor name and assign the floor to your point of sale." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:34 +msgid "" +"Click on **Save & Close** and then on **Save**. Congratulations, your point " +"of sale is now in Restaurant mode. The first time you start a session, you " +"will arrive on an empty map." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:40 +msgid ":doc:`table`" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:3 +msgid "How to handle split bills?" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:8 +msgid "" +"Split bills only work for point of sales that are in **restaurant** mode." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:15 +msgid "In the settings tick the option **Bill Splitting**." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:23 +#: ../../point_of_sale/restaurant/transfer.rst:8 +msgid "From the dashboard, click on **New Session**." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:28 +msgid "Choose a table and start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:33 +msgid "" +"When customers want to pay and split the bill, there are two ways to achieve" +" this:" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:36 +msgid "based on the total" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:38 +msgid "based on products" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:44 +msgid "Splitting based on the total" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:46 +msgid "" +"Just click on **Payment**. You only have to insert the money tendered by " +"each customer." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:49 +msgid "" +"Click on the payment method (cash, credit card,...) and enter the amount. " +"Repeat it for each customer." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:55 +msgid "" +"When it's done, click on validate. This is how to split the bill based on " +"the total amount." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:59 +msgid "Split the bill based on products" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:61 +msgid "On the main view, click on **Split**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:66 +msgid "" +"Select the products the first customer wants to pay and click on **Payment**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:71 +msgid "You get the total, process the payment and click on **Validate**" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:76 +msgid "Follow the same procedure for the next customer of the same table." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:78 +msgid "When all the products have been paid you go back to the table map." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:3 +msgid "How to configure your table map?" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:6 +msgid "Make your table map" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:8 +msgid "" +"Once your point of sale has been configured for restaurant usage, click on " +"**New Session**:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:14 +msgid "" +"This is your main floor, it is empty for now. Click on the **+** icon to add" +" a table." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:20 +msgid "" +"Drag and drop the table to change its position. Once you click on it, you " +"can edit it." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:23 +msgid "Click on the corners to change the size." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:28 +msgid "The number of seats can be set by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:33 +msgid "The table name can be edited by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:38 +msgid "You can switch from round to square table by clicking on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:43 +msgid "The color of the table can modify by clicking on this icon :" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:48 +msgid "This icon allows you to duplicate the table:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:53 +msgid "To drop a table click on this icon:" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:58 +msgid "" +"Once your plan is done click on the pencil to leave the edit mode. The plan " +"is automatically saved." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:65 +msgid "Register your orders" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:67 +msgid "" +"Now you are ready to make your first order. You just have to click on a " +"table to start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:70 +msgid "" +"You can come back at any time to the map by clicking on the floor name :" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:76 +msgid "Edit a table map" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:78 +msgid "On your map, click on the pencil icon to go in edit mode :" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:3 +msgid "How to handle tips?" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:8 +#: ../../point_of_sale/shop/seasonal_discount.rst:63 +msgid "From the dashboard, click on :menuselection:`More --> Settings`." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:13 +msgid "Add a product for the tip." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:18 +msgid "" +"In the tip product page, be sure to set a sale price of ``0€`` and to remove" +" all the taxes in the accounting tab." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:25 +msgid "Adding a tip" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:27 +msgid "On the payment page, tap on **Tip**" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:32 +msgid "Tap down the amount of the tip:" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:37 +msgid "" +"The total amount has been updated and you can now register the payment." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:3 +msgid "How to transfer a customer from table?" +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:5 +msgid "" +"This only work for Point of Sales that are configured in restaurant mode." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:13 +msgid "" +"Choose a table, for example table ``T1`` and start registering an order." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:18 +msgid "" +"Register an order. For some reason, customers want to move to table ``T9``. " +"Click on **Transfer**." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:24 +msgid "Select to which table you want to transfer customers." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:29 +msgid "You see that the order has been added to the table ``T9``" +msgstr "" + +#: ../../point_of_sale/shop.rst:3 +msgid "Advanced Shop Features" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:3 +msgid "How to set up cash control?" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:5 +msgid "" +"Cash control permits you to check the amount of the cashbox at the opening " +"and closing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:9 +msgid "Configuring cash control" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:11 +msgid "" +"On the **Point of Sale** dashboard, click on :menuselection:`More --> " +"Settings`." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:17 +msgid "On this page, scroll and tick the the option **Cash Control**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:23 +msgid "Starting a session" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:25 +msgid "On your point of sale dashboard click on **new session**:" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:30 +msgid "" +"Before launching the point of sale interface, you get the open control view." +" Click on set an opening balance to introduce the amount in the cashbox." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:37 +msgid "" +"Here you can insert the value of the coin or bill, and the amount present in" +" the cashbox. The system sums up the total, in this example we have " +"``86,85€`` in the cashbox. Click on **confirm**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:44 +msgid "" +"You can see that the opening balance has changed and when you click on " +"**Open Session** you will get the main point of sale interface." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:61 +msgid "" +"Once the order is completed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84€`` " +"and pays with a ``20€`` note. When it's done, click on **Validate**." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:73 +msgid "" +"At the time of closing the session, click on the **Close** button on the top" +" right. Click again on the **Close** button to exit the point of sale " +"interface. On this page, you will see a summary of the transactions. At this" +" moment you can take the money out." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:81 +msgid "" +"For instance you want to take your daily transactions out of your cashbox." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:87 +msgid "" +"Now you can see that the theoretical closing balance has been updated and it" +" only remains you to count your cashbox to set a closing balance." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:93 +msgid "You can now validate the closing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:96 +#: ../../point_of_sale/shop/refund.rst:20 +#: ../../point_of_sale/shop/seasonal_discount.rst:92 +msgid ":doc:`invoice`" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:97 +#: ../../point_of_sale/shop/invoice.rst:116 +#: ../../point_of_sale/shop/seasonal_discount.rst:93 +msgid ":doc:`refund`" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:98 +#: ../../point_of_sale/shop/invoice.rst:117 +#: ../../point_of_sale/shop/refund.rst:21 +msgid ":doc:`seasonal_discount`" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:3 +msgid "How to invoice from the POS interface?" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:8 +msgid "" +"On the **Dashboard**, you can see your points of sales, click on **New " +"session**:" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:14 +msgid "You are on the ``main`` point of sales view :" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:19 +msgid "" +"On the right you can see the list of your products with the categories on " +"the top. Switch categories by clicking on it." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:22 +msgid "" +"If you click on a product, it will be added in your cart. You can directly " +"set the correct **Quantity/Weight** by typing it on the keyboard." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:26 +msgid "Add a customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:29 +msgid "By selecting in the customer list" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:31 +#: ../../point_of_sale/shop/invoice.rst:54 +msgid "On the main view, click on **Customer** (above **Payment**):" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:36 +msgid "You must set a customer in order to be able to issue an invoice." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:41 +msgid "" +"You can search in the list of your customers or create new ones by clicking " +"on the icon." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:48 +msgid "" +"For more explanation about adding a new customer. Please read the document " +":doc:`../advanced/register`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:52 +msgid "By using a barcode for customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:59 +msgid "Select a customer and click on the pencil to edit." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:64 +msgid "Set a the barcode for customer by scanning it." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:69 +msgid "" +"Save modifications and now when you scan the customer's barcode, he is " +"assigned to the order" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:73 +msgid "" +"Be careful with the **Barcode Nomenclature**. By default, customers' " +"barcodes have to begin with 042. To check the default barcode nomenclature, " +"go to :menuselection:`Point of Sale --> Configuration --> Barcode " +"Nomenclatures`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:82 +msgid "Payment and invoicing" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:84 +msgid "" +"Once the cart is processed, click on **Payment**. You can choose the " +"customer payment method. In this example, the customer owes you ``10.84 €`` " +"and pays with by a ``VISA``." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:88 +msgid "" +"Before clicking on **Validate**, you have to click on **Invoice** in order " +"to create an invoice from this order." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:94 +msgid "Your invoice is printed and you can continue to make orders." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:97 +msgid "Retrieve invoices of a specific customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:99 +msgid "" +"To retrieve the customer's invoices, go to the **Sale** application, click " +"on :menuselection:`Sales --> Customers`." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:102 +msgid "On the customer information view, click on the **Invoiced** button :" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:107 +msgid "" +"You will get the list all his invoices. Click on the invoice to get the " +"details." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:114 +#: ../../point_of_sale/shop/refund.rst:19 +#: ../../point_of_sale/shop/seasonal_discount.rst:91 +msgid ":doc:`cash_control`" +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:3 +msgid "How to return and refund products?" +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:5 +msgid "" +"To refund a customer, from the PoS main view, you have to insert negative " +"values. For instance in the last order you count too many ``pumpkins`` and " +"you have to pay back one." +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:12 +msgid "" +"You can see that the total is negative, to end the refund, you only have to " +"process the payment." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:3 +msgid "How to apply Time-limited or seasonal discounts?" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:8 +msgid "To apply time-limited or seasonal discount, use the pricelists." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:10 +msgid "You have to create it and to apply it on the point of sale." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:13 +msgid "Sales application configuration" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:15 +msgid "" +"In the **Sales** application, go to :menuselection:`Configuration --> " +"Settings`. Tick **Advanced pricing based on formula**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:23 +msgid "Creating a pricelist" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:25 +msgid "" +"Once the setting has been applied, a **Pricelists** section appears under " +"the configuration menu on the sales application." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:31 +msgid "Click on it, and then on **Create**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:36 +msgid "" +"Create a **Pricelist** for your point of sale. Each pricelist can contain " +"several items with different prices and different dates. It can be done on " +"all products or only on specific ones. Click on **Add an item**." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "" +"If unchecked, it will allow you to hide the pricelist without removing it." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Allow the end user to choose this price list" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:45 +msgid "" +"For example, the price of the oranges costs ``3€`` but for two days, we want" +" to give a ``10%`` discount to our PoS customers." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:51 +msgid "" +"You can do it by adding the product or its category and applying a " +"percentage discount. Other price computation can be done for the pricelist." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:55 +msgid "After you save and close, your pricelist is ready to be used." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:61 +msgid "Applying your pricelist to the Point of Sale" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:68 +msgid "On the right, you will be able to assign a pricelist." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:74 +msgid "" +"You just have to update the pricelist to apply the time-limited discount(s)." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:80 +msgid "" +"When you start a new session, you can see that the price have automatically " +"been updated." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:87 +msgid "When you update a pricelist, you have to close and open the session." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/practical.po b/locale/tr/LC_MESSAGES/practical.po new file mode 100644 index 000000000..90aa14706 --- /dev/null +++ b/locale/tr/LC_MESSAGES/practical.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../practical.rst:3 +msgid "Practical Information" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/project.po b/locale/tr/LC_MESSAGES/project.po new file mode 100644 index 000000000..596a011ec --- /dev/null +++ b/locale/tr/LC_MESSAGES/project.po @@ -0,0 +1,1697 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Murat Kaplan <muratk@projetgrup.com>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../project.rst:5 +msgid "Project" +msgstr "" + +#: ../../project/advanced.rst:3 +msgid "Advanced" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:3 +msgid "How to use projects to handle claims/issues?" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:5 +msgid "" +"A company selling support services often has to deal with problems occurring" +" during the implementation of the project. These issues have to be solved " +"and followed up as fast as possible in order to ensure the deliverability of" +" the project and a positive customer satisfaction." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:10 +msgid "" +"For example, as an IT company offering the implementation of your software, " +"you might have to deal with customers emails experiencing technical " +"problems. Odoo offers the opportunity to create dedicated support projects " +"which automatically generate tasks upon receiving an customer support email." +" This way, the issue can then be assigned directly to an employee and can be" +" closed more quickly." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:18 +#: ../../project/advanced/so_to_task.rst:24 +#: ../../project/configuration/time_record.rst:12 +#: ../../project/configuration/visualization.rst:15 +#: ../../project/planning/assignments.rst:10 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../project/advanced/claim_issue.rst:20 +msgid "" +"The following configuration are needed to be able to use projects for " +"support and issues. You need to install the **Project management** and the " +"**Issue Tracking** modules." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:31 +msgid "Create a project" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:33 +msgid "" +"The first step in order to set up a claim/issue management system is to " +"create a project related to those claims. Let's start by simply creating a " +"**support project**. Enter the Project application dashboard, click on " +"create and name your project **Support**. Tick the **Issues** box and rename" +" the field if you want to customize the Issues label (e.g. **Bugs** or " +"**Cases**). As issues are customer-oriented tasks, you might want to set the" +" Privacy/Visibility settings to **Customer project** (therefore your client " +"will be able to follow his claim in his portal)." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:43 +msgid "" +"You can link the project to a customer if the project has been created to " +"handle a specific client issues, otherwise you can leave the field empty." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:51 +msgid "Invite followers" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:53 +msgid "" +"You can decide to notify your employees as soon as a new issue will be " +"created. On the **Chatter** (bottom of the screen), you will notice two " +"buttons on the right : **Follow** (green) and **No follower** (white). Click" +" on the first to receive personally notifications and on the second to add " +"others employees as follower of the project (see screenshot below)." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:63 +msgid "Set up your workflow" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:65 +msgid "" +"You can easily personalize your project stages to suit your workflow by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column** (see image below). If you want to " +"rearrange the order of your stages, you can easily do so by dragging and " +"dropping the column you want to move to the desired location. You can also " +"edit, fold or unfold anytime your stages by using the **setting** icon on " +"your desired stage." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:77 +msgid "Generate issues from emails" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:79 +msgid "" +"When your project is correctly set up and saved, you will see it appearing " +"in your dashboard. Note that an email address for that project is " +"automatically generated, with the name of the project as alias." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:87 +msgid "" +"If you cannot see the email address on your project, go to the menu " +":menuselection:`Settings --> General Settings` and configure your alias " +"domain. Hit **Apply** and go back to your **Projects** dashboard where you " +"will now see the email address under the name of your project." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:92 +msgid "" +"Every time one of your client will send an email to that email address, a " +"new issue will be created." +msgstr "" + +#: ../../project/advanced/claim_issue.rst:96 +#: ../../project/advanced/so_to_task.rst:113 +#: ../../project/planning/assignments.rst:137 +msgid ":doc:`../configuration/setup`" +msgstr "" + +#: ../../project/advanced/claim_issue.rst:97 +msgid ":doc:`../configuration/collaboration`" +msgstr "" + +#: ../../project/advanced/feedback.rst:3 +msgid "How to gather feedback from customers?" +msgstr "" + +#: ../../project/advanced/feedback.rst:6 +#: ../../project/configuration/setup.rst:6 +#: ../../project/configuration/time_record.rst:6 ../../project/overview.rst:3 +#: ../../project/overview/main_concepts.rst:3 +msgid "Overview" +msgstr "" + +#: ../../project/advanced/feedback.rst:8 +msgid "" +"As a manager, it's not always simple to follow everything your teams do. " +"Having a simple customer feedback can be very interesting to evaluate the " +"performances of your teams. You can very easily gather feedbacks from your " +"customers using Odoo." +msgstr "" + +#: ../../project/advanced/feedback.rst:13 +msgid "" +"An e-mail can be sent during the project to get the customer feedbacks. He " +"just has to choose between 3 smileys to assess your work (Smile, Neutral or " +"Sad)." +msgstr "" + +#: ../../project/advanced/feedback.rst:18 +msgid "How to gather feedbacks from customers" +msgstr "" + +#: ../../project/advanced/feedback.rst:20 +msgid "" +"Before getting started some configuration is necessary. First of all it's " +"necessary to install the **Project** application. To do so simply go to the " +"apps module and install it." +msgstr "" + +#: ../../project/advanced/feedback.rst:27 +msgid "" +"Moreover, in the same menu, you have to install the **Project Rating** " +"module." +msgstr "" + +#: ../../project/advanced/feedback.rst:33 +msgid "" +"Next, go back into the back-end and enter the project module. Select the " +"**Configuration** button and click on **Settings** in the dropdown menu. " +"Next select **Allow activating customer rating on projects, at issue " +"completion**. Don't forget to apply your changes." +msgstr "" + +#: ../../project/advanced/feedback.rst:42 +msgid "How to get a Customer feedback?" +msgstr "" + +#: ../../project/advanced/feedback.rst:44 +msgid "" +"A e-mail can be sent to the customers at each stage of the ongoing projects." +msgstr "" + +#: ../../project/advanced/feedback.rst:47 +msgid "" +"First, you need to choose for which projects you want to get a feedback." +msgstr "" + +#: ../../project/advanced/feedback.rst:50 +msgid "Project configuration" +msgstr "" + +#: ../../project/advanced/feedback.rst:52 +msgid "" +"Go to the **Project** application, in the project settings select the " +"**Customer satisfaction** option." +msgstr "" + +#: ../../project/advanced/feedback.rst:59 +msgid "Email Template" +msgstr "" + +#: ../../project/advanced/feedback.rst:61 +msgid "" +"Go to the stage settings (click on the gear icon on the top of the stage " +"column, then select **Edit**). Choose the e-mail template that will be used." +" You can directly edit it from there." +msgstr "" + +#: ../../project/advanced/feedback.rst:68 +msgid "Here is an email example that a customer can receive :" +msgstr "" + +#: ../../project/advanced/feedback.rst:74 +msgid "" +"The customer just has to click on a smiley (Smile, Neutral or Sad) to assess" +" your work. The customer can reply to the email to add more information. It " +"will be added to the chatter of the task." +msgstr "" + +#: ../../project/advanced/feedback.rst:79 +msgid "Reporting" +msgstr "" + +#: ../../project/advanced/feedback.rst:81 +msgid "" +"You have a brief summary on the satisfaction in the upper right corner of " +"the project." +msgstr "" + +#: ../../project/advanced/feedback.rst:88 +msgid "How to display the ratings on your website?" +msgstr "" + +#: ../../project/advanced/feedback.rst:90 +msgid "" +"First of all it's necessary to install the **Website Builder** application. " +"To do so simply go to the apps module and search for the website builder." +msgstr "" + +#: ../../project/advanced/feedback.rst:97 +msgid "" +"Moreover, in the same menu, you have to install the **Website Rating Project" +" Issue** module." +msgstr "" + +#: ../../project/advanced/feedback.rst:103 +msgid "" +"Then, you will be able to publish your result on your website by clicking on" +" the website button in the upper right corner and confirming it in the front" +" end of the website." +msgstr "" + +#: ../../project/advanced/feedback.rst:111 +msgid ":doc:`claim_issue`" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:3 +msgid "How to create tasks from sales orders?" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:5 +msgid "" +"In this section, we will see the integration between Odoo's **Project " +"management** and **Sales** modules and more precisely how to generate tasks " +"from sales order lines." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:9 +msgid "" +"In project management, a task is an activity that needs to be accomplished " +"within a defined period of time. For a company selling services, the task " +"typically represents the service that has been sold to the customer and that" +" needs to be delivered. This is why it is useful to be able to generate a " +"task from a sale order in order to streamline the process between the Sales " +"and Services departments." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:16 +msgid "" +"As an example, you may sell a pack of ``50 Hours`` of support at " +"``$25,000``. The price is fixed and charged initially. But you want to keep " +"track of the support service you did for the customer. On the sale order, " +"the service will trigger the creation of a task from which the consultant " +"will record timesheets and, if needed, reinvoice the client according to the" +" overtime spent on the project." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:27 +msgid "Install the required applications" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:29 +msgid "" +"In order to be able to generate a task from a sale order you will need to " +"install the **Sales Management** and **Project** application. Simply go into" +" the application module and install the following:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:39 +msgid "" +"Moreover if you wish to be able to invoice your customers based on time " +"spent on the task, it is also necessary to install the **Timesheet** module." +" Simply go into the application module and install the following:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:47 +msgid "Create and set up a product" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:49 +msgid "" +"You need to configure your service on the product form itself in order to " +"generate a task every time it will be sold. From the **Sales** module, use " +"the menu :menuselection:`Sales --> Products` and create a new product with " +"the`following setup:" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:54 +msgid "**Name**: Technical Support" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:56 +msgid "**Product Type**: Service" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:58 +msgid "" +"**Unit of Measure**: Hours (go to :menuselection:`Configuration --> " +"Settings` and, under **Unit of measures**, check the **Some products may be " +"sold/purchased in different unit of measures (advanced)** radio button)" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:63 +msgid "" +"**Invoicing policy**: You can set up your invoice policy either on ordered " +"quantity or on delivered quantity. You can easily follow the amount of hours" +" that were delivered and/or invoiced to your client." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:68 +msgid "" +"**Track Service**: Create a task and track hours, as your product is a " +"service invoiceable by hours you have to set the units of measures of the " +"product to hours as well." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:76 +msgid "" +"Link your task to an existing project or create a new one on the fly if the " +"product is specific to one project. Otherwise, you can leave it blank, odoo " +"will then create a project per SO." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:81 +msgid "Create the Sales Order" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:83 +msgid "" +"Once the product is set up, you can create a quotation or a sale order with " +"the related product. Once the quotation is confirmed and transformed into a " +"sale order, the task will be created." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:91 +msgid "Access the task generated from the sale order" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:93 +msgid "On the Project module, your new task will appear :" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:95 +msgid "" +"either on a related project if you have selected one in the product form" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:98 +msgid "" +"either on a new project with the name of related the sale order as title " +"(you can easily change the name of the project by clicking on " +":menuselection:`More --> Settings`)" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:105 +msgid "" +"On the task itself, you will now be able to record timesheets and to invoice" +" your customers based on your invoicing policy." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:109 +msgid "" +"On Odoo, the central document is the sales order, which means that the " +"source document of the task is the related sales order." +msgstr "" + +#: ../../project/advanced/so_to_task.rst:114 +msgid ":doc:`../../sales/invoicing/services/reinvoice`" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:115 +msgid ":doc:`../../sales/invoicing/services/support`" +msgstr "" + +#: ../../project/application.rst:3 +msgid "Awesome Timesheet App" +msgstr "" + +#: ../../project/application/intro.rst:3 +msgid "Demonstration Video" +msgstr "" + +#: ../../project/application/intro.rst:11 +#: ../../project/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../project/application/intro.rst:13 +msgid "" +"Awesome Timesheet is a mobile app that helps me to instantly record any time" +" spent on projects in just a click. It's so effortless." +msgstr "" + +#: ../../project/application/intro.rst:16 +msgid "" +"Regardless of the device, the timesheet app is just one click away. Look at " +"the chrome plugin. No need to sign in, just click and start. It's smooth. It" +" works offline too and is automatically synchronized with my Odoo account." +msgstr "" + +#: ../../project/application/intro.rst:21 +msgid "" +"Plus, I get individual statistics via the mobile and chrome plugin. I can go" +" further in the analysis in my Odoo account. I receive reports of timesheets" +" per user, drill-down per project, and much more." +msgstr "" + +#: ../../project/application/intro.rst:25 +msgid "" +"Awesome Timesheet is fully integrated with Odoo invoicing, the customer " +"billing is done automatically. But also with Odoo projects. It's time-" +"saving!" +msgstr "" + +#: ../../project/application/intro.rst:28 +msgid "Download awesome timesheet now and gain in productivity." +msgstr "" + +#: ../../project/configuration.rst:3 +msgid "Configuration and basic usage" +msgstr "" + +#: ../../project/configuration/collaboration.rst:3 +msgid "How to manage & collaborate on tasks?" +msgstr "" + +#: ../../project/configuration/collaboration.rst:6 +msgid "Responsibilities" +msgstr "" + +#: ../../project/configuration/collaboration.rst:8 +msgid "In Odoo, you can assign the person who is in charge of the task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:10 +msgid "" +"When creating a task, by default you are responsible for it. You can change " +"this by simply typing the username of someone else and choosing it from the " +"suggestions in the drop down menu." +msgstr "" + +#: ../../project/configuration/collaboration.rst:15 +msgid "" +"If you add someone new, you can \"Create & Edit\" a new user on the fly. In " +"order to do so, you need the administrator rights." +msgstr "" + +#: ../../project/configuration/collaboration.rst:19 +msgid "Followers" +msgstr "" + +#: ../../project/configuration/collaboration.rst:21 +msgid "" +"In a task, you can add other users as **Followers**. Adding a follower means" +" that this person will be notified of any changes that might happen in the " +"task. The goal is to allow outside contribution from the chatter. This can " +"be invaluable when you need the advice of colleagues from other departments." +" You could also invite customers to take part in the task. They'll be " +"notified by email of the conversation in the chatter, and will be able to " +"take part in it simply by replying to the mail. The followers can see the " +"whole task like you, with the description and the chatter." +msgstr "" + +#: ../../project/configuration/collaboration.rst:32 +msgid "Project: follow a project to follow the pipe" +msgstr "" + +#: ../../project/configuration/collaboration.rst:34 +msgid "" +"You can decide to follow a Project. In this situation, you'll be notified of" +" any changes from the project: tasks sliding from one stage to " +"another,conversation taking place,, etc. You'll receive all the information " +"in your inbox. This feature is perfect for a Project Manager who wants to " +"see the big picture all the time." +msgstr "" + +#: ../../project/configuration/collaboration.rst:41 +msgid "Task: follow a specific task" +msgstr "" + +#: ../../project/configuration/collaboration.rst:43 +msgid "" +"Following a task is the same idea as following a project, except you are " +"focused on a specific part of the project. All notifications or changes in " +"that task also appear in your inbox." +msgstr "" + +#: ../../project/configuration/collaboration.rst:48 +msgid "Choose which action to follow" +msgstr "" + +#: ../../project/configuration/collaboration.rst:50 +msgid "" +"You can choose what you want to follow by clicking on the down arrow in the " +"Following button." +msgstr "" + +#: ../../project/configuration/collaboration.rst:53 +msgid "" +"By default, you follow the discussions but you can also choose to be " +"notified when a note is logged in, when a task is created, blocked or ready " +"to go, and when the stage of the task has changed." +msgstr "" + +#: ../../project/configuration/collaboration.rst:61 +msgid "Time management: analytic accounts" +msgstr "" + +#: ../../project/configuration/collaboration.rst:63 +msgid "" +"Whether it helps you for estimation of future projects or data for billing " +"or invoicing, time tracking in Project Management is a real plus." +msgstr "" + +#: ../../project/configuration/collaboration.rst:67 +msgid "" +"The Odoo Timesheet app is perfectly integrated with Odoo Project and can " +"help you track time easily." +msgstr "" + +#: ../../project/configuration/collaboration.rst:70 +msgid "" +"Once Odoo Timesheet is installed, the timesheet option is automatically " +"available in projects and on tasks." +msgstr "" + +#: ../../project/configuration/collaboration.rst:73 +msgid "" +"To avoid any confusion, Odoo works with analytic accounts. An analytic " +"account is the name that will always be the reference for a specific project" +" or contract. Each time a project is created, an analytic account is " +"automatically created under the same name." +msgstr "" + +#: ../../project/configuration/collaboration.rst:79 +msgid "Record a timesheet on a project:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:81 +msgid "Click on the settings of a project." +msgstr "" + +#: ../../project/configuration/collaboration.rst:86 +msgid "Click on the Timesheet button in the top grey menu." +msgstr "" + +#: ../../project/configuration/collaboration.rst:91 +msgid "" +"You get the Odoo Timesheet. Click on Create and a line will appear with " +"today's date and time. Your project name is automatically selected as the " +"Analytic Account. No task is set, you can choose to add a specific task for " +"it, or not." +msgstr "" + +#: ../../project/configuration/collaboration.rst:99 +msgid "" +"If you go now to Odoo Timesheet, your line will be recorded among your other" +" timesheets." +msgstr "" + +#: ../../project/configuration/collaboration.rst:103 +msgid "Record a timesheet on a task:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:105 +msgid "Within a task, the timesheet option is also available." +msgstr "" + +#: ../../project/configuration/collaboration.rst:107 +msgid "" +"In the task, click on the Edit button. Go on the Timesheet tab and click on " +"Add an item." +msgstr "" + +#: ../../project/configuration/collaboration.rst:110 +msgid "" +"A line will appear with the name of the project already selected in the " +"Analytic account." +msgstr "" + +#: ../../project/configuration/collaboration.rst:113 +msgid "" +"Again, you'll find back these timesheet lines in the Odoo Timesheet " +"application." +msgstr "" + +#: ../../project/configuration/collaboration.rst:119 +msgid "" +"At the end of your project, you can get a real idea of the time you spent on" +" it by searching based on the Analytic Account name of your project." +msgstr "" + +#: ../../project/configuration/collaboration.rst:124 +msgid "Document Management in tasks" +msgstr "" + +#: ../../project/configuration/collaboration.rst:126 +msgid "" +"You can manage documents related to tasks whether they're plans, pictures of" +" the formatting, etc. An image is sometimes more informative than a thousand" +" words! You have two ways to add a document to a task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:130 +msgid "" +"1. You can add an image/document to your task by clicking on the Attachment " +"tab on the top of the form." +msgstr "" + +#: ../../project/configuration/collaboration.rst:136 +msgid "" +"2. You can add an image/document to your task through the Chatter. You can " +"log a note/send a message and attach a file to it. Or if someone sends an " +"email with an attachment, the document will be automatically saved in the " +"task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:145 +msgid "" +"If you have an important image that helps to understand the tasks you can " +"set it up as Cover Image. It'll show up in the Kanban view directly." +msgstr "" + +#: ../../project/configuration/collaboration.rst:152 +msgid "Collaborate on tasks" +msgstr "" + +#: ../../project/configuration/collaboration.rst:154 +msgid "" +"Tasks in Odoo Project are made to help you to work easily together with your" +" colleagues. This helps you save time and energy." +msgstr "" + +#: ../../project/configuration/collaboration.rst:157 +msgid "" +"The idea is to stay up to date with what interests you. You can collaborate " +"with your colleagues by writing on the same task at the same time, with task" +" delegation and the Chatter." +msgstr "" + +#: ../../project/configuration/collaboration.rst:162 +msgid "Create a task from an email" +msgstr "" + +#: ../../project/configuration/collaboration.rst:164 +msgid "" +"You can configure an email address linked to your project. When an email is " +"sent to that address, it automatically creates a task in the first step of " +"the project, with all the recipients (To/Cc/Bcc) as followers." +msgstr "" + +#: ../../project/configuration/collaboration.rst:168 +msgid "" +"With Odoo Online, the mail gateway is already configured and so every " +"project gets an automatic email address." +msgstr "" + +#: ../../project/configuration/collaboration.rst:171 +msgid "" +"The email is always the name of the project (with \"-\" instead of the " +"space), you'll see it under the name of your project in the Project " +"Dashboard." +msgstr "" + +#: ../../project/configuration/collaboration.rst:178 +msgid "" +"This email address create by default following the project name can be " +"changed." +msgstr "" + +#: ../../project/configuration/collaboration.rst:181 +msgid "The alias of the email address can be changed by the project manager." +msgstr "" + +#: ../../project/configuration/collaboration.rst:183 +msgid "To do so, go to the Project Settings and click on the Email Tab." +msgstr "" + +#: ../../project/configuration/collaboration.rst:185 +msgid "You can directly edit your project email address." +msgstr "" + +#: ../../project/configuration/collaboration.rst:191 +msgid "The Chatter, status and follow-up." +msgstr "" + +#: ../../project/configuration/collaboration.rst:193 +msgid "" +"The Chatter is a very useful tool. It is a communication tool and shows the " +"history of the task." +msgstr "" + +#: ../../project/configuration/collaboration.rst:196 +msgid "" +"In the Chatter, you can see when the task has been created, when it has " +"passed from one stage to another, etc. Any changes made to that task are " +"logged into the Chatter automatically by the system. It also includes the " +"history of the interaction between you and your customer or colleagues. All " +"interactions are logged on the chatter, making it easy for the task leader " +"to remember past interactions." +msgstr "" + +#: ../../project/configuration/collaboration.rst:203 +msgid "" +"You can interact with followers whether there are internal (your colleagues)" +" or external (the client for example) by logging a note or important " +"information. Also, if you want to send an email to all the followers of that" +" specific task, you can choose to add a message to notify all of them. For " +"both of these options, the date and time is saved on the entry." +msgstr "" + +#: ../../project/configuration/collaboration.rst:214 +msgid "The description of the task, the Pad" +msgstr "" + +#: ../../project/configuration/collaboration.rst:216 +msgid "" +"Odoo allows you to replace the task description field by an Etherpad " +"collaborative note (http://etherpad.org). This means that you can " +"collaborate on tasks in real time with several users contributing to the " +"same content. Every user has their own color and you can replay the whole " +"creation of the content." +msgstr "" + +#: ../../project/configuration/collaboration.rst:222 +msgid "" +"To activate this option, go to :menuselection:`Project Settings --> Pads`, " +"tick \"Collaborative rich text on task description\"." +msgstr "" + +#: ../../project/configuration/collaboration.rst:229 +msgid "" +"If you just need the pad and not the whole task page, you can click on the " +"icon on the top right to get to the pad directly in a full screen view. " +"Click on the ``</>`` icon to get the direct URL of the task description: " +"useful if you want to send it to someone without adding this person as a " +"follower." +msgstr "" + +#: ../../project/configuration/collaboration.rst:239 +msgid "Tasks states" +msgstr "" + +#: ../../project/configuration/collaboration.rst:242 +msgid "Set the state of a task" +msgstr "" + +#: ../../project/configuration/collaboration.rst:244 +msgid "" +"The status of the task is the easiest way to inform your colleagues when you" +" are working on a task, if the task is ready or if it is blocked. It is a " +"visual indicator that is seen in a glance." +msgstr "" + +#: ../../project/configuration/collaboration.rst:248 +msgid "" +"You can change the status of the task from the kanban view or directly from " +"the task. Just click on the status ball to get the choices:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:258 +msgid "Custom states" +msgstr "" + +#: ../../project/configuration/collaboration.rst:260 +msgid "" +"You can decide what the different status mean for each stage of your " +"project. On the kanban view, click on the gear icon on the top of the stage," +" then click on edit:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:267 +msgid "Next to the color ball, write the explanation of the state." +msgstr "" + +#: ../../project/configuration/collaboration.rst:272 +msgid "Now, the explanation will be displayed instead of the generic text:" +msgstr "" + +#: ../../project/configuration/collaboration.rst:278 +msgid "Color Tags" +msgstr "" + +#: ../../project/configuration/collaboration.rst:280 +msgid "" +"In every task, you can add a tag. Tags are very useful to categorize the " +"tasks. It helps you to highlight a task from the Kanban view or better find " +"them thanks to the filters." +msgstr "" + +#: ../../project/configuration/collaboration.rst:284 +msgid "" +"If you are always working with a specific type of tag, you can highlight the" +" tasks containing the tag with the colors. Each tag can get a specific " +"color, it's very visual on the Kanban view." +msgstr "" + +#: ../../project/configuration/collaboration.rst:291 +msgid "" +"In order to make it appear on the kanban view, you have to set a color on " +"the tag, directly from the task:" +msgstr "" + +#: ../../project/configuration/setup.rst:3 +msgid "How to set up & configure a project?" +msgstr "" + +#: ../../project/configuration/setup.rst:8 +msgid "" +"Odoo Project allows you to manage a project together with your whole team, " +"and to communicate with any member for each project and task." +msgstr "" + +#: ../../project/configuration/setup.rst:11 +msgid "" +"It works with projects containing tasks following customizable stages. A " +"project can be internal or customer-oriented. A task is something to perform" +" as part of a project. You will be able to give different tasks to several " +"employees working on this project." +msgstr "" + +#: ../../project/configuration/setup.rst:17 +msgid "Installing the Project module" +msgstr "" + +#: ../../project/configuration/setup.rst:19 +msgid "" +"Open the **Apps** module, search for **Project Management**, and click on " +"**Install**." +msgstr "" + +#: ../../project/configuration/setup.rst:26 +msgid "Creating a new project" +msgstr "" + +#: ../../project/configuration/setup.rst:28 +msgid "" +"Open the **Project** application, and click on **Create**. From this window," +" you can specify the name of the project and set up the privacy of the " +"project." +msgstr "" + +#: ../../project/configuration/setup.rst:32 +msgid "The privacy setting works as:" +msgstr "" + +#: ../../project/configuration/setup.rst:34 +msgid "**Customer Project**: visible in portal if the customer is a follower." +msgstr "" + +#: ../../project/configuration/setup.rst:37 +msgid "**All Employees**: employees see all tasks or issues." +msgstr "" + +#: ../../project/configuration/setup.rst:39 +msgid "" +"**Private Project**: followers can see only the followed tasks or issues" +msgstr "" + +#: ../../project/configuration/setup.rst:42 +msgid "" +"You can also specify if the project is destined to a customer, or leave the " +"**Customer** field empty if not." +msgstr "" + +#: ../../project/configuration/setup.rst:48 +msgid "When you have entered all the required details, click on **Save**." +msgstr "" + +#: ../../project/configuration/setup.rst:51 +msgid "Manage your project's stages" +msgstr "" + +#: ../../project/configuration/setup.rst:54 +msgid "Add your project's stages" +msgstr "" + +#: ../../project/configuration/setup.rst:56 +msgid "On your project's dashboard. Click on **# Tasks**." +msgstr "" + +#: ../../project/configuration/setup.rst:61 +msgid "" +"In the new window, add a new column and name it according to the first stage" +" of your project, then add as many columns as there are stages in your " +"project." +msgstr "" + +#: ../../project/configuration/setup.rst:68 +msgid "" +"For each stage, there are markers for the status of tasks within a stage, " +"that you can personalize to fit your needs." +msgstr "" + +#: ../../project/configuration/setup.rst:71 +msgid "" +"Drag your mouse pointer over a stage name, and click on the appearing " +"bearing, and on the opening menu, click on **Edit**." +msgstr "" + +#: ../../project/configuration/setup.rst:77 +msgid "" +"A new window will open. The color dots and star icon correspond to " +"customizable markers applied on tasks, making it easier to know what task " +"requires attention. You can give them any signification you like." +msgstr "" + +#: ../../project/configuration/setup.rst:84 +msgid "Click on **Save** when you are done." +msgstr "" + +#: ../../project/configuration/setup.rst:87 +msgid "Rearrange stages" +msgstr "" + +#: ../../project/configuration/setup.rst:89 +msgid "" +"You can easily personalize this view to better suit your business needs by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column**. If you want to rearrange the order" +" of your stages, you can easily do so by dragging and dropping the column " +"you want to move to the desired location. You can also fold or unfold your " +"stages by using the **Setting** icon on your desired stage." +msgstr "" + +#: ../../project/configuration/setup.rst:100 +msgid ":doc:`visualization`" +msgstr "" + +#: ../../project/configuration/setup.rst:101 +msgid ":doc:`collaboration`" +msgstr "" + +#: ../../project/configuration/setup.rst:102 +msgid ":doc:`time_record`" +msgstr "" + +#: ../../project/configuration/time_record.rst:3 +msgid "How to record time spent?" +msgstr "" + +#: ../../project/configuration/time_record.rst:8 +msgid "" +"Odoo allows you to record the time spent per employee and per project, for " +"simple reports as well as for direct invoicing to the customer." +msgstr "" + +#: ../../project/configuration/time_record.rst:14 +msgid "" +"In order to record the time spent on projects, you must first activate the " +"invoicing of timesheets. Into the **Project** application, open " +":menuselection:`Configuration --> Settings`. In the **Timesheets** section " +"of the page, tick **Activate timesheets on issues**." +msgstr "" + +#: ../../project/configuration/time_record.rst:23 +msgid "" +"Activating the option will install the Sales, Invoicing, Issue Tracking, " +"Employee and Timesheet apps." +msgstr "" + +#: ../../project/configuration/time_record.rst:27 +msgid "Recording timesheets" +msgstr "" + +#: ../../project/configuration/time_record.rst:29 +msgid "" +"You can record the time spent in projects straight from the projects " +"application. You can either record timesheets in a project, or in a task." +msgstr "" + +#: ../../project/configuration/time_record.rst:34 +msgid "Recording in a project" +msgstr "" + +#: ../../project/configuration/time_record.rst:36 +msgid "" +"In the **Project** application dashboard, open the **More** menu of the " +"project you want to record timesheets for, and click on **Timesheets**." +msgstr "" + +#: ../../project/configuration/time_record.rst:42 +msgid "" +"In the new window, click on **Create** and insert the required details, then" +" click on **Save**." +msgstr "" + +#: ../../project/configuration/time_record.rst:49 +msgid "Recording in a task" +msgstr "" + +#: ../../project/configuration/time_record.rst:51 +msgid "" +"In the **Project** app, open the project you want to record timesheets for, " +"and open the task on which you have been working." +msgstr "" + +#: ../../project/configuration/time_record.rst:54 +msgid "" +"In the task, click on **Edit**, open the **Timesheets** tab and click on " +"**Add an item**. Insert the required details, then click on **Save**." +msgstr "" + +#: ../../project/configuration/visualization.rst:3 +msgid "How to visualize a project's tasks?" +msgstr "" + +#: ../../project/configuration/visualization.rst:5 +msgid "How to visualize a project's tasks" +msgstr "" + +#: ../../project/configuration/visualization.rst:7 +msgid "" +"Tasks are assignments that members of your organisations have to fulfill as " +"part of a project. In day to day business, your company might struggle due " +"to the important amount of tasks to fulfill. Those task are already complex " +"enough. Having to remember them all and follow up on them can be a real " +"burden. Luckily, Odoo enables you to efficiently visualize and organize the " +"different tasks you have to cope with." +msgstr "" + +#: ../../project/configuration/visualization.rst:17 +msgid "" +"The only configuration needed is to install the project module in the module" +" application." +msgstr "" + +#: ../../project/configuration/visualization.rst:24 +msgid "Creating Tasks" +msgstr "" + +#: ../../project/configuration/visualization.rst:26 +msgid "" +"Once you created a project, you can easily generate tasks for it. Simply " +"open the project and click on create a task." +msgstr "" + +#: ../../project/configuration/visualization.rst:32 +msgid "" +"You then first give a name to your task, the related project will " +"automatically be filled in, assign the project to someone, and select a " +"deadline if there is one." +msgstr "" + +#: ../../project/configuration/visualization.rst:40 +#: ../../project/planning/assignments.rst:47 +msgid "Get an overview of activities with the kanban view" +msgstr "" + +#: ../../project/configuration/visualization.rst:42 +msgid "" +"Once you created several tasks, they can be managed and followed up thanks " +"to the Kanban view." +msgstr "" + +#: ../../project/configuration/visualization.rst:45 +msgid "" +"The Kanban view is a post-it like view, divided in different stages. It " +"enables you to have a clear view on the stages your tasks are in and which " +"one have the higher priorities." +msgstr "" + +#: ../../project/configuration/visualization.rst:49 +#: ../../project/planning/assignments.rst:53 +msgid "" +"The Kanban view is the default view when accessing a project, but if you are" +" on another view, you can go back to it any time by clicking the kanban view" +" logo in the upper right corner" +msgstr "" + +#: ../../project/configuration/visualization.rst:57 +msgid "How to nototify your collegues about the status of a task?" +msgstr "" + +#: ../../project/configuration/visualization.rst:63 +#: ../../project/planning/assignments.rst:80 +msgid "Sort tasks by priority" +msgstr "" + +#: ../../project/configuration/visualization.rst:65 +msgid "" +"On each one of your columns, you have the ability to sort your tasks by " +"priority. Tasks with a higher priority will be automatically moved to the " +"top of the column. From the Kanban view, click on the star in the bottom " +"left of a task to tag it as **high priority**. For the tasks that are not " +"tagged, Odoo will automatically classify them according to their deadlines." +msgstr "" + +#: ../../project/configuration/visualization.rst:72 +msgid "" +"Note that dates that passed their deadlines will appear in red (in the list " +"view too) so you can easily follow up the progression of different tasks." +msgstr "" + +#: ../../project/configuration/visualization.rst:80 +#: ../../project/planning/assignments.rst:119 +msgid "Keep an eye on deadlines with the Calendar view" +msgstr "" + +#: ../../project/configuration/visualization.rst:82 +msgid "" +"If you add a deadline in your task, they will appear in the calendar view. " +"As a manager, this view enables you to keep an eye on all deadline in a " +"single window." +msgstr "" + +#: ../../project/configuration/visualization.rst:89 +#: ../../project/planning/assignments.rst:128 +msgid "" +"All the tasks are tagged with a color corresponding to the employee assigned" +" to them. You can easily filter the deadlines by employees by ticking the " +"related boxes on the right of the calendar view." +msgstr "" + +#: ../../project/configuration/visualization.rst:94 +#: ../../project/planning/assignments.rst:133 +msgid "" +"You can easily change the deadline from the Calendar view by dragging and " +"dropping the task to another case." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo Project" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:13 +msgid "" +"As a business manager, I have a varied job involving multiple stakeholders. " +"To manage every task seamlessly, Odoo Projects is of great help." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:17 +msgid "" +"With Odoo Projects, our project team members can easily plan and execute the" +" launching of a new product line in Canada. I organized this project by " +"creating different stages. It allows us to clearly identify the status of " +"any task at any time, and for any user. It is convenient for any other " +"project manager too." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:24 +msgid "" +"These well-structured project stages are fully customizable. Here I identify" +" one missing stage, I can easily add it in just a click. In our project " +"management process, I proceed to a final review, so I add this stage. Odoo " +"projects is designed to work for any kind of business." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:30 +msgid "" +"Once a task is done, each colleague can highlight it by changing its status." +" That will help the project manager to review the task before changing the " +"stage with a simple drag and drop. Easy, right?" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:35 +msgid "" +"We can also organize the different tasks by adapting the view. Here, I " +"select the list view, which shows other information such as the working time" +" progress. If I click on my task, I land on the form view where I can edit " +"the planned hours and enter my timesheets. This is a great tool for any " +"project manager. Controlling the working time progress and the time spent " +"for each team member is essential. I set the time for the sales team " +"training to 24 hours. Today, I prepared the material, so I will log 4 hours " +"in the timesheet. The working time progress updates automatically. Thanks to" +" this timesheet integration, the project manager has a thorough follow-up on" +" the progress of each task." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:49 +msgid "" +"Another great feature in Odoo projects is the forecast tool. When it is " +"activated, I can plan resources per project and the workload. Therefore, the" +" time allocation for other projects is much easier. For this project, I have" +" to train members of the sales team. It will require 50% of my time until " +"the end of the week. As project manager, I can do this resource allocation " +"for any user and adapt it according to their other projects. This will " +"prevent any form of time overlap. I can reassign a task or adapt the " +"deadline. Odoo projects is the perfect app for strategic and executive " +"planning." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:61 +msgid "" +"Plus, every aspect of any project can be analyzed, thanks to the reports. " +"For example, We can have a report of effective hours spent in comparison " +"with the planned hours. I can assess the profitability of any project, any " +"task, or any team member. I can also look at the number of hours assigned to" +" each team member." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:68 +msgid "" +"Another element of an excellent project management is communication. This is" +" a key factor for the success of any project. While dealing with multiple " +"stakeholders, being able to share documents directly in the task is very " +"helpful. With Odoo projects, I can discuss through the chat feature that is " +"always one-click away. I can also start a new conversation with anyone in my" +" team." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:76 +msgid "" +"In addition to being a powerful app for managing projects seamlessy, Odoo " +"projects is also an effective customer service or after-sales app. With it, " +"I can follow any customer issue, even create a dedicated support project. " +"The app also automatically creates an invoice of time spent on tasks or " +"issues." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:83 +msgid "" +"Odoo projects is a powerful, yet easy-to-use app. At first, I used the " +"planner to clearly state my objectives and set up the project app. Get this " +"app, it will help you get started quickly too." +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:88 +msgid "Start your free trial now and better manage your projects with Odoo!" +msgstr "" + +#: ../../project/overview/main_concepts/introduction.rst:91 +msgid "Start your free trial now with the CRM sales people love" +msgstr "" + +#: ../../project/planning.rst:3 +msgid "Planning your project" +msgstr "" + +#: ../../project/planning/assignments.rst:3 +msgid "How to plan and track employees' assignments?" +msgstr "" + +#: ../../project/planning/assignments.rst:5 +msgid "" +"Following and planning your employees' assignments can be a heavy challenge " +"especially when you manage several people. Luckily, using Odoo Project, you " +"can handle it in only a couple of clicks." +msgstr "" + +#: ../../project/planning/assignments.rst:12 +msgid "" +"The only necessary configuration is to install the **Project Management** " +"module. To do so, go in the application module, search for project and " +"install the application." +msgstr "" + +#: ../../project/planning/assignments.rst:19 +msgid "" +"If you wish to manage time estimation, you will need to enable timesheets on" +" tasks. From the **Project** application, go to " +":menuselection:`Configuration --> Settings` in the dropdown menu. Then, " +"under **Time Work Estimation**, select the **manage time estimation on " +"tasks** option. Do not forget to apply your changes." +msgstr "" + +#: ../../project/planning/assignments.rst:28 +msgid "" +"This feature will create a progress bar in the form view of your tasks. " +"Every time your salesperson will add working time in his timesheet, the bar " +"will be updated accordingly, based on the initially planned hours." +msgstr "" + +#: ../../project/planning/assignments.rst:36 +msgid "Manage tasks with views" +msgstr "" + +#: ../../project/planning/assignments.rst:38 +msgid "" +"You can have an overview of your different task thanks to the multiple views" +" available with Odoo. Three main views will help you to plan and follow up " +"on your employees' tasks: the kanban view, the list view (using timesheets) " +"and the calendar view." +msgstr "" + +#: ../../project/planning/assignments.rst:43 +msgid "" +"Create and edit tasks in order to fill up your pipeline. Don't forget to " +"fill in a responsible person and an estimated time if you have one." +msgstr "" + +#: ../../project/planning/assignments.rst:49 +msgid "" +"The Kanban view is a post-it like view, divided in different stages. It " +"enables you to have a clear view on the stages your tasks are in and the " +"ones having the higher priorities." +msgstr "" + +#: ../../project/planning/assignments.rst:61 +msgid "Add/rearrange stages" +msgstr "" + +#: ../../project/planning/assignments.rst:63 +msgid "" +"You can easily personalize your project to suit your business needs by " +"creating new columns. From the Kanban view of your project, you can add " +"stages by clicking on **Add new column** (see image below). If you want to " +"rearrange the order of your stages, you can easily do so by dragging and " +"dropping the column you want to move to the desired location. You can also " +"fold or unfold your stages by using the **setting** icon on your desired " +"stage." +msgstr "" + +#: ../../project/planning/assignments.rst:75 +msgid "" +"Create one column per stage in your working process. For example, in a " +"development project, stages might be: Specifications, Development, Test, " +"Done." +msgstr "" + +#: ../../project/planning/assignments.rst:82 +msgid "" +"On each one of your columns, you have the ability to sort your tasks by " +"priority. Tasks with a higher priority will automatically be moved to the " +"top of the column. From the Kanban view, click on the star in the bottom " +"left of a task to tag it as **high priority**. For the tasks that are not " +"tagged, Odoo will automatically classify them according to their deadlines." +msgstr "" + +#: ../../project/planning/assignments.rst:89 +msgid "" +"Note that dates that passed their deadlines will appear in red( in the list " +"view too) so you can easily follow up the progression of different tasks." +msgstr "" + +#: ../../project/planning/assignments.rst:97 +msgid "Don't forget you can filter your tasks with the filter menu." +msgstr "" + +#: ../../project/planning/assignments.rst:100 +msgid "Track the progress of each task with the list view" +msgstr "" + +#: ../../project/planning/assignments.rst:102 +msgid "" +"If you enabled the **Manage Time Estimation on Tasks**, your employees will " +"be able to log their activities on tasks under the **Timesheets** sub-menu " +"along with their duration. The **Working Time Progress** bar will be updated" +" each time the employee will add an activity." +msgstr "" + +#: ../../project/planning/assignments.rst:110 +msgid "" +"As a manager, you can easily overview the time spent on tasks for all " +"employees by using the list view. To do so, access the project of your " +"choice and click on the List view icon (see below). The last column will " +"show you the progression of each task." +msgstr "" + +#: ../../project/planning/assignments.rst:121 +msgid "" +"If you add a deadline in your task, they will appear in the calendar view. " +"As a manager, this view enables you to keep an eye on all deadlines in a " +"single window." +msgstr "" + +#: ../../project/planning/assignments.rst:138 +msgid ":doc:`forecast`" +msgstr "" + +#: ../../project/planning/forecast.rst:3 +msgid "How to forecast tasks?" +msgstr "" + +#: ../../project/planning/forecast.rst:6 +msgid "Introduction to forecast" +msgstr "" + +#: ../../project/planning/forecast.rst:8 +msgid "" +"Scheduling and forecasting tasks is another way to manage projects. In Odoo," +" the Forecast option gives you access to the Gantt chart." +msgstr "" + +#: ../../project/planning/forecast.rst:11 +msgid "" +"So far, you've been working with the Kanban view, which shows you the " +"progress of a project and its related tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:14 +msgid "" +"Now, with the Forecast option, the Gantt view gives you the big picture. " +"It's highly visual which is a real plus for complex projects, and it helps " +"team members to collaborate better." +msgstr "" + +#: ../../project/planning/forecast.rst:18 +msgid "" +"This option is a real benefit in terms of planning and organizing the " +"workload and human resources." +msgstr "" + +#: ../../project/planning/forecast.rst:22 +msgid "How to configure the projects?" +msgstr "" + +#: ../../project/planning/forecast.rst:25 +msgid "Configure the project application" +msgstr "" + +#: ../../project/planning/forecast.rst:27 +msgid "" +"The **Forecast** option helps you to organize your projects. This is perfect" +" when you need to set up a project with a specific deadline. Therefore, each" +" task is assigned a specific timeframe (amount of hours) in which your " +"employee should complete it!" +msgstr "" + +#: ../../project/planning/forecast.rst:32 +msgid "" +"First you need to activate the **Forecast** option for the whole project " +"application:" +msgstr "" + +#: ../../project/planning/forecast.rst:35 +msgid "" +"Go to :menuselection:`Project --> Configuration --> Settings`. Select the " +"Forecast option and click **Apply**." +msgstr "" + +#: ../../project/planning/forecast.rst:41 +msgid "" +"Once this is done, you still need to activate the **Forecast** option " +"specifically for your **Project** (maybe you don't need the Gantt chart for " +"all the projects that you manage)." +msgstr "" + +#: ../../project/planning/forecast.rst:46 +msgid "Configure a specific project." +msgstr "" + +#: ../../project/planning/forecast.rst:48 +msgid "" +"When creating a new project, make sure to select the option \"Allow " +"Forecast\" in your project settings." +msgstr "" + +#: ../../project/planning/forecast.rst:51 +msgid "You'll see the **Forecast** option appearing in the top menu." +msgstr "" + +#: ../../project/planning/forecast.rst:56 +msgid "" +"If you add the Forecasting option to an existing project, whether there are " +"task deadlines or not scheduled, the task won't be displayed." +msgstr "" + +#: ../../project/planning/forecast.rst:59 +msgid "The tasks of a project are not related to a forecast." +msgstr "" + +#: ../../project/planning/forecast.rst:62 +msgid "How to create a forecast?" +msgstr "" + +#: ../../project/planning/forecast.rst:64 +msgid "" +"Before creating a project with forecast, list all the tasks with the " +"projected time they should take. It will help you to coordinate the work." +msgstr "" + +#: ../../project/planning/forecast.rst:68 +msgid "" +"In order to display the projects in the Gantt chart, you need to create the " +"forecast from the task page. To create a forecast, click on the top left " +"corner of the task, **Create a Forecast**." +msgstr "" + +#: ../../project/planning/forecast.rst:76 +msgid "" +"You can also create a new Forecast easily by directly clicking on an empty " +"space in the Gantt chart calendar." +msgstr "" + +#: ../../project/planning/forecast.rst:79 +msgid "" +"The Forecast interface will fill in the name of the Project and the task " +"automatically. You just need to add the dates and the time the task should " +"take." +msgstr "" + +#: ../../project/planning/forecast.rst:87 +msgid "" +"The \"Effective hours\" field appears only if you have the **Timesheet** app" +" installed on your database. This option helps you to see the progress of a " +"task thanks to the integration with Timesheet." +msgstr "" + +#: ../../project/planning/forecast.rst:91 +msgid "" +"For example: When a user fills in a Timesheet with your Project name " +"(Analytic account), with 10 hours spent, the forecast will display 10 hours " +"in the Effective hours field." +msgstr "" + +#: ../../project/planning/forecast.rst:96 +msgid "What are the difference between the views?" +msgstr "" + +#: ../../project/planning/forecast.rst:98 +msgid "" +"In the **Project** app menu you have a **Forecast** menu. This sub-menu " +"helps you to see the Gantt chart from different points of view: by users or " +"by projects." +msgstr "" + +#: ../../project/planning/forecast.rst:103 +msgid "By users : people management" +msgstr "" + +#: ../../project/planning/forecast.rst:105 +msgid "" +"This option displays the Gantt chart with the people assigned. Odoo's Gantt " +"chart shows you who's involved; it gives you the big picture of the project." +" It's very useful to allocate your resources effectively." +msgstr "" + +#: ../../project/planning/forecast.rst:109 +msgid "" +"On the left side, first level, you can see which users are involved. Then, " +"on the second level you see which projects they are assigned to. On the " +"third, you see which tasks they're on." +msgstr "" + +#: ../../project/planning/forecast.rst:113 +msgid "" +"Each task is represented by a coloured rectangle. This rectangle reflects " +"the duration of the task in the calendar." +msgstr "" + +#: ../../project/planning/forecast.rst:116 +msgid "" +"The top rectangle on the first level is the sum of all the tasks compiled " +"from the third level. If it's green, it means that the total time allocated " +"to that user is less than 100%. When it's red, it means that this user is " +"assigned to multiple tasks which total more than 100% of his/her time." +msgstr "" + +#: ../../project/planning/forecast.rst:126 +msgid "Plan the workload" +msgstr "" + +#: ../../project/planning/forecast.rst:128 +msgid "" +"When creating a forecast, you have to select the time the user should spend " +"on it. 100% means that your user should work on it full time during those " +"days. He/She has no other tasks to work on. So you can decide from 1 to 100%" +" how your users should organize their time between different tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:134 +msgid "" +"The power of integration helps you to avoid double booking an employee. For " +"example, if your expert is already at 40% on another task in another " +"project, you can book him/her for only 60% for that period." +msgstr "" + +#: ../../project/planning/forecast.rst:138 +msgid "" +"In the example below, the user \"Administrator\" is working on 2 projects " +"(\"IT1367 Delivery Phases\" and \"Implementation Process56\"). The user is " +"assigned to both projects with a total of 110% of their time. This is too " +"much so the Project Manager should change the users assigned to the task. " +"Otherwise, the PM can change the dedicated time or the dates, to make sure " +"that this is feasible." +msgstr "" + +#: ../../project/planning/forecast.rst:149 +#: ../../project/planning/forecast.rst:191 +msgid "Gantt view advantages" +msgstr "" + +#: ../../project/planning/forecast.rst:151 +msgid "" +"This Gantt view ‘by user' helps you to better plan your human resources. You" +" avoid confusion about the the tasks and the assignations of the users. The " +"Gantt Chart is highly visual and helps to comprehend all the different " +"elements at once. Also, you immediately know what has to be done next. This " +"method helps you to better understand the relations between the tasks." +msgstr "" + +#: ../../project/planning/forecast.rst:158 +#: ../../project/planning/forecast.rst:193 +msgid "The dynamic view of the Gantt in Odoo allows you to:" +msgstr "" + +#: ../../project/planning/forecast.rst:160 +#: ../../project/planning/forecast.rst:195 +msgid "" +"change the time and date of a forecast by clicking and sliding the tasks in " +"the future or in the past" +msgstr "" + +#: ../../project/planning/forecast.rst:163 +#: ../../project/planning/forecast.rst:198 +msgid "create a new forecast into the Gantt chart immediately" +msgstr "" + +#: ../../project/planning/forecast.rst:165 +#: ../../project/planning/forecast.rst:200 +msgid "modify an existing forecast" +msgstr "" + +#: ../../project/planning/forecast.rst:167 +#: ../../project/planning/forecast.rst:202 +msgid "change the length of a task by extending or shortening the rectangle." +msgstr "" + +#: ../../project/planning/forecast.rst:170 +msgid "By projects: project management" +msgstr "" + +#: ../../project/planning/forecast.rst:172 +msgid "" +"The Gantt Chart is the perfect view of a project to better understand the " +"interactions between the tasks. You can avoid overlapping tasks or starting " +"one too early if another one isn't finished. Odoo Gantt chart is clear and " +"helps you to coordinate tasks efficiently." +msgstr "" + +#: ../../project/planning/forecast.rst:177 +msgid "" +"This option displays the Gantt chart by showing the projects on the first " +"level of hierarchy." +msgstr "" + +#: ../../project/planning/forecast.rst:180 +msgid "" +"On the left side, first level, you can see the projects. Then, on the second" +" level you see which users are assigned. On the third, you see which tasks " +"they're on." +msgstr "" + +#: ../../project/planning/forecast.rst:184 +msgid "" +"This view won't show your HR time. The colours don't apply. (see **By " +"Users** section)" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/purchase.po b/locale/tr/LC_MESSAGES/purchase.po new file mode 100644 index 000000000..a254ca72c --- /dev/null +++ b/locale/tr/LC_MESSAGES/purchase.po @@ -0,0 +1,2923 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Güven YILMAZ <guvenyilmaz@outlook.com.tr>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../purchase.rst:5 +msgid "Purchase" +msgstr "" + +#: ../../purchase/overview.rst:3 +#: ../../purchase/replenishment/flows/dropshipping.rst:6 +#: ../../purchase/replenishment/flows/purchase_triggering.rst:6 +#: ../../purchase/replenishment/flows/warning_triggering.rst:6 +#: ../../purchase/replenishment/multicompany/setup.rst:6 +msgid "Overview" +msgstr "" + +#: ../../purchase/overview/process.rst:3 +msgid "Process Overview" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:3 +msgid "Request for Quotation, Purchase Tender or Purchase Order?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:5 +msgid "" +"Although they are intimately related, Requests for Quotation, Purchase " +"Tenders and Purchase Orders are not the same." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:8 +msgid "" +"A **Request for Quotation** (RfQ) is used when you plan to purchase some " +"products and you would like to receive a quote for those products. In Odoo, " +"the Request for Quotation is used to send your list of desired products to " +"your supplier. Once your supplier has answered your request, you can choose " +"to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:15 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:5 +msgid "" +"A **Purchase Tender** (PT), also known as Call for Bids, is used to drive " +"competition between several suppliers in order to get the best offer for a " +"list of products. In comparison to the RfQ, a Purchase Tender is sent to " +"multiple suppliers, stating each are competing with one another, and that " +"the best offer will win. The main interest is that it usually leads to " +"better offers." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:22 +msgid "" +"The **Purchase Order** (PO) is the actual order that you place to the " +"supplier that you chose, either through a RfQ, a Purchase Tender, or simply " +"when you already know which supplier to order from." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:27 +msgid "When to use?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:29 +msgid "" +"A **RfQ** is interesting when you have never purchased the products with " +"that supplier before and therefore don't know their price. It is also useful" +" if you want to challenge your suppliers once you have a well-established " +"relationship with them. You can also use it to assess the cost of a project " +"and see if it makes it feasible." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:35 +msgid "" +"A **Purchase Tender** is used for public offers that require an open " +"offering from several suppliers. It is also useful when you need to make a " +"one-off order for a product and you would like to get the best offer, no " +"matter which supplier it is. It may be used when your supplier has not been " +"up to your standards and you would like to either push them to deliver a " +"better service, or find a replacement in their competitors." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:43 +msgid "When not to use?" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:45 +msgid "" +"**RfQ**\\ s become unnecessary once you have established your favorite " +"supplier for each item, and will only increase the delay in the delivery of " +"your items. In that case, the process will be simpler by starting straight " +"from a Purchase Order." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:50 +msgid "" +"**Purchase Tenders** are a long and tedious process that will likely take " +"more than several weeks in the best cases. If you need a quick delivery, " +"this is not the way to go. Also, if you have a well-established relationship" +" with one supplier, think twice before you initiate a PT with them as it " +"might tear the relationship and finally lead to less interesting deals." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:58 +#: ../../purchase/replenishment/flows/compute_date.rst:139 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:39 +msgid "Example" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:60 +msgid "" +"My company builds wooden furniture. For the new series of table we are " +"designing, we need some screws, metal frames and rubber protections." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:63 +msgid "" +"I create a Request for Quotation in Odoo with those products to my usual " +"supplier, and send it by email. He answers back with an offer. However, I am" +" not convinced by the offer, and I want to see if anyone can give a better " +"one." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:68 +msgid "" +"I decide to push competition a bit and set up a Purchase Tender, that Odoo " +"will send to a list of suppliers I specified. Out of the 8 offers I receive," +" one gets my attention and I decide to go ahead with that one." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:72 +msgid "" +"I confirm the order to the supplier by creating a Purchase Order from the " +"PT, and Odoo automatically asks delivery of the items to the supplier." +msgstr "" + +#: ../../purchase/overview/process/difference.rst:77 +#: ../../purchase/purchases/master/suppliers.rst:16 +#: ../../purchase/purchases/master/uom.rst:22 +#: ../../purchase/purchases/rfq/analyze.rst:24 +#: ../../purchase/purchases/rfq/bills.rst:31 +#: ../../purchase/purchases/rfq/create.rst:16 +#: ../../purchase/purchases/rfq/reception.rst:14 +#: ../../purchase/purchases/tender/partial_purchase.rst:14 +#: ../../purchase/replenishment/flows/dropshipping.rst:13 +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:58 +#: ../../purchase/replenishment/flows/warning_triggering.rst:21 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../purchase/overview/process/difference.rst:79 +msgid "" +"If you want to know how to create a **Purchase Order**, read the " +"documentation on :doc:`from_po_to_invoice`" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:82 +msgid "" +"If you want to know how to create a **RfQ**, read the documentation on " +":doc:`../../purchases/rfq/create`" +msgstr "" + +#: ../../purchase/overview/process/difference.rst:85 +msgid "" +"If you want to know how to create a **Purchase Tender**, read the " +"documentation on :doc:`../../purchases/tender/manage_multiple_offers`" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:3 +msgid "From purchase order to invoice and receptions" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:5 +msgid "" +"For most of your everyday purchases, chances are you already know where to " +"purchase and at what price. For these cases, a simple Purchase Order (PO) " +"will allow you to handle the whole process." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:9 +msgid "" +"In Odoo, a purchase order can be created as is, but can also be the result " +"of a Request for Quotation or of a Purchase Tender. Therefore, every " +"purchase made in Odoo has a PO." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:13 +msgid "" +"The PO will generate an invoice, and depending on the contract with your " +"supplier, you will be required to pay the invoice before or after delivery." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:18 +msgid "Install the Purchase Management application" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:20 +msgid "" +"From the **Apps** application, search and install the **Purchase " +"Management** application." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:27 +msgid "Creating a Purchase Order" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:29 +msgid "" +"In the **Purchases** app, open the **Purchase** menu and click on **Purchase" +" Orders**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:32 +msgid "In the **Purchase Orders** window, click on **Create**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:37 +msgid "" +"From the new window, insert the **Vendor** and type in the **Order Date**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:40 +msgid "In the **Products** section, click on **Add an item**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:45 +msgid "Select your product from the list and add a description if necessary." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:47 +msgid "The **Scheduled Date** menu corresponds to the expected delivery date." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:49 +msgid "" +"Type in the quantity which you wish to purchase, then click on **Save** and " +"on **Confirm Order**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:53 +msgid "" +"If you wish to go through the complete flow and create a **Request for " +"Quotation** for this order, refer to the document on " +":doc:`../../purchases/rfq/create`" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:57 +msgid "" +"As you can see, the status of the PO has switched to ``Purchase Order``." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:63 +msgid "Registering invoice, payments and receiving products" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:65 +msgid "" +"Depending on the contract you have with your supplier, you can either pay " +"for the purchase upon delivery of the goods, or get the goods delivered " +"after payment." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:70 +msgid "Payment upon or after reception" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:72 +msgid "Still from your purchase order, click on **Receive Products**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:74 +msgid "" +"In the next page, check that the number of products received corresponds to " +"the number ordered, then manually enter the delivered quantity and click on " +"**Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:81 +msgid "" +"Go back to the PO. In the PO, a **Shipment** and an **Invoice** button have " +"appeared." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:87 +msgid "" +"Click on the **Invoices** button, then click on **Validate**. The invoice is" +" now registered in the system. Click on **Register Payment**, insert the " +"detail of the payment, and click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:94 +#: ../../purchase/overview/process/from_po_to_invoice.rst:124 +msgid "" +"Your products are now ready for picking and storage, and the invoice is " +"marked as paid." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:98 +msgid "Upfront payment" +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:100 +msgid "" +"From the **Purchase Order** page, open the **Invoices** tab, then click on " +"**Create**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:103 +msgid "" +"In the next page, click on **Validate**. The invoice is now registered in " +"the system. Click on **Register Payment**, insert the detail of the payment," +" and click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:110 +msgid "" +"Go back to the PO. In the PO, a **Shipment** tab and an **Invoice** tab have" +" appeared." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:116 +msgid "" +"Click on **Receive Products**, then in the new page, click on **Validate**." +msgstr "" + +#: ../../purchase/overview/process/from_po_to_invoice.rst:121 +msgid "" +"A window will appear, asking if you wish to process every item at once. " +"Click on **Apply**." +msgstr "" + +#: ../../purchase/purchases.rst:3 +msgid "Purchases" +msgstr "Satınalma" + +#: ../../purchase/purchases/master.rst:3 +msgid "Master Data" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:3 +msgid "How to import supplier pricelists?" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:8 +msgid "" +"Big companies use to import supplier pricelists day to day. Indeed, prices " +"are always changing and you need to get price up to date to deal with a high" +" number of products." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:12 +msgid "" +"To manage supplier prices on product form, read this document " +"(:doc:`suppliers`). Here we will show you how to import customer prices." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:16 +msgid "Required configuration" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:18 +msgid "In purchase settings, you have 2 options:" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:20 +msgid "Manage vendor price on the product form" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:22 +msgid "Allow using and importing vendor pricelists" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:24 +msgid "Here we are selecting: **Allow using and importing vendor pricelists**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:30 +msgid "Import vendor pricelists" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:32 +msgid "" +"There are 2 scenarios: import the vendor pricelist for the first time, or " +"update an existing vendor pricelist. In both scenarios, we assume your " +"product list and vendor list is updated and you want to import the price " +"list of vendors for a given product." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:40 +msgid "" +"To import a list from a document, the best pratice is to export first to get" +" an example of data formating and a proper header to reimport." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:50 +msgid "Import the list for the first time" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:53 +msgid "Prepare the document" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:55 +msgid "" +"In :menuselection:`Purchase --> Purchase --> Supplier Pricelists`, export a " +"template of document to get import/export compatible and get the right " +"format to import in mass. Create manually a data and export it " +"(:menuselection:`select --> Action --> Export`)" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:63 +msgid "Here is the list of fields you can import:" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Header of the document to import (csv, xls)**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Meaning and how to get it**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:66 +msgid "**Example**" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "name_id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "Vendor ID -> export supplier list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:68 +msgid "\\_\\_export\\_\\_.res\\_partner\\_12" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "product_code" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "Vendor product Code -> free text" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:70 +msgid "569874" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "price" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "Vendor Price -> free text" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:72 +msgid "1500" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "product_tmpl_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "Product Template ID -> export you product list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:74 +msgid "\\_\\_export\\_\\_.product_template_13" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:76 +msgid "currency_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:76 +msgid "Currency -> to get it export the currency list" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "date_end" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "End date of the price validity" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:78 +msgid "2015-10-22" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "min_qty" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "Minimal quantity to purchase from this vendor" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:80 +msgid "2" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "product_id.id" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "Product Variante name -> export your variant list to get it" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:82 +msgid "\\_\\_export\\_\\_.product\\_13" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "date_start" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "Start date of price validity" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:84 +msgid "2015-12-31" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:87 +msgid "You obtain a document which can be imported, fill in your vendor pices" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:92 +msgid "" +"Import this document in Odoo. Click on **Import** in the list view and " +"upload your document. You can validate and check error. Once the system " +"tells you everything is ok, you can import the list." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:102 +msgid "" +"After the import, the **Vendors** section in **Inventory** tab of the " +"product form is filled in." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:106 +msgid "Update the vendor pricelist" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:108 +msgid "" +"When the pricelist of your suppliers change, it is necessary to update " +"existing prices." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:111 +msgid "" +"Follow the procedure of the first scenario in order to export existing data " +"from :menuselection:`Purchases --> Purchase --> Vendor Pricelist`. Select " +"everything, and export from the **Action** menu." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:115 +msgid "" +"Change price, end date, add a line, change a supplier, ... and then reimport" +" in Odoo. Thanks to the ID, the list will be updated. Either the id is " +"recognized and the line is updated or the ID is not known by Odoo and it " +"will create a new pricelist line." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:120 +msgid "" +"After the import, the **Vendors** section in **Inventory** tab of the " +"product form is updated." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:3 +msgid "How to set several suppliers on a product?" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:5 +msgid "" +"Keeping track of your vendors can be a real burden in day-to-day business " +"life. Prices can change and you might have several suppliers for one " +"product. With Odoo you have the possibility to directly link vendors with " +"the corresponding product and specify prices automatically the first time " +"you purchase them." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:11 +msgid "" +"We will take the following example: We need to buy ``5 t-shirts``. We found " +"a **Vendor**; called ``Bob&Jerry's`` and we want to issue a request for " +"quotation." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:19 +msgid "Install the purchase module" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:21 +msgid "" +"The first step to set your suppliers on your products is to install the " +"purchase module. Go into your **App** module and install the **Purchase** " +"module." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:29 +msgid "" +"By installing the purchase module, the inventory and invoicing module will " +"be installed as well." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:33 +msgid "Create a Vendor" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:35 +msgid "" +"The second step is to create a vendor. In this case we'll create the vendor " +"``Bob&Jerry's``. Enter the purchase module, select :menuselection:`Purchase " +"--> Vendors` and create a new vendor." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:39 +msgid "" +"You can choose if the contact is a company or a person, fill in basic " +"information such as address, phone, email,..." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:42 +msgid "" +"If you did not create the contact from the purchase module you will need to " +"go in the **Sales and Purchases** tab as well and indicate that the contact " +"is a **Vendor** (see picture below). If the contact is created from the " +"purchase module this box will be ticked automatically." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:51 +msgid "Create a product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:53 +msgid "" +"Next we can create the product we want to buy. We don't know the price of " +"the t-shirt yet because we still need to issue our **Request for " +"Quotation**." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:57 +msgid "" +"To create a product enter your purchase module select " +":menuselection:`Purchase --> Products` and create a new product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:60 +msgid "" +"We will call our product ``T-shirt`` and specify that the product can be " +"sold and purchased." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:67 +msgid "Add Vendors to the product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:69 +msgid "" +"The next action is to add vendors to the product. There are two ways to " +"handle this. If you issue a purchase order for the first time Odoo will " +"automatically link the vendor and its price to the product. You can also add" +" vendors manually" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:75 +msgid "By issuing a first Purchase Order to new vendor" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:77 +msgid "" +"When issuing a purchase order for the first time to a vendor, he will " +"automatically be linked to the product by Odoo. For our example let's say " +"that we issue a first purchase order to ``Bob&Jerry's`` for ``5 t-shirts`` " +"at ``12.35 euros / piece``." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:82 +msgid "" +"First create your purchase order with the correct product and supplier (see " +"picture below, or the documentation page :doc:`../rfq/create` for more " +"information)" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:89 +msgid "" +"When we save and validate the purchase order the vendor will automatically " +"be added to the product's vendors list. To check this enter the purchase " +"module, select :menuselection:`Purchase --> Products` and select our T-shirt" +" product. By opening the **Inventory** tab we notice that our vendor and its" +" price has automatically been added." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:98 +msgid "" +"Note that every first time the product is purchased from a new vendor, Odoo " +"will automatically link the contact and price with the product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:103 +msgid "By adding manually" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:105 +msgid "" +"We can of course also add vendors and vendors information manually. On the " +"same page than previously, simply click on **Edit** and click the **Add an " +"item** button." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:112 +msgid "" +"When adding a new **Vendor** you are also able to add extra information such" +" as the vendor product name or code, the validity of the price and the " +"eventual minimum quantity required. These informations can be added and " +"modified for existing vendors by simply clicking on the vendors line." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:3 +msgid "How to purchase in different unit of measures than sales?" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:5 +msgid "" +"In day-to-day business, it may happen that your supplier uses a different " +"unit of measure than you do in sales. This can cause confusion between sales" +" and purchase representative and even make you lose a lot of time converting" +" measures. Luckily in Odoo, you can handle different units of measures " +"between sales and purchase very easily." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:11 +msgid "Let's take the following examples:" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:13 +msgid "" +"You buy water from a supplier. The supplier is american and sells his water " +"in **Gallons**. Your customers however are European. You would thus like to " +"see your purchases quantities expressed in **Gallons** and the sold " +"quantities in **Liters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:18 +msgid "" +"You buy curtains from a supplier. The supplier sells you the curtains in the" +" unit **roll** and you sell the curtains in **square meters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:25 +msgid "Install purchase and sales modules" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:27 +msgid "" +"The first step is to make sure that the apps **Sales** and **Purchase** are " +"correctly installed." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:31 +msgid "|uom01|" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:31 +msgid "|uom02|" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:36 +msgid "Enable the Unit of Measures option" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:38 +msgid "" +"Enter the purchase module, select :menuselection:`Configuration --> " +"Settings` and tick the **Some products may be sold/purchased in different " +"unit of measures (advanced)** box." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:46 +msgid "Specify sales and purchase unit of measures" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:49 +msgid "Standard units of measures" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:51 +msgid "" +"Let's take the classic units of measures existing in Odoo as first example. " +"Please remember that differents units of measures between sales and purchase" +" necessarily need to share the same category. Categories include: **Unit**, " +"**weight**, **working time**, **volume**, etc." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:57 +msgid "" +"It is possible to create your own category and unit of measure if it is not " +"standard in Odoo (see next chapter)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:60 +msgid "" +"Let's assume we buy water from our vendors in **Gallons** and sell to our " +"customers in **Liters**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:63 +msgid "" +"We go into the purchase module select :menuselection:`Purchase --> " +"Products`." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:65 +msgid "" +"Create your own product or select an existing one. In the products general " +"information you have the possibility to select the **Unit of measure** (will" +" be used in sales, inventory,...) and the **Purchase Unit of Measure** (for " +"purchase)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:70 +msgid "" +"In this case select **Liters** for **Unit of Measure** and **Gallons** for " +"**Purchase Unit of Measure**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:77 +msgid "Create your own unit of measure and unit of measure category" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:79 +msgid "" +"Let's take now our second example (you buy curtains from a supplier, the " +"supplier sells you the curtains in the unit **roll** and you sell the " +"curtains in **square meters**)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:83 +msgid "" +"The two measures are part of two different categories. Remember, you cannot " +"relate an existing measure from one category with an existing measure of " +"another category. We thus first have to create a shared **Measure Category**" +" where both units have a conversion relationship." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:88 +msgid "" +"To do so, go into your sales module select :menuselection:`Configuration -->" +" Products --> Unit of Measure`. Create a new unit of **Measure Category** by" +" selecting the dropdown list and clicking on create and edit (see picture " +"below)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:96 +msgid "" +"Create a new unit of measure. In this case our category will be called " +"**Inter-Category-Computation**." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:102 +msgid "" +"The next step is to create the **Rolls** and **Square meter** units of " +"measure and to link them to the new category. To do so, go into your " +"purchase module select :menuselection:`Configuration --> Products --> Units " +"of Measure`." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:106 +msgid "Create two new units:" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:108 +msgid "" +"The **Roll** unit who is part of the Inter-Category-Computation category and" +" is the **Reference Unit type** (see picture below). The Reference Unit type" +" is the measure set as a reference within the category. Meaning that other " +"measures will be converted depending on this measure (ex: 1 roll = 10 square" +" meters, 2 rolls = 20 square meters, etc.)." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:118 +msgid "" +"For the **Square Meter**, we will specify that ``1 Roll = 10 square meters``" +" of curtain. It will thus be necessary to specify that as type, the square " +"meter is bigger than the reference unit. The **Bigger Ratio** is ``10`` as " +"``one Roll = 10 square meters``." +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:126 +msgid "" +"It is now possible to input **square meters** as Unit of measure and a " +"**Roll** as Purchase Unit of Measure in the product form." +msgstr "" + +#: ../../purchase/purchases/rfq.rst:3 +msgid "Request for Quotations" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:3 +msgid "How to analyze the performance of my vendors?" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:5 +msgid "" +"If your company regularly buys products from several suppliers, it would be " +"useful to get statistics on your purchases. There are several reasons to " +"track and analyze your vendor's performance :" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:9 +msgid "You can see how dependant from a supplier your company is;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:11 +msgid "you can negotiate discounts on prices;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:13 +msgid "You can check the average delivery time per supplier;" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:15 +msgid "Etc." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:17 +msgid "" +"For example, an IT products reseller that issues dozens of purchase orders " +"to several suppliers each week may want to measure for each product the " +"total price paid for each vendor and the delivery delay. The insights " +"gathered by the company will help it to better analyze, forecast and plan " +"their future orders." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:27 +#: ../../purchase/purchases/tender/partial_purchase.rst:17 +msgid "Install the Purchase Management module" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:29 +msgid "" +"From the **Apps** menu, search and install the **Purchase Management** " +"module." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:36 +msgid "Issue some purchase orders" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:38 +msgid "" +"Of course, in order to analyze your vendors' performance, you need to issue " +"some **Request For Quotations** (RfQ) and confirm some **Purchase Orders**. " +"If you want to know how to generate a purchase order, please read the " +"documentation :doc:`../../overview/process/from_po_to_invoice`." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:44 +msgid "Analyzing your vendors" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:47 +msgid "Generate flexible reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:49 +msgid "" +"You have access to your vendors' performances on the Reports menu. By " +"default, the report groups all your purchase orders on a pivot table by " +"**total price**, **product quantity** and **average price** for the **each " +"month** and for **each supplier**. Simply by accessing this basic report, " +"you can get a quick overview of your actual performance. You can add a lot " +"of extra data to your report by clicking on the **Measures** icon." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:60 +msgid "" +"By clicking on the **+** and **-** icons, you can drill up and down your " +"report in order to change the way your information is displayed. For " +"example, if I want to see all the products bought for the current month, I " +"need to click on the **+** icon on the vertical axis and then on " +"\"Products\"." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:67 +msgid "" +"Depending on the data you want to highlight, you may need to display your " +"reports in a more visual view. You can transform your report in just a click" +" in 3 graph views : a **Pie Chart**, a **Bar Chart** and a **Line Chart**: " +"These views are accessible through the icons highlighted on the screenshot " +"below." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:77 +msgid "" +"On the contrary to the pivot table, a graph can only be computed with one " +"dependent and one independent measure." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:81 +msgid "Customize reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:83 +msgid "" +"You can easily customize your purchase reports depending on your needs. To " +"do so, use the **Advanced search view** located in the right hand side of " +"your screen, by clicking on the magnifying glass icon at the end of the " +"search bar button. This function allows you to highlight only selected data " +"on your report. The **filters** option is very useful in order to display " +"some categories of datas, while the **Group by** option improves the " +"readability of your reports. Note that you can filter and group by any " +"existing field, making your customization very flexible and powerful." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:97 +msgid "" +"You can save and reuse any customized filter by clicking on **Favorites** " +"from the **Advanced search view** and then on **Save current search**. The " +"saved filter will then be accessible from the **Favorites** menu." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:103 +#: ../../purchase/purchases/rfq/create.rst:76 +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:75 +#: ../../purchase/purchases/tender/partial_purchase.rst:77 +msgid ":doc:`../../overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:3 +msgid "How to setup two levels of approval for purchase orders?" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:6 +msgid "Two level approval setup" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:8 +msgid "" +"Double validation on purchases forces a validation when the purchased amount" +" exceeds a certain limit." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:11 +msgid "" +"Install **Purchase Management** module and then go to **General Settings** " +"to configure the company data." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:17 +msgid "" +"Set here the amount limit for second approval and set approval from manager " +"side." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:21 +#: ../../purchase/replenishment/flows/purchase_triggering.rst:47 +msgid "Process" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:23 +msgid "" +"Logged as a purchase user, create a purchase order for more than the amount " +"set above, and confirm it. The purchase order is set in a state **To " +"Approve**" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:29 +msgid "The manager gets the order to approve and validates the final order." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:34 +msgid "Once approved, the purchase order follows the normal process." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:3 +msgid "How to control supplier bills?" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:5 +msgid "" +"The **Purchase** application allows you to manage your purchase orders, " +"incoming products, and vendor bills all seamlessly in one place." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:8 +msgid "" +"If you want to set up a vendor bill control process, the first thing you " +"need to do is to have purchase data in Odoo. Knowing what has been purchased" +" and received is the first step towards understanding your purchase " +"management processes." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:13 +msgid "Here is the standard work flow in Odoo:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:15 +msgid "" +"You begin with a **Request for Quotation (RFQ)** to send out to your " +"vendor(s)." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:18 +msgid "" +"Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase " +"Order (PO)**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:21 +msgid "" +"Confirming the PO generates an **Incoming Shipment** if you purchased any " +"stockable products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:24 +msgid "" +"Upon receiving a **Vendor Bill** from your Vendor, validate the bill with " +"products received in the previous step to ensure accuracy." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:27 +msgid "" +"This process may be done by three different people within the company, or " +"only one." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:34 +msgid "Installing the Purchase and Inventory applications" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:36 +msgid "" +"From the **Apps** application, search for the **Purchase** module and " +"install it. Due to certain dependencies, installing purchase will " +"automatically install the **Inventory** and **Accounting** applications." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:41 +msgid "Creating products" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:43 +msgid "" +"Creating products in Odoo is essential for quick and efficient purchasing " +"within Odoo. Simply navigate to the **Products** submenu under **Purchase**," +" and click **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:50 +msgid "" +"When creating the product, Pay attention to the **Product Type** field, as " +"it is important:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:53 +msgid "" +"Products that are set as **Stockable** or **Consumable** will allow you to " +"keep track of their inventory levels. These options imply stock management " +"and will allow for receiving these kinds of products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:58 +msgid "" +"Conversely, products that are set as a **Service** or **Digital Product** " +"will not imply stock management, simply due to the fact that there is no " +"inventory to manage. You will not be able to receive products under either " +"of these designations." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:64 +msgid "" +"It is recommended that you create a **Miscellaneous** product for all " +"purchases that occur infrequently and do not require inventory valuation or " +"management. If you create such a product, it is recommend to set the product" +" type to **Service**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:70 +msgid "Managing your Vendor Bills" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:73 +msgid "Purchasing products or services" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:75 +msgid "" +"From the purchase application, you can create a purchase order with as many " +"products as you need. If the vendor sends you a confirmation or quotation " +"for an order, you may record the order reference number in the **Vendor " +"Reference** field. This will enable you to easily match the PO with the the " +"vendor bill later (as the vendor bill will probably include the Vendor " +"Reference)" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:85 +msgid "" +"Validate the purchase order and receive the products from the **Inventory** " +"application." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:89 +msgid "Receiving Products" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:91 +msgid "" +"If you purchased any stockable products that you manage the inventory of, " +"you will need to receive the products from the **Inventory** application " +"after you confirm a purchase order. From the **Inventory** dashboard, you " +"should see a button linking you directly to the transfer of products. This " +"button is outlined in red below:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:100 +msgid "" +"Navigating this route will take you to a list of all orders awaiting to be " +"received." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:106 +msgid "" +"If you have a lot of awaiting orders, apply a filter using the search bar in" +" the upper right. With this search bar, you may filter based on the " +"**Vendor** (or **Partner**), the product, or the source document, also known" +" as the reference of your purchase order. You also have the capability to " +"group the orders by different criteria under **Group By**. Selecting an item" +" from this list will open the following screen where you then will receive " +"the products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:117 +msgid "Purchasing **Service** products does not trigger a delivery order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:120 +msgid "Managing Vendor Bills" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:122 +msgid "" +"When you receive a **Vendor Bill** for a previous purchase, be sure to " +"record it in the **Purchases** application under the **Control Menu**. You " +"need to create a new vendor bill even if you already registered a purchase " +"order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:130 +msgid "" +"The first thing you will need to do upon creating a **Vendor Bill** is to " +"select the appropriate **Vendor** as this will also pull up any associated " +"accounting or pricelist information. From there, you can choose to specify " +"any one or multiple purchase orders to populate the vendor bill with. When " +"you select a purchase order from the list, Odoo will pull any uninvoiced " +"products associated to that purchase order and automatically populate that " +"information below. If you are having a hard time finding the appropriate " +"vendor bill, you may search through the list by inputting the vendor " +"reference number or your internal purchase order number." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:144 +msgid "" +"While the invoice is in draft state, you can make any modifications you need" +" (i.e. remove or add product lines, modify quantities, and change prices)." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:149 +msgid "Your vendor may send you several bills for the same purchase order if:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:151 +msgid "" +"Your vendor is in back-order and is sending you invoices as they ship the " +"products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:154 +msgid "Your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:156 +msgid "" +"Every time you record a new vendor bill, Odoo will automatically populate " +"the product quantities based on what has been received from the vendor. If " +"this value is showing a zero, this means that you have not yet received this" +" product and simply serves as a reminder that the product is not in hand and" +" you may need to inquire further into this. At any point in time, before you" +" validate the vendor bill, you may override this zero quantity." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:165 +msgid "Vendor Bill Matching" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:168 +msgid "What to do if your vendor bill does not match what you received" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:170 +msgid "" +"If the bill you receive from the vendor has different quantities than what " +"Odoo automatically populates as quantities, this could be due to several " +"reasons:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:174 +msgid "" +"The vendor is incorrectly charging you for products and/or services that you" +" have not ordered." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:177 +msgid "" +"The vendor is billing you for products that you might not have received yet," +" as the invoicing control may be based on ordered or received quantities." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:181 +msgid "Or the vendor did not bill you for previously purchased products." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:183 +msgid "" +"In these instances it is recommended that you verify that the bill, and any " +"associated purchase order to the vendor, are accurate and that you " +"understand what you have ordered and what you have already received." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:187 +msgid "" +"If you are unable to find a purchase order related to a vendor bill, this " +"could be due to one of a few reasons:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:190 +msgid "" +"The vendor has already invoiced you for this purchase order, therefore it is" +" not going to appear anywhere in the selection." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:193 +msgid "" +"Someone in the company forgot to record a purchase order for this vendor." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:196 +msgid "Or the vendor is charging you for something you did not order." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:199 +msgid "How product quantities are managed" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:201 +msgid "" +"By default, services are managed based on ordered quantities, while " +"stockables and consumables are managed based on received quantities." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:204 +msgid "" +"If you need to manage products based on ordered quantities over received " +"quantities, you will need to enable **Debug Mode** from the **About Odoo** " +"information. Once debug mode is activated, select the product(s) you wish to" +" modify, and you should see a new field appear, labeled **Control Purchase " +"Bills**." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:213 +msgid "" +"You can then change the default management method for the selected product " +"to be based on either:" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:216 +msgid "Ordered quantities" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:218 +msgid "Received quantities" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:221 +msgid "Batch Billing" +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:223 +msgid "" +"When creating a vendor bill and selecting the appropriate purchase order, " +"you may continue to select additional purchase orders and Odoo will add the " +"additional line items from that purchase order. If you have not deleted the " +"previous line items from the first purchase order the bill will be linked to" +" all the appropriate purchase orders." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:3 +msgid "How to cancel a purchase order?" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:5 +msgid "" +"Due to misunderstandings, human errors or change of plans, it is sometimes " +"necessary to cancel purchase orders sent to suppliers. Odoo allows you to do" +" it, even if some or even all of the ordered goods already arrived in your " +"warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:10 +msgid "" +"We will first take as example the case where you order **3 iPad mini** that " +"haven't arrived in your transfers yet. As the installation of the inventory " +"application is required when using the **Purchase** module, it is also " +"interesting to see the case of partially delivered goods that you want to " +"cancel." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:17 +msgid "Create a Purchase Order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:19 +msgid "" +"The first step to create a **Purchase Order** is to create a **Request for " +"Quotation (RFQ)** from the menu :menuselection:`Purchases --> Purchase --> " +"Requests for quotation`. Confirm your RFQ to have a confirmed purchase order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:25 +msgid "" +"To learn more about the purchase order process, read the documentation page " +":doc:`../../overview/process/from_po_to_invoice`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:30 +msgid "Cancel your Purchase Order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:33 +msgid "Use case 1 : you didn't receive your goods yet" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:35 +msgid "" +"If you confirmed your purchase order and did not received your goods yet, " +"you can simply cancel the PO it by clicking the cancel button." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:41 +msgid "" +"Odoo will automatically cancel the outstanding shipments related to this PO " +"and the status bar will switch from **Purchase order** to **Cancelled**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:48 +msgid "Use case 2 : partially delivered goods" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:50 +msgid "" +"In this case, **2** of the **3 iPad Mini** arrived before you needed to " +"cancel the PO." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:54 +msgid "Register good received and cancel backorder" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:56 +msgid "" +"The first thing to do will be to register the goods received and to cancel " +"the arrival of the **third iPad Mini** that is still supposed to be shipped." +" From the PO, click on **Receive products** and, on the **iPad Mini order " +"line**, manually change the received quantities under the Column **Done**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:66 +msgid "To learn more, see :doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:68 +msgid "" +"When clicking on **Validate**, Odoo will warn you that you have processed " +"less products than the initial demand (2 instead of 3 in our case) and will " +"ask you the permission to create a backorder." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:75 +msgid "" +"Click on **No backorder** to cancel the supply of the remaining product. You" +" will notice than the quantity to receive has been changed accordingly and, " +"therefore, the delivery status has switched to **Done**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:83 +msgid "Create reverse transfer" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:85 +msgid "" +"Now, you need to return the iPad Minis that you have received to your vendor" +" location. To do so, click on the **Reverse** button from the same document." +" A reverse transfer window will pop up. Enter the quantity to return and the" +" corresponding location and click on **Return**." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:93 +msgid "" +"Process the return shipment and control that the stock move is from your " +"stock to your vendor location." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:99 +msgid "" +"When the reverse transfer is done, the status of your purchase order will be" +" automatically set to done, meaning that your PO has been completely " +"cancelled." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:104 +#: ../../purchase/purchases/rfq/reception.rst:120 +msgid ":doc:`bills`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:105 +msgid ":doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:3 +msgid "How to create a Request for Quotation?" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:5 +msgid "" +"A Request for Quotation (RfQ) is used when you plan to purchase some " +"products and you would like to receive a quote for those products. In Odoo, " +"the Request for Quotation is used to send your list of desired products to " +"your supplier. Once your supplier has answered your request, you can choose " +"to go ahead with the offer and purchase or to turn down the offer." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:12 +msgid "" +"For more information on best uses, please read the chapter " +":doc:`../../overview/process/difference`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:19 +msgid "Creating a Request for Quotation" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:21 +msgid "" +"In the Purchases module, open :menuselection:`Purchase --> Requests for " +"Quotation` and click on **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:27 +msgid "" +"Select your supplier in the **Vendor** menu, or create it on-the-fly by " +"clicking on **Create and Edit**. In the **Order Date** field, select the " +"date to which you wish to proceed to the actual order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoming Shipments" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Reference of the sales order or bid sent by the vendor. It's used to do the " +"matching when you receive the products as this reference is usually written " +"on the delivery order sent by your vendor." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Depicts the date where the Quotation should be validated and converted into " +"a purchase order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Reference of the document that generated this purchase order request (e.g. a" +" sales order or an internal procurement request)" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "This will determine picking type of incoming shipment" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Put an address if you want to deliver directly from the vendor to the " +"customer. Otherwise, keep empty to deliver to your own company." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Technical field used to display the Drop Ship Address" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"International Commercial Terms are a series of predefined commercial terms " +"used in international transactions." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:35 +msgid "View *Request for Quotation* in our Online Demonstration" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:37 +msgid "" +"In **Products**, click on Add an item. Select the product you wish to order " +"in the **Product** menu. Specify the **Quantity** by inserting the number " +"and selecting the unit of measure. In the **Unit Price** field, specify the " +"price you would like to be offered (you can also leave the field blank if " +"you don't know what the price should be) , and add the expected delivery " +"date in the Scheduled Date field. Click on **Save**, then **Print Rfq** or " +"**Send Rfq by email** (make sure an email address is specified for this " +"supplier or enter a new one)." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:51 +msgid "" +"After having clicked on **Send**, you will notice that the RFQ's status will" +" switch from **Draft** to **RFQ Sent**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:57 +msgid "" +"Once your supplier has replied with an offer, update the RfQ by clicking on " +"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, " +"payment terms, etc.), then click on **Save** to issue a Purchase Order." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:62 +msgid "" +"To proceed with the order, click on **Confirm Order** to send the order to " +"the supplier. The RfQ's status will switch to **Purchase Order**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:68 +msgid "" +"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right" +" corner of the order will show 1 Shipment and 0 Invoice." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:3 +msgid "How to control product received? (entirely & partially)" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:5 +msgid "" +"The **Purchase** app allows you to manage your purchase orders, to control " +"products to receive and to control supplier bills." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:8 +msgid "" +"If you want to get product forecasts and receptions under control, the first" +" thing to do is to deploy the Odoo purchase process. Knowing what have been " +"purchased is the basis of forecasting and controlling receptions." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:17 +msgid "Install the Purchase and Inventory applications" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:19 +msgid "" +"Start by installing the Purchase application from the **Apps** module. This " +"will automatically trigger the installation of the **Inventory** app (among " +"others), which is required with **Purchase**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:27 +msgid "Create products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:29 +msgid "" +"Then, you need to create the products you want to purchase. Go to the " +"**Purchase** app, then :menuselection:`Purchase --> Products`, and click on " +"**Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:36 +msgid "When creating the product, the **Product Type** field is important:" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:38 +msgid "" +"**Stockable & Consumable**: products need to be received in the inventory." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:41 +msgid "" +"**Services & Digital Products** (only when the **eCommerce** app is " +"installed): there is no control about what you receive or not." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:45 +msgid "" +"It's always good to create a **Miscellaneous** product for all the products " +"you purchased rarely and for which you don't want to manage the stocks or " +"have purchase/sale statistics. If you create such a product, we recommend to" +" set his product type field as **Service**." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:52 +msgid "Control products receptions" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:55 +msgid "Purchase products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:57 +msgid "" +"From the purchase application, create a purchase order with a few products. " +"If the vendor sent you a sale order or a quotation, put its reference in the" +" **Vendor Reference** field. This will allow you to easily do the matching " +"with the delivery order later on (as the delivery order will probably " +"include the **Vendor Reference** of his sale order)." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:67 +msgid "" +"See the documentation page :doc:`../../overview/process/from_po_to_invoice` " +"for a full overview of the purchase process." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:71 +msgid "Receive Products" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:73 +msgid "" +"If you purchased physical goods (stockable or consumable products), you can " +"receive the products from the **Inventory** application. From the " +"**Inventory** dashboard, you should see a button **X To Receive**, on the " +"receipt box of the related warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:81 +msgid "" +"Click on this button and you access a list of all awaiting orders for this " +"warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:87 +msgid "" +"If you have a lot of awaiting orders, you can use the filter bar to search " +"on the **Vendor** (also called **Partner** in Odoo), the product or the " +"source document, which is the reference of your purchase order. You can open" +" the document that matches with the received delivery order and process all " +"the lines within it." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:96 +msgid "" +"You may validate the whole document at once by clicking on the **Validate** " +"button or you can control all products, one by one, by manually change the " +"**Done** quantity (what has actually been received). When a line is green, " +"it means the quantity received matches to what have been expected." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:103 +msgid "" +"If you work with lots or serial numbers, you can not set the processed " +"quantity, but you have to provide all the lots or serial numbers to record " +"the quantity received." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:107 +msgid "" +"When you validate the reception, if you have received less products than the" +" initial demand, Odoo will ask youthe permission to create a backorder." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:114 +msgid "" +"If you plan to receive the remaining product in the future, select **Create " +"Backorder**. Odoo will create a new documents for the awaiting products. If " +"you choose **No Backorder**, the order is considered as fulfilled." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:121 +msgid ":doc:`cancel`" +msgstr "" + +#: ../../purchase/purchases/tender.rst:3 +msgid "Purchase Tenders" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:3 +msgid "How to manage Purchase Tenders" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:12 +msgid "" +"For more information on best uses, please read the chapter `Request for " +"Quotation, Purchase Tender or Purchase Order? " +"<https://www.odoo.com/documentation/user/10.0/purchase/overview/process/difference.html>`__" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:17 +msgid "Activate the Purchase Tender function" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:19 +msgid "" +"By default, the Purchase Tender is not activated. To be able to use PTs, you" +" must first activate the option." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:22 +msgid "" +"In the Purchases module, open the Configuration menu and click on Settings. " +"In the Purchase Order section, locate the **Calls for Tenders** and tick the" +" box Allow using call for tenders... (advanced), then click on **Apply**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:31 +msgid "Create a Purchase Tender" +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:33 +msgid "" +"To create a new Purchase Tender, open :menuselection:`Purchase --> Purchase " +"Agreements (PA)`." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:39 +msgid "" +"In the Purchase Agreements window, click on **Create**. A new Purchase " +"Agreement window opens." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:42 +msgid "In the **Agreement Type** field, choose Purchase Tender." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:44 +msgid "You do not have to define a **Vendor**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:46 +msgid "" +"In the **Products** section, click on **Add an item**. Select products in " +"the Product list, then insert **Quantity**. You can add as many products as " +"you wish." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:53 +msgid "Click on **Confirm Call**." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:55 +msgid "" +"Now click on the button **New Quotation**. A RfQ is created with the " +"products chosen on the PT. Choose a **Vendor** and send the RfQ to the " +"vendor. Repeat this operation for each vendor." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:62 +msgid "Once all the RfQs are sent, you can click on **Validate** on the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:64 +msgid "" +"The vendors will send their offers, you can update the RfQs accordingly. " +"Then, choose the ones you want to accept by clicking on **Confirm Order** on" +" the RfQs and **Cancel** the others." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:68 +msgid "You can now click on **Done** on the PT." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:70 +msgid "" +"View `Purchase Tenders " +"<https://demo.odoo.com/?module=purchase_requisition.action_purchase_requisition>`__" +" in our Online Demonstration." +msgstr "" + +#: ../../purchase/purchases/tender/manage_multiple_offers.rst:77 +msgid ":doc:`../../overview/process/difference`" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:3 +msgid "" +"How to purchase partially at two vendors for the same purchase tenders?" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:5 +msgid "" +"For some Purchase Tenders (PT), you might sometimes want to be able to " +"select only a part of some of the offers you received. In Odoo, this is made" +" possible through the advanced mode of the **Purchase** module." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:10 +msgid "" +"If you want to know how to handle a simple **Purchase Tender**, read the " +"document on :doc:`manage_multiple_offers`." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:19 +msgid "From the **Apps** menu, install the **Purchase Management** app." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:25 +msgid "Activating the Purchase Tender and Purchase Tender advanced mode" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:27 +msgid "" +"In order to be able to select elements of an offer, you must activate the " +"advanced mode." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:30 +msgid "" +"To do so, go into the **Purchases** module, open the **Configuration** menu " +"and click on **Settings**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:33 +msgid "" +"In the **Calls for Tenders** section, tick the option **Allow using call for" +" tenders to get quotes from multiple suppliers(...)**, and in the **Advanced" +" Calls for Tenders** section, tick the option **Advanced call for tender " +"(...)** then click on **Apply**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:42 +msgid "Selecting elements of a RFQ/Bid" +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:44 +msgid "" +"Go to :menuselection:`Purchase --> Purchase Tenders`. Create a purchase " +"tender containing several products, and follow the usual sequence all the " +"way to the **Bid Selection** status." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:49 +msgid "" +"When you closed the call, click on **Choose Product Lines** to access the " +"list of products and the bids received for all of them." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:55 +msgid "" +"Unroll the list of offers you received for each product, and click on the " +"*v* symbol (**Confirm order**) next to the offers you wish to proceed with. " +"The lines for which you've confirmed the order turn blue. When you're " +"finished, click on **Generate PO** to create a purchase order for each " +"product and supplier." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:64 +msgid "" +"When you come back to you purchase tender, you can see that the status has " +"switched to **PO Created** and that the **Requests for Quotations** now have" +" a status of **Purchase Order** or **Cancelled**." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:72 +msgid "" +"From there, follow the documentation " +":doc:`../../overview/process/from_po_to_invoice` to proceed with the " +"delivery and invoicing." +msgstr "" + +#: ../../purchase/purchases/tender/partial_purchase.rst:76 +msgid ":doc:`manage_multiple_offers`" +msgstr "" + +#: ../../purchase/replenishment.rst:3 +msgid "Replenishment" +msgstr "" + +#: ../../purchase/replenishment/flows.rst:3 +msgid "Replenishment Flows" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:3 +msgid "How are the order date and scheduled dates computed?" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:5 +msgid "" +"Scheduled dates are computed in order to be able to plan deliveries, " +"receptions and so on. Depending on the habits of your company, Odoo " +"automatically generates scheduled dates via the scheduler. The Odoo " +"scheduler computes everything per line, whether it's a manufacturing order, " +"a delivery order, a sale order, etc. The dates that are computed are " +"dependent on the different leads times configured in Odoo." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:13 +msgid "Configuring lead times" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:15 +msgid "" +"Configuring **lead times** is an essential move in order to compute " +"scheduled dates. Lead times are the delays (in term of delivery, " +"manufacturing, ...) promised to your different partners and/or clients. " +"Configuration of the different lead times are made as follows:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:21 +msgid "On a product level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:24 +msgid "Supplier lead time:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:26 +msgid "" +"The supplier lead time is the time needed for the supplier to deliver your " +"purchased product. To configure the Supplier lead time select a product " +"(from the Purchase module, go to :menuselection:`Purchase --> Product`), and" +" go in the **Inventory** tab. You will have to add a **Vendor** to your " +"product in order to select a supplier lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:36 +msgid "" +"It is possible to add more than one vendor per product and thus different " +"delivery lead times depending on the vendor." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:39 +msgid "" +"Once a vendor is selected, click on it to open its form and indicate its " +"delivery lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:46 +msgid "" +"In this case security days have no influence, the scheduled delivery days " +"will be equal to: Date of the purchase order + Delivery Lead Time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:50 +msgid "Customer lead time" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:52 +msgid "" +"The customer lead time is the time needed to get your product from your " +"store/warehouse to your customer. It can be configured for any product. " +"Simply select a product (from the **Sales** module, go to " +":menuselection:`Sales --> Product`), and go into the **Sales** tab to " +"indicate your customer lead time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:62 +msgid "On the company level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:64 +msgid "" +"On company level, it is possible to parameter **security days** in order to " +"cope with eventual delays and to be sure to meet your engagements. The idea " +"is to subtract **backup** days from the computed scheduled date in case of " +"delays." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:70 +msgid "Sales Safety days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:72 +msgid "" +"Sales Safety days are **back-up** days to ensure you will be able to deliver" +" your clients engagements on time. They are margins of errors for delivery " +"lead times. Security days are the same logic as the early wristwatch, in " +"order to arrive on time. The idea is to subtract the numbers of security " +"days from the calculation and thus to compute a scheduled date earlier than " +"the one you promised to your client. That way you are sure to be able to " +"keep your commitment." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:80 +msgid "" +"To set up your security dates, go to the app :menuselection:`Settings --> " +"General settings`, and click on **Configure your company data**." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:87 +msgid "Go the **Configuration** tab to indicate the number of safety days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:93 +msgid "" +"Note that you can in this menu configure a default **Manufacturing** lead " +"time." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:97 +msgid "Purchase days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:99 +msgid "Purchase days response to the same logic than sales security days." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:101 +msgid "" +"They are margins of error for vendor lead times. When the system generates " +"purchase orders for procuring products, they will be scheduled in order to " +"cope with unexpected vendor delays. Purchase lead time can be found in the " +"same menu as the sales safety days (see screenshot above)." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:108 +msgid "On route level" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:110 +msgid "" +"The internal transfers due to the movement of stocks can also influence the " +"computed date." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:113 +msgid "" +"The delays due to internal transfers can be specified in the **Inventory** " +"module when creating a new push rule for a new route." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:117 +msgid "" +"Read the documentation " +":doc:`../../../../inventory/routes/concepts/push_rule` to learn more." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:125 +msgid "On document level:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:128 +msgid "Requested date" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:130 +msgid "" +"Odoo offers the possibility to indicate a requested date by the client " +"straight on the sale order, under the tab **Other information**. If this " +"date is earlier than the theoretically computed date, Odoo will " +"automatically display a warning." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:141 +msgid "" +"As an example, you may sell a car today (January 1st), that is purchased on " +"order, and you promise to deliver your customer within 20 days (January 20)." +" In such a scenario, the scheduler may trigger the following events, based " +"on your configuration:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:146 +msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:148 +msgid "" +"January 18: receive the product from your supplier (1 day of Purchase days)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:151 +msgid "" +"January 10: deadline to order at your supplier (9 days of supplier delivery " +"lead time)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:154 +msgid "" +"January 8: trigger a purchase request to your purchase team, since the team " +"needs on average 2 days to find the right supplier and order." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:3 +msgid "How to setup drop-shipping?" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:8 +msgid "" +"Drop shipping allows to deliver the goods directly from the supplier to the " +"customer. It means that the products does not transit through your stock." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:15 +msgid "" +"First, configure the **Routes** and **Dropshipping**. Go to " +":menuselection:`Inventory --> Configuration --> Settings`. Check **Advanced " +"routing of products using rules** in the **Routes** section and **Allow " +"suppliers to deliver directly to your customers** in the **Drop Shipping** " +"section." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:24 +msgid "" +"You have to allow the choice of the route on the sale order. Go to the " +"**Sales** application, :menuselection:`Configuration --> Settings` and tick " +"**Choose specific routes on sales order lines (advanced)**." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:32 +msgid "How to use drop-shipping?" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:34 +msgid "" +"Create the sale order and select the route as **Dropshipping** on the " +"concerned order lines." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:40 +msgid "" +"Once the order has been confirmed, no move will be created from your stock. " +"The goods will be delivered directly from your vendor to your customer." +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:45 +msgid "" +"In order to be able to invoice the delivery, you must set the invoice policy" +" of your product on **Ordered quantities**." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:3 +msgid "How to trigger the purchase of products based on sales?" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:8 +msgid "" +"When you work in just-in-time, you don't manage stock so you directly order " +"the product you need from your vendor." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:11 +msgid "The usual flow is:" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:13 +msgid "Create a sale order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:15 +msgid "Purchase the product" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:17 +msgid "Receive and pay the bill" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:19 +msgid "Deliver your product" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:21 +msgid "Invoice your customer" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:24 +msgid "Product configuration" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:26 +msgid "" +"In the purchases application, open the **Purchase** menu and click on " +"**Products**. Open the product on which you want to do your purchases based " +"on sales." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:30 +msgid "" +"Next to Routes, tick **Buy** and **Make to order** as a procurement method. " +"When you are generating sales order, Odoo will automatically reorder the " +"same quantity through procurement." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:37 +msgid "Don't forget to set a vendor otherwise the rule won't be triggered." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:39 +msgid "" +"You can also configure minimum stock rules that will trigger the purchase " +"orders." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:43 +msgid "" +"To know how to configure a minimum stock rule, please read the document " +":doc:`setup_stock_rule`." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:50 +msgid "Sale order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:52 +msgid "" +"To create a sale order, go to the **Sales** application, " +":menuselection:`Sales --> Sales order` and create a new sale order." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:58 +msgid "" +"After confirming it, you will see one **Delivery** associated with this sale" +" order on the **button** on the top of it." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:64 +msgid "" +"Click on the **Delivery** button to see the transfer order. The status of " +"the outgoing shipment is **Waiting Another Operation**. It won't be done " +"until the purchase order is confirmed and received." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:69 +msgid "Purchase order" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:71 +msgid "" +"The purchase order is automatically created. Go to the **Purchase** " +"application :menuselection:`Purchase --> Request for Quotation`. The source " +"document is the sale order that triggered the procurement." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:79 +msgid "" +"If you make some more sales that trigger procurements to the same vendor, it" +" will be added to the existing request for quotation. Once it is confirmed, " +"the next procurements will create a new request for quotation." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:85 +msgid "Receipt and delivery" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:87 +msgid "" +"Go the the **Inventory** application. Click on **# To Receive** on the " +"**Receipts** tile." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:93 +msgid "Select the receipt from your vendor and **Validate** it." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:98 +msgid "" +"Go back to the **Inventory** dashboard. In the delivery order, click on **# " +"To Do**. The delivery order is now ready to ship." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:104 +msgid "" +"The status of the delivery changed from **Waiting Availability** to " +"**Available**. Validate the transfer to confirm the delivery." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:111 +msgid ":doc:`setup_stock_rule`" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:112 +msgid ":doc:`warning_triggering`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:3 +msgid "How to setup a minimum stock rule?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:5 +msgid "" +"For some items you hold in stock, it might be useful to have rules making " +"sure you never run out of stocks (for example, products with a high demand, " +"or large items requiring a lot of storage space meaning they're harder to " +"stock)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:10 +msgid "" +"Odoo allows you to set up rules so that an automatic replenishment for those" +" items is made, based on minimum stocks available." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:14 +msgid "When should I use Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:16 +msgid "" +"Reordering Rules work best for items that have a high demand and high flow. " +"It will relieve you from a lot of work to focus on the rest of your " +"activities knowing that stocks will always be right." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:20 +msgid "" +"It can also be used when you have limited storage space and you need to keep" +" large items in stock. In this case, you can keep as little as 1 item in " +"stock, and have a new one ordered as a stock replenishment as soon as the " +"item in stock is sold." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:26 +msgid "When should I avoid Reordering Rules?" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:28 +msgid "" +"If you are offering a new product and don't know yet how fast it will go, " +"you should handle stocks yourself first, and setup reordering rules only a " +"few months into the sale to have better forecasts of the demand." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:32 +msgid "" +"If you sell items that have a limited lifetime, such as fashion items, " +"technology items, or products working together with a system that is meant " +"to evolve, you have to be very well informed on when to stop automated " +"replenishments, in order to avoid having to sell these items at a price that" +" will not allow you to break even." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:41 +msgid "" +"My company sells modern furniture. We sell a set of table and chairs that " +"are available in 4 seatings and 6 seatings." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:44 +msgid "" +"To keep things simple, we stock tables and chairs separately, but sell them " +"all together to our clients as a kit. In order to make sure we can always " +"deliver a complete set of table and chairs, I setup a Reordering Rule for " +"the chairs to make sure I always have at least 10 chairs in stock, but no " +"more than 20. This way, I can sell up to 5 sets of table at once while " +"keeping my stock low enough not to eat up all my storage space." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:52 +msgid "" +"The last table I sold was a 4 seatings, and there were 12 chairs left in my " +"stock. Because the stock in chairs is now only 8 chairs, Odoo will " +"automatically order 12 new chairs to fill up my stock to the maximum amount." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:61 +msgid "Set up your product" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:63 +msgid "" +"In the Purchases module, open the Purchase menu and click on Products. Open " +"the product to which you would like to add a Reordering Rule (or create a " +"new one)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:67 +msgid "3 conditions for correct reordering rule :" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:69 +msgid "" +"In :menuselection:`General information --> Product type`, make the product " +"stockable (as soon as this is done, the icon \"Reordering rule will appear)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:71 +msgid "" +"In :menuselection:`Inventory --> route`, tick the \"Buy\" box (and untick " +"the Make To Order box)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:73 +msgid "" +"Select a vendor (don't forget to put a minimal quantity greater than 0)" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:76 +msgid "Create a reordering rule" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:78 +msgid "Click on the Reordering Rules tab, click on Create. A new page opens." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:83 +msgid "" +"By default, Reordering Rules in Odoo are named as \"OP/XXXXX\" but you are " +"free to use any nomenclature. You can modify it via the **Name** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:86 +msgid "The **Product** field is the product you are creating the rule for." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:88 +msgid "" +"Select the warehouse to which the product should be delivered in the " +"**Warehouse** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:91 +msgid "" +"If you have configured multiple warehouses and location, specify the " +"location in which the product will be stored in the **Location** field." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:96 +msgid "" +":doc:`../../../inventory/settings/warehouses/difference_warehouse_location`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:102 +msgid "" +"In the **Minimum Quantity** field, insert the quantity to which the system " +"will trigger a new order for replenishment." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:105 +msgid "" +"In the **Maximum Quantity** field, insert the maximum of items that has to " +"be stocked. The replenishing order will be based on that quantity to " +"reorder." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:109 +msgid "" +"The **Quantity Multiple** is the lowest number of items that can be ordered " +"at once. For instance, some items may be only available for purchase in a " +"set of 2." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:113 +msgid "" +"In the Misc section, the **Active** box allows you to activate or deactivate" +" the rule." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:116 +msgid "In the **Lead Time** section, you can enter:" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:118 +msgid "" +"the number of Day(s) to purchase: correspond to the number of days for the " +"supplier to receive the order" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:120 +msgid "the number of Day(s) to get the products" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:122 +msgid "" +"By default, the lead times are in calendar days. You can change that in " +":menuselection:`Inventory --> Configuration --> Settings --> Minimum Stock " +"Rules`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:125 +msgid "When you have entered all the info, click on Save." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:127 +msgid "" +"From now on, every time a product with a reordering rule reaches the minimum" +" stock, the system will automatically send a RfQ to your supplier based on " +"your maximum quantity to replenish your stock." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:131 +msgid "" +"The replenishments will take place when the scheduler in the Inventory " +"module runs. By default in Odoo, the schedulers will run every night at " +"12:00PM." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:135 +msgid "" +"To know how to configure and run the schedulers manually, read the document " +"on :doc:`../../../inventory/management/misc/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:140 +msgid ":doc:`../../../inventory/management/misc/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:3 +#: ../../purchase/replenishment/flows/warning_triggering.rst:69 +msgid "How to trigger a warning when purchasing at a specific vendor?" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:8 +msgid "" +"The **Warning Messages and Alerts** module allow you to configure alerts on " +"the customers and vendors or products." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:11 +msgid "" +"You can select the following types of warnings and create different warnings" +" for purchases and sales:" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:14 +msgid "" +"Warning: This option displays the warning message during the process, but " +"allows the user to continue." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:17 +msgid "" +"Blocking Message: The message displays a warning message, but the user " +"cannot continue the process further." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:24 +msgid "Module Installation" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:26 +msgid "" +"First, you need to install the **Warning Messages and Alerts** module. Go to" +" **Apps** and look for it (don't forget to remove the **Apps** filter)." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:33 +msgid "Vendor or Customer warnings" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:35 +msgid "" +"Go to :menuselection:`Purchases --> Vendors` or to :menuselection:`Sales -->" +" Customers`." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:37 +msgid "Open the vendor or the customer and click on the **Warnings** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:42 +#: ../../purchase/replenishment/flows/warning_triggering.rst:62 +msgid "The available warnings are:" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:44 +msgid "Warning on the **Sales Order**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:46 +msgid "Warning on the **Purchase Order**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:48 +msgid "Warning on the **Picking**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:50 +msgid "Warning on the **Invoice**" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:53 +msgid "Product Warnings" +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:55 +msgid "" +"Go to :menuselection:`Purchases --> Products` or to :menuselection:`Sales " +"--> Products`." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:57 +msgid "Open the product and click on the **Notes** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:64 +msgid "Warning when selling this product." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:66 +msgid "Warning when Purchasing this product." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:71 +msgid "" +"Go to the Purchases application, click on :menuselection:`Purchase --> " +"Vendors`. Go to the **Warnings** tab." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:74 +msgid "" +"Under **Warning on the Purchase Order**, choose **Warning** and write your " +"warning." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:80 +msgid "" +"Create a **Request for Quotation**. Go to :menuselection:`Purchase --> " +"Request for Quotation` and click on **Create**. Choose the vendor on which a" +" warning was set." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:84 +msgid "When choosing the vendor, the warning will appear." +msgstr "" + +#: ../../purchase/replenishment/flows/warning_triggering.rst:90 +msgid "" +"If you set a blocking message instead of a warning message, you won't be " +"able to choose the vendor." +msgstr "" + +#: ../../purchase/replenishment/multicompany.rst:3 +msgid "Multi-Companies" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:3 +msgid "How to setup a multi-company sale/purchase flow?" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:8 +msgid "" +"Odoo is an outstanding solution to help small companies growing their " +"business. But it also perfectly meets the needs of multinational " +"companies.The inter-company feature helps you to buy and/or sell products " +"and services between different branches within your conglomerate." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:17 +msgid "" +"Purchase orders and sales orders can be related. If a company within your " +"group creates a purchase or a sales order, the corresponding document is " +"automatically created for your company. All you have to do is check that " +"everything is correct and confirm the sale. You can automate the validation " +"on your sales and purchase orders." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:24 +msgid "It is also possible to only handle invoices and refunds." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:27 +msgid "Manage intercompany rules" +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:29 +msgid "" +"Go to :menuselection:`Settings --> General Settings`. Flag **Manage multiple" +" companies** and then **Manage Inter Company**." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:32 +msgid "Click on **Apply**." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:37 +msgid "New options will appear." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:42 +msgid "" +"In the drop-down list, choose the company on which you want to add rules." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:45 +msgid "" +"If you click on **SO and PO setting for inter company**, you will get extra " +"options." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:51 +msgid "" +"When you are done, click on **Apply**, then you can repeat the same steps " +"for the other companies." +msgstr "" + +#: ../../purchase/replenishment/multicompany/setup.rst:55 +msgid "" +"In order to be able to manage the inter-company rules, be sure that your " +"user has the rights to manage the companies." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting.rst:3 +msgid "Trouble-Shooting" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:3 +msgid "How to check that everything is working fine?" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:6 +msgid "Vendor Bills" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:8 +msgid "" +"Even if you don't have the rights to the accounting application, you can " +"still control the vendor bills." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:11 +msgid "" +"Go to the **Purchases** application: :menuselection:`Control --> Vendor " +"Bills`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:17 +msgid "Incoming Products" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:19 +msgid "" +"Even if you don't have the rights to the inventory application, you can " +"still control the incoming products." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:22 +msgid "" +"Go to the **Purchases** application: :menuselection:`Control --> Incoming " +"Products`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:28 +msgid "Procurements exceptions" +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:30 +msgid "Here, you need the **Inventory Manager** access rights." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:32 +msgid "" +"Go to the **Inventory** application: :menuselection:`Control --> Procurement" +" Exceptions`." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:37 +msgid "" +"To understand why the procurement is not running, open the exception and " +"check the message in the chatter." +msgstr "" + +#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:43 +msgid "" +"Usually, the problem is located on the procurement rules. Either there are " +"no stock rules, or there are no vendor associated to a product." +msgstr "" diff --git a/locale/tr/LC_MESSAGES/recruitment.po b/locale/tr/LC_MESSAGES/recruitment.po new file mode 100644 index 000000000..8a20bf397 --- /dev/null +++ b/locale/tr/LC_MESSAGES/recruitment.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 9.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2016-11-22 13:16+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../recruitment.rst:5 +msgid "Recruitment" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/sales.po b/locale/tr/LC_MESSAGES/sales.po new file mode 100644 index 000000000..4ee5af152 --- /dev/null +++ b/locale/tr/LC_MESSAGES/sales.po @@ -0,0 +1,1863 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Güven YILMAZ <guvenyilmaz@outlook.com.tr>, 2017\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../sales.rst:5 +msgid "Sales" +msgstr "Satış" + +#: ../../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: 1. A long term client who needs to view online quotations. 2." +" Accounting consultant who needs to keep track of the company's financials." +msgstr "" + +#: ../../sales/advanced/portal.rst:16 +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:20 +msgid "How to give portal access to customers?" +msgstr "" + +#: ../../sales/advanced/portal.rst:23 +msgid "From Contacts Module" +msgstr "" + +#: ../../sales/advanced/portal.rst:25 +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:35 +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:38 +msgid "Select **Portal Access Management**. A pop up window appears." +msgstr "" + +#: ../../sales/advanced/portal.rst:43 +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:49 +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/services.rst:3 +msgid "Services" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:3 +msgid "How to invoice milestones of a project?" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:5 +msgid "" +"There are different kind of service sales: prepaid volume of hours/days " +"(e.g. support contract), billing based on time and material (e.g. billing " +"consulting hours) or a fixed price contract (e.g. a project)." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:9 +msgid "" +"In this section, we will have a look at how to invoice milestones of a " +"project." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:12 +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. For example, a marketing agency" +" hired for a new product launch could break down a project into the " +"following milestones, each of them considered as one service with a fixed " +"price on the sale order :" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:19 +msgid "Milestone 1 : Marketing strategy audit - 5 000 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:21 +msgid "Milestone 2 : Brand Identity - 10 000 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:23 +msgid "Milestone 3 : Campaign launch & PR - 8 500 euros" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:25 +msgid "" +"In this case, an invoice will be sent to the customer each time a milestone " +"will be successfully reached. That 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 times." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:32 +msgid "" +"You can also use milestones to invoice percentages of the entire project. " +"For example, for a million euros project, your company might require a 15% " +"upfront payment, 30% at the midpoint and the balance at the contract " +"conclusion. In that case, each payment will be considered as one milestone." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:39 +#: ../../sales/invoicing/services/reinvoice.rst:26 +#: ../../sales/invoicing/services/reinvoice.rst:95 +#: ../../sales/invoicing/services/support.rst:17 +#: ../../sales/quotation/online/creation.rst:6 +#: ../../sales/quotation/setup/different_addresses.rst:14 +#: ../../sales/quotation/setup/first_quote.rst:21 +#: ../../sales/quotation/setup/optional.rst:16 +msgid "Configuration" +msgstr "Yapılandırma" + +#: ../../sales/invoicing/services/milestones.rst:42 +msgid "Install the Sales application" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:44 +#: ../../sales/invoicing/services/reinvoice.rst:28 +msgid "" +"In order to sell services and to send invoices, you need to install the " +"**Sales** application, from the **Apps** icon." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:51 +msgid "Create products" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:53 +msgid "" +"In Odoo, each milestone of your project is considered as a product. From the" +" **Sales** application, use the menu :menuselection:`Sales --> Products`, " +"create a new product with the following setup:" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:57 +msgid "**Name**: Strategy audit" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:59 +#: ../../sales/invoicing/services/support.rst:50 +msgid "**Product Type**: Service" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:61 +msgid "" +"**Invoicing Policy**: Delivered Quantities, since you will invoice your " +"milestone after it has been delivered" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:64 +msgid "" +"**Track Service**: Manually set quantities on order, as you complete each " +"milestone, you will manually update their quantity from the **Delivered** " +"tab on your sale order" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:72 +msgid "Apply the same configuration for the others milestones." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:75 +msgid "Managing your project" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:78 +msgid "Quotations and sale orders" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:80 +msgid "" +"Now that your milestones (or products) are created, you can create a " +"quotation or a sale order with each line corresponding to one milestone. For" +" each line, set the **Ordered Quantity** to ``1`` as each milestone is " +"completed once. Once the quotation is confirmed and transformed into a sale " +"order, you will be able to change the delivered quantities when the " +"corresponding milestone has been achieved." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:91 +msgid "Invoice milestones" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:93 +msgid "" +"Let's assume that your first milestone (the strategy audit) has been " +"successfully delivered and you want to invoice it to your customer. On the " +"sale order, click on **Edit** and set the **Delivered Quantity** of the " +"related product to ``1``." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:99 +msgid "" +"As soon as the above modification has been saved, you will notice that the " +"color of the line has changed to blue, meaning that the service can now be " +"invoiced. In the same time, the invoice status of the SO has changed from " +"**Nothing To Invoice** to **To Invoice**" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:104 +msgid "" +"Click on **Create invoice** and, in the new window that pops up, select " +"**Invoiceable lines** and validate. It will create a new invoice (in draft " +"status) with only the **strategy audit** product as invoiceable." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:112 +msgid "" +"In order to be able to invoice a product, you need to set up the " +"**Accounting** application and to configure an accounting journal and a " +"chart of account. Click on the following link to learn more: " +":doc:`../../../accounting/overview/getting_started/setup`" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:117 +msgid "" +"Back on your sale order, you will notice that the **Invoiced** column of " +"your order line has been updated accordingly and that the **Invoice Status**" +" is back to **Nothing to Invoice**." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:121 +msgid "Follow the same workflow to invoice your remaining milestones." +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:124 +msgid ":doc:`reinvoice`" +msgstr "" + +#: ../../sales/invoicing/services/milestones.rst:125 +#: ../../sales/invoicing/services/reinvoice.rst:185 +msgid ":doc:`support`" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:3 +msgid "How to re-invoice expenses to your customers?" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.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 " +"employee paying a parking spot for a meeting with your client. As a company," +" you would like to be able to invoice that expense to your client." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:11 +msgid "" +"In this documentation we will see two use cases. The first, very basic, " +"consists of invoicing a simple expense to your client like you would do for " +"a product. The second, more advanced, will consist of invoicing expenses " +"entered in your expense system by your employees directly to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:18 +msgid "Use case 1: Simple expense invoicing" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:20 +msgid "" +"Let's take the following example. You are working on a promotion campaign " +"for one of your customers (``Agrolait``) and you have to print a lot of " +"copies. Those copies are an expense for your company and you would like to " +"invoice them." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:35 +msgid "Create product to be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:37 +msgid "You will need now to create a product called ``Copies``." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:39 +#: ../../sales/invoicing/services/reinvoice.rst:112 +msgid "" +"From your **Sales** module, go to :menuselection:`Sales --> Products` and " +"create a product as follows:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:42 +msgid "**Product type**: consumable" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:44 +msgid "" +"**Invoicing policy**: on delivered quantities (you will manually set the " +"quantities to invoice on the sale order)" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:51 +msgid "Create a sale order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:53 +msgid "" +"Now that your product is correctly set up, you can create a sale order for " +"that product (from the menu :menuselection:`Sales --> Sales Orders`) with " +"the ordered quantities set to 0. Click on **Confirm the Sale** to create the" +" sale order. You will be able then to manually change the delivered " +"quantities on the sale order to reinvoice the copies to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:64 +#: ../../sales/invoicing/services/reinvoice.rst:177 +msgid "Invoice expense to your client" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:66 +msgid "" +"At the end of the month, you have printed ``1000`` copies on behalf of your " +"client and you want to re-invoice them. From the related sale order, click " +"on **Delivered Quantities**, manually enter the correct amount of copies and" +" click on **Save**. Your order line will turn blue, meaning that it is ready" +" to be invoiced. Click on **Create invoice**." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:73 +msgid "" +"The total amount on your sale order will be of 0 as it is computed on the " +"ordered quantities. It is your invoice which will compute the correct amount" +" due by your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:77 +msgid "" +"The invoice generated is in draft, so you can always control the quantities " +"and change the amount if needed. You will notice that the amount to be " +"invoiced is based here on the delivered quantities." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:84 +msgid "Click on validate to issue the payment to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:87 +msgid "Use case 2: Invoice expenses via the expense module" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:89 +msgid "" +"To illustrate this case, let's imagine that your company sells some " +"consultancy service to your customer ``Agrolait`` and both parties agreed " +"that the distance covered by your consultant will be re-invoiced at cost." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:97 +msgid "Here, you will need to install two more modules:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:99 +msgid "Expense Tracker" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:101 +msgid "" +"Accounting, where you will need to activate the analytic accounting from the" +" settings" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:108 +msgid "Create a product to be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:110 +msgid "You will now need to create a product called ``Kilometers``." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:115 +msgid "Product can be expensed" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:117 +msgid "Product type: Service" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:119 +msgid "Invoicing policy: invoice based on time and material" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:121 +msgid "Expense invoicing policy: At cost" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:123 +msgid "Track service: manually set quantities on order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:129 +msgid "Create a sales order" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:131 +msgid "" +"Still from the Sales module, go to :menuselection:`Sales --> Sales Orders` " +"and add your product **Consultancy** on the order line." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:135 +msgid "" +"If your product doesn't exist yet, you can configure it on the fly from the " +"SO. Just type the name on the **product** field and click on **Create and " +"edit** to configure it." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:139 +msgid "" +"Depending on your product configuration, an **Analytic Account** may have " +"been generated automatically. If not, you can easily create one in order to " +"link your expenses to the sale order. Do not forget to confirm the sale " +"order." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:148 +msgid "" +"Refer to the documentation :doc:`../../../accounting/others/analytic/usage` " +"to learn more about that concept." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:152 +msgid "Create expense and link it to SO" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:154 +msgid "" +"Let's assume that your consultant covered ``1.000km`` in October as part of " +"his consultancy project. We will create a expense for it and link it to the " +"related sales order thanks to the analytic account." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:158 +msgid "" +"Go to the **Expenses** module and click on **Create**. Record your expense " +"as follows:" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:161 +msgid "**Expense description**: Kilometers October 2015" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:163 +msgid "**Product**: Kilometers" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:165 +msgid "**Quantity**: 1.000" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:167 +msgid "**Analytic account**: SO0019 - Agrolait" +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:172 +msgid "" +"Click on **Submit to manager**. As soon as the expense has been validated " +"and posted to the journal entries, a new line corresponding to the expense " +"will automatically be generated on the sale order." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:179 +msgid "You can now invoice the invoiceable lines to your customer." +msgstr "" + +#: ../../sales/invoicing/services/reinvoice.rst:186 +msgid ":doc:`milestones`" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:3 +msgid "How to invoice a support contract (prepaid hours)?" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:5 +msgid "" +"There are different kinds of service sales: prepaid volume of hours/days " +"(e.g. support contract), billing based on time and material (e.g. billing " +"consulting hours) and a fixed price contract (e.g. a project)." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:9 +msgid "" +"In this section, we will have a look at how to sell and keep track of a pre-" +"paid support contract." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:12 +msgid "" +"As an example, you may sell a pack of ``50 Hours`` of support at " +"``$25,000``. The price is fixed and charged initially. But you want to keep " +"track of the support service you did for the customer." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:20 +msgid "Install the Sales and Timesheet applications" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:22 +msgid "" +"In order to sell services, you need to install the **Sales** application, " +"from the **Apps** icon. Install also the **Timesheets** application if you " +"want to track support services you worked on every contract." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:33 +msgid "Create Products" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:35 +msgid "" +"By default, products are sold by number of units. In order to sell services " +"``per hour``, you must allow using multiple unit of measures. From the " +"**Sales** application, go to the menu :menuselection:`Configuration --> " +"Settings`. From this screen, activate the multiple **Unit of Measures** " +"option." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:44 +msgid "" +"In order to sell a support contract, you must create a product for every " +"support contract you sell. From the **Sales** application, use the menu " +":menuselection:`Sales --> Products`, create a new product with the following" +" setup:" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:48 +msgid "**Name**: Technical Support" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:52 +msgid "**Unit of Measure**: Hours" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:54 +msgid "" +"**Invoicing Policy**: Ordered Quantities, since the service is prepaid, we " +"will invoice the service based on what has been ordered, not based on " +"delivered quantities." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:58 +msgid "" +"**Track Service**: Timesheet on contracts. An analytic account will " +"automatically be created for every order containing this service so that you" +" can track hours in the related account." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:66 +msgid "" +"There are different ways to track the service related to a sales order or " +"product sold. With the above configuration, you can only sell one support " +"contract per order. If your customer orders several service contracts on " +"timesheet, you will have to split the quotation into several orders." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:72 +msgid "" +"Note that you can sell in different unit of measure than hours, example: " +"days, pack of 40h, etc. To do that, just create a new unit of measure in the" +" **Unit of Measure** category and set a conversion ratio compared to " +"**Hours** (example: ``1 day = 8 hours``)." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:78 +msgid "Managing support contract" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:81 +msgid "Quotations and Sales Orders" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:83 +msgid "" +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:93 +msgid "Timesheets" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:95 +msgid "" +"To track the service you do on a specific contract, you should use the " +"timesheet application. An analytic account related to the sale order has " +"been automatically created (``SO009 - Agrolait`` on the screenshot here " +"above), so you can start tracking services as soon as it has been sold." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:104 +msgid "Control delivered support on the sales order" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:106 +msgid "" +"From the **Sales** application, use the menu :menuselection:`Sales --> Sales" +" Orders` to control the progress of every order. On the sales order line " +"related to the support contract, you should see the **Delivered Quantities**" +" that are updated automatically, based on the number of hours in the " +"timesheet." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:116 +msgid "Upselling and renewal" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:118 +msgid "" +"If the number of hours you performed on the support contract is bigger or " +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:127 +msgid "" +"If you use Odoo CRM, a good practice is to create an opportunity for every " +"sale order in upselling invoice status so that you easily track your " +"upselling effort." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:131 +msgid "" +"If you sell an extra support contract, you can either add a new line on the " +"existing sales order (thus, you continue to timesheet on the same order) or " +"create a new order (thus, people will timesheet their hours on the new " +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:138 +msgid "Special Configuration" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:140 +msgid "" +"When creating the product form, you may set a different approach to track " +"the service:" +msgstr "" + +#: ../../sales/invoicing/services/support.rst:143 +msgid "" +"**Create task and track hours**: in this mode, a task is created for every " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " +"contract). The advantage of this solution is that it allows to sell several " +"service contracts within the same sales order." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:150 +msgid "" +"**Manually**: you can use this mode if you don't record timesheets in Odoo. " +"The number of hours you worked on a specific contract can be recorded " +"manually on the sales order line directly, in the delivered quantity field." +msgstr "" + +#: ../../sales/invoicing/services/support.rst:156 +msgid ":doc:`../../../inventory/settings/products/uom`" +msgstr "" + +#: ../../sales/overview.rst:3 +#: ../../sales/quotation/setup/different_addresses.rst:6 +#: ../../sales/quotation/setup/first_quote.rst:6 +#: ../../sales/quotation/setup/optional.rst:6 +#: ../../sales/quotation/setup/terms_conditions.rst:6 +msgid "Overview" +msgstr "" + +#: ../../sales/overview/main_concepts.rst:3 +msgid "Main Concepts" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:3 +msgid "Introduction to Odoo Sales" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:11 +msgid "Transcript" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:13 +msgid "" +"As a sales manager, closing opportunities with Odoo Sales is really simple." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:16 +msgid "" +"I selected a predefined quotation for a new product line offer. The " +"products, the service details are already in the quotation. Of course, I can" +" adapt the offer to fit my clients needs." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:20 +msgid "" +"The interface is really smooth. I can add references, some catchy phrases " +"such as closing triggers (*here, you save $500 if you sign the quote within " +"15 days*). I have a beautiful and modern design. This will help me close my " +"opportunities more easily." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:26 +msgid "" +"Plus, reviewing the offer from a mobile phone is easy. Really easy. The " +"customer got a clear quotation with a table of content. We can communicate " +"easily. I identified an upselling opportunity. So, I adapt the offer by " +"adding more products. When the offer is ready, the customer just need to " +"sign it online in just a few clicks. Odoo Sales is integrated with major " +"shipping services: UPS, Fedex, USPS and more. The signed offer creates a " +"delivery order automatically." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:35 +msgid "That's it, I sucesfully sold my products in just a few clicks." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:37 +msgid "" +"Oh, I also have the transaction and communication history at my fingertips. " +"It's easy for every stakeholder to know clearly the past interaction. And " +"any information related to the transaction." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:42 +msgid "" +"If you want to show information, I would do it from a customer form, " +"something like:" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:45 +msgid "Kanban of customers, click on one customer" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:47 +msgid "Click on opportunities, click on quotation" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:49 +msgid "Come back to customers (breadcrum)" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:51 +msgid "Click on customer statement letter" +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:53 +msgid "" +"Anytime, I can get an in-depth report of my sales activity. Revenue by " +"salespeople or department. Revenue by category of product, drill-down to " +"specific products, by quarter or month,... I like this report: I can add it " +"to my dashboard in just a click." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:58 +msgid "" +"Odoo Sales is a powerful, yet easy-to-use app. At first, I used the sales " +"planner. Thanks to it, I got tips and tricks to boost my sales performance." +msgstr "" + +#: ../../sales/overview/main_concepts/introduction.rst:62 +msgid "" +"Try Odoo Sales now and get beautiful quotations, amazing dashboards and " +"increase your success rate." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:3 +msgid "Overview of the invoicing process" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:16 +msgid ":menuselection:`Sales Order --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:18 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:22 +msgid "" +"Invoice on ordered quantity: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:25 +msgid "Invoice based on delivered quantity: see next section" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:27 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:31 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice ready" +" to invoice line, invoice a percentage (advance), invoice a fixed advance." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:36 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:41 +msgid ":menuselection:`Sales Order --> Delivery --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:43 +msgid "" +"Retailers and eCommerce usually invoice based on delivered quantity , " +"instead of sales order. This approach is suitable for businesses where the " +"quantities you deliver may differs from the ordered quantities: foods " +"(invoice based on actual Kg)." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:48 +msgid "" +"This way, if you deliver a partial order, you only invoice for what you " +"really delivered. If you do back orders (deliver partially and the rest " +"later), the customer will receive two invoices, one for each delivery order." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:57 +msgid ":menuselection:`Recurring Contracts (subscriptions) --> Invoices`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:59 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:67 +msgid ":menuselection:`eCommerce Order --> Invoice`" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:69 +msgid "" +"An eCommerce order will also trigger the creation of the invoice when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:75 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:77 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:82 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:85 +msgid "if you need to create a refund" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:87 +msgid "If you need to give a discount" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:89 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:91 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:94 +msgid "Others" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:96 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:98 +msgid "membership: invoice your members every year" +msgstr "" + +#: ../../sales/overview/main_concepts/invoicing.rst:100 +msgid "repairs: invoice your after-sale services" +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. As pricelists only suggest prices, " +"they can be overridden by users completing sales orders. Choose your pricing" +" strategy from :menuselection:`Sales --> Settings`." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:16 +msgid "Several prices per product" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:18 +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:23 +msgid "Prices per customer segment" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:25 +msgid "" +"Create pricelists for your customer segments: e.g. registered, premium, etc." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:30 +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:38 +msgid "Temporary prices" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:40 +msgid "Apply deals for bank holidays, etc. Enter start and end dates dates." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:46 +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:50 +msgid "Prices per minimum quantity" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:56 +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:60 +msgid "Discounts, margins, roundings" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:62 +msgid "" +"The third option 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:69 +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:77 +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:84 +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:86 +msgid "Make sure at least one pricelist item covers all your products." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:88 +msgid "There are 3 modes of computation: fix price, discount & formula." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:93 +msgid "Here are different price settings made possible thanks to formulas." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:96 +msgid "Discounts with roundings" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:98 +msgid "e.g. 20% discounts with prices rounded up to 9.99." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:104 +msgid "Costs with markups (retail)" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:106 +msgid "e.g. sale price = 2*cost (100% markup) with $5 of minimal margin." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:112 +msgid "Prices per country" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:113 +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:116 +msgid "The default pricelist can be replaced when creating a sales order." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:118 +msgid "You can change the pricelists sequence by drag & drop in list view." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:121 +msgid "Compute and show discount % to customers" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:123 +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:125 +msgid "" +"Check *Allow discounts on sales order lines* in :menuselection:`Sales --> " +"Configuration --> Settings --> Quotations & Sales --> Discounts`." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:126 +msgid "Apply the option in the pricelist setup form." +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:133 +msgid ":doc:`currencies`" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:134 +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/taxes.rst:3 +msgid "Set taxes" +msgstr "" + +#: ../../sales/quotation.rst:3 +msgid "Quotation" +msgstr "" + +#: ../../sales/quotation/online.rst:3 +msgid "Online Quotation" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:3 +msgid "How to create and edit an online quotation?" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:9 +msgid "Enable Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:11 +msgid "" +"To send online quotations, you must first enable online quotations in the " +"Sales app from :menuselection:`Configuration --> Settings`. Doing so will " +"prompt you to install the Website app if you haven't already." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:18 +msgid "" +"You can view the online version of each quotation you create after enabling " +"this setting by selecting **Preview** from the top of the quotation." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:25 +msgid "Edit Your Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:27 +msgid "" +"The online quotation page can be edited for each quotation template in the " +"Sales app via :menuselection:`Configuration --> Quotation Templates`. From " +"within any quotation template, select **Edit Template** to be taken to the " +"corresponding page of your website." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:34 +msgid "" +"You can add text, images, and structural elements to the quotation page by " +"dragging and dropping blocks from the pallet on the left sidebar menu. A " +"table of contents will be automatically generated based on the content you " +"add." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:38 +msgid "" +"Advanced descriptions for each product on a quotation are displayed on the " +"online quotation page. These descriptions are inherited from the product " +"page in your eCommerce Shop, and can be edited directly on the page through " +"the inline text editor." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:45 +msgid "" +"You can choose to allow payment immediately after the customer validates the" +" quote by selecting a payment option on the quotation template." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:48 +msgid "" +"You can edit the webpage of an individual quotation as you would for any web" +" page by clicking the **Edit** button. Changes made in this way will only " +"affect the individual quotation." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:52 +msgid "Using Online Quotations" +msgstr "" + +#: ../../sales/quotation/online/creation.rst:54 +msgid "" +"To share an online quotation with your customer, copy the URL of the online " +"quotation, then share it with customer." +msgstr "" + +#: ../../sales/quotation/online/creation.rst:60 +msgid "" +"Alternatively, your customer can access their online quotations by logging " +"into your website through the customer portal. Your customer can accept or " +"reject the quotation, print it, or negotiate the terms in the chat box. You " +"will also receive a notification in the chatter within Odoo whenever the " +"customer views the quotation." +msgstr "" + +#: ../../sales/quotation/setup.rst:3 +msgid "Setup" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:3 +msgid "How to use different invoice and delivery addresses?" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:8 +msgid "" +"It is possible to configure different addresses for delivery and invoicing. " +"This is very useful, because it could happen that your clients have multiple" +" locations and that the invoice address differs from the delivery location." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:16 +msgid "" +"First, go to the Sales application, then click on " +":menuselection:`Configuration --> Settings` and activate the option **Enable" +" the multiple address configuration from menu**." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:24 +msgid "Set the addresses on the contact form" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:26 +msgid "" +"Invoice and/or shipping addresses and even other addresses are added on the " +"contact form. To do so, go to the contact application, select the customer " +"and in the **Contacts & Addresses** tab click on **Create**" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:33 +msgid "" +"A new window will open where you can specify the delivery or the invoice " +"address." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:39 +msgid "" +"Once you validated your addresses, it will appear in the **Contacts & " +"addresses** tab with distinctive logos." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:46 +msgid "On the quotations and sales orders" +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:48 +msgid "" +"When you create a new quotation, the option to select an invoice address and" +" a delivery address is now available. Both addresses will automatically be " +"filled in when selecting the customer." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:56 +msgid "" +"Note that you can also create invoice and delivery addresses on the fly by " +"selecting **Create and edit** in the dropdown menu." +msgstr "" + +#: ../../sales/quotation/setup/different_addresses.rst:59 +msgid "When printing your sales orders, you'll notice the two addresses." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:3 +msgid "How to create my first quotation?" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:8 +msgid "" +"Quotations are documents sent to customers to offer an estimated cost for a " +"particular set of goods or services. The customer can accept the quotation, " +"in which case the seller will have to issue a sales order, or refuse it." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:13 +msgid "" +"For example, my company sells electronic products and my client Agrolait " +"showed interest in buying ``3 iPads`` to facilitate their operations. I " +"would like to send them a quotation for those iPads with a sales price of " +"``320 USD`` by iPad with a ``5%`` discount." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:18 +msgid "This section will show you how to proceed." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:24 +msgid "Install the Sales Management module" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:26 +msgid "" +"In order to be able to issue your first quotation, you'll need to install " +"the **Sales Management** module from the app module in the Odoo backend." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:34 +msgid "Allow discounts on sales order line" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:36 +msgid "" +"Allowing discounts on quotations is a common sales practice to improve the " +"chances to convert the prospect into a client." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:39 +msgid "" +"In our example, we wanted to grant ``Agrolait`` with a ``5%`` discount on " +"the sale price. To enable the feature, go into the **Sales** application, " +"select :menuselection:`Configuration --> Settings` and, under **Quotations " +"and Sales**, tick **Allow discounts on sales order line** (see picture " +"below) and apply your changes." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:49 +msgid "Create your quotation" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:51 +msgid "" +"To create your first quotation, click on :menuselection:`Sales --> " +"Quotations` and click on **Create**. Then, complete your quotation as " +"follows:" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:55 +msgid "Customer and Products" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:57 +msgid "" +"The basic elements to add to any quotation are the customer (the person you " +"will send your quotation to) and the products you want to sell. From the " +"quotation view, choose the prospect from the **Customer** drop-down list and" +" under **Order Lines**, click on **Add an item** and select your product. Do" +" not forget to manually add the number of items under **Ordered Quantity** " +"and the discount if applicable." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:67 +msgid "" +"If you don't have any customer or product recorded on your Odoo environment " +"yet, you can create them on the fly directly from your quotations :" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:71 +msgid "" +"To add a new customer, click on the **Customer** drop-down menu and click on" +" **Create and edit**. In this new window, you will be able to record all the" +" customer details, such as the address, website, phone number and person of " +"contact." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:76 +msgid "" +"To add a new product, under **Order line**, click on add an item and on " +"**Create and Edit** from the drop-down list. You will be able to record your" +" product information (product type, cost, sale price, invoicing policy, " +"etc.) along with a picture." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:82 +msgid "Taxes" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:84 +msgid "" +"To parameter taxes, simply go on the taxes section of the product line and " +"click on **Create and Edit**. Fill in the details (for example if you are " +"subject to a ``21%`` taxe on your sales, simply fill in the right amount in " +"percentage) and save." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:93 +msgid "Terms and conditions" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:95 +msgid "" +"You can select the expiration date of your quotation and add your company's " +"terms and conditions directly in your quotation (see picture below)." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:103 +msgid "Preview and send quotation" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:105 +msgid "" +"If you want to see what your quotation looks like before sending it, click " +"on the **Print** button (upper left corner). It will give you a printable " +"PDF version with all your quotation details." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:113 +msgid "" +"Update your company's details (address, website, logo, etc) appearing on " +"your quotation from the the **Settings** menu on the app switcher, and on " +"click on the link :menuselection:`Settings --> General settings --> " +"Configure company data`." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:118 +msgid "" +"Click on **Send by email** to automatically send an email to your customer " +"with the quotation as an attachment. You can adjust the email body before " +"sending it and even save it as a template if you wish to reuse it." +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:127 +msgid ":doc:`../online/creation`" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:128 +msgid ":doc:`optional`" +msgstr "" + +#: ../../sales/quotation/setup/first_quote.rst:129 +msgid ":doc:`terms_conditions`" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:3 +msgid "How to display optional products on a quotation?" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:8 +msgid "" +"The use of suggested products is a marketing strategy that attempts to " +"increase the amount a customer spends once they begin the buying process. " +"For instance, a customer purchasing a cell phone could be shown accessories " +"like a protective case, a screen cover, and headset. In Odoo, a customer can" +" be presented with additional products that are relevant to their chosen " +"purchase in one of several locations." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:18 +msgid "" +"Suggested products can be added to quotations directly, or to the ecommerce " +"platform via each product form. In order to use suggested products, you will" +" need to have the **Ecommerce** app installed:" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:23 +msgid "Quotations" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:25 +msgid "" +"To add suggested products to quotations, you must first enable online " +"quotations in the Sales app from :menuselection:`Configuration --> " +"Settings`. Doing so will prompt you to install the Website app if you " +"haven't already." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:32 +msgid "" +"You will then be able to add suggested products to your individual " +"quotations and quotation templates under the **Suggested Products** tab of a" +" quotation." +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:39 +msgid "Website Sales" +msgstr "" + +#: ../../sales/quotation/setup/optional.rst:41 +msgid "" +"You can add suggested products to a product on its product form, under the " +"Website heading in the **Sales** tab. **Suggested products** will appear on " +"the *product* page, and **Accessory Products** will appear on the *cart* " +"page prior to checkout." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:3 +msgid "How to link terms and conditions to a quotation?" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:8 +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 so customer can read " +"all those terms before committing to anything." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:13 +msgid "" +"Thanks to Odoo you can easily include your default terms and conditions on " +"every quotation, sales order and invoice." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:16 +msgid "" +"Let's take the following example: Your company sells water bottles to " +"restaurants and you would like to add the following standard terms and " +"conditions on all your quotations:" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:20 +msgid "" +"*Safe storage of the products of MyCompany is necessary in order to ensure " +"their quality, MyCompany will not be held accountable in case of unsafe " +"storage of the products.*" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:25 +msgid "General terms and conditions" +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:27 +msgid "" +"General terms and conditions can be specified in the Sales settings. They " +"will then automatically appear on every sales document from the quotation to" +" the invoice." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:31 +msgid "" +"To specify your Terms and Conditions go into : :menuselection:`Sales --> " +"Configuration --> Settings --> Default Terms and Conditions`." +msgstr "" + +#: ../../sales/quotation/setup/terms_conditions.rst:36 +msgid "" +"After saving, your terms and conditions will appear on your new quotations, " +"sales orders and invoices (in the system but also on your printed " +"documents)." +msgstr "" + +#: ../../sales/sale_ebay.rst:3 +msgid "eBay" +msgstr "" diff --git a/locale/tr/LC_MESSAGES/website.po b/locale/tr/LC_MESSAGES/website.po new file mode 100644 index 000000000..cd6813831 --- /dev/null +++ b/locale/tr/LC_MESSAGES/website.po @@ -0,0 +1,1383 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo Business package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo Business 10.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Language-Team: Turkish (https://www.transifex.com/odoo/teams/41243/tr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: tr\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#: ../../website.rst:5 +msgid "Website" +msgstr "" + +#: ../../website/optimize.rst:3 +msgid "Optimize" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:3 +msgid "How to track your website's traffic in Google Analytics" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:5 +msgid "To follow your website's traffic with Google Analytics:" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:7 +msgid "" +"`Create a Google Analytics account <https://www.google.com/analytics/>`__ if" +" you don't have any." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:10 +msgid "" +"Go through the creation form and accept the conditions to get the tracking " +"ID." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:15 +msgid "Copy the tracking ID to insert it in Odoo." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:20 +msgid "" +"Go to the *Configuration* menu of your Odoo's Website app. In the settings, " +"turn on Google Analytics and paste the tracking ID. Then save the page." +msgstr "" + +#: ../../website/optimize/google_analytics.rst:27 +msgid "" +"To make your first steps in Google Analytics, refer to `Google " +"Documentation. " +"<https://support.google.com/analytics/answer/1008015?hl=en/>`__" +msgstr "" + +#: ../../website/optimize/google_analytics.rst:31 +msgid ":doc:`google_analytics_dashboard`" +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:3 +msgid "How to track your website's traffic from your Odoo Dashboard" +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:5 +msgid "" +"You can follow your traffic's statistics straight from your Odoo Website " +"Dashboard thanks to Google Analytics." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:8 +msgid "" +"A preliminary step is creating a Google Analytics account and entering the " +"tracking ID in your Website's settings (see :doc:`google_analytics`)." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:11 +msgid "" +"Go to `Google APIs platform <https://console.developers.google.com>`__ to " +"generate Analytics API credentials. Log in with your Google account." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:14 +msgid "Select Analytics API." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:19 +msgid "" +"Create a new project and give it a name (e.g. Google Analytics in Odoo)." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:24 +msgid "Enable the API." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:29 +msgid "" +"Create credentials to use in Odoo. Select *Web browser (Javascript)* as " +"calling source and *User data* as kind of data." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:38 +msgid "" +"Then enter the name of the application (e.g. Odoo) and the allowed pages on " +"which you will be redirected. The *Authorized JavaScript origin* is your " +"Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance " +"URL followed by /google_account/authentication." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:47 +msgid "" +"Go through the Consent Screen step by entering a product name (e.g. Google " +"Analytics in Odoo). Feel free to check the customizations options but this " +"is not mandatory. The Consent Screen will only show up when you enter the " +"Client ID in Odoo for the first time." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:52 +msgid "" +"Finally you are provided with your Client ID. Copy and paste it in Odoo." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:57 +msgid "" +"Open your Website Dashboard in Odoo and link your Analytics account. to past" +" your Client ID." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:63 +msgid "As a last step, authorize Odoo to access Google API." +msgstr "" + +#: ../../website/optimize/seo.rst:3 +msgid "How to do Search Engine Optimisation in Odoo" +msgstr "" + +#: ../../website/optimize/seo.rst:6 +msgid "How is SEO handled in Odoo?" +msgstr "" + +#: ../../website/optimize/seo.rst:8 +msgid "" +"Search Engine Optimization (SEO) is a set of good practices to optimize your" +" website so that you get a better ranking in search engines like Google. In " +"short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../website/optimize/seo.rst:12 +msgid "" +"Some examples of SEO rules: your web pages should load faster, your page " +"should have one and only one title ``<h1>``, your website should have a " +"``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../website/optimize/seo.rst:16 +msgid "" +"The Odoo Website Builder is probably the most SEO-ready CMS out there. We " +"consider SEO a top priority. To guarantee Odoo Website and Odoo eCommerce " +"users have a great SEO, Odoo abstracts all the technical complexities of SEO" +" and handles everything for you, in the best possible way." +msgstr "" + +#: ../../website/optimize/seo.rst:23 +msgid "Page speed" +msgstr "" + +#: ../../website/optimize/seo.rst:26 +msgid "Introduction" +msgstr "" + +#: ../../website/optimize/seo.rst:28 +msgid "" +"The time to load a page is an important criteria for Google. A faster " +"website not only improves your visitor's experience, but Google gives you a " +"better page ranking if your page loads faster than your competitors. Some " +"studies have shown that, if you divide the time to load your pages by two " +"(e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also " +"divided by two. (25% to 12.5%). One extra second to load a page could `cost " +"$1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-" +"could-cost-amazon-16-billion-sales>`__." +msgstr "" + +#: ../../website/optimize/seo.rst:40 +msgid "" +"Fortunately, Odoo does all the magic for you. Below, you will find the " +"tricks Odoo uses to speed up your page loading time. You can compare how " +"your website ranks using these two tools:" +msgstr "" + +#: ../../website/optimize/seo.rst:44 +msgid "" +"`Google Page Speed " +"<https://developers.google.com/speed/pagespeed/insights/>`__" +msgstr "" + +#: ../../website/optimize/seo.rst:46 +msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" +msgstr "" + +#: ../../website/optimize/seo.rst:49 +msgid "Static resources: CSS" +msgstr "" + +#: ../../website/optimize/seo.rst:51 +msgid "" +"All CSS files are pre-processed, concatenated, minified, compressed and " +"cached (server side and browser side). The result:" +msgstr "" + +#: ../../website/optimize/seo.rst:54 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../website/optimize/seo.rst:56 +msgid "" +"this CSS file is shared and cached amongst pages, so that when the visitor " +"clicks on another page, the browser doesn't have to even load a single CSS " +"resource." +msgstr "" + +#: ../../website/optimize/seo.rst:60 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../website/optimize/seo.rst:62 +msgid "" +"**Pre-processed:** The CSS framework used by Odoo 9 is bootstrap 3. Although" +" a theme might use another framework, most of `Odoo themes " +"<https://www.odoo.com/apps/themes>`__ extend and customize bootstrap " +"directly. Since Odoo supports Less and Sass, so you can modify CSS rules, " +"instead of overwriting them through extra CSS lines, resulting in a smaller " +"file." +msgstr "" + +#: ../../website/optimize/seo.rst:70 +msgid "**Both files in the <head>**" +msgstr "" + +#: ../../website/optimize/seo.rst:70 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../website/optimize/seo.rst:72 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:72 ../../website/optimize/seo.rst:73 +#: ../../website/optimize/seo.rst:79 ../../website/optimize/seo.rst:121 +msgid ".text-muted {" +msgstr "" + +#: ../../website/optimize/seo.rst:73 ../../website/optimize/seo.rst:80 +#: ../../website/optimize/seo.rst:122 +msgid "color: #666;" +msgstr "" + +#: ../../website/optimize/seo.rst:74 +msgid "color: #777;" +msgstr "" + +#: ../../website/optimize/seo.rst:74 +msgid "background: yellow" +msgstr "" + +#: ../../website/optimize/seo.rst:75 +msgid "background: yellow;" +msgstr "" + +#: ../../website/optimize/seo.rst:75 ../../website/optimize/seo.rst:76 +#: ../../website/optimize/seo.rst:81 ../../website/optimize/seo.rst:123 +msgid "}" +msgstr "" + +#: ../../website/optimize/seo.rst:78 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:84 +msgid "" +"**Concatenated:** every module or library you might use in Odoo has its own " +"set of CSS, Less or Sass files (eCommerce, blog, theme, etc.) Having several" +" CSS files is great for the modularity, but not good for the performance " +"because most browsers can only perform 6 requests in parallel resulting in " +"lots of files that are loaded in series. The latency time to transfer a file" +" is usually much longer than the actual data transfer time, for small files " +"like .JS and .CSS. Thus, the time to load CSS resources depends more on the " +"number of requests to be done than the actual file size." +msgstr "" + +#: ../../website/optimize/seo.rst:94 +msgid "" +"To address this issue, all CSS / Less / Sass files are concatenated into a " +"single .CSS file to send to the browser. So a visitor has **only one .CSS " +"file to load** per page, which is particularly efficient. As the CSS is " +"shared amongst all pages, when the visitor clicks on another page, the " +"browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../website/optimize/seo.rst:100 +msgid "" +"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. " +"By doing this, additional page views from the same visitor will not have to " +"load CSS files at all. But some modules might include huge CSS/Javascript " +"resources that you do not want to prefetch at the first page because they " +"are too big. In this case, Odoo splits this resource into a second bundle " +"that is loaded only when the page using it is requested. An example of this " +"is the backend that is only loaded when the visitor logs in and accesses the" +" backend (/web)." +msgstr "" + +#: ../../website/optimize/seo.rst:110 +msgid "" +"If the CSS file is very big, Odoo will split it into two smaller files to " +"avoid the 4095 selectors limit per sheet of Internet Explorer 8. But most " +"themes fit below this limit." +msgstr "" + +#: ../../website/optimize/seo.rst:114 +msgid "" +"**Minified:** After being pre-processed and concatenated, the resulting CSS " +"is minified to reduce its size." +msgstr "" + +#: ../../website/optimize/seo.rst:118 +msgid "**Before minification**" +msgstr "" + +#: ../../website/optimize/seo.rst:118 +msgid "**After minification**" +msgstr "" + +#: ../../website/optimize/seo.rst:120 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../website/optimize/seo.rst:120 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../website/optimize/seo.rst:126 +msgid "" +"The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../website/optimize/seo.rst:129 +msgid "" +"Then, a cached version is stored on the server side (so we do not have to " +"pre-process, concatenate, minify at every request) and the browser side (so " +"the same visitor will load the CSS only once for all pages he will visit)." +msgstr "" + +#: ../../website/optimize/seo.rst:135 +msgid "" +"If you are in debug mode, the CSS resources are neither concatenated nor " +"minified. That way, it's easier to debug (but it's much slower)" +msgstr "" + +#: ../../website/optimize/seo.rst:140 +msgid "Static resources: Javascript" +msgstr "" + +#: ../../website/optimize/seo.rst:142 +msgid "" +"As with CSS resources, Javascript resources are also concatenated, minified," +" compressed and cached (server side and browser side)." +msgstr "" + +#: ../../website/optimize/seo.rst:145 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../website/optimize/seo.rst:147 +msgid "" +"One for all pages of the website (including code for parallax effects, form " +"validation, …)" +msgstr "" + +#: ../../website/optimize/seo.rst:150 +msgid "" +"One for common Javascript code shared among frontend and backend (bootstrap)" +msgstr "" + +#: ../../website/optimize/seo.rst:153 +msgid "" +"One for backend specific Javascript code (Odoo Web Client interface for your" +" employees using Odoo)" +msgstr "" + +#: ../../website/optimize/seo.rst:156 +msgid "" +"Most visitors to your website will only need the first two bundles, " +"resulting in a maximum of two Javascript files to load to render one page. " +"As these files are shared across all pages, further clicks by the same " +"visitor will not load any other Javascript resource." +msgstr "" + +#: ../../website/optimize/seo.rst:162 +msgid "" +"If you work in debug mode, the CSS and javascript are neither concatenated, " +"nor minified. Thus, it's much slower. But it allows you to easily debug with" +" the Chrome debugger as CSS and Javascript resources are not transformed " +"from their original versions." +msgstr "" + +#: ../../website/optimize/seo.rst:168 +msgid "Images" +msgstr "" + +#: ../../website/optimize/seo.rst:170 +msgid "" +"When you upload new images using the website builder, Odoo automatically " +"compresses them to reduce their sizes. (lossless compression for .PNG and " +".GIF and lossy compression for .JPG)" +msgstr "" + +#: ../../website/optimize/seo.rst:174 +msgid "" +"From the upload button, you have the option to keep the original image " +"unmodified if you prefer to optimize the quality of the image rather than " +"performance." +msgstr "" + +#: ../../website/optimize/seo.rst:182 +msgid "" +"Odoo compresses images when they are uploaded to your website, not when " +"requested by the visitor. Thus, it's possible that, if you use a third-party" +" theme, it will provide images that are not compressed efficiently. But all " +"images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../website/optimize/seo.rst:188 +msgid "" +"When you click on an image, Odoo shows you the Alt and title attributes of " +"the ``<img>`` tag. You can click on it to set your own title and Alt " +"attributes for the image." +msgstr "" + +#: ../../website/optimize/seo.rst:195 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../website/optimize/seo.rst:200 +msgid "" +"Odoo's pictograms are implemented using a font (`Font Awesome " +"<https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes)." +" Thus, you can use as many pictograms as you want in your page, they will " +"not result in extra requests to load the page." +msgstr "" + +#: ../../website/optimize/seo.rst:209 +msgid "CDN" +msgstr "" + +#: ../../website/optimize/seo.rst:211 +msgid "" +"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, " +"images) are loaded from a Content Delivery Network. Using a Content Delivery" +" Network has three advantages:" +msgstr "" + +#: ../../website/optimize/seo.rst:215 +msgid "" +"Load resources from a nearby server (most CDN have servers in main countries" +" around the globe)" +msgstr "" + +#: ../../website/optimize/seo.rst:218 +msgid "" +"Cache resources efficiently (no computation resources usage on your own " +"server)" +msgstr "" + +#: ../../website/optimize/seo.rst:221 +msgid "" +"Split the resource loading on different services allowing to load more " +"resources in parallel (since the Chrome limit of 6 parallel requests is by " +"domain)" +msgstr "" + +#: ../../website/optimize/seo.rst:225 +msgid "" +"You can configure your CDN options from the **Website Admin** app, using the" +" Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../website/optimize/seo.rst:232 +msgid "HTML Pages" +msgstr "" + +#: ../../website/optimize/seo.rst:234 +msgid "" +"Odoo allows to minify HTML pages, from the **Website Admin** app, using the " +":menuselection:`Configuration` menu. This will automatically remove extra " +"space and tabs in your HTML code, reduce some tags code, etc." +msgstr "" + +#: ../../website/optimize/seo.rst:241 +msgid "" +"On top of that, the HTML pages can be compressed, but this is usually " +"handled by your web server (NGINX or Apache)." +msgstr "" + +#: ../../website/optimize/seo.rst:244 +msgid "" +"The Odoo Website builder has been optimized to guarantee clean and short " +"HTML code. Building blocks have been developed to produce clean HTML code, " +"usually using bootstrap and the HTML editor." +msgstr "" + +#: ../../website/optimize/seo.rst:248 +msgid "" +"As an example, if you use the color picker to change the color of a " +"paragraph to the primary color of your website, Odoo will produce the " +"following code:" +msgstr "" + +#: ../../website/optimize/seo.rst:252 +msgid "``<p class=\"text-primary\">My Text</p>``" +msgstr "" + +#: ../../website/optimize/seo.rst:254 +msgid "" +"Whereas most HTML editors (such as CKEditor) will produce the following " +"code:" +msgstr "" + +#: ../../website/optimize/seo.rst:257 +msgid "``<p style=\"color: #AB0201\">My Text</p>``" +msgstr "" + +#: ../../website/optimize/seo.rst:260 +msgid "Responsive Design" +msgstr "" + +#: ../../website/optimize/seo.rst:262 +msgid "" +"As of 2015, websites that are not mobile-friendly are negatively impacted in" +" Google Page ranking. All Odoo themes rely on Bootstrap 3 to render " +"efficiently according to the device: desktop, tablet or mobile phone." +msgstr "" + +#: ../../website/optimize/seo.rst:270 +msgid "" +"As all Odoo modules share the same technology, absolutely all pages in your " +"website are mobile friendly. (as opposed to traditional CMS which have " +"mobile friendly themes, but some specific modules or pages are not designed " +"to be mobile friendly as they all have their own CSS frameworks)" +msgstr "" + +#: ../../website/optimize/seo.rst:277 +msgid "Browser caching" +msgstr "" + +#: ../../website/optimize/seo.rst:279 +msgid "" +"Javascript, images and CSS resources have an URL that changes dynamically " +"when their content change. As an example, all CSS files are loaded through " +"this URL: " +"`http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css " +"<http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. " +"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of " +"your website." +msgstr "" + +#: ../../website/optimize/seo.rst:286 +msgid "" +"This allows Odoo to set a very long cache delay (XXX) on these resources: " +"XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../website/optimize/seo.rst:294 +msgid "Scalability" +msgstr "" + +#: ../../website/optimize/seo.rst:296 +msgid "" +"In addition to being fast, Odoo is also more scalable than traditional CMS' " +"and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link " +"provides an analysis of the major open source CMS and eCommerce compared to " +"Odoo when it comes to high query volumes." +msgstr "" + +#: ../../website/optimize/seo.rst:301 +msgid "" +"`*https://www.odoo.com/slides/slide/197* <https://www.odoo.com/slides/slide" +"/odoo-cms-performance-comparison-and-optimisation-197>`__" +msgstr "" + +#: ../../website/optimize/seo.rst:303 +msgid "" +"Here is the slide that summarizes the scalability of Odoo eCommerce and Odoo" +" CMS. (based on Odoo version 8, Odoo 9 is even faster)" +msgstr "" + +#: ../../website/optimize/seo.rst:310 +msgid "URLs handling" +msgstr "" + +#: ../../website/optimize/seo.rst:313 +msgid "URLs Structure" +msgstr "" + +#: ../../website/optimize/seo.rst:315 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../website/optimize/seo.rst:317 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../website/optimize/seo.rst:319 +msgid "With the following components:" +msgstr "" + +#: ../../website/optimize/seo.rst:321 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../website/optimize/seo.rst:323 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../website/optimize/seo.rst:325 +msgid "" +"**/fr\\_FR** = the language of the page. This part of the URL is removed if " +"the visitor browses the main language of the website (english by default, " +"but you can set another language as the main one). Thus, the English version" +" of this page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../website/optimize/seo.rst:331 +msgid "" +"**/shop/product** = every module defines its own namespace (/shop is for the" +" catalog of the eCommerce module, /shop/product is for a product page). This" +" name can not be customized to avoid conflicts in different URLs." +msgstr "" + +#: ../../website/optimize/seo.rst:336 +msgid "" +"**my-great-product** = by default, this is the slugified title of the " +"product this page refers to. But you can customize it for SEO purposes. A " +"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending " +"on the namespace, this could be different objects (blog post, page title, " +"forum post, forum comment, product category, etc)" +msgstr "" + +#: ../../website/optimize/seo.rst:343 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../website/optimize/seo.rst:345 +msgid "" +"Note that any dynamic component of an URL can be reduced to its ID. As an " +"example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../website/optimize/seo.rst:348 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../website/optimize/seo.rst:350 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../website/optimize/seo.rst:352 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../website/optimize/seo.rst:355 +msgid "" +"This could be useful to easily get shorter version of an URL and handle " +"efficiently 301 redirects when the name of your product changes over time." +msgstr "" + +#: ../../website/optimize/seo.rst:359 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../website/optimize/seo.rst:362 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../website/optimize/seo.rst:364 +msgid "In the above example:" +msgstr "" + +#: ../../website/optimize/seo.rst:366 +msgid "Company News: is the title of the blog" +msgstr "" + +#: ../../website/optimize/seo.rst:368 +msgid "The Odoo Story: is the title of a specific blog post" +msgstr "" + +#: ../../website/optimize/seo.rst:370 +msgid "" +"When an Odoo page has a pager, the page number is set directly in the URL " +"(does not have a GET argument). This allows every page to be indexed by " +"search engines. Example:" +msgstr "" + +#: ../../website/optimize/seo.rst:374 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../website/optimize/seo.rst:377 +msgid "" +"Having the language code as fr\\_FR is not perfect in terms of SEO. Although" +" most search engines treat now \"\\_\" as a word separator, it has not " +"always been the case. We plan to improve that for Odoo 10." +msgstr "" + +#: ../../website/optimize/seo.rst:382 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../website/optimize/seo.rst:384 +msgid "" +"When the URL of a page changes (e.g. a more SEO friendly version of your " +"product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../website/optimize/seo.rst:387 +msgid "Odoo will automatically update all its links to the new URL" +msgstr "" + +#: ../../website/optimize/seo.rst:389 +msgid "" +"If external websites still points to the old URL, a 301 redirect will be " +"done to route visitors to the new website" +msgstr "" + +#: ../../website/optimize/seo.rst:392 +msgid "As an example, this URL:" +msgstr "" + +#: ../../website/optimize/seo.rst:394 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:396 +msgid "Will automatically redirect to :" +msgstr "" + +#: ../../website/optimize/seo.rst:398 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:400 +msgid "" +"In short, just change the title of a blog post or the name of a product, and" +" the changes will apply automatically everywhere in your website. The old " +"link still works for links coming from external website. (with a 301 " +"redirect to not lose the SEO link juice)" +msgstr "" + +#: ../../website/optimize/seo.rst:406 +msgid "HTTPS" +msgstr "" + +#: ../../website/optimize/seo.rst:408 +msgid "" +"As of August 2014, Google started to add a ranking boost to secure HTTPS/SSL" +" websites. So, by default all Odoo Online instances are fully based on " +"HTTPS. If the visitor accesses your website through a non HTTPS url, it gets" +" a 301 redirect to its HTTPS equivalent." +msgstr "" + +#: ../../website/optimize/seo.rst:414 +msgid "Links: nofollow strategy" +msgstr "" + +#: ../../website/optimize/seo.rst:416 +msgid "" +"Having website that links to your own page plays an important role on how " +"your page ranks in the different search engines. The more your page is " +"linked from external and quality websites, the better is it for your SEO." +msgstr "" + +#: ../../website/optimize/seo.rst:421 +msgid "Odoo follows the following strategies to manage links:" +msgstr "" + +#: ../../website/optimize/seo.rst:423 +msgid "" +"Every link you create manually when creating page in Odoo is \"dofollow\", " +"which means that this link will contribute to the SEO Juice for the linked " +"page." +msgstr "" + +#: ../../website/optimize/seo.rst:427 +msgid "" +"Every link created by a contributor (forum post, blog comment, ...) that " +"links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../website/optimize/seo.rst:430 +msgid "" +"But every link posted by a contributor that links to an external website is " +"\"nofollow\". In that way, you do not run the risk of people posting links " +"on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../website/optimize/seo.rst:435 +msgid "" +"Note that, when using the forum, contributors having a lot of Karma can be " +"trusted. In such case, their links will not have a ``rel=\"nofollow\"`` " +"attribute." +msgstr "" + +#: ../../website/optimize/seo.rst:440 +msgid "Multi-language support" +msgstr "" + +#: ../../website/optimize/seo.rst:443 +msgid "Multi-language URLs" +msgstr "" + +#: ../../website/optimize/seo.rst:445 +msgid "" +"If you run a website in multiple languages, the same content will be " +"available in different URLs, depending on the language used:" +msgstr "" + +#: ../../website/optimize/seo.rst:448 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (English version = " +"default)" +msgstr "" + +#: ../../website/optimize/seo.rst:450 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../website/optimize/seo.rst:452 +msgid "" +"In this example, fr\\_FR is the language of the page. You can even have " +"several variations of the same language: pt\\_BR (Portuguese from Brazil) , " +"pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../website/optimize/seo.rst:457 +msgid "Language annotation" +msgstr "" + +#: ../../website/optimize/seo.rst:459 +msgid "" +"To tell Google that the second URL is the French translation of the first " +"URL, Odoo will add an HTML link element in the header. In the HTML <head> " +"section of the English version, Odoo automatically adds a link element " +"pointing to the other versions of that webpage;" +msgstr "" + +#: ../../website/optimize/seo.rst:464 +msgid "" +"<link rel=\"alternate\" hreflang=\"fr\" " +"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" +msgstr "" + +#: ../../website/optimize/seo.rst:467 +msgid "With this approach:" +msgstr "" + +#: ../../website/optimize/seo.rst:469 +msgid "" +"Google knows the different translated versions of your page and will propose" +" the right one according to the language of the visitor searching on Google" +msgstr "" + +#: ../../website/optimize/seo.rst:473 +msgid "" +"You do not get penalized by Google if your page is not translated yet, since" +" it is not a duplicated content, but a different version of the same " +"content." +msgstr "" + +#: ../../website/optimize/seo.rst:478 +msgid "Language detection" +msgstr "" + +#: ../../website/optimize/seo.rst:480 +msgid "" +"When a visitor lands for the first time at your website (e.g. " +"yourwebsite.com/shop), his may automatically be redirected to a translated " +"version according to his browser language preference: (e.g. " +"yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../website/optimize/seo.rst:485 +msgid "" +"Odoo redirects visitors to their prefered language only the first time " +"visitors land at your website. After that, it keeps a cookie of the current " +"language to avoid any redirection." +msgstr "" + +#: ../../website/optimize/seo.rst:489 +msgid "" +"To force a visitor to stick to the default language, you can use the code of" +" the default language in your link, example: yourwebsite.com/en\\_US/shop. " +"This will always land visitors to the English version of the page, without " +"using the browser language preferences." +msgstr "" + +#: ../../website/optimize/seo.rst:496 +msgid "Meta Tags" +msgstr "" + +#: ../../website/optimize/seo.rst:499 +msgid "Titles, Keywords and Description" +msgstr "" + +#: ../../website/optimize/seo.rst:501 +msgid "" +"Every web page should define the ``<title>``, ``<description>`` and " +"``<keywords>`` meta data. These information elements are used by search " +"engines to rank and categorize your website according to a specific search " +"query. So, it is important to have titles and keywords in line with what " +"people search in Google." +msgstr "" + +#: ../../website/optimize/seo.rst:507 +msgid "" +"In order to write quality meta tags, that will boost traffic to your " +"website, Odoo provides a **Promote** tool, in the top bar of the website " +"builder. This tool will contact Google to give you information about your " +"keywords and do the matching with titles and contents in your page." +msgstr "" + +#: ../../website/optimize/seo.rst:516 +msgid "" +"If your website is in multiple languages, you can use the Promote tool for " +"every language of a single page;" +msgstr "" + +#: ../../website/optimize/seo.rst:519 +msgid "" +"In terms of SEO, content is king. Thus, blogs play an important role in your" +" content strategy. In order to help you optimize all your blog post, Odoo " +"provides a page that allows you to quickly scan the meta tags of all your " +"blog posts." +msgstr "" + +#: ../../website/optimize/seo.rst:528 +msgid "" +"This /blog page renders differently for public visitors that are not logged " +"in as website administrator. They do not get the warnings and keyword " +"information." +msgstr "" + +#: ../../website/optimize/seo.rst:533 +msgid "Sitemap" +msgstr "" + +#: ../../website/optimize/seo.rst:535 +msgid "" +"Odoo will generate a ``/sitemap.xml`` file automatically for you. For " +"performance reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../website/optimize/seo.rst:538 +msgid "" +"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you " +"have a lot of pages, Odoo will automatically create a Sitemap Index file, " +"respecting the `sitemaps.org protocol " +"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 " +"chunks per file." +msgstr "" + +#: ../../website/optimize/seo.rst:544 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../website/optimize/seo.rst:546 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../website/optimize/seo.rst:548 +msgid "" +"``<lastmod>`` : last modification date of the resource, computed " +"automatically based on related object. For a page related to a product, this" +" could be the last modification date of the product or the page" +msgstr "" + +#: ../../website/optimize/seo.rst:553 +msgid "" +"``<priority>`` : modules may implement their own priority algorithm based on" +" their content (example: a forum might assign a priority based on the number" +" of votes on a specific post). The priority of a static page is defined by " +"it's priority field, which is normalized. (16 is the default)" +msgstr "" + +#: ../../website/optimize/seo.rst:560 +msgid "Structured Data Markup" +msgstr "" + +#: ../../website/optimize/seo.rst:562 +msgid "" +"Structured Data Markup is used to generate Rich Snippets in search engine " +"results. It is a way for website owners to send structured data to search " +"engine robots; helping them to understand your content and create well-" +"presented search results." +msgstr "" + +#: ../../website/optimize/seo.rst:567 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../website/optimize/seo.rst:570 +msgid "" +"Odoo implements micro data as defined in the `schema.org " +"<http://schema.org>`__ specification for events, eCommerce products, forum " +"posts and contact addresses. This allows your product pages to be displayed " +"in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../website/optimize/seo.rst:580 +msgid "robots.txt" +msgstr "" + +#: ../../website/optimize/seo.rst:582 +msgid "" +"Odoo automatically creates a ``/robots.txt`` file for your website. Its " +"content is:" +msgstr "" + +#: ../../website/optimize/seo.rst:585 +msgid "User-agent: \\*" +msgstr "" + +#: ../../website/optimize/seo.rst:587 +msgid "Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../website/optimize/seo.rst:590 +msgid "Content is king" +msgstr "" + +#: ../../website/optimize/seo.rst:592 +msgid "" +"When it comes to SEO, content is usually king. Odoo provides several modules" +" to help you build your contents on your website:" +msgstr "" + +#: ../../website/optimize/seo.rst:595 +msgid "" +"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their " +"content is automatically indexed on the web page. Example: " +"`https://www.odoo.com/slides/public-channel-1 <https://www.odoo.com/slides" +"/public-channel-1>`__" +msgstr "" + +#: ../../website/optimize/seo.rst:599 +msgid "" +"**Odoo Forum**: let your community create contents for you. Example: " +"`https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of" +" Odoo.com landing pages)" +msgstr "" + +#: ../../website/optimize/seo.rst:603 +msgid "" +"**Odoo Mailing List Archive**: publish mailing list archives on your " +"website. Example: `https://www.odoo.com/groups/community-59 " +"<https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)" +msgstr "" + +#: ../../website/optimize/seo.rst:608 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../website/optimize/seo.rst:611 +msgid "" +"The 404 page is a regular page, that you can edit like any other page in " +"Odoo. That way, you can build a great 404 page to redirect to the top " +"content of your website." +msgstr "" + +#: ../../website/optimize/seo.rst:616 +msgid "Social Features" +msgstr "" + +#: ../../website/optimize/seo.rst:619 +msgid "Twitter Cards" +msgstr "" + +#: ../../website/optimize/seo.rst:621 +msgid "" +"Odoo does not implement twitter cards yet. It will be done for the next " +"version." +msgstr "" + +#: ../../website/optimize/seo.rst:625 +msgid "Social Network" +msgstr "" + +#: ../../website/optimize/seo.rst:627 +msgid "" +"Odoo allows to link all your social network accounts in your website. All " +"you have to do is to refer all your accounts in the **Settings** menu of the" +" **Website Admin** application." +msgstr "" + +#: ../../website/optimize/seo.rst:632 +msgid "Test Your Website" +msgstr "" + +#: ../../website/optimize/seo.rst:634 +msgid "" +"You can compare how your website rank, in terms of SEO, against Odoo using " +"WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__" +msgstr "" + +#: ../../website/publish.rst:3 +msgid "Publish" +msgstr "" + +#: ../../website/publish/domain_name.rst:3 +msgid "How to use my own domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:5 +msgid "" +"By default, your Odoo Online instance and website have a *.odoo.com* domain " +"name, for both the URL and the emails. But you can change to a custom one " +"(e.g. www.yourcompany.com)." +msgstr "" + +#: ../../website/publish/domain_name.rst:10 +msgid "What is a good domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:11 +msgid "" +"Your website address is as important to your branding as the name of your " +"business or organization, so put some thought into changing it for a proper " +"domain. Here are some tips:" +msgstr "" + +#: ../../website/publish/domain_name.rst:15 +msgid "Simple and obvious" +msgstr "" + +#: ../../website/publish/domain_name.rst:16 +msgid "Easy to remember and spell" +msgstr "" + +#: ../../website/publish/domain_name.rst:17 +msgid "The shorter the better" +msgstr "" + +#: ../../website/publish/domain_name.rst:18 +msgid "Avoid special characters" +msgstr "" + +#: ../../website/publish/domain_name.rst:19 +msgid "Aim for a .com and/or your country extension" +msgstr "" + +#: ../../website/publish/domain_name.rst:21 +msgid "" +"Read more: `How to Choose a Domain Name for Maximum SEO " +"<https://www.searchenginejournal.com/choose-a-domain-name-maximum-" +"seo/158951/>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:24 +msgid "How to buy a domain name" +msgstr "" + +#: ../../website/publish/domain_name.rst:25 +msgid "Buy your domain name at a popular registrar:" +msgstr "" + +#: ../../website/publish/domain_name.rst:27 +msgid "`GoDaddy <https://www.godaddy.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:28 +msgid "`Namecheap <https://www.namecheap.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:29 +msgid "`OVH <https://www.ovh.com>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:31 +msgid "" +"Steps to buy a domain name are pretty much straight forward. In case of " +"issue, check out those easy tutorials:" +msgstr "" + +#: ../../website/publish/domain_name.rst:34 +msgid "`GoDaddy <https://roadtoblogging.com/buy-domain-name-from-godaddy>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:35 +msgid "" +"`Namecheap <https://www.loudtips.com/buy-domain-name-hosting-namecheap//>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:37 +msgid "" +"Feel free to buy an email server to have email addresses using your domain " +"name. However don't buy any extra service to create or host your website. " +"This is Odoo's job!" +msgstr "" + +#: ../../website/publish/domain_name.rst:42 +msgid "How to apply my domain name to my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:43 +msgid "" +"First let's authorize the redirection (yourcompany.com -> " +"yourcompany.odoo.com):" +msgstr "" + +#: ../../website/publish/domain_name.rst:45 +msgid "Open your Odoo.com account from your homepage." +msgstr "" + +#: ../../website/publish/domain_name.rst:50 +msgid "Go to the *Manage Databases* page." +msgstr "" + +#: ../../website/publish/domain_name.rst:55 +msgid "" +"Click on *Domains* to the right of the database you would like to redirect." +msgstr "" + +#: ../../website/publish/domain_name.rst:60 +msgid "" +"A database domain prompt will appear. Enter your custom domain (e.g. " +"www.yourcompany.com)." +msgstr "" + +#: ../../website/publish/domain_name.rst:67 +msgid "" +"We can now apply the redirection from your domain name's manager account:" +msgstr "" + +#: ../../website/publish/domain_name.rst:69 +msgid "Log in to your account and search for the DNS Zones management page." +msgstr "" + +#: ../../website/publish/domain_name.rst:71 +msgid "" +"Create a CNAME record *www.yourdomain.com* pointing to *mywebsite.odoo.com*." +" If you want to use the naked domain (e.g. yourdomain.com), you need to " +"redirect *yourdomain.com* to *www.yourdomain.com*." +msgstr "" + +#: ../../website/publish/domain_name.rst:75 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../website/publish/domain_name.rst:77 +msgid "`GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:78 +msgid "" +"`Namecheap " +"<https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-" +"can-i-set-up-a-cname-record-for-my-domain>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:79 +msgid "" +"`OVH " +"<https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:82 +msgid "How to enable SSL (HTTPS) for my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:84 +msgid "" +"To enable SSL, please use a third-party CDN service provider such as " +"CloudFlare.com." +msgstr "" + +#: ../../website/publish/domain_name.rst:90 +msgid ":doc:`../../discuss/email_servers`" +msgstr "" + +#: ../../website/publish/translate.rst:3 +msgid "How to translate my website" +msgstr "" + +#: ../../website/publish/translate.rst:6 +msgid "Overview" +msgstr "" + +#: ../../website/publish/translate.rst:8 +msgid "" +"In addition to creating great modern websites, Odoo gives you the " +"possibility to translate it in different languages." +msgstr "" + +#: ../../website/publish/translate.rst:12 +msgid "Process" +msgstr "" + +#: ../../website/publish/translate.rst:14 +msgid "" +"Once your website is created, you have the opportunity to translate it in as" +" many different languages as you want." +msgstr "" + +#: ../../website/publish/translate.rst:17 +msgid "" +"There are two ways to translate your website, you can do it manually or " +"automatically with the Gengo App. If you want to do it automatically, go to " +"the **App** module and Install **Automated translations through Gengo Api** " +"and **Website Gengo Translator**. If you want to do it manually, don't " +"install anything, and follow the next step." +msgstr "" + +#: ../../website/publish/translate.rst:23 +msgid "" +"Now go to your website. On the bottom right corner of the page, click on " +"**Add a language**." +msgstr "" + +#: ../../website/publish/translate.rst:29 +msgid "" +"Choose the language in which you want to translate your website and then " +"click on **Load.**" +msgstr "" + +#: ../../website/publish/translate.rst:35 +msgid "" +"You will see that Now, next to English there is also French, which means " +"that the page for the translation has been created. You can also see that " +"some of the text has been translated automatically." +msgstr "" + +#: ../../website/publish/translate.rst:42 +msgid "" +"To translate the content of the website, click on **Translate** (here " +"**Traduire** since we want to translate the website in French)." +msgstr "" + +#: ../../website/publish/translate.rst:45 +msgid "" +"There, if you have installed the Gengo Translator, You will see that next to" +" the **Translate** button you also have a button **Translate " +"automatically**. Once you click on that button, you will be asked some " +"information on your account. If you don't have an account yet, go to " +"`*https://gengo.com/auth/form/login/* " +"<https://gengo.com/auth/form/login/>`__ in order to create one. You need to " +"ask for a public key and a private key." +msgstr "" + +#: ../../website/publish/translate.rst:53 +msgid "" +"The content you wish to translate will then be translated automatically." +msgstr "" + +#: ../../website/publish/translate.rst:58 +msgid "" +"Now you can see that most of the content is highlighted in yellow or in " +"green. The yellow represents the content that you have to translate by " +"yourself. The green represents the content that has already been translated " +"automatically." +msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/accounting.po b/locale/zh_CN/LC_MESSAGES/accounting.po index 5de286264..31977eaaa 100644 --- a/locale/zh_CN/LC_MESSAGES/accounting.po +++ b/locale/zh_CN/LC_MESSAGES/accounting.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: 苏州远鼎 <tiexinliu@126.com>, 2017\n" +"Last-Translator: Yaorong Li <55yaorong.li@gmail.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -92,7 +92,6 @@ msgstr "" #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:23 #: ../../accounting/receivables/getting_paid/automated_followups.rst:31 msgid "Configuration" msgstr "配置" @@ -862,7 +861,6 @@ msgstr "如果您选择一批存款, Odoo将自动填充所匹配的支票存款 #: ../../accounting/bank/misc/batch.rst:124 #: ../../accounting/payables/pay/sepa.rst:113 -#: ../../accounting/receivables/customer_payments/paypal.rst:134 msgid "Troubleshooting" msgstr "排查" @@ -1600,6 +1598,11 @@ msgid "" "configured as well as the currency of the journal" msgstr "在选项卡日记帐分录, 默认的借记卡和信用卡帐号可同时配置为期刊的货币" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "类型" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1618,44 +1621,80 @@ msgstr "" msgid "Select 'General' for miscellaneous operations journals." msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "公司" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Company related to this journal" msgstr "此日记账相关的公司" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "简码" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The journal entries of this journal will be named using this prefix." msgstr "这个日记账中的日记账分录会被用这个前缀命名" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Refund Sequence" +msgstr "专用退款序列" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if you don't want to share the same sequence for invoices and" " refunds made from this journal" msgstr "如果你不想在此日记账中共用发票和退款的序列号, 请选择这个方框." +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "分录序列" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the journal " "entries of this journal." msgstr "这个字段包含和这个日记中日记账分录数量相关的信息" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Refund Entry Sequence" +msgstr "退款分录序列" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field contains the information related to the numbering of the refund " "entries of this journal." msgstr "这个字段包含和这个日记账的退款分录的数量相关的信息" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "默认借方科目" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for debit amount" msgstr "它将作为一个默认借方科目" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "默认贷方科目" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "It acts as a default account for credit amount" msgstr "它将充当贷方金额的默认科目" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Currency" +msgstr "货币" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "The currency used to enter statement" msgstr "货币用来输入状态" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Debit Methods" +msgstr "借记方式" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for collecting money. Odoo modules offer various payments " @@ -1663,6 +1702,10 @@ msgid "" "order to manage payments outside of the software." msgstr "收钱的付款形式。Odoo模块提供各种各样的付款处理工具，但是你也可以一直在系统外用手工的付款方法管理付款" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Payment Methods" +msgstr "付款方式" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Means of payment for sending money. Odoo modules offer various payments " @@ -1670,53 +1713,94 @@ msgid "" "order to manage payments outside of the software." msgstr "付钱的付款形式。Odoo模块提供各种各样的付款处理工具，但是你也可以一直在系统外用手工的付款方法管理付款" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "分组发票明细行" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "If this box is checked, the system will try to group the accounting lines " "when generating them from invoices." msgstr "如果这个框已被检查,系统会集成行来生成发票。" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "利润科目" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a profit when the ending balance of a cash register differs" " from what the system computes" msgstr "当现金出纳机的关账余额与系统计算的有差异时，用于登记利润" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "损失科目" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Used to register a loss when the ending balance of a cash register differs " "from what the system computes" msgstr "现金登记的期末余额与系统计算的有差异时候用来登记损失" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Show journal on dashboard" +msgstr "在仪表板显示日记账" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Whether this journal should be displayed on the dashboard or not" msgstr "不管这个日记账是否显示在仪表板" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Technical feature used to know whether check printing was enabled as payment" " method." msgstr "从技术特征可以知道，是否可将支票作为付款方式。" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "支票序列" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Checks numbering sequence." msgstr "支票编号序列。" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "手动编号" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 #: ../../accounting/payables/pay/check.rst:0 msgid "Check this option if your pre-printed checks are not numbered." msgstr "勾选此选项如果你的预先印制支票是没有编号的。" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "下一个支票号码" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Sequence number of the next printed check." msgstr "下个打印支票的序列编号" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Active in Point of Sale" +msgstr "在POS有效" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "Check this box if this journal define a payment method that can be used in a" " point of sale." msgstr "如果这个日记账中定义了能够在‘POS’用的付款方式就勾选这个选项" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "授权差异的总金额" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "" "This field depicts the maximum difference allowed between the ending balance" @@ -1924,6 +2008,10 @@ msgstr "如果您手动创建的资产, 你仍然需要建立供应商账单这 msgid "Explanation of the fields:" msgstr "字段的说明 :" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Status" +msgstr "状态" + #: ../../accounting/others/adviser/assets.rst:0 msgid "When an asset is created, the status is 'Draft'." msgstr "当资产被创建，则状态为“草稿”。" @@ -1940,22 +2028,42 @@ msgid "" "line of depreciation is posted, the asset automatically goes in that status." msgstr "当折旧结束时, 可以手动关闭资产。如果发布的最后一行折旧,资产自动进入那个状态。" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category" +msgstr "类别" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Category of asset" msgstr "资产类别" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "日期 " + #: ../../accounting/others/adviser/assets.rst:0 msgid "Date of asset" msgstr "资产日期" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "毛值" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Gross value of asset" msgstr "资产的毛值" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "剩余价值" + #: ../../accounting/others/adviser/assets.rst:0 msgid "It is the amount you plan to have that you cannot depreciate." msgstr "计划的量, 不能减少。" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "计算方法" + #: ../../accounting/others/adviser/assets.rst:0 msgid "Choose the method to use to compute the amount of depreciation lines." msgstr "选择折旧的计算方式." @@ -1970,6 +2078,10 @@ msgid "" "* Degressive: Calculated on basis of: Residual Value * Degressive Factor" msgstr "* 递减: 计算基于: 残值 * 递减因子" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Time Method Based On" +msgstr "时间方式基于" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Choose the method to use to compute the dates and number of depreciation " @@ -1988,6 +2100,10 @@ msgid "" "depreciations won't go beyond." msgstr "*结束日期:选择2个折旧的间隔和折旧的最后期限." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Prorata Temporis" +msgstr "即时按比例分配" + #: ../../accounting/others/adviser/assets.rst:0 msgid "" "Indicates that the first depreciation entry for this asset have to be done " @@ -1995,10 +2111,18 @@ msgid "" "year" msgstr "表明第一次折旧从购买日期开始,而不是从年度第一个月开始." +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "折旧数量" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The number of depreciations needed to depreciate your asset" msgstr "被折旧资产的折旧数量" +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "在一个期间内的月数" + #: ../../accounting/others/adviser/assets.rst:0 msgid "The amount of time between two depreciations, in months" msgstr "折旧期间，以月计算" @@ -3578,14 +3702,26 @@ msgid "" " entries." msgstr "科目类型用于信息目的，用于生成合乎各国财税规范的报告，以及设置会计年度关闭的规则，并生成期初分录" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Tags" +msgstr "摘要" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Optional tags you may want to assign for custom reporting" msgstr "你可能想赋予给定义报告的选项标签" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Account Currency" +msgstr "科目币种" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Forces all moves for this account to have this account currency." msgstr "强制这个科目所有的凭证拥有这个科目的币种" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Type" +msgstr "内部类型" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "The 'Internal Type' is used for features available on different types of " @@ -3593,6 +3729,10 @@ msgid "" " for vendor/customer accounts." msgstr "'内部类型'用于不同类型的科目: 流动性用于现金或银行账户, 应收/应付用于供应商/客户账户。" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Allow Reconciliation" +msgstr "允许调节" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "" "Check this box if this account allows invoices & payments matching of " @@ -7804,21 +7944,37 @@ msgstr "" msgid "Explanation of the fields of the payment screen:" msgstr "付款界面字段的解释 :" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Has Invoices" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Technical field used for usability purposes" msgstr "技术字段可使用" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to hide the payment method if the selected journal has " "only one available which is 'manual'" msgstr "当所选的账设置为“手动”, 支付方式的字段被隐藏." +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "代码" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "Technical field used to adapt the interface to the payment type selected." msgstr "技术字段根据付款方式来调整。" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "支票号码" + #: ../../accounting/payables/pay/check.rst:0 msgid "" "The selected journal is configured to print check numbers. If your pre-" @@ -10111,8 +10267,8 @@ msgstr ":doc:`recording` " #: ../../accounting/receivables/customer_payments/credit_cards.rst:167 #: ../../accounting/receivables/customer_payments/recording.rst:128 -msgid ":doc:`paypal`" -msgstr ":doc:`paypal` " +msgid ":doc:`../../bank/feeds/paypal`" +msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:169 #: ../../accounting/receivables/customer_payments/recording.rst:130 @@ -10350,222 +10506,6 @@ msgid "" "Reporting (check the KPI average debtors days)." msgstr "你可以从报告下的执行概要得到你公司的DSO (检查KPI平均债务人天数)" -#: ../../accounting/receivables/customer_payments/paypal.rst:3 -msgid "How to accept paypal payments on invoices?" -msgstr "如何接受PayPal付款？" - -#: ../../accounting/receivables/customer_payments/paypal.rst:5 -msgid "" -"The \"Paypal Payment Acquirer\" module allows you to accept payments via " -"paypal, for your sales orders, invoices, or online orders. As paypal accepts" -" payments through credit cards (VISA, Mastercard, …), you will be able to " -"process most payment methods." -msgstr "" -" **PayPal 付款收单方** " -"模块允许你通过paypal为销售订单，发票，以及在线订单接受付款。因为paypal接受通过信用卡(VISA，万事达)付款，你就能处理大多数的付款方式。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:10 -msgid "Paypal support two modes:" -msgstr "Paypal 支持两种模式 :" - -#: ../../accounting/receivables/customer_payments/paypal.rst:12 -msgid "" -"Paypal Merchant Account: the user is redirected to paypal to do the payment " -"(either with a credit card or a paypal account)" -msgstr "Paypal Merchant 帐户：用户定义paypal用于付款(通过信用卡或paypal帐户)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:15 -msgid "" -"PayPal PayFlow Pro (S2S, Server 2 Server): the user is not redirected to " -"paypal and the payment can be done in the background. This method is mostly " -"used for subscription businesses where you need to charge your customers " -"periodically." -msgstr "" -"PayPal PayFlow Pro(S2S，Server 2服务器)：用户不重新定义用paypal " -"支付并且付款可在后台完成。这种方法主要用于订阅业务，需要定期向客户收取费用。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:20 -msgid "As of today, Odoo only support the normal Paypal Merchant Account." -msgstr "截至今天，Odoo只支持常规的Paypal Merchant 帐户。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:26 -msgid "Install the \"PayPal Payment Acquirer\" module" -msgstr "安装 \" PayPal 付款收单方\" 模块" - -#: ../../accounting/receivables/customer_payments/paypal.rst:28 -msgid "Start by installing the **PayPal Payment Acquirer** module." -msgstr "从安装 **PayPal 付款收单方** 模块开始。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:30 -msgid "" -"Once the module is installed, you should see a new payment acquirer in the " -"Setting application, menu \"Payment Acquirers\"." -msgstr "一旦模块被安装了, 你应该看到设置应用里面的新付款托收，菜单\"付款收单方\" :" - -#: ../../accounting/receivables/customer_payments/paypal.rst:36 -msgid "" -"By default, Paypal is configured to work in a test environment, out-of-the-" -"box. It means you can already test the full order to payment flow with the " -"paypal sandbox, without having to configure the next steps." -msgstr "默认情况下，Paypal在测试环境中工作。这意味着你可以用Paypal付款流程的全阶段测试，而无需配置。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:42 -msgid "Creating and configuring a PayPal merchant account" -msgstr "创建和配置一个PayPal merchant帐户" - -#: ../../accounting/receivables/customer_payments/paypal.rst:45 -msgid "Create a basic Paypal account" -msgstr "创建一个基本的 Paypal 账户" - -#: ../../accounting/receivables/customer_payments/paypal.rst:47 -msgid "Existing or newly created Personal Paypal account can be used." -msgstr "现有的或新创建的个人Paypal帐户可使用." - -#: ../../accounting/receivables/customer_payments/paypal.rst:49 -msgid "Or upgrade your account to Business account (merchant) if needed" -msgstr "或将账户升级到商业帐户(商人)，如果需要的话" - -#: ../../accounting/receivables/customer_payments/paypal.rst:55 -msgid "Paypal Account Summary page" -msgstr "Paypal 账户概览页面" - -#: ../../accounting/receivables/customer_payments/paypal.rst:58 -msgid "Paypal Configuration" -msgstr "Paypal 配置" - -#: ../../accounting/receivables/customer_payments/paypal.rst:60 -msgid "" -"Access \"Seller preferences\" menu from `PayPal website " -"<https://www.paypal.com/myaccount/home>`__" -msgstr "" -"进入 \"Seller preferences\" 菜单, 从 `PayPal " -"网站<https://www.paypal.com/myaccount/home>`__" - -#: ../../accounting/receivables/customer_payments/paypal.rst:66 -msgid "" -"Access \"Website preferences\" and configure Auto Return (Payment Data " -"Transfer must be left to Off)" -msgstr "访问“Website preferences”和配置自动返回(支付数据传输必须关闭)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:69 -msgid "**Database name**: yourcompany" -msgstr " **数据库名称**: 你的公司" - -#: ../../accounting/receivables/customer_payments/paypal.rst:70 -#: ../../accounting/receivables/customer_payments/paypal.rst:88 -msgid "**Website URL**: https://yourcompany.odoo.com/" -msgstr " **网址**: https: //yourcompany.odoo.com/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:71 -msgid "**Return URL**: https://yourcompany.odoo.com/shop/confirmation" -msgstr " **返回网址**: https: //yourcompany.odoo.com/shop/confirmation" - -#: ../../accounting/receivables/customer_payments/paypal.rst:76 -msgid "These settings will redirect your buyer to your web confirmation page." -msgstr "这些设置将重定向买家到网站确认页。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:80 -msgid "Access and edit Instant payment notifications settings - IPN" -msgstr "访问和编辑即时付款通知设置- IPN" - -#: ../../accounting/receivables/customer_payments/paypal.rst:85 -msgid "Example" -msgstr "例子" - -#: ../../accounting/receivables/customer_payments/paypal.rst:87 -msgid "**Database name**: \"yourcompany\"" -msgstr " **数据库名称**: “你的公司\" " - -#: ../../accounting/receivables/customer_payments/paypal.rst:89 -msgid "**Notification URL**: https://yourcompany.odoo.com/payment/paypal/ipn/" -msgstr " **通知网址**: https: //yourcompany.odoo.com/payment/paypal/ipn/" - -#: ../../accounting/receivables/customer_payments/paypal.rst:91 -msgid "" -"Verify that your Notify URL uses the correct protocol (HTTP / HTTPS). If you" -" use the odoo.com domain, we advise you to use HTTPS." -msgstr "验证您的Notify URL 时候使用了正确的协议(HTTP / HTTPS)。如果你使用odoo.com域，我们建议您使用HTTPS。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:94 -msgid "" -"Set the encoding to UTF-8 from the menu :menuselection:`Settings --> " -"Language Encoding --> More Options --> More selling tools`" -msgstr "" -"从菜单 :menuselection:`设置 --> 语言编码 --> 更多选项 --> 更多 selling tools` 设置编码为 UTF-8" - -#: ../../accounting/receivables/customer_payments/paypal.rst:103 -msgid "" -"Record your Merchant Paypal ID (personal or business account both will have " -"it) it will be entered in Odoo backend :menuselection:`Paypal Settings --> " -"Account Options`." -msgstr "" -"记录你的Merchant Paypal ID (个人或企业账户, 或者两者)它将进入Odoo后端 :menuselection:`Paypal " -"Settings --> Account Options`." - -#: ../../accounting/receivables/customer_payments/paypal.rst:111 -msgid "" -"If you want your customers to be able to pay through Paypal while not having" -" a Paypal account- following setting \"Paypal Account Optional\" needs to be" -" set to **ON**. All users will be able to choose Credit/debit card payment " -"option - Paypal account not required." -msgstr "" -"如果想让没有Paypal账户的客户用Paypal支付, 将 \"Paypal Account Optional\"设置为**ON**.\n" -"所有的用户可选择信用卡/借记卡支付, 不需要Paypal账户。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:120 -msgid "Setup your Paypal Payment Acquirer account credentials in Odoo" -msgstr "在Odoo 设置Paypal付款收单方账号证明。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:122 -msgid "" -":menuselection:`Settings --> Payments --> Payment Acquirers --> Paypal`" -msgstr ":menuselection:`设置--> 付款--> 付款收单方--> Paypal` " - -#: ../../accounting/receivables/customer_payments/paypal.rst:124 -msgid "**Paypal Email ID**: your paypal account email address" -msgstr " **Paypal Email ID**: 你的 paypal 账户 email 地址" - -#: ../../accounting/receivables/customer_payments/paypal.rst:126 -msgid "**Paypal Merchant ID**: ID retrieved at previous step" -msgstr " **Paypal商家ID**: 在上一步检索到的ID" - -#: ../../accounting/receivables/customer_payments/paypal.rst:136 -msgid "" -"If your eCommerce customer gets this Error Message after completing Paypal " -"payment instead of being redirected to your database:" -msgstr "如果你的电子商务客户在完成Paypal支付后收到错误信息, 而不是被重定向到您的数据库：" - -#: ../../accounting/receivables/customer_payments/paypal.rst:142 -msgid "" -"Verify the settings you have `configured in Paypal <WebsitePreferences_>`_:" -msgstr "验证您的设置 `configured in Paypal <WebsitePreferences_>`_:" - -#: ../../accounting/receivables/customer_payments/paypal.rst:144 -msgid "" -"Auto Return should be on (the value can be quite generic, like " -"<odoo_instance>/shop/confirmation; the correct URL will be set for each " -"transaction)" -msgstr "自动回应应为(该值可以是通用的，像<odoo_instance>/shop/confirmation; 正确的URL设置将应用于每个交易)" - -#: ../../accounting/receivables/customer_payments/paypal.rst:148 -msgid "Payment Data Transfer should be off" -msgstr "支付数据传输应关闭" - -#: ../../accounting/receivables/customer_payments/paypal.rst:150 -msgid "" -"On-premise databases must be accessible through classic HTTP/HTTPS ports " -"(80/443) for Paypal to work correctly, usually through a reverse proxy. " -"Contact your integrating partner if you are unsure this is the case. " -"Databases hosted on odoo.com are already configured correctly." -msgstr "" -"Paypal如需正常工作, 数据库必须通过HTTP / HTTPS端口访问(80 / " -"443)，通常是通过一个反向代理。如果不确定，联系你的合作伙伴。数据库托管在Odoo.com已正确配置。" - -#: ../../accounting/receivables/customer_payments/paypal.rst:157 -#: ../../accounting/receivables/customer_payments/recording.rst:127 -msgid ":doc:`credit_cards`" -msgstr ":doc:`credit_cards` " - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "有哪些不同的方式来记录付款？" @@ -10724,6 +10664,10 @@ msgid "" " with two journal entries for the same transaction." msgstr "内部银行转款，在仪表板上选择转出的银行，并在付款界面，选择转入的帐户。不需要在另一个银行帐户中重复操作，否则将重复交易。" +#: ../../accounting/receivables/customer_payments/recording.rst:127 +msgid ":doc:`credit_cards`" +msgstr ":doc:`credit_cards` " + #: ../../accounting/receivables/getting_paid.rst:3 msgid "How to get paid?" msgstr "如何收款？" diff --git a/locale/zh_CN/LC_MESSAGES/discuss.po b/locale/zh_CN/LC_MESSAGES/discuss.po index f9e922ece..54ad6a9d1 100644 --- a/locale/zh_CN/LC_MESSAGES/discuss.po +++ b/locale/zh_CN/LC_MESSAGES/discuss.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Kate Lee <kateleelpk@gmail.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" @@ -23,7 +23,7 @@ msgid "Discuss" msgstr "讨论" #: ../../discuss/email_servers.rst:3 -msgid "How to use my own email servers to send and receive messages in Odoo" +msgid "How to use my own email servers to send and receive email in Odoo" msgstr "" #: ../../discuss/email_servers.rst:6 @@ -31,138 +31,230 @@ msgid "When is it needed" msgstr "" #: ../../discuss/email_servers.rst:7 -msgid "You need it if you use Odoo Community or Enterprise." -msgstr "" - -#: ../../discuss/email_servers.rst:10 -msgid "What if I use Odoo Online" -msgstr "" - -#: ../../discuss/email_servers.rst:11 msgid "" -"You are done! Odoo Online comes up with an embedded and ready-to-use email " -"server (*@yourcompany.odoo.com*). We recommend to keep this default setting " -"as is as it is really convenient." +"Using your own email servers is required to send and receive messages in " +"Odoo Community or Enterprise. Odoo Online embeds an out-of-box email " +"solution that works straight away. However you can still use your own email " +"servers with the online edition. Some insights are provided here below." +msgstr "" + +#: ../../discuss/email_servers.rst:14 +msgid "How to set it up" msgstr "" #: ../../discuss/email_servers.rst:15 msgid "" -"Indeed, while it is branded by Odoo, the visible source of any message sent " -"from Odoo will be your personal email address (your Odoo login). Your " -"contacts will therefore trust your messages." -msgstr "" - -#: ../../discuss/email_servers.rst:20 -msgid "How does it work when a contact replies to an email sent from Odoo" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers* (watch out: this checkbox only shows up after" +" Odoo 10). Then, go through the following steps." msgstr "" #: ../../discuss/email_servers.rst:21 msgid "" -"Default reply-to is a generic address used to automatically route any " -"incoming email to the discussion thread of the origin business object " -"(opportunity, order, task, etc.) and to the inbox of all its followers. By " -"default this address is \"catchall@\" but it can be changed. Thanks to it, " -"you get a perfect message thread in Odoo and you don't pollute your external" -" email box with Odoo-related topics." +"Office 365 doesn't allow external hosts like Odoo. Consequently you can't " +"use Office 365 email servers to send or receive messages in Odoo." msgstr "" -#: ../../discuss/email_servers.rst:29 -msgid "How to use my own email servers" -msgstr "" - -#: ../../discuss/email_servers.rst:30 -msgid "" -"You need to be a system admin to set this up. Go to :menuselection:`Settings" -" --> General Settings` and check *External Email Servers* (watch out: this " -"checkbox only shows up after Odoo 10). Then, go through the following steps." -msgstr "" - -#: ../../discuss/email_servers.rst:36 +#: ../../discuss/email_servers.rst:26 msgid "Set an outgoing email server for outbound messages" msgstr "" -#: ../../discuss/email_servers.rst:37 +#: ../../discuss/email_servers.rst:27 msgid "" "You need the SMTP data of your email provider (Gmail, Outlook, Yahoo, AOL, " "etc.) as well as your admin credentials. Once all the information has been " "filled out, click on *Test Connection*." msgstr "" -#: ../../discuss/email_servers.rst:45 +#: ../../discuss/email_servers.rst:35 msgid "Set an incoming email server for inbound messages" msgstr "" -#: ../../discuss/email_servers.rst:46 +#: ../../discuss/email_servers.rst:36 msgid "" "Fill out the form according to your email provider’s settings. Leave the " "*Actions to Perform on Incoming Mails* blank. Once all the information has " "been filled out, click on *TEST & CONFIRM*." msgstr "" -#: ../../discuss/email_servers.rst:53 +#: ../../discuss/email_servers.rst:43 msgid "" "By default inbound messages are fetched every 5 minutes. You can change this" " value in developer mode. Go to :menuselection:`Settings --> Technical --> " "Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*." msgstr "" -#: ../../discuss/email_servers.rst:59 +#: ../../discuss/email_servers.rst:49 msgid "Set the domain name" msgstr "" -#: ../../discuss/email_servers.rst:60 +#: ../../discuss/email_servers.rst:50 msgid "" "Enter the domain name of your email servers (e.g. mycompany.com) in General " "Settings." msgstr "" -#: ../../discuss/email_servers.rst:67 +#: ../../discuss/email_servers.rst:57 msgid "Create a catchall address" msgstr "" -#: ../../discuss/email_servers.rst:68 +#: ../../discuss/email_servers.rst:58 +msgid "" +"When a contact replies to an email sent from Odoo, the *reply-to* address is" +" a generic address used to route the reply to the right discussion thread in" +" Odoo (opportunity, order, task, etc.) and to the inbox of all its " +"followers. By default this address is \"catchall@\" but it can be changed." +msgstr "" + +#: ../../discuss/email_servers.rst:63 msgid "" "Create a catchall address in your email server settings. We advise you to " "use \"catchall@\" so that everything works out straight away. If you want to" " use another alias, you have extra steps in Odoo:" msgstr "" -#: ../../discuss/email_servers.rst:72 +#: ../../discuss/email_servers.rst:67 msgid "Activate the developer mode from your Settings Dashboard." msgstr "" -#: ../../discuss/email_servers.rst:77 +#: ../../discuss/email_servers.rst:72 msgid "" "Refresh your screen. Then go to :menuselection:`Settings --> Technical --> " "Parameters --> System Parameters` and enter your custom catchall alias in " "*mail.catchall.alias*." msgstr "" -#: ../../discuss/email_servers.rst:84 +#: ../../discuss/email_servers.rst:79 msgid "You can edit the email alias used for bounced messages the same way." msgstr "" -#: ../../discuss/email_servers.rst:87 -msgid "How to perfectly combine Odoo Discuss and my traditional email tool" +#: ../../discuss/email_servers.rst:82 +msgid "How to use my own email servers with Odoo Online" msgstr "" -#: ../../discuss/email_servers.rst:88 +#: ../../discuss/email_servers.rst:83 +msgid "" +"Odoo Online comes up with an embedded and ready-to-use email server " +"(*@yourcompany.odoo.com*). We recommend to keep this default setting as it " +"is really convenient. Indeed, while it is Odoo-labelled, the visible source " +"of any message sent from Odoo will be your personal email address (your Odoo" +" login). Your contacts will therefore trust your messages." +msgstr "" + +#: ../../discuss/email_servers.rst:90 +msgid "" +"You can still use your own email servers if you want your contacts to see " +"your historic email address when they reply to your messages or if you want " +"to manage the reputation of your email servers yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:94 +msgid "There are 2 methods:" +msgstr "" + +#: ../../discuss/email_servers.rst:96 +msgid "" +"[Recommended] **Use a catchall redirection** (your server -> Odoo server) to" +" receive emails in Odoo in real time thanks to the Odoo email server. Create" +" a catchall address in your email server settings. Then apply following " +"redirection: catchall@yourdomain.ext -> catchall@yourcompany.odoo.com. " +"That's it you're ready to go!" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"**Use a catchall mailbox** to exclusively use your own email server. That " +"way you can also manage your email server reputation (blacklisting, etc). " +"However, incoming messages are fetched from the email server thanks to a " +"cron running every hour. This is the shortest time lap for crons in Online " +"instances. If you opt for this solution, simply follow the procedure of " +"above section." +msgstr "" + +#: ../../discuss/email_servers.rst:111 +msgid "How to be SPF-compliant when using external email servers in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Sender Policy Framework (SPF) is an email-validation system that checks that" +" incoming mail from a domain comes from a host authorized by that domain's " +"administrator. Such a security system is used in most email servers. If you " +"don't comply with it, your emails sent from Odoo will be likely flagged as " +"spam." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "" +"To be SPF-compliant, you need to authorize Odoo as a sending host in your " +"domain name settings:" +msgstr "" + +#: ../../discuss/email_servers.rst:121 +msgid "Sign in to your domain’s account at your domain host." +msgstr "" + +#: ../../discuss/email_servers.rst:122 +msgid "Locate the page for updating your domain’s DNS records." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If no TXT record is set, create one with following definition: v=spf1 " +"include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:125 +msgid "In case a TXT record is already set, add \"include:_spf.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:127 +msgid "e.g. for a Gmail server it should be:" +msgstr "" + +#: ../../discuss/email_servers.rst:129 +msgid "v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:131 +msgid "" +"Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:134 +msgid "" +"Your new SPF record can take up to 48 hours to go into effect, but this " +"usually happens more quickly." +msgstr "" + +#: ../../discuss/email_servers.rst:137 +msgid "" +"Adding more than one SPF record for a domain can cause problems with mail " +"delivery and spam classification. Instead, we recommend using only one SPF " +"record by modifying it to authorize Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:142 +msgid "How to choose between Odoo and my traditional email box" +msgstr "" + +#: ../../discuss/email_servers.rst:143 msgid "" "Odoo Discuss is a perfect tool to send and read messages related to business" -" objects. But it doesn't aim to replace a full-featured email software " -"(Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " +" documents. However it doesn't aim to replace a full-featured email solution" +" (Gmail, Outlook, Yahoo, AOL, etc.). We recommend to take the most out of " "both systems without mingling them: What is related to Odoo business objects" -" or applications goes into Odoo; What is not stays into your external email " -"boxes." +" or applications goes into Odoo; What is not can be managed into your " +"external email box." msgstr "" -#: ../../discuss/email_servers.rst:95 +#: ../../discuss/email_servers.rst:150 msgid "" "To do so, create specific email aliases to use in Odoo (to generate leads or" " opportunities, helpdesk tickets, etc.). If you take an email alias already " "used for messaging outside of Odoo, incoming messages will land into both " -"systems. This will negatively impact your productivity when it comes to " -"process them." +"systems. This will negatively impact your productivity." msgstr "" #: ../../discuss/mail_twitter.rst:3 diff --git a/locale/zh_CN/LC_MESSAGES/ecommerce.po b/locale/zh_CN/LC_MESSAGES/ecommerce.po index ff9991bf2..a2b0d79e0 100644 --- a/locale/zh_CN/LC_MESSAGES/ecommerce.po +++ b/locale/zh_CN/LC_MESSAGES/ecommerce.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: fausthuang <faust_huang@hotmail.com>, 2017\n" +"Last-Translator: Eddie Lim <bhweelim@yahoo.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -655,23 +655,21 @@ msgid "Launch my website" msgstr "" #: ../../ecommerce/shopper_experience.rst:3 -msgid "Improve shopper experience" +msgid "Get paid" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:3 -msgid "How to set up payment methods" +msgid "How to get paid with payment acquirers" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:5 msgid "" -"To collect payments, you can either request your customers to process it " -"manually (e.g. wire transfer) or redirect them to payment acquirers. The " -"payment process described hereunder is common to both eCommerce and online " -"quotations." +"Odoo embeds several payment methods to get paid on eCommerce, Sales and " +"Invoicing apps." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:10 -msgid "Payment methods" +msgid "What are the payment methods available" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:13 @@ -681,451 +679,561 @@ msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:15 msgid "" "Wire Transfer is the default payment method available. The aim is providing " -"your customers with your bank details so that they can pay via their bank. " -"This is very easy to start with but slow and inefficient process-wise. Opt " -"for online acquirers as soon as you can!" +"your customers with your bank details so they can pay on their own via their" +" bank. This is very easy to start with but slow and inefficient process-" +"wise. Opt for online acquirers as soon as you can!" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:21 -msgid "" -"For B2B users: you can create new manually-processed payment methods (check," -" purchase order, etc.) by renaming 'Wire Transfer' or duplicating it." +msgid "Payment acquirers" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:25 -msgid "Online payment acquirers" +#: ../../ecommerce/shopper_experience/payment.rst:23 +msgid "" +"Redirect your customers to payment platforms to collect money effortless and" +" track the payment status (call-back). Odoo supports more and more platforms" +" over time:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:27 -msgid "" -"Redirect your customers to payment acquirer platforms to collect money " -"effortless. Odoo supports more and more platforms over time: Paypal, " -"Ingenico, Authorize.net, etc. Once the payment accepted, orders are " -"confirmed in Odoo so that the delivery & invoicing processes are triggered " -"automatically." +msgid "`Paypal <paypal.html>`__" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:28 +msgid "Ingenico" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:29 +msgid "Authorize.net" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:30 +msgid "Adyen" +msgstr "Adyen" + +#: ../../ecommerce/shopper_experience/payment.rst:31 +msgid "Buckaroo" +msgstr "Buckaroo" + +#: ../../ecommerce/shopper_experience/payment.rst:32 +msgid "PayUmoney" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:33 -msgid "Custom (advanced)" -msgstr "" +msgid "Sips" +msgstr "Sips" -#: ../../ecommerce/shopper_experience/payment.rst:35 -msgid "" -"Can be used to request payments to any payment acquirer not listed in Odoo." -msgstr "" +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" +msgstr "条带" #: ../../ecommerce/shopper_experience/payment.rst:38 -msgid "Edit a payment method" +msgid "How to go live" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:40 msgid "" -"To make payment methods intuitive for your customers feel free to customize " -"them by editing:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:42 -msgid "the name," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:44 -msgid "the picture," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:46 -msgid "" -"the notification messages (thank you & next step, error, cancellation)." +"Once the payment method ready, make it visible in the payment interface and " +"activate the **Production** mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:48 +msgid "How to let customers save and reuse credit cards" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:49 msgid "" -"Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers`" -" to do so." +"To ease the payment of returning customers, you can let them save and reuse " +"a credit card if they want to. If so, a payment token will be saved in Odoo." +" This option is available with Ingenico and Authorize.net." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:51 -msgid "Generic setup" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:53 -msgid "Review the elements here above." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:55 -msgid "Enter your credentials (online acquirers only)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:57 -msgid "Choose your order confirmation preference (see below)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:59 -msgid "Publish the payment method." +#: ../../ecommerce/shopper_experience/payment.rst:54 +#: ../../ecommerce/shopper_experience/payment.rst:68 +msgid "You can turn this on from the acquirer configuration form." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:61 -msgid "Test the payment flow in *Test* mode (default mode)." +msgid "How to debit credit cards to pay subscriptions" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:63 -msgid "Switch to *Production* mode." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:65 +#: ../../ecommerce/shopper_experience/payment.rst:62 msgid "" -"Se your default payment acquirer in :menuselection:`Accounting --> " -"Configuration --> Settings`. It will be auto-selected for your customers " -"when they enter the payment screen." +"`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to " +"bill services automatically on a recurring basis. Along with it, you can " +"have an automatic debit of the customer's credit card." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:69 +#: ../../ecommerce/shopper_experience/payment.rst:66 +msgid "This option is available with Ingenico and Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:73 msgid "" -"Rely on the documentation related to your payment acquirer to go through " -"step 2, 5 and 6. Some acquirers provides you with specific credentials for " -"test and production modes (Paypal). Others let you switch mode in their " -"setup interface (Authorize.net)." +"That way a payment token will be recorded when the customer goes for the " +"subscription and an automatic debit will occur whenever an invoice is issued" +" from the subscription." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:74 +#: ../../ecommerce/shopper_experience/payment.rst:79 +msgid "How to use other acquirers (advanced)" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:81 msgid "" -"With Ingenico and Authorize.net, you can let your customers save and reuse a" -" payment card to accelerate the process on next checkouts. See *Store Card " -"Data* in Configuration tab." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:78 -msgid "Payment flow" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:80 -msgid "" -"When choosing the payment method, the customer is taken to the payment " -"acquirer interface to process the payment." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:83 -msgid "" -"Once done he is taken back to Odoo's confirmation page. The transaction " -"status shows up:" +"Odoo can submit single payment requests and redirect to any payment " +"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction" +" status. So you will confirm orders manually once you get paid." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:85 -msgid "" -"*Pending*: the order will be confirmed as soon as you authorize the " -"transaction in the acquirer interface." +msgid "How to:" msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:87 -msgid "*Confirmed*: the payment has been authorized automatically." +msgid "Switch to developer mode." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:89 -msgid "" -"A confirmation email is sent to the customer with a copy of the order in " -"pdf. It shows the payment status." +msgid "Take the **Custom** payment method." msgstr "" #: ../../ecommerce/shopper_experience/payment.rst:91 -msgid "Launch the delivery and invoicing from:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:93 msgid "" -"eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:95 -msgid "" -"online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales " -"Orders`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:97 -msgid "" -"For internal tracking purposes, a link to the transaction status is provided" -" in the sales order." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:100 -msgid "" -"If the customer cancels the payment while on the payment acquirer form, it " -"is taken back to the store page (or online quotation) in order to reprocess " -"the order. The payment is marked as *Cancelled* in Odoo." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:105 -msgid "" -"You can edit the confirmation email template from :menuselection:`Website " -"Admin --> Configuration --> Settings`." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:109 -msgid "Order confirmation preferences" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:111 -msgid "There are 4 different behaviors available for any payment acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:114 -msgid "No automatic confirmation" -msgstr "无自动确认" - -#: ../../ecommerce/shopper_experience/payment.rst:116 -msgid "" -"This is the default mode for *Wire Transfer*. It means Odoo does not confirm" -" orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid " -"Order*). Once you get the payment, you are expected to confirm the order " -"manually to pursue the process (delivery, invoicing)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:121 -msgid "" -"Authorize the amount and confirm the SO on acquirer confirmation (capture " -"manually)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:123 -msgid "" -"Odoo confirms the order as soon as the payment success notification comes " -"in. To get the money however, you need to capture it from your payment " -"transaction. In lots of countries you are indeed requested to deliver your " -"goods before capturing the amount." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:128 -msgid "" -"Authorize & capture the amount and confirm the SO on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:130 -msgid "" -"This is the default mode for payment acquirers. The amount is captured " -"automatically." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:133 -msgid "" -"For B2B: if you use a manual payment method like *Wire Transfer* and don't " -"expect any upfront payment to launch the delivery, switch to this mode as " -"well." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:137 -msgid "" -"Authorize & capture the amount, confirm the SO and auto-validate the invoice" -" on acquirer confirmation" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:139 -msgid "" -"If you invoice upfront and not at the delivery, switch to this last mode to " -"automate everything. You are requested to select a Payment Journal to record" -" such payments (see " -":doc:`../../accounting/receivables/customer_payments/credit_cards`)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:144 -msgid "Custom payment acquirers (advanced)" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:146 -msgid "" -"Odoo can submit payment requests and redirect to any payment acquirer. In " -"such a case, you need to confirm the sale manually in Odoo once you get paid" -" because Odoo cannot read any payment status sent by the acquirer." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:150 -msgid "To configure this:" -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:152 -msgid "switch to developer mode," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:154 -msgid "edit the *Custom* payment method," -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:156 -msgid "" -"set up the payment form (S2S Form Template) as instructed by your payment " +"Set up the payment form (S2S Form Template) as instructed by your payment " "acquirer. You can start from *default_acquirer_button* that you can " "duplicate." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:160 -msgid "Recurring payments & Installment plans" +#: ../../ecommerce/shopper_experience/payment.rst:96 +msgid "Other configurations" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:162 +#: ../../ecommerce/shopper_experience/payment.rst:98 msgid "" -"The Ingenico integration allows you to process and manage recurring payments" -" from Odoo Subscriptions app out-of-the-box (more information coming soon)." +"Odoo can also be used for more advanced payment processes like installment " +"plans (e.g. `Paypal Installment Plans " +"<https://developer.paypal.com/docs/classic/paypal-payments-standard" +"/integration-guide/installment_buttons>`__)." msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:165 +#: ../../ecommerce/shopper_experience/payment.rst:102 msgid "" -"With some customization, Odoo can also trigger installment plans if this is " -"permitted by your payment acquirer’s API:" +"Such a customization service is made on-demand by our technical experts " +"based on your own requirements. A business advisor can reach you out for " +"such matter. `Contact us. <https://www.odoo.com/page/contactus>`__" msgstr "" -#: ../../ecommerce/shopper_experience/payment.rst:168 -msgid "" -"e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic" -"/paypal-payments-standard/integration-guide/installment_buttons)." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:170 -msgid "" -"Such a service is made on-demand by our technical experts based on your own " -"requirements. Ask our business advisors at info@odoo.com." -msgstr "" - -#: ../../ecommerce/shopper_experience/payment.rst:175 +#: ../../ecommerce/shopper_experience/payment.rst:109 msgid ":doc:`paypal`" msgstr ":doc:`paypal` " +#: ../../ecommerce/shopper_experience/payment.rst:110 +msgid ":doc:`wire_transfer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3 +msgid "How to manage orders paid with payment acquirers" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:5 +msgid "" +"Odoo confirms orders automatically as soon as the payment is authorized by a" +" payment acquirer. This triggers the delivery. If you invoice based on " +"ordered quantities, you are also requested to invoice the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:12 +msgid "What are the payment status" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:13 +msgid "" +"At anytime, the salesman can check the transaction status from the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:18 +msgid "*Draft*: transaction under processing." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:20 +msgid "" +"*Pending*: the payment acquirer keeps the transaction on hold and you need " +"to authorize it from the acquirer interface." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:23 +msgid "" +"*Authorized*: the payment has been authorized but not yet captured. In Odoo," +" the order is already confirmed. Once the delivery done, you can capture the" +" amount from the acquirer interface (or from Odoo if you use Authorize.net)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:28 +msgid "" +"*Done*: the payment is authorized and captured. The order has been " +"confirmed." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:30 +msgid "" +"*Error*: an error has occured during the transaction. The customer needs to " +"retry the payment. The order is still in draft." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:34 +msgid "" +"*Cancelled*: when the customer cancels the payment in the payment acquirer " +"form. They are taken back to Odoo in order to modify the order." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:37 +msgid "" +"Specific messages are provided to your customers for every payment status, " +"when they are redirected to Odoo after the transaction. To edit such " +"messages, go to the *Messages* tab of the payment method." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:44 +msgid "Auto-validate invoices at order" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:46 +msgid "" +"When the order is confirmed you can also have an invoice automatically " +"issued and paid. This fully-automated made for businesses that invoice " +"orders straight on." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53 +msgid "" +"If you choose this mode you are requested to select a payment journal in " +"order to record payments in your books. This payment is automatically " +"reconcilied with the invoice, marking it as paid. Select your **bank " +"account** if you get paid immediately on your bank account. If you don't you" +" can create a specific journal for the payment acquirer (type = Bank). That " +"way, you can track online payments in an intermediary account of your books " +"until you get paid into your bank account (see `How to register credit card " +"payments " +"<../../accounting/receivables/customer_payments/credit_cards.html>`__)." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64 +msgid "Capture the payment after the delivery" +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65 +msgid "" +"With this mode, the order is confirmed but the amount is kept on hold. Once " +"the delivery processed, you can capture the payment from Odoo. This mode is " +"only available with Authorize.net." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72 +msgid "" +"To capture the payment, open the transaction from the order. Then click " +"*Capture Transaction*." +msgstr "" + +#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78 +msgid "" +"With other payment acquirers, you can manage the capture in their own " +"interfaces, not from Odoo." +msgstr "" + #: ../../ecommerce/shopper_experience/paypal.rst:3 -msgid "How to collect payments with Paypal" +msgid "How to get paid with Paypal" msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:5 msgid "" -"Paypal is the easiest payment method to configure. It is also the only one " -"without any subscription free." -msgstr "" - -#: ../../ecommerce/shopper_experience/paypal.rst:9 -msgid "Setup your Paypal account" +"Paypal is the easiest online payment method to configure. It is also the " +"only one without any subscription free. We definitely advise it to any " +"starter." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:11 -msgid "" -"1. Create a business account at Paypal.com (see: https://www.paypal.com/in" -"/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-" -"outside) or upgrade your account to Business account (merchant) if you have " -"a basic account." +msgid "Set up your Paypal account" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:15 +#: ../../ecommerce/shopper_experience/paypal.rst:13 msgid "" -"2. Log in to your account at Paypal.com and go to :menuselection:`My Account" -" --> Profile --> My Selling Tools`. There click *PayPal button language " -"encoding* under *More Selling Tools* section. Then, click *More Options* and" -" replace the two default encoding formats by *UTF-8*." +"Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade " +"your account to *Business account* if you have a basic account." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:20 -msgid "Open Paypal setup form in Odoo and enter your *Email ID*." +#: ../../ecommerce/shopper_experience/paypal.rst:16 +msgid "" +"Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your " +"**Profile**." msgstr "" #: ../../ecommerce/shopper_experience/paypal.rst:22 -msgid "" -"4. The Paypal Merchant ID is not mandatory (extra verification level). It is" -" provided in Paypal under :menuselection:`My Account --> Overview`." +msgid "Now enter the menu **My selling tools**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:25 -msgid "" -"5. Configure the IPN feedback (Paypal contacting your Odoo instance without " -"needing the redirection). The setting can be found in " -":menuselection:`Profile --> My Selling Tools --> Instant payment " -"notification`. Activate it and set it to " -"<odoo_instance_url>/payment/paypal/ipn." +#: ../../ecommerce/shopper_experience/paypal.rst:27 +msgid "Let's start with the **Website Preferences**." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:30 +#: ../../ecommerce/shopper_experience/paypal.rst:29 msgid "" -"6. To test the workflow, you can create sandbox accounts by logging in at " -"https://developer.paypal.com/webapps/developer/applications/myapps with the " -"same Paypal credentials. Two default sandbox accounts are automatically " -"generated when you register to Paypal: one is a buyer, the other is a " -"shopper." +"Turn on **Auto Return** and enter the **Return URL**: " +"<odoo_instance_url>/shop/confirmation. Verify that this address uses the " +"correct protocol (HTTP/HTTPS)." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:35 +#: ../../ecommerce/shopper_experience/paypal.rst:36 msgid "" -"7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com " -"(same password than real account) and apply the same format change." +"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is " +"generated. You will be later requested to enter it in Odoo." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:39 +#: ../../ecommerce/shopper_experience/paypal.rst:43 msgid "" -"To automatically redirect your customers when the payment is completed, go " -"to your Website Preferences and turn *Auto Return* on. Set *Return URL* to " -"<odoo_instance_url>/shop/confirmation. Verify that your *Notify URL* uses " -"the correct protocol (HTTP/HTTPS)." +"Then, get back to your profile to activate the **Instant Payment " +"Notification (IPN)** in *My selling tools*." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:44 -msgid "" -"If you want your customers to pay without creating a Paypal account, *Paypal" -" Account Optional* needs to be turned on." +#: ../../ecommerce/shopper_experience/paypal.rst:46 +msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:48 +#: ../../ecommerce/shopper_experience/paypal.rst:51 +msgid "" +"Now you must change the encoding format of the payment request sent by Odoo " +"to Paypal. To do so, get back to *My selling tools* and click **PayPal " +"button language encoding** in *More Selling Tools* section." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:58 +msgid "" +"Then, click *More Options* and set the two default encoding formats as " +"**UTF-8**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:66 +msgid "" +"If you want your customers to pay without creating a Paypal account, " +"**Paypal Account Optional** needs to be turned on." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Paypal's payment method in Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:75 +msgid "" +"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->" +" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your " +"**Merchant ID** and check **Use IPN**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:82 +msgid "" +"They are both provided in your Paypal profile, under :menuselection:`My " +"business info`." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:85 +msgid "" +"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so," +" open the *Settings* and activate the **Developer Mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:91 +msgid "" +"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System" +" Parameters` and create a parameter with following values:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:94 +msgid "Key: payment_paypal.pdt_token" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:95 +msgid "Value: your Paypal *Identity Token*" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:103 +msgid "" +"Your configuration is now ready! You can make Paypal visible on your " +"merchant interface and activate the **Production mode**." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:112 msgid "Transaction fees" msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:50 +#: ../../ecommerce/shopper_experience/paypal.rst:114 msgid "" "You can charge an extra to the customer to cover the transaction fees Paypal" " charges you. Once redirected to Paypal, your customer sees an extra applied" " to the order amount." msgstr "" -#: ../../ecommerce/shopper_experience/paypal.rst:53 +#: ../../ecommerce/shopper_experience/paypal.rst:117 msgid "" -"To activate this, go to the *Configuration* tab and check *Add Extra Fees*. " -"Default fees are the ones charged by Paypal." +"To activate this, go to the *Configuration* tab of Paypal config form in " +"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:123 +msgid "" +"To apply the right fees for your country, please refer to `Paypal Fees " +"<https://www.paypal.com/webapps/mpp/paypal-fees>`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:128 +msgid "Test the payment flow" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:130 +msgid "" +"You can test the entire payment flow thanks to Paypal Sandbox accounts." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:132 +msgid "" +"Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your" +" Paypal credentials. This will create two sandbox accounts:" +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:136 +msgid "" +"A business account (to use as merchant, e.g. " +"pp.merch01-facilitator@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:137 +msgid "" +"A default personal account (to use as shopper, e.g. " +"pp.merch01-buyer@example.com)." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:139 +msgid "" +"Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the " +"merchant account and follow the same configuration instructions." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:142 +msgid "" +"Enter your sandbox credentials in Odoo and make sure Paypal is still set on " +"*Test* mode. Also, make sure the confirmation mode of Paypal is not " +"*Authorize & capture the amount, confirm the SO and auto-validate the " +"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be " +"automatically generated when the transaction is completed." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:150 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:3 -msgid "How customers can access their portal" +msgid "How customers can access their customer account" msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:5 msgid "" -"It has never been so easy for your customers to access their documents " -"through a portal. Forget endless signup forms, Odoo makes it as easy as ABC." -" With eCommerce and Online Quotation apps, your customers are requested to " -"create a portal account (name, email, password only) from the very first " -"order confirmation or online quotation email they get from you." +"It has never been so easy for your customers to access their customer " +"account. Forget endless signup forms, Odoo makes it as easy as ABC. They are" +" suggested to sign up (name, email, password) when the order is placed, and " +"not before. Indeed, nothing is more annoying than going through a signup " +"process before buying something." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:12 +#: ../../ecommerce/shopper_experience/portal.rst:14 msgid "Sign up" msgstr "注册" -#: ../../ecommerce/shopper_experience/portal.rst:14 +#: ../../ecommerce/shopper_experience/portal.rst:16 msgid "" -"When clicking the link in the email or when clicking *Sign up* in the " -"checkout process, your customer is directed to the *Sign up* page." -msgstr "" - -#: ../../ecommerce/shopper_experience/portal.rst:21 -msgid "Customer account" +"The invitation to sign up shows up when the customer wants to visualize the " +"order from order confirmation email." msgstr "" #: ../../ecommerce/shopper_experience/portal.rst:23 +msgid "Customer account" +msgstr "" + +#: ../../ecommerce/shopper_experience/portal.rst:25 msgid "" -"Once logged in the customer will access his account by clicking *My Account*" +"Once logged in the customer will access the account by clicking *My Account*" " in the login dropdown menu." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:29 +#: ../../ecommerce/shopper_experience/portal.rst:31 msgid "" -"From the portal menu all the customer history can be reviewed. The main " -"address (billing) can also be modified." +"THere they find all their history. The main address (billing) can also be " +"modified." msgstr "" -#: ../../ecommerce/shopper_experience/portal.rst:36 +#: ../../ecommerce/shopper_experience/portal.rst:37 msgid "" -"If a portal user is a contact of a company (*Company* field set in customer " -"detail form), this last will see all the documents of the company and all " -"its other contacts through the portal." +"If the customer is set as a contact of a company in your address book, they " +"will see all the documents whose the customer belongs to this company." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:3 +msgid "How to get paid with wire transfers" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:5 +msgid "" +"**Wire Transfer** is the default payment method available. The aim is " +"providing your customers with your bank details so they can pay on their " +"own. This is very easy to start with but slow and inefficient process-wise. " +"Opt for payment acquirers as soon as you can!" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:13 +msgid "How to provide customers with payment instructions" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:14 +msgid "" +"Put your payment instructions in the **Thanks Message** of your payment " +"method." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:19 +msgid "They will appear to the customers when they place an order." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:26 +msgid "How to manage an order once you get paid" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:28 +msgid "" +"Whenever a customer pays by wire transfer, the order stays in an " +"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get " +"paid, you confirm the order manually to launch the delivery." +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:35 +msgid "How to create other manual payment methods" +msgstr "" + +#: ../../ecommerce/shopper_experience/wire_transfer.rst:37 +msgid "" +"If you manage a B2B business, you can create other manually-processed " +"payment methods like paying by check. To do so, just rename *Wire Transfer* " +"or duplicate it." msgstr "" #: ../../ecommerce/taxes.rst:3 diff --git a/locale/zh_CN/LC_MESSAGES/general.po b/locale/zh_CN/LC_MESSAGES/general.po index ab276c61d..6cca95dbc 100644 --- a/locale/zh_CN/LC_MESSAGES/general.po +++ b/locale/zh_CN/LC_MESSAGES/general.po @@ -6,11 +6,11 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: liAnGjiA <liangjia@qq.com>, 2017\n" +"Last-Translator: Jeffery CHEN <jeffery9@gmail.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -23,8 +23,8 @@ msgid "General" msgstr "常规" #: ../../general/auth.rst:3 -msgid "Authentification" -msgstr "" +msgid "Authentication" +msgstr "身份验证" #: ../../general/auth/google.rst:3 msgid "How to allow users to sign in with their Google account" @@ -84,64 +84,196 @@ msgid "" msgstr "" #: ../../general/base_import.rst:3 -msgid "BASE IMPORT" -msgstr "基础资料数据导入" +msgid "Data Import" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:3 +msgid "How to adapt an import template" +msgstr "" + +#: ../../general/base_import/adapt_template.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 "" + +#: ../../general/base_import/adapt_template.rst:11 +msgid "How to customize the file" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:13 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:15 +#: ../../general/base_import/import_faq.rst:26 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:20 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:27 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:31 +msgid "Why an “ID” column" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:33 +msgid "" +"The **ID** (External 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 "" + +#: ../../general/base_import/adapt_template.rst:36 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:38 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:39 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../general/base_import/adapt_template.rst:42 +msgid "How to import relation fields" +msgstr "" + +#: ../../general/base_import/adapt_template.rst:44 +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 "" + +#: ../../general/base_import/adapt_template.rst:48 +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 "" #: ../../general/base_import/import_faq.rst:3 -msgid "Import CSV file to Odoo" -msgstr "导入CSV文件到Odoo" +msgid "How to import data into Odoo" +msgstr "" -#: ../../general/base_import/import_faq.rst:8 -msgid "Frequently Asked Questions" -msgstr "常见问题" +#: ../../general/base_import/import_faq.rst:6 +msgid "How to start" +msgstr "" -#: ../../general/base_import/import_faq.rst:12 -msgid "Need to import data from an other application?" -msgstr "需要从其他应用程序中导入数据？" - -#: ../../general/base_import/import_faq.rst:14 +#: ../../general/base_import/import_faq.rst:7 msgid "" -"In order to re-create relationships between different records, you should " -"use the unique identifier from the original application and map it to the " -"**ID** (External ID) column in Odoo. When you import an other record that " -"links to the first one, use **XXX/ID** (XXX/External ID) to the original " -"unique identifier." +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../general/base_import/import_faq.rst:11 +msgid "Open the view of the object you want to populate and click *Import*." msgstr "" #: ../../general/base_import/import_faq.rst:16 msgid "" -"The **ID** (External ID) will also be used to update the original import if " -"you need to re-import modified data later, it's thus good practice to " -"specify it whenever possible." +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." msgstr "" -#: ../../general/base_import/import_faq.rst:21 -msgid "I cannot find the field I want to map my column to?" +#: ../../general/base_import/import_faq.rst:22 +msgid "How to adapt the template" msgstr "" -#: ../../general/base_import/import_faq.rst:23 -msgid "" -"Odoo try to find with some heuristic, based on the first ten lines of the " -"files, the type of field for each columns inside your file. For example if " -"you have a column only containing numbers, only the fields that are of type " -"integer will be displayed for you to choose from. While this behaviour might" -" be good and easy for most cases scenarios, it is also possible that it goes" -" wrong sometimes or that you want to map your column to a field that is not " -"proposed by default." +#: ../../general/base_import/import_faq.rst:24 +msgid "Add, remove and sort columns to fit at best your data structure." msgstr "" #: ../../general/base_import/import_faq.rst:25 -msgid "" -"If that happens, you just have to check the **Show all fields for completion" -" (advanced)** option, you will then be able to choose from the complete list" -" of fields for each columns." +msgid "We advise to not remove the **ID** one (see why in the next section)." msgstr "" -#: ../../general/base_import/import_faq.rst:30 +#: ../../general/base_import/import_faq.rst:31 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../general/base_import/import_faq.rst:39 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../general/base_import/import_faq.rst:44 +msgid "How to import from another application" +msgstr "" + +#: ../../general/base_import/import_faq.rst:46 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../general/base_import/import_faq.rst:54 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../general/base_import/import_faq.rst:60 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../general/base_import/import_faq.rst:62 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../general/base_import/import_faq.rst:71 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../general/base_import/import_faq.rst:79 msgid "Where can I change the date import format?" msgstr "" -#: ../../general/base_import/import_faq.rst:32 +#: ../../general/base_import/import_faq.rst:81 msgid "" "Odoo can automatically detect if a column is a date and it will try to guess" " the date format from a set of most used date format. While this process can" @@ -151,7 +283,7 @@ msgid "" " day and which one is the month in a date like '01-03-2016'." msgstr "" -#: ../../general/base_import/import_faq.rst:34 +#: ../../general/base_import/import_faq.rst:83 msgid "" "To view which date format Odoo has found from your file you can check the " "**Date Format** that is shown when clicking on **Options** under the file " @@ -159,7 +291,7 @@ msgid "" " the *ISO 8601* to define the format." msgstr "" -#: ../../general/base_import/import_faq.rst:37 +#: ../../general/base_import/import_faq.rst:86 msgid "" "If you are importing an excel (.xls, .xlsx) file, you can use date cells to " "store dates as the display of dates in excel is different from the way it is" @@ -167,11 +299,11 @@ msgid "" "whatever your locale date format is." msgstr "" -#: ../../general/base_import/import_faq.rst:42 +#: ../../general/base_import/import_faq.rst:91 msgid "Can I import numbers with currency sign (e.g.: $32.00)?" msgstr "" -#: ../../general/base_import/import_faq.rst:44 +#: ../../general/base_import/import_faq.rst:93 msgid "" "Yes, we fully support numbers with parenthesis to represent negative sign as" " well as numbers with currency sign attached to them. Odoo also " @@ -181,56 +313,56 @@ msgid "" "crash." msgstr "" -#: ../../general/base_import/import_faq.rst:46 +#: ../../general/base_import/import_faq.rst:95 msgid "" "Examples of supported numbers (using thirty-two thousands as an example):" msgstr "" -#: ../../general/base_import/import_faq.rst:48 +#: ../../general/base_import/import_faq.rst:97 msgid "32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:49 +#: ../../general/base_import/import_faq.rst:98 msgid "32000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:50 +#: ../../general/base_import/import_faq.rst:99 msgid "32,000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:51 +#: ../../general/base_import/import_faq.rst:100 msgid "-32000.00" msgstr "" -#: ../../general/base_import/import_faq.rst:52 +#: ../../general/base_import/import_faq.rst:101 msgid "(32000.00)" msgstr "" -#: ../../general/base_import/import_faq.rst:53 +#: ../../general/base_import/import_faq.rst:102 msgid "$ 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:54 +#: ../../general/base_import/import_faq.rst:103 msgid "(32000.00 €)" msgstr "" -#: ../../general/base_import/import_faq.rst:56 +#: ../../general/base_import/import_faq.rst:105 msgid "Example that will not work:" msgstr "" -#: ../../general/base_import/import_faq.rst:58 +#: ../../general/base_import/import_faq.rst:107 msgid "ABC 32.000,00" msgstr "" -#: ../../general/base_import/import_faq.rst:59 +#: ../../general/base_import/import_faq.rst:108 msgid "$ (32.000,00)" msgstr "" -#: ../../general/base_import/import_faq.rst:64 +#: ../../general/base_import/import_faq.rst:113 msgid "What can I do when the Import preview table isn't displayed correctly?" msgstr "" -#: ../../general/base_import/import_faq.rst:66 +#: ../../general/base_import/import_faq.rst:115 msgid "" "By default the Import preview is set on commas as field separators and " "quotation marks as text delimiters. If your csv file does not have these " @@ -238,20 +370,20 @@ msgid "" " CSV file bar after you select your file)." msgstr "" -#: ../../general/base_import/import_faq.rst:68 +#: ../../general/base_import/import_faq.rst:117 msgid "" "Note that if your CSV file has a tabulation as separator, Odoo will not " "detect the separations. You will need to change the file format options in " "your spreadsheet application. See the following question." msgstr "" -#: ../../general/base_import/import_faq.rst:73 +#: ../../general/base_import/import_faq.rst:122 msgid "" "How can I change the CSV file format options when saving in my spreadsheet " "application?" msgstr "" -#: ../../general/base_import/import_faq.rst:75 +#: ../../general/base_import/import_faq.rst:124 msgid "" "If you edit and save CSV files in speadsheet applications, your computer's " "regional settings will be applied for the separator and delimiter. We " @@ -260,17 +392,17 @@ msgid "" "filter settings' > Save)." msgstr "" -#: ../../general/base_import/import_faq.rst:77 +#: ../../general/base_import/import_faq.rst:126 msgid "" "Microsoft Excel will allow you to modify only the encoding when saving (in " "'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)." msgstr "" -#: ../../general/base_import/import_faq.rst:82 +#: ../../general/base_import/import_faq.rst:131 msgid "What's the difference between Database ID and External ID?" msgstr "" -#: ../../general/base_import/import_faq.rst:84 +#: ../../general/base_import/import_faq.rst:133 msgid "" "Some fields define a relationship with another object. For example, the " "country of a contact is a link to a record of the 'Country' object. When you" @@ -280,58 +412,58 @@ msgid "" "import." msgstr "" -#: ../../general/base_import/import_faq.rst:86 +#: ../../general/base_import/import_faq.rst:135 msgid "" "For example, to reference the country of a contact, Odoo proposes you 3 " "different fields to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:88 +#: ../../general/base_import/import_faq.rst:137 msgid "Country: the name or code of the country" msgstr "国家：国家的名称或代码" -#: ../../general/base_import/import_faq.rst:89 +#: ../../general/base_import/import_faq.rst:138 msgid "" "Country/Database ID: the unique Odoo ID for a record, defined by the ID " "postgresql column" msgstr "" -#: ../../general/base_import/import_faq.rst:90 +#: ../../general/base_import/import_faq.rst:139 msgid "" "Country/External ID: the ID of this record referenced in another application" " (or the .XML file that imported it)" msgstr "" -#: ../../general/base_import/import_faq.rst:92 +#: ../../general/base_import/import_faq.rst:141 msgid "For the country Belgium, you can use one of these 3 ways to import:" msgstr "" -#: ../../general/base_import/import_faq.rst:94 +#: ../../general/base_import/import_faq.rst:143 msgid "Country: Belgium" msgstr "国家: 比利时" -#: ../../general/base_import/import_faq.rst:95 +#: ../../general/base_import/import_faq.rst:144 msgid "Country/Database ID: 21" msgstr "" -#: ../../general/base_import/import_faq.rst:96 +#: ../../general/base_import/import_faq.rst:145 msgid "Country/External ID: base.be" msgstr "Country/External ID: base.be" -#: ../../general/base_import/import_faq.rst:98 +#: ../../general/base_import/import_faq.rst:147 msgid "" "According to your need, you should use one of these 3 ways to reference " "records in relations. Here is when you should use one or the other, " "according to your need:" msgstr "" -#: ../../general/base_import/import_faq.rst:100 +#: ../../general/base_import/import_faq.rst:149 msgid "" "Use Country: This is the easiest way when your data come from CSV files that" " have been created manually." msgstr "" -#: ../../general/base_import/import_faq.rst:101 +#: ../../general/base_import/import_faq.rst:150 msgid "" "Use Country/Database ID: You should rarely use this notation. It's mostly " "used by developers as it's main advantage is to never have conflicts (you " @@ -339,13 +471,13 @@ msgid "" "Database ID)" msgstr "" -#: ../../general/base_import/import_faq.rst:102 +#: ../../general/base_import/import_faq.rst:151 msgid "" "Use Country/External ID: Use External ID when you import data from a third " "party application." msgstr "" -#: ../../general/base_import/import_faq.rst:104 +#: ../../general/base_import/import_faq.rst:153 msgid "" "When you use External IDs, you can import CSV files with the \"External ID\"" " column to define the External ID of each record you import. Then, you will " @@ -354,23 +486,23 @@ msgid "" "Products and their Categories." msgstr "" -#: ../../general/base_import/import_faq.rst:106 +#: ../../general/base_import/import_faq.rst:155 msgid "" "`CSV file for categories " "<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:108 +#: ../../general/base_import/import_faq.rst:157 msgid "" "`CSV file for Products " "<../../_static/example_files/External_id_3rd_party_application_products.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:112 +#: ../../general/base_import/import_faq.rst:161 msgid "What can I do if I have multiple matches for a field?" msgstr "如果我有多对一的字段怎么做？" -#: ../../general/base_import/import_faq.rst:114 +#: ../../general/base_import/import_faq.rst:163 msgid "" "If for example you have two product categories with the child name " "\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " @@ -381,20 +513,20 @@ msgid "" "the duplicates' values or your product category hierarchy." msgstr "" -#: ../../general/base_import/import_faq.rst:116 +#: ../../general/base_import/import_faq.rst:165 msgid "" "However if you do not wish to change your configuration of product " "categories, we recommend you use make use of the external ID for this field " "'Category'." msgstr "" -#: ../../general/base_import/import_faq.rst:121 +#: ../../general/base_import/import_faq.rst:170 msgid "" "How can I import a many2many relationship field (e.g. a customer that has " "multiple tags)?" msgstr "" -#: ../../general/base_import/import_faq.rst:123 +#: ../../general/base_import/import_faq.rst:172 msgid "" "The tags should be separated by a comma without any spacing. For example, if" " you want your customer to be linked to both tags 'Manufacturer' and " @@ -402,19 +534,19 @@ msgid "" " of your CSV file." msgstr "" -#: ../../general/base_import/import_faq.rst:125 +#: ../../general/base_import/import_faq.rst:174 msgid "" "`CSV file for Manufacturer, Retailer " "<../../_static/example_files/m2m_customers_tags.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:130 +#: ../../general/base_import/import_faq.rst:179 msgid "" "How can I import a one2many relationship (e.g. several Order Lines of a " "Sales Order)?" msgstr "" -#: ../../general/base_import/import_faq.rst:132 +#: ../../general/base_import/import_faq.rst:181 msgid "" "If you want to import sales order having several order lines; for each order" " line, you need to reserve a specific row in the CSV file. The first order " @@ -425,41 +557,41 @@ msgid "" "you can import, based on demo data." msgstr "" -#: ../../general/base_import/import_faq.rst:135 +#: ../../general/base_import/import_faq.rst:184 msgid "" "`File for some Quotations " "<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:137 +#: ../../general/base_import/import_faq.rst:186 msgid "" "The following CSV file shows how to import purchase orders with their " "respective purchase order lines:" msgstr "" -#: ../../general/base_import/import_faq.rst:139 +#: ../../general/base_import/import_faq.rst:188 msgid "" "`Purchase orders with their respective purchase order lines " "<../../_static/example_files/o2m_purchase_order_lines.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:141 +#: ../../general/base_import/import_faq.rst:190 msgid "" "The following CSV file shows how to import customers and their respective " "contacts:" msgstr "" -#: ../../general/base_import/import_faq.rst:143 +#: ../../general/base_import/import_faq.rst:192 msgid "" "`Customers and their respective contacts " "<../../_static/example_files/o2m_customers_contacts.csv>`_." msgstr "" -#: ../../general/base_import/import_faq.rst:148 +#: ../../general/base_import/import_faq.rst:197 msgid "Can I import several times the same record?" msgstr "我可以导入多次相同的记录？" -#: ../../general/base_import/import_faq.rst:150 +#: ../../general/base_import/import_faq.rst:199 msgid "" "If you import a file that contains one of the column \"External ID\" or " "\"Database ID\", records that have already been imported will be modified " @@ -469,17 +601,17 @@ msgid "" "depending if it's new or not." msgstr "" -#: ../../general/base_import/import_faq.rst:152 +#: ../../general/base_import/import_faq.rst:201 msgid "" "This feature allows you to use the Import/Export tool of Odoo to modify a " "batch of records in your favorite spreadsheet application." msgstr "" -#: ../../general/base_import/import_faq.rst:157 +#: ../../general/base_import/import_faq.rst:206 msgid "What happens if I do not provide a value for a specific field?" msgstr "" -#: ../../general/base_import/import_faq.rst:159 +#: ../../general/base_import/import_faq.rst:208 msgid "" "If you do not set all fields in your CSV file, Odoo will assign the default " "value for every non defined fields. But if you set fields with empty values " @@ -487,11 +619,11 @@ msgid "" "assigning the default value." msgstr "" -#: ../../general/base_import/import_faq.rst:164 +#: ../../general/base_import/import_faq.rst:213 msgid "How to export/import different tables from an SQL application to Odoo?" msgstr "" -#: ../../general/base_import/import_faq.rst:166 +#: ../../general/base_import/import_faq.rst:215 msgid "" "If you need to import data from different tables, you will have to recreate " "relations between records belonging to different tables. (e.g. if you import" @@ -499,7 +631,7 @@ msgid "" "person and the company they work for)." msgstr "" -#: ../../general/base_import/import_faq.rst:168 +#: ../../general/base_import/import_faq.rst:217 msgid "" "To manage relations between tables, you can use the \"External ID\" " "facilities of Odoo. The \"External ID\" of a record is the unique identifier" @@ -509,7 +641,7 @@ msgid "" "'company_1', 'person_1' instead of '1')" msgstr "" -#: ../../general/base_import/import_faq.rst:170 +#: ../../general/base_import/import_faq.rst:219 msgid "" "As an example, suppose you have a SQL database with two tables you want to " "import: companies and persons. Each person belong to one company, so you " @@ -519,27 +651,27 @@ msgid "" "PostgreSQL database</a>)" msgstr "" -#: ../../general/base_import/import_faq.rst:172 +#: ../../general/base_import/import_faq.rst:221 msgid "" "We will first export all companies and their \"External ID\". In PSQL, write" " the following command:" msgstr "" -#: ../../general/base_import/import_faq.rst:178 +#: ../../general/base_import/import_faq.rst:227 msgid "This SQL command will create the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:185 +#: ../../general/base_import/import_faq.rst:234 msgid "" "To create the CSV file for persons, linked to companies, we will use the " "following SQL command in PSQL:" msgstr "" -#: ../../general/base_import/import_faq.rst:191 +#: ../../general/base_import/import_faq.rst:240 msgid "It will produce the following CSV file::" msgstr "" -#: ../../general/base_import/import_faq.rst:199 +#: ../../general/base_import/import_faq.rst:248 msgid "" "As you can see in this file, Fabien and Laurence are working for the Bigees " "company (company_1) and Eric is working for the Organi company. The relation" @@ -549,7 +681,7 @@ msgid "" " who shared the same ID 1 in the orignial database)." msgstr "" -#: ../../general/base_import/import_faq.rst:201 +#: ../../general/base_import/import_faq.rst:250 msgid "" "The two files produced are ready to be imported in Odoo without any " "modifications. After having imported these two CSV files, you will have 4 " diff --git a/locale/zh_CN/LC_MESSAGES/inventory.po b/locale/zh_CN/LC_MESSAGES/inventory.po index be31f6e75..f1edcccf5 100644 --- a/locale/zh_CN/LC_MESSAGES/inventory.po +++ b/locale/zh_CN/LC_MESSAGES/inventory.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: 苏州远鼎 <tiexinliu@126.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" @@ -748,16 +748,28 @@ msgstr "" "最小库存规则的配置是在菜单项 :menuselection:`库存(Inventory) --> 存货控制(Inventory Control) -->" " 再定点规则(Reordering Rule)` 的下拉菜单中。然后点击 **创建** 去设置给定产品最小和最大库存数值。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Active" +msgstr "有效" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "If the active field is set to False, it will allow you to hide the " "orderpoint without removing it." msgstr "如果没有选中“可用”字段，那么将隐藏需求单记录且不会删除它。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "单位" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "Default Unit of Measure used for all stock operation." msgstr "所有库存作业的默认计量单位" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "补货组" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Moves created through this orderpoint will be put in this procurement group." @@ -765,6 +777,10 @@ msgid "" "into one big picking." msgstr "通过此订购点创建的移动将放在此补货组中。如果没有被提供，由补货规则生成的移动将被组合到一个大分拣。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "最小数量" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity specified for this field," @@ -772,6 +788,10 @@ msgid "" "Quantity." msgstr "当虚拟库存小于指定的最小数量，Odoo生成补货将预测数量带到最大数量。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "最大数量" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "When the virtual stock goes below the Min Quantity, Odoo generates a " @@ -779,12 +799,20 @@ msgid "" "Max Quantity." msgstr "当虚拟库存低于最小数量， Odoo生成补货将预测数量带到最大数量。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "数量倍数" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "The procurement quantity will be rounded up to this multiple. If it is 0, " "the exact quantity will be used." msgstr "补货数量会翻转到此倍数。 如果它是0, 那么确切的数量会被使用。" +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "前置时间" + #: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 msgid "" "Number of days after the orderpoint is triggered to receive the products or " diff --git a/locale/zh_CN/LC_MESSAGES/legal.po b/locale/zh_CN/LC_MESSAGES/legal.po deleted file mode 100644 index 75f1d9191..000000000 --- a/locale/zh_CN/LC_MESSAGES/legal.po +++ /dev/null @@ -1,2021 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Wei \"oldrev\" Li <liwei@sandwych.com>, 2017\n" -"Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: zh_CN\n" -"Plural-Forms: nplurals=1; plural=0;\n" - -#: ../../legal.rst:5 -msgid "Legal" -msgstr "" - -#: ../../legal.rst:15 ../../legal/licenses.rst:5 -#: ../../legal/licenses/licenses.rst:6 -msgid "Licenses" -msgstr "" - -#: ../../legal.rst:17 -msgid ":ref:`licenses`" -msgstr "" - -#: ../../legal.rst:20 ../../legal/terms.rst:5 -msgid "Terms and Conditions" -msgstr "条款和条件" - -#: ../../legal.rst:38 -msgid ":ref:`enterprise_agreement` |nbsp| |nbsp| |download_enterprise|" -msgstr "" - -#: ../../legal.rst:40 -msgid ":ref:`enterprise_agreement_fr` |nbsp| |nbsp| |download_enterprise_fr|" -msgstr "" - -#: ../../legal.rst:47 ../../legal/others.rst:5 -msgid "Other legal references" -msgstr "" - -#: ../../legal.rst:49 -msgid "" -"`Odoo Online Service Level Agreement <https://www.odoo.com/page/odoo-online-" -"sla>`_" -msgstr "" - -#: ../../legal.rst:50 -msgid "" -"`Odoo Online Acceptable Use Policy <https://www.odoo.com/page/odoo-online-" -"acceptable-use-policy>`_" -msgstr "" - -#: ../../legal.rst:51 -msgid ":ref:`cla`" -msgstr "" - -#: ../../legal/licenses/licenses.rst:11 -msgid "Odoo 10 Community Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:13 -msgid "" -"Odoo 10 Community Edition is licensed under `LGPL version 3 " -"<http://www.gnu.org/licenses/lgpl-3.0.en.html>`_ (also known as LGPLv3). " -"See also the `GPL FAQ <http://www.gnu.org/licenses/gpl-faq.en.html>`_ and " -"the `compatibility matrix <http://www.gnu.org/licenses/gpl-" -"faq.en.html#AllCompatibility>`_." -msgstr "" - -#: ../../legal/licenses/licenses.rst:22 -msgid "Odoo 10 Enterprise Edition" -msgstr "" - -#: ../../legal/licenses/licenses.rst:24 -msgid "" -"Odoo 10 Enterprise Edition is licensed under the Odoo Enterprise Edition " -"License v1.0, defined as follows:" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:1 -#: ../../legal/terms/i18n/enterprise_fr.rst:487 -msgid "Odoo Enterprise Edition License v1.0" -msgstr "Odoo 企业版授权协议 v1.0" - -#: ../../legal/licenses/enterprise_license.txt:3 -msgid "" -"This software and associated files (the \"Software\") can only be used " -"(executed, modified, executed after modifications) with a valid Odoo " -"Enterprise Subscription for the correct number of users." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:7 -msgid "" -"With a valid Partnership Agreement with Odoo S.A., the above permissions are" -" also granted, as long as the usage is limited to a testing or development " -"environment." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:11 -msgid "" -"You may develop Odoo modules based on the Software and distribute them under" -" the license of your choice, provided that it is compatible with the terms " -"of the Odoo Enterprise Edition License (For example: LGPL, MIT, or " -"proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:16 -msgid "" -"You may use Odoo modules published under any license along with the " -"Software, provided that their license is compatible with the terms of the " -"Odoo Enterprise License (Including, but not limited to, any module published" -" on the Odoo Apps Store on odoo.com/apps)" -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:21 -#: ../../legal/licenses/licenses.rst:69 -msgid "" -"It is forbidden to publish, distribute, sublicense, or sell copies of the " -"Software or modified copies of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:24 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/enterprise_license.txt:27 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE" -" AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM," -" OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN " -"THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:43 -msgid "Odoo Apps" -msgstr "" - -#: ../../legal/licenses/licenses.rst:45 -msgid "" -"Unless otherwise stated, Odoo Apps by Odoo SA (including the website themes)" -" are published under the Odoo Proprietary License v1.0, defined as follows" -msgstr "" - -#: ../../legal/licenses/licenses.rst:54 -msgid "Odoo Proprietary License v1.0" -msgstr "" - -#: ../../legal/licenses/licenses.rst:56 -msgid "" -"This software and associated files (the \"Software\") may only be used " -"(executed, modified, executed after modifications) if you have purchased a " -"valid license from the authors, typically via Odoo Apps, or if you have " -"received a written agreement from the authors of the Software (see the " -"COPYRIGHT file)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:62 -msgid "" -"You may develop Odoo modules that use the Software as a library (typically " -"by depending on it, importing it and using its resources), but without " -"copying any source code or material from the Software. You may distribute " -"those modules under the license of your choice, provided that this license " -"is compatible with the terms of the Odoo Proprietary License (For example: " -"LGPL, MIT, or proprietary licenses similar to this one)." -msgstr "" - -#: ../../legal/licenses/licenses.rst:72 -msgid "" -"The above copyright notice and this permission notice must be included in " -"all copies or substantial portions of the Software." -msgstr "" - -#: ../../legal/licenses/licenses.rst:75 -msgid "" -"THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR" -" IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " -"FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " -"AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " -"LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " -"FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS" -" IN THE SOFTWARE." -msgstr "" - -#: ../../legal/licenses/licenses.rst:91 -msgid "Odoo 9" -msgstr "" - -#: ../../legal/licenses/licenses.rst:93 -msgid "" -"The licenses for both editions of Odoo 9 were respectively the same as for " -":ref:`odoo_community_license` and :ref:`odoo_enterprise_license`." -msgstr "" - -#: ../../legal/licenses/licenses.rst:100 -msgid "Odoo 8" -msgstr "" - -#: ../../legal/licenses/licenses.rst:102 -msgid "" -"Odoo 8 is licensed under `AGPL version 3 " -"<http://www.gnu.org/licenses/agpl-3.0.en.html>`_ (also known as AGPLv3). " -"See also the `GPL FAQ <http://www.gnu.org/licenses/gpl-faq.en.html>`_ and " -"the `compatibility matrix <http://www.gnu.org/licenses/gpl-" -"faq.en.html#AllCompatibility>`_." -msgstr "" - -#: ../../legal/others/cla.rst:5 -msgid "Contributor License Agreement" -msgstr "" - -#: ../../legal/others/cla.rst:7 -msgid "" -"In order to contribute to any of the Odoo projects, companies and " -"individuals have to sign the Odoo Contributor License Agreement (CLA)." -msgstr "" - -#: ../../legal/others/cla.rst:10 -msgid "" -"More information about this requirement, the procedure to sign the " -"agreement, and a FAQ can be found on our `GitHub project page " -"<https://github.com/odoo/odoo/blob/8.0/doc/cla/sign-cla.md>`_." -msgstr "" - -#: ../../legal/others/privacy.rst:5 -msgid "Privacy Policy" -msgstr "" - -#: ../../legal/others/privacy.rst:7 -msgid "" -"Temporary version at `<https://www.odoo.com/page/odoo-privacy-policy>`__ " -"(needs cleanup)" -msgstr "" - -#: ../../legal/terms/enterprise.rst:6 -msgid "Odoo Enterprise Subscription Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:8 -msgid "Version 5b - Last revision: June 30, 2016." -msgstr "" - -#: ../../legal/terms/enterprise.rst:10 -msgid "" -"By subscribing to the Odoo Enterprise services (the \"Services\") provided " -"by Odoo SA and its affiliates (collectively, \"Odoo SA\") in relation with " -"Odoo Enterprise Edition or Odoo Community Edition (the \"Software\"), you " -"(the \"Customer\") are agreeing to be bound by the following terms and " -"conditions (the \"Agreement\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:18 -msgid "1 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/enterprise.rst:20 -msgid "" -"The duration of this Agreement (the “Term”) shall be minimally one year and " -"as specified in writing at the signature of this Agreement, beginning on the" -" date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term by registered mail to the other party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:28 -msgid "2 Definitions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:34 -msgid "User" -msgstr "用户" - -#: ../../legal/terms/enterprise.rst:31 -msgid "" -"Any active user account with access to the Software in creation and/or " -"edition mode. Deactivated user accounts and accounts used by external people" -" (or systems) who only have limited access to the Software through the " -"portal facilities (known as \"portal Users\") are not counted as Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:42 -#: ../../legal/terms/i18n/enterprise_fr.rst:55 -msgid "Bug" -msgstr "" - -#: ../../legal/terms/enterprise.rst:37 -msgid "" -"Is considered a Bug any failure of the Software that results in a complete " -"stop, error traceback or security breach, and is not directly caused by a " -"defective installation or configuration. Non-compliance with specifications " -"or requirements will be considered as Bugs at the discretion of Odoo SA " -"(typically, when the Software does not produce the results or performance it" -" was designed to produce, or when a country-specific feature does not meet " -"legal accounting requirements anymore)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:51 -msgid "Covered Versions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:45 -msgid "" -"All Services provided under this Agreement are applicable only to the " -"Covered Versions of the Software, which include the 3 (three) most recently " -"released major versions." -msgstr "" - -#: ../../legal/terms/enterprise.rst:48 -msgid "" -"To be covered by the current Agreement, Customer’s installations have to run" -" the most recent Covered Version at the time of this Agreement’s signature. " -"When this is not the case, additional costs are applicable, as described in " -":ref:`charges`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:56 ../../legal/terms/partnership.rst:42 -msgid "3 Access to Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/enterprise.rst:58 -msgid "" -"For the duration of this Agreement, Odoo SA gives the Customer a non-" -"exclusive, non-transferable license to use (execute, modify, execute after " -"modification) the Odoo Enterprise Edition software, under the terms set " -"forth in :ref:`appendix_a`." -msgstr "" - -#: ../../legal/terms/enterprise.rst:62 -msgid "" -"The Customer agrees to take all necessary measures to guarantee the " -"unmodified execution of the part of the Software that verifies the validity " -"of the Odoo Enterprise Edition usage and collects statistics for that " -"purpose, including but not limited to the running of an instance and the " -"number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:67 -msgid "" -"Odoo SA commits not to disclose individual or named figures to third parties" -" without the consent of the Customer, and to deal with all collected data in" -" compliance with its official Privacy Policy, as published on `Odoo SA's " -"website <https://www.odoo.com>`_." -msgstr "" - -#: ../../legal/terms/enterprise.rst:71 -msgid "" -"Upon expiration or termination of this Agreement, this license is revoked " -"immediately and the Customer agrees to stop using the Odoo Enterprise " -"Edition software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:74 -msgid "" -"Should the Customer breach the terms of this section, the Customer agrees to" -" pay Odoo SA an extra fee equal to 300% of the applicable list price for the" -" actual number of Users." -msgstr "" - -#: ../../legal/terms/enterprise.rst:81 -msgid "4 Included Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:84 -msgid "4.1 Bug Fixing Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:86 -msgid "" -"For the duration of this Agreement, Odoo SA commits to making all reasonable" -" efforts to remedy any Bug of the Software submitted by the Customer through" -" the appropriate channel (typically, Odoo SA's service desk email address or" -" website form), and to start handling such Customer submissions within 2 " -"business days." -msgstr "" - -#: ../../legal/terms/enterprise.rst:91 -msgid "" -"The Customer understands that Bugs caused by a modification or extension " -"that is not part of the official Software will not be covered by this " -"service." -msgstr "" - -#: ../../legal/terms/enterprise.rst:94 -msgid "" -"As soon as the Bug is fixed an appropriate remedy will be communicated to " -"the Customer. If the bug has been addressed in a more recent revision of the" -" Covered Version of the Software used by the Customer, the Customer agrees " -"to update its systems to that revision in order to obtain the correction. " -"The Customer will not be asked to upgrade to a more recent Covered Version " -"of the Software as a remedy to a Bug." -msgstr "" - -#: ../../legal/terms/enterprise.rst:100 -msgid "" -"When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the " -"Bug in all more recent Covered Versions of the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:103 -msgid "" -"Both parties acknowledge that as specified in the license of the Software " -"and in the :ref:`liability` section of this Agreement, Odoo SA cannot be " -"held liable for Bugs in the Software." -msgstr "" - -#: ../../legal/terms/enterprise.rst:108 -msgid "4.2 Security Advisories Service" -msgstr "" - -#: ../../legal/terms/enterprise.rst:110 -msgid "" -"For the duration of this Agreement, Odoo SA commits to sending a \"Security " -"Advisory\" to the Customer for any security Bug that are discovered in the " -"Covered Versions of the Software, at least 2 weeks before making the " -"Security Advisory public, unless the Bug has already been disclosed publicly" -" by a third party. Security Advisories include a complete description of the" -" Bug, its cause, its possible impacts on the Customer's systems, and the " -"corresponding remedy for each Covered Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:117 -msgid "" -"The Customer understands that the Bug and the information in the Security " -"Advisory must be treated are Confidential Information as described in " -":ref:`confidentiality` during the embargo period prior to the public " -"disclosure." -msgstr "" - -#: ../../legal/terms/enterprise.rst:124 -msgid "4.3 Upgrade Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:129 -msgid "Upgrade Service for the Software" -msgstr "" - -#: ../../legal/terms/enterprise.rst:131 -msgid "" -"For the duration of this Agreement, the Customer can submit upgrade requests" -" through the appropriate channel (typically Odoo SA's upgrade service " -"website), in order to convert a database of the Software from one Covered " -"Version of the Software to a more recent Covered Version (the \"Target " -"Version\")." -msgstr "" - -#: ../../legal/terms/enterprise.rst:135 -msgid "" -"Upgrade requests must include a complete backup copy of the Customer's " -"database and the associated data (typically obtained from the Backup menu of" -" the Software). Where necessary for data security or regulation reasons, the" -" Upgrade Service includes an optional tool to anonymize identifiable data " -"inside a database before submitting the upgrade request, and a tool to " -"restore the anonymized data after the upgrade." -msgstr "" - -#: ../../legal/terms/enterprise.rst:141 -msgid "" -"This service provided through an automated platform in order to allow the " -"Customer to perform unattended upgrades once a previous version of the " -"Customer's database has been successfully upgraded for a Covered Version. " -"The Customer may submit successive upgrade requests for a database, and " -"agrees to submit at least 1 upgrade request for testing purposes before " -"submitting the final upgrade request." -msgstr "" - -#: ../../legal/terms/enterprise.rst:147 -msgid "" -"The Upgrade Service is limited to the technical conversion and adaptation of" -" the Customer's database to make it compatible with the Target Version, and " -"the correction of any Bug directly caused by the upgrade operation and not " -"normally occurring in the Target Version." -msgstr "" - -#: ../../legal/terms/enterprise.rst:151 -msgid "" -"It is the sole responsibility of the Customer to verify and validate the " -"upgraded database in order to detect Bugs, to analyze the impact of changes " -"and new features implemented in the Target Version, and to convert and adapt" -" for the Target Version any third-party extensions of the Software that were" -" installed in the database before the upgrade (except where applicable as " -"foreseen in section :ref:`upgrade_extra`). The Customer may submit multiple " -"upgrade requests for a database, until an acceptable result is achieved." -msgstr "" - -#: ../../legal/terms/enterprise.rst:162 -msgid "Upgrade Service for third-party extensions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:164 -msgid "" -"For the duration of this Agreement, the Customer may request optional " -"upgrade services for third-party extension modules of the Software, in " -"addition to the regular Upgrade Services. This optional service is subject " -"to additional fees (as described in charges_) and includes the technical " -"adaptation of third-party modules installed in the Customer's database and " -"their corresponding data in order to be compatible with the Target Version. " -"The Customer will receive an upgraded version of all installed third-party " -"modules along with the upgraded database." -msgstr "" - -#: ../../legal/terms/enterprise.rst:174 -msgid "5 Charges and Fees" -msgstr "" - -#: ../../legal/terms/enterprise.rst:179 -msgid "5.1 Standard charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:181 -msgid "" -"The standard charges for the Odoo Enterprise subscription, the Bug Fixing " -"Service, Security Advisories Service and the Upgrade Service are based on " -"the number of Users and the Software version used by the Customer, and " -"specified in writing at the signature of the Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:185 -msgid "" -"When during the Term, the Customer has more Users than specified at the time" -" of signature of this Agreement, the Customer agrees to pay an extra fee " -"equivalent to the applicable list price (at the beginning of the Term) for " -"the additional Users, for the remainder of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:189 -msgid "" -"If at the time of the signature of this Agreement, the Customer uses a " -"Covered Version that is not the most recent one, the standard charges will " -"be increased by 50% for the duration of the first Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:196 -msgid "5.2 Renewal charges" -msgstr "" - -#: ../../legal/terms/enterprise.rst:198 -msgid "" -"Upon renewal as covered in section :ref:`term`, if the per-User charges " -"applied during the previous Term are lower than the most current applicable " -"per-User list price, the per-User charges will increase by up to 7%, unless " -"Odoo SA provides written notice of a new price to the Customer at least 60 " -"days prior to the end of the Term." -msgstr "" - -#: ../../legal/terms/enterprise.rst:207 -msgid "5.3 Charges for Upgrade Services of third-party modules" -msgstr "" - -#: ../../legal/terms/enterprise.rst:211 -msgid "" -"The additional charge for the Upgrade Service for third-party modules is EUR" -" (€) 1000.00 (one thousand euros) per 1000 Lines of Code in the third-party " -"modules, rounded up to the next thousand lines. Lines of Code include all " -"text lines in the source code of those modules, regardless of the " -"programming language (Python, Javascript, etc.) or data format (XML, CSV, " -"etc.), excluding blank lines and comment lines." -msgstr "" - -#: ../../legal/terms/enterprise.rst:217 -msgid "" -"Odoo SA reserves the right to reject an upgrade request for third-party " -"modules under the above conditions if the quality of the source code of " -"those modules is too low, or if these modules constitute an interface with " -"third-party software or systems. The upgrade of such modules will subject to" -" a separate offer, outside of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:225 -msgid "5.4 Taxes" -msgstr "" - -#: ../../legal/terms/enterprise.rst:229 -msgid "" -"All fees and charges are exclusive of all applicable federal, provincial, " -"state, local or other governmental taxes, fees or charges (collectively, " -"\"Taxes\"). The Customer is responsible for paying all Taxes associated with" -" purchases made by the Customer under this Agreement, except when Odoo SA is" -" legally obliged to pay or collect Taxes for which the Customer is " -"responsible." -msgstr "" - -#: ../../legal/terms/enterprise.rst:238 -msgid "6 Conditions of Services" -msgstr "" - -#: ../../legal/terms/enterprise.rst:241 -msgid "6.1 Customer Obligations" -msgstr "" - -#: ../../legal/terms/enterprise.rst:245 -msgid "The Customer agrees to:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:247 -msgid "" -"pay Odoo SA any applicable charges for the Services of the present " -"Agreement, in accordance with the payment conditions specified in the " -"corresponding invoice ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:249 -msgid "" -"immediately notify Odoo SA when the actual number of Users exceeds the " -"number of Users specified at the signature of the Agreement, and in this " -"event, pay the applicable additional fee as described in section " -":ref:`charges_standard`;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:252 -msgid "" -"take all measures necessary to guarantee the unmodified execution of the " -"part of the Software that verifies the validity of the Odoo Enterprise " -"Edition usage, as described in :ref:`enterprise_access` ;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:255 -msgid "" -"grant Odoo SA the necessary access to verify the validity of the Odoo " -"Enterprise Edition usage upon request (e.g. if the automatic validation is " -"found to be inoperant for the Customer);" -msgstr "" - -#: ../../legal/terms/enterprise.rst:257 -msgid "" -"appoint 1 dedicated Customer contact person for the entire duration of the " -"Agreement;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:258 -msgid "" -"take all reasonable measures to protect Customer’s files and databases and " -"to ensure Customer’s data is safe and secure, acknowledging that Odoo SA " -"cannot be held liable for any data loss;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:265 -msgid "6.2 No Soliciting or Hiring" -msgstr "" - -#: ../../legal/terms/enterprise.rst:267 -msgid "" -"Except where the other party gives its consent in writing, each party, its " -"affiliates and representatives agree not to solicit or offer employment to " -"any employee of the other party who is involved in performing or using the " -"Services under this Agreement, for the duration of the Agreement and for a " -"period of 12 months from the date of termination or expiration of this " -"Agreement. In case of any breach of the conditions of this section that " -"leads to the termination of said employee toward that end, the breaching " -"party agrees to pay to the other party an amount of EUR (€) 30 000.00 " -"(thirty thousand euros)." -msgstr "" - -#: ../../legal/terms/enterprise.rst:279 -msgid "6.3 Publicity" -msgstr "" - -#: ../../legal/terms/enterprise.rst:281 -msgid "" -"Except where notified otherwise in writing, each party grants the other a " -"non-transferable, non-exclusive, royalty free, worldwide license to " -"reproduce and display the other party’s name, logos and trademarks, solely " -"for the purpose of referring to the other party as a customer or supplier, " -"on websites, press releases and other marketing materials." -msgstr "" - -#: ../../legal/terms/enterprise.rst:290 -msgid "6.4 Confidentiality" -msgstr "" - -#: ../../legal/terms/enterprise.rst:298 -msgid "Definition of \"Confidential Information\":" -msgstr "" - -#: ../../legal/terms/enterprise.rst:293 -msgid "" -"All information disclosed by a party (the \"Disclosing Party\") to the other" -" party (the \"Receiving Party\"), whether orally or in writing, that is " -"designated as confidential or that reasonably should be understood to be " -"confidential given the nature of the information and the circumstances of " -"disclosure. In particular any information related to the business, affairs, " -"products, developments, trade secrets, know-how, personnel, customers and " -"suppliers of either party should be regarded as confidential." -msgstr "" - -#: ../../legal/terms/enterprise.rst:300 -msgid "" -"For all Confidential Information received during the Term of this Agreement," -" the Receiving Party will use the same degree of care that it uses to " -"protect the confidentiality of its own similar Confidential Information, but" -" not less than reasonable care." -msgstr "" - -#: ../../legal/terms/enterprise.rst:304 -msgid "" -"The Receiving Party may disclose Confidential Information of the Disclosing " -"Party to the extent compelled by law to do so, provided the Receiving Party " -"gives the Disclosing Party prior notice of the compelled disclosure, to the " -"extent permitted by law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:311 -msgid "6.5 Termination" -msgstr "" - -#: ../../legal/terms/enterprise.rst:313 -msgid "" -"In the event that either Party fails to fulfill any of its obligations " -"arising herein, and if such breach has not been remedied within 30 calendar " -"days from the written notice of such breach, this Agreement may be " -"terminated immediately by the non-breaching Party." -msgstr "" - -#: ../../legal/terms/enterprise.rst:317 -msgid "" -"Further, Odoo SA may terminate the Agreement immediately in the event the " -"Customer fails to pay the applicable fees for the Services within the due " -"date specified on the corresponding invoice." -msgstr "" - -#: ../../legal/terms/enterprise.rst:324 -msgid "Surviving Provisions:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:321 -msgid "" -"The sections \":ref:`confidentiality`”, “:ref:`disclaimers`”, " -"“:ref:`liability`”, and “:ref:`general_provisions`” will survive any " -"termination or expiration of this Agreement." -msgstr "" - -#: ../../legal/terms/enterprise.rst:329 -msgid "7 Warranties, Disclaimers, Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:334 -msgid "7.1 Warranties" -msgstr "" - -#: ../../legal/terms/enterprise.rst:338 -msgid "" -"For the duration of this Agreement, Odoo SA commits to using commercially " -"reasonable efforts to execute the Services in accordance with the generally " -"accepted industry standards provided that:" -msgstr "" - -#: ../../legal/terms/enterprise.rst:341 -msgid "" -"the Customer’s computing systems are in good operational order and the " -"Software is installed in a suitable operating environment;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:343 -msgid "" -"the Customer provides adequate troubleshooting information and access so " -"that Odoo SA can identify, reproduce and address problems;" -msgstr "" - -#: ../../legal/terms/enterprise.rst:345 -msgid "all amounts due to Odoo SA have been paid." -msgstr "" - -#: ../../legal/terms/enterprise.rst:347 -msgid "" -"The Customer's sole and exclusive remedy and Odoo SA's only obligation for " -"any breach of this warranty is for Odoo SA to resume the execution of the " -"Services at no additional charge." -msgstr "" - -#: ../../legal/terms/enterprise.rst:353 -msgid "7.2 Disclaimers" -msgstr "" - -#: ../../legal/terms/enterprise.rst:357 -msgid "" -"Except as expressly provided herein, neither party makes any warranty of any" -" kind, whether express, implied, statutory or otherwise, and each party " -"specifically disclaims all implied warranties, including any implied " -"warranty of merchantability, fitness for a particular purpose or non-" -"infringement, to the maximum extent permitted by applicable law." -msgstr "" - -#: ../../legal/terms/enterprise.rst:362 -msgid "" -"Odoo SA does not warrant that the Software complies with any local or " -"international law or regulations." -msgstr "" - -#: ../../legal/terms/enterprise.rst:367 -msgid "7.3 Limitation of Liability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:369 -msgid "" -"To the maximum extent permitted by law, the aggregate liability of each " -"party together with its affiliates arising out of or related to this " -"Agreement will not exceed 50% of the total amount paid by the Customer under" -" this Agreement during the 12 months immediately preceding the date of the " -"event giving rise to such claim. Multiple claims shall not enlarge this " -"limitation." -msgstr "" - -#: ../../legal/terms/enterprise.rst:374 -msgid "" -"In no event will either party or its affiliates be liable for any indirect, " -"special, exemplary, incidental or consequential damages of any kind, " -"including but not limited to loss of revenue, profits, savings, loss of " -"business or other financial loss, costs of standstill or delay, lost or " -"corrupted data, arising out of or in connection with this Agreement " -"regardless of the form of action, whether in contract, tort (including " -"strict negligence) or any other legal or equitable theory, even if a party " -"or its affiliates have been advised of the possibility of such damages, or " -"if a party or its affiliates' remedy otherwise fails of its essential " -"purpose." -msgstr "" - -#: ../../legal/terms/enterprise.rst:385 -#: ../../legal/terms/i18n/enterprise_fr.rst:418 -msgid "7.4 Force Majeure" -msgstr "" - -#: ../../legal/terms/enterprise.rst:387 -msgid "" -"Neither party shall be liable to the other party for the delay in any " -"performance or failure to render any performance under this Agreement when " -"such failure or delay is caused by governmental regulations, fire, strike, " -"war, flood, accident, epidemic, embargo, appropriation of plant or product " -"in whole or in part by any government or public authority, or any other " -"cause or causes, whether of like or different nature, beyond the reasonable " -"control of such party as long as such cause or causes exist." -msgstr "" - -#: ../../legal/terms/enterprise.rst:398 -msgid "8 General Provisions" -msgstr "" - -#: ../../legal/terms/enterprise.rst:403 -msgid "8.1 Governing Law" -msgstr "" - -#: ../../legal/terms/enterprise.rst:405 -msgid "" -"Both parties agree that the laws of Belgium will apply, should any dispute " -"arise out of or in connection with this Agreement, without regard to choice " -"or conflict of law principles. To the extent that any lawsuit or court " -"proceeding is permitted hereinabove, both parties agree to submit to the " -"sole jurisdiction of the Nivelles (Belgium) court for the purpose of " -"litigating all disputes." -msgstr "" - -#: ../../legal/terms/enterprise.rst:414 -msgid "8.2 Severability" -msgstr "" - -#: ../../legal/terms/enterprise.rst:416 -msgid "" -"In case any one or more of the provisions of this Agreement or any " -"application thereof shall be invalid, illegal or unenforceable in any " -"respect, the validity, legality and enforceability of the remaining " -"provisions of this Agreement and any application thereof shall be in no way " -"thereby affected or impaired. Both parties undertake to replace any invalid," -" illegal or unenforceable provision of this Agreement by a valid provision " -"having the same effects and objectives." -msgstr "" - -#: ../../legal/terms/enterprise.rst:427 -msgid "9 Appendix A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:6 -msgid "Odoo Enterprise Subscription Agreement (FR)" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:9 -msgid "" -"Ceci est une traduction en français du contrat “Odoo Enterprise Subscription" -" Agreement”. Cette traduction est fournie dans l’espoir qu’elle facilitera " -"sa compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes du contrat “Odoo Enterprise Subscription Agreement” " -"est la :ref:`version originale <enterprise_agreement>`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:15 -msgid "" -"This is a french translation of the \"Odoo Enterprise Subscription " -"Agreement”. This translation is provided in the hope that it will facilitate" -" understanding, but it has no legal value. The only official reference of " -"the terms and conditions of the “Odoo Enterprise Subscription Agreement” is " -"the :ref:`original english version <enterprise_agreement>`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:21 -msgid "Version 5b - Dernière modification: 30 juin 2016." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:23 -msgid "" -"En vous abonnant aux services de Odoo Enterprise (les \"Services\") fournis " -"par Odoo SA et ses filiales (collectivement, \"Odoo SA\") en relation avec " -"Odoo Enterprise Edition ou Odoo Community Edition (le \"Logiciel\"), vous " -"(le \"Client\") acceptez d'être lié par les conditions générales suivantes " -"(le \"Contrat\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:31 -msgid "1 Durée du Contrat" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:33 -msgid "" -"La durée du présent contrat (la \"Durée\") doit être au minimum d'un an et " -"telle que spécifiée par écrit à la signature du Contrat, à compter de la " -"date de la signature. Celui-ci est automatiquement reconduit pour une même " -"durée, à moins que l'une des parties n’envoie à l'autre partie un préavis " -"écrit de résiliation, par lettre recommandée, et au moins 30 jours avant la " -"date d'échéance du contrat ." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:41 -msgid "2 Définitions" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:47 -msgid "Utilisateur" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:44 -msgid "" -"Tout compte utilisateur actif donnant accès au Logiciel en mode création " -"et/ou édition. Les comptes désactivés ainsi que ceux utilisés par des " -"personnes ou systèmes extérieur(e)s n'ayant qu'un accès limité au Logiciel " -"via le portail (\"Utilisateurs Portail\") ne sont pas comptés comme " -"Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:50 -msgid "" -"Désigne toute défaillance du Logiciel qui se traduit par un arrêt complet, " -"un message d'erreur avec trace d'exécution, ou une brèche de sécurité, et " -"n'est pas directement causé par un problème d'installation ou une " -"configuration défectueuse. Un non-respect des spécifications ou des besoins " -"sera considéré comme un Bug à la discrétion d'Odoo SA (en général, lorsque " -"le Logiciel ne produit pas les résultats ou la performance pour lesquels il " -"a été conçu, ou lorsqu'une fonctionnalité spécifique à un pays ne répond " -"plus aux exigences comptables légales de ce pays)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:65 -msgid "Versions Couvertes" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:58 -msgid "" -"Tous les Services dans le cadre du présent contrat s'appliquent uniquement " -"aux Versions Couvertes du Logiciel, qui comprennent les trois (3) plus " -"récentes versions majeures." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:61 -msgid "" -"Afin d'être considérées comme couvertes par le Contrat, les installations du" -" client doivent utiliser la Version couverte la plus récente au moment de " -"la signature du Contrat. Dans le cas contraire, des frais supplémentaires " -"sont d'application, tels que décrit dans la section :ref:`charges_fr`" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:70 -msgid "3 Accès à Odoo Enterprise Edition" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:72 -msgid "" -"Pour toute la durée du présent Contrat, Odoo SA octroie au Client une " -"licence non exclusive, non transférable d'utilisation (exécution, " -"modification, exécution après modification) du logiciel Odoo Enterprise " -"Edition, conformément aux conditions énoncées à la section " -":ref:`appendix_a_fr`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:76 -msgid "" -"Le Client accepte de prendre toutes les mesures nécessaires pour garantir " -"l'exécution sans aucune modification de la partie du Logiciel qui vérifie la" -" validité de l'utilisation d'Odoo Enterprise Edition et recueille des " -"statistiques à cet effet, y compris mais sans s'y limiter, l'exécution du " -"Logiciel et le nombre d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:81 -msgid "" -"Odoo SA s'engage à ne pas divulguer à une tierce partie d'informations " -"chiffrées personnelles ou spécifiques sans le consentement du Client, et à " -"traiter toutes les données recueillies en respectant sa politique officielle" -" de confidentialité, telle que publiée sur `le site web d'Odoo SA " -"<https://www.odoo.com>`_." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:86 -msgid "" -"À l'expiration ou la résiliation de ce Contrat, cette licence est " -"immédiatement révoquée et le Client accepte de cesser toute utilisation du " -"logiciel Odoo Enterprise Edition." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:89 -msgid "" -"Si le Client devait enfreindre les dispositions de la présente section, il " -"accepte de payer à Odoo SA des frais supplémentaires équivalents à 300 % du " -"tarif en vigueur applicable correspondant au nombre réel d'Utilisateurs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:97 -msgid "4 Services inclus" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:100 -msgid "4.1 Service de correction de Bugs" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:102 -msgid "" -"Pour la durée de ce Contrat, Odoo SA s'engage à déployer tous les efforts " -"raisonnables pour corriger tout Bug du Logiciel qui pourrait être signalé " -"par le Client en suivant la procédure appropriée (généralement par le biais " -"d'un e-mail adressé au service d'assistance d'Odoo SA ou via le formulaire " -"correspondant sur le site web), et de commencer à traiter ces signalements " -"du Client dans un délai de 2 jours ouvrables." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:108 -msgid "" -"Le Client accepte que les Bugs causés par toute modification ou extension " -"qui ne fait pas partie de la version officielle du Logiciel ne seront pas " -"couverts par ce service." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:111 -msgid "" -"Dès que le Bug est remédié, un correctif approprié sera communiqué au " -"Client. Si le Bug a été résolu dans une nouvelle mise à jour de la Version " -"Couverte du Logiciel utilisée par le Client, ce dernier s'engage à " -"actualiser ses systèmes vers la nouvelle mise à jour, afin d'obtenir le " -"correctif. Il ne sera jamais demandé au Client de passer à une Version " -"Couverte plus récente pour obtenir un correctif." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:117 -msgid "" -"Lorsqu'un Bug est corrigé dans une Version Couverte, Odoo SA s'engage à le " -"corriger dans toutes les Versions Couvertes plus récentes du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:120 -msgid "" -"Les deux parties reconnaissent que comme spécifié dans la licence du " -"Logiciel et à la section :ref:`liability_fr` de ce Contrat, Odoo SA ne peut " -"être tenue responsable des Bugs du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:125 -msgid "4.2 Service d'alertes de sécurité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:127 -msgid "" -"Pour la durée du Contrat, Odoo SA s'engage à envoyer une \"alerte de " -"sécurité\"\" au Client pour tout Bug présentant un risque de sécurité qui " -"serait découvert dans les Versions Couvertes du Logiciel, au moins 2 " -"semaines avant de rendre ladite alerte de sécurité publique, et ce à moins " -"que le Bug ait déjà été rendu public par un tiers. Les alertes de sécurité " -"comprennent une description complète du Bug, de sa cause, ses conséquences " -"possibles sur les systèmes du Client, et le correctif correspondant pour " -"chaque Version Couverte." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:134 -msgid "" -"Le Client s'engage à traiter le Bug de sécurité et les informations figurant" -" dans l'alerte de sécurité comme des Informations Confidentielles telles que" -" décrites à la section :ref:`confidentiality_fr` pendant toute la période " -"d'embargo avant la divulgation publique." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:141 -msgid "4.3 Service de migration" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:146 -msgid "Service de migration du Logiciel" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:148 -msgid "" -"Pour la durée du présent Contrat, le Client peut soumettre des demandes de " -"migration en suivant les procédures appropriées (généralement, via le site " -"du service de migration d'Odoo SA), afin de convertir une base de données du" -" Logiciel d'une Version Couverte du Logiciel à une Version Couverte plus " -"récente (la \"Version Cible\")." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:153 -msgid "" -"Les demandes de migration doivent inclure une copie de sauvegarde complète " -"de la base de données du Client et les données associées (généralement " -"obtenues à partir du menu Backup du Logiciel). Lorsque cela est nécessaire " -"pour des raisons de sécurité des données ou de réglementation, le Service de" -" migration inclut un outil facultatif pour rendre anonymes les données " -"identifiables figurant dans la base de données, avant de soumettre la " -"demande de migration, et un outil pour restaurer les données rendues " -"anonymes après la migration." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:160 -msgid "" -"Ce service est fourni par le biais d'une plateforme automatisée, afin de " -"permettre au Client d'effectuer des migration sans intervention humain, dès " -"lors qu’une version précédente de la base de données du Client a été migrée " -"avec succès pour une Version Couverte donnée. Le client peut soumettre des " -"demandes de migration successives pour une base de données, et accepte de " -"soumettre au moins 1 demande de mifration de test avant de soumettre la " -"demande de migration finale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:167 -msgid "" -"Le service de migration est limité à la conversion et à l'adaptation " -"techniques de la base de données du Client pour la rendre compatible avec la" -" Version Cible, et à la correction de tout Bug directement causé par " -"l'opération de migration, et ne se produisant normalement pas dans la " -"Version Cible." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:172 -msgid "" -"Il incombe au Client de vérifier et valider la base de données migrée afin " -"de détecter tout Bug, d'analyser l'impact des changements et des nouvelles " -"fonctionnalités ajoutées dans la Version Cible, de convertir et d'adapter " -"pour la Version Cible les modules tiers du Logiciel qui auraient été " -"installées dans la base de données avant la migration (sauf le cas échéant, " -"comme prévu à la section :ref:`upgrade_extra_fr`). Le client peut soumettre " -"plusieurs demandes de migration pour une base de données, jusqu'à ce qu'un " -"résultat satisfaisant soit obtenu." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:183 -msgid "Service de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:185 -msgid "" -"Pour la durée du Contrat, le Client a la possibilité de faire une demande de" -" migration pour des modules d'extension tiers, en plus de la migration " -"normale du Logiciel. Ce service en option implique des frais supplémentaires" -" (décrits dans la section charges_fr_) et comprend l'adaptation technique " -"des modules tiers installés dans la base de données du Client et de leurs " -"données correspondantes afin qu'elles soient compatibles avec la Version " -"Cible. Le Client recevra une version migrée de tous les modules tiers " -"installés accompagnée de la base de données migrée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:196 -msgid "5 Tarifs et Frais" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:201 -msgid "5.1 Tarifs standards" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:203 -msgid "" -"Les tarifs standards pour le contrat d'abonnement à Odoo Enterprise, le " -"service de correction de Bugs, le service d'alertes de sécurité et le " -"service de migration sont basés sur le nombre d'Utilisateurs et la version " -"du Logiciel utilisée par le Client, et précisés par écrit à la signature du " -"contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:208 -msgid "" -"Pendant la durée du contrat, si le Client a plus d'Utilisateurs que spécifié" -" au moment de la signature du présent Contrat, le Client accepte de payer un" -" supplément équivalent au tarif en vigueur applicable (au début du Contrat) " -"pour les utilisateurs supplémentaires, pour le reste de la durée." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:213 -msgid "" -"Si, au moment de la signature du présent Contrat, le Client utilise une " -"Version Couverte qui n'est pas l'une des plus récentes, les tarifs standards" -" seront augmentés de 50% pour la première Durée du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:221 -msgid "5.2 Tarifs de reconduction" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:223 -msgid "" -"Lors de la reconduction telle que décrite à la section :ref:`term_fr`, si " -"les tarifs par Utilisateur qui ont été appliqués pendant la Durée précédente" -" sont inférieurs aux tarifs par Utilisateur en vigueur les plus récents, les" -" tarifs par Utilisateur augmenteront automatiquement de maximum 7%, à moins " -"qu'Odoo SA ne notifie par écrit un nouveau tarif au client, au moins 60 " -"jours avant l’échéance du contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:232 -msgid "5.3 Tarifs de migration des modules tiers" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:234 -msgid "" -"Les frais supplémentaires pour le service de migration des modules tiers " -"sont de 1000,00- euros (€) (mille euros) pour 1000 lignes de code de modules" -" tiers, le nombre de lignes étant arrondi au millier de lignes supérieur. " -"Les lignes de code comprennent toutes les lignes de texte dans le code " -"source de ces modules, quel que soit le langage de programmation (Python, " -"Javascript, etc.) ou format de données (XML, CSV, etc.), à l'exclusion des " -"lignes vides et des lignes de commentaires." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:240 -msgid "" -"Odoo SA se réserve le droit de refuser une demande de migration pour des " -"modules tiers conformément aux conditions décrites ci-dessus, si la qualité " -"du code source de ces modules est trop faible, ou si ces modules font partie" -" d'une interface d'intégration avec des logiciels ou systèmes tiers. La " -"migration de ces modules sera soumise à une proposition distincte, non " -"couverte par le présent Contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:250 -msgid "5.4 Taxes et impôts" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:252 -msgid "" -"Tous les frais et tarifs sont indiqués hors taxes et hors impôts, frais et " -"charges fédérales, provinciales, locales ou autres taxes gouvernementales " -"applicables (collectivement, les \"Taxes\"). Le Client est responsable du " -"paiement de toutes les Taxes liées aux achats effectués par le Client en " -"vertu du présent Contrat, sauf lorsque Odoo SA est légalement tenue de payer" -" ou de percevoir les Taxes dont le client est responsable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:261 -msgid "6 Conditions des Services" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:264 -msgid "6.1 Obligations du Client" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:266 -msgid "Le Client accepte de / d':" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:268 -msgid "" -"Payer à Odoo SA les frais applicables pour les Services en vertu du présent " -"Contrat, conformément aux conditions de paiement spécifiées dans la facture " -"correspondante ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:270 -msgid "" -"Aviser immédiatement Odoo SA si le nombre réel d'Utilisateurs dépasse le " -"nombre d'Utilisateurs spécifiés à la signature du Contrat, et dans ce cas, " -"de régler les frais supplémentaires applicables telles que décrits à la " -"section :ref:`charges_standard_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:273 -msgid "" -"Prendre toutes les mesures nécessaires pour garantir l'exécution non " -"modifiée de la partie du Logiciel qui vérifie la validité de l'utilisation " -"de Odoo Enterprise Edition, comme décrit à la section " -":ref:`enterprise_access_fr`;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:276 -msgid "" -"Fournir tout accès nécessaire à Odoo SA pour vérifier la validité de " -"l'utilisation d'Odoo Enterprise Edition sur demande (par exemple, si la " -"validation automatique ne fonctionne pas pour le Client) ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:279 -msgid "" -"Désigner 1 personne de contact représentant le Client pour toute la durée du" -" contrat ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:280 -msgid "" -"Prendre toutes les mesures raisonnables pour protéger les fichiers et les " -"bases de données du Client et s'assurer que les données du Client sont en " -"sûreté et sécurisées, en reconnaissant qu'Odoo SA ne peut être tenue " -"responsable de toute perte de données ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:288 -msgid "6.2 Non solicitation ou embauche" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:290 -msgid "" -"Sauf si l'autre partie donne son consentement par écrit, chaque partie, ses " -"sociétés affiliées et ses représentants conviennent de ne pas solliciter ou " -"offrir un emploi à tout employé de l'autre partie qui est impliqué dans " -"l'exécution ou l'utilisation des Services en vertu du présent Contrat, " -"pendant la Durée du Contrat et pendant une période de 12 mois à compter de " -"la date de résiliation ou de l'expiration du présent Contrat. En cas de " -"violation des conditions de la présente section qui conduirait à la " -"démission dudit employé à cette fin, la partie ayant enfreint ces " -"dispositions accepte de payer à l'autre partie un montant forfaitaire de 30 " -"000,00 euros (€) (trente mille euros)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:303 -msgid "6.3 Publicité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:305 -msgid "" -"Sauf demande contraire par écrit, chaque partie accorde à l'autre partie une" -" licence mondiale libre de droits, non transférable, non exclusive pour " -"reproduire et afficher le nom, les logos et les marques de l'autre partie, " -"dans le seul but de citer l'autre partie en tant que client ou fournisseur, " -"sur les sites Web, dans des communiqués de presse et autres documents de " -"marketing." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:313 -msgid "6.4 Confidentialité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:324 -msgid "Définition des \"Informations Confidentielles\" :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:316 -msgid "" -"Désigne toutes les informations divulguées par une partie (la \"Partie " -"Communicante\") à l'autre partie (la \"Partie Bénéficiaire\"), que ce soit " -"oralement ou par écrit, qui sont désignées comme confidentielles ou qui " -"devraient raisonnablement être comprises comme étant confidentielles étant " -"donné la nature des informations et les circonstances de la divulgation. En " -"particulier, toute information liée aux activités, aux affaires, aux " -"produits, aux développements, aux secrets commerciaux, au savoir-faire, au " -"personnel, aux clients et aux fournisseurs de l'une des parties doit être " -"considérée comme confidentielle." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:326 -msgid "" -"Pour toute Information Confidentielle reçue pendant la durée du présent " -"contrat, la Partie Bénéficiaire utilisera le même degré de précaution " -"qu'elle utilise pour protéger la confidentialité de ses propres Informations" -" Confidentielles de même importance. Ce degré de précaution devra " -"correspondre au minimum à une précaution raisonnable." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:331 -msgid "" -"La Partie Bénéficiaire peut divulguer les Informations Confidentielles de la" -" Partie Communicante dans la mesure où la loi l'y oblige, à condition que la" -" Partie Bénéficiaire avise au préalable par écrit la Partie Communicante de " -"son obligation de divulgation, dans la mesure permise par la loi." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:339 -msgid "6.5 Résiliation" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:341 -msgid "" -"Dans le cas où l'une des parties ne remplit pas ses obligations découlant du" -" présent contrat, et si une telle violation n’est pas résolue dans les 30 " -"jours civils à compter de la notification écrite de cette violation, le " -"présent contrat peut être résilié immédiatement par la partie qui n'a pas " -"commis la violation." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:347 -msgid "" -"En outre, Odoo SA peut résilier le contrat immédiatement dans le cas où le " -"Client ne paie pas les frais applicables pour les services à la date " -"d'échéance indiquée sur la facture correspondante." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:354 -msgid "Durée de l'applicabilité des dispositions:" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:352 -msgid "" -"Les sections \":ref:`confidentiality_fr`\", “:ref:`disclaimers_fr`\", " -"“:ref:`liability_fr`\", et “:ref:`general_provisions_fr`\" survivront la " -"résiliation ou l'expiration du présent contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:359 -msgid "7 Limitations de garantie et de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:364 -msgid "7.1 Garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:366 -msgid "" -"Pendant la durée du présent contrat, Odoo SA s'engage à déployer les efforts" -" raisonnables sur le plan commercial pour exécuter les Services conformément" -" aux normes du secteur généralement acceptées à condition que :" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:370 -msgid "" -"Les systèmes informatiques du Client soient en bon état de fonctionnement et" -" que le Logiciel soit installé dans un système d'exploitation approprié ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:372 -msgid "" -"Le Client fournisse les informations adéquates nécessaires au dépannage et à" -" l'accès, de telle sorte qu'Odoo SA puisse identifier, reproduire et gérer " -"les problèmes ;" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:374 -msgid "Tous les montants dus à Odoo SA aient été réglés." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:376 -msgid "" -"La reprise de l'exécution des Services par Odoo SA sans frais " -"supplémentaires constitue la seule et unique réparation pour le Client et la" -" seule obligation d'Odoo SA pour toute violation de cette garantie." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:383 -msgid "7.2 Limitation de garantie" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:385 -msgid "" -"Mis à part les dispositions expresses du présent Contrat, aucune des parties" -" ne donne de garantie d'aucune sorte, expresse, implicite, légale ou autre, " -"et chaque partie décline expressément toutes garanties implicites, y compris" -" toute garantie implicite de qualité marchande, d'adéquation à un usage " -"particulier ou de non- contrefaçon, dans les limites autorisées par la loi " -"en vigueur." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:391 -msgid "" -"Odoo SA ne garantit pas que le Logiciel soit conforme à toute loi ou " -"réglementation locale ou internationale." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:398 -msgid "7.3 Limitation de responsabilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:400 -msgid "" -"Dans la limite autorisée par la loi, la responsabilité globale de chaque " -"partie, ainsi que de ses filiales, découlant ou liée au présent Contrat ne " -"dépassera pas 50% du montant total réglé par le Client en vertu du présent " -"Contrat au cours des 12 mois précédant la date de l'événement donnant lieu à" -" une telle réclamation. Des réclamations multiples n'augmenteront pas cette " -"limite." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:405 -msgid "" -"Les parties et leurs filiales ne pourront en aucun cas être tenues " -"responsables des dommages indirects, spéciaux, accessoires ou consécutifs de" -" quelque nature que ce soit, y compris, mais sans s'y limiter, la perte de " -"revenus, perte de profits, perte d’économies, perte commerciale ou toute " -"autre perte financière, les coûts relatifs à l'arrêt ou au retard, la perte " -"ou altération des données, découlant ou en relation avec le présent Contrat," -" quelle que soit la forme de l'action, qu'elle soit fondée sur une " -"obligation contractuelle, délictuelle (y compris la stricte négligence) ou " -"fondée sur toute autre règle de droit ou d'équité, même si la partie ou ses " -"filiales ont été informées du risque de tels dommages, ou si le recours " -"proposé par la partie ou ses filiales n'atteint pas son but essentiel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:420 -msgid "" -"Aucune des parties ne sera tenue pour responsable envers l'autre partie de " -"tout retard ou manquement d'exécution en vertu du présent Contrat, si ce " -"manquement ou retard est causé par une règlementation gouvernementale, un " -"incendie, une grève, une guerre, une inondation, un accident, une épidémie, " -"un embargo, la saisie d'une usine ou d'un produit dans son intégralité ou en" -" partie par un gouvernement ou une autorité publique, ou toute (s) autre (s)" -" cause (s), qu’elle (s) soit (soient) de nature similaire ou différente, " -"pour autant que cette cause soit hors du contrôle raisonnable de la partie " -"concernée, et tant qu'une telle cause existe." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:431 -msgid "8 Dispositions générales" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:436 -msgid "8.1 Droit applicable" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:438 -msgid "" -"Les parties conviennent que les lois de Belgique seront applicables en cas " -"de litige découlant ou en relation avec le présent Contrat, sans tenir " -"compte des règles ou dispositions en matière de compétence législative ou de" -" conflit de lois. Dans la mesure où une poursuite ou procédure judiciaire ou" -" administrative serait autorisée ci-avant, les parties conviennent de se " -"soumettre à la compétence exclusive du tribunal de Nivelles (Belgique) aux " -"fins de la procédure de tout litige." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:448 -msgid "8.2 Divisibilité" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:450 -msgid "" -"Dans le cas où une ou plusieurs des dispositions du présent contrat ou toute" -" autre application de celles-ci se trouvent non valables, illégales ou non " -"exécutoires, la validité, la légalité et le caractère exécutoire des autres " -"dispositions du présent contrat et toute application de celles-ci ne doivent" -" en aucun cas en être affectés ou compromis. Les parties s'engagent à " -"remplacer toute disposition non valable, illégale ou non exécutoire du " -"présent contrat par une disposition valable ayant les mêmes effets et " -"objectifs." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:460 -msgid "9 Appendice A: Odoo Enterprise Edition License" -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:462 -msgid "" -"Odoo 9 Enterprise Edition est publié sous la licence Odoo Enterprise Edition" -" License v1.0, définie ci-dessous." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:466 -msgid "" -"Ceci est une traduction en français de la licence “Odoo Enterprise Edition " -"License”. Cette traduction est fournie dans l’espoir qu’elle facilitera sa " -"compréhension, mais elle n'a aucune valeur légale. La seule référence " -"officielle des termes de la licence “Odoo Enterprise Edition License” est la" -" :ref:`version originale <odoo_enterprise_license>`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:472 -msgid "" -"This is a french translation of the \"Odoo Enterprise Edition License”. This" -" translation is provided in the hope that it will facilitate understanding, " -"but it has no legal value. The only official reference of the terms of the " -"“Odoo Enterprise Edition License” is the :ref:`original english version " -"<odoo_enterprise_license>`." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:489 -msgid "" -"Ce logiciel et les fichiers associés (le \"Logiciel\") ne peuvent être " -"utilisés (c'est-à-dire exécutés, modifiés, ou exécutés avec des " -"modifications) qu'avec un contrat Odoo Enterprise Subscription en ordre de " -"validité, et pour le nombre d'utilisateurs prévus dans ce contrat." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:494 -msgid "" -"Un contrat de Partnariat avec Odoo S.A. en ordre de validité donne les mêmes" -" permissions que ci-dessus, mais uniquement pour un usage restreint à un " -"environnement de test ou de développement." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:498 -msgid "" -"Vous êtes autorisé à développer des modules Odoo basés sur le Logiciel et à " -"les distribuer sous la license de votre choix, pour autant que cette licence" -" soit compatible avec les conditions de la licence Odoo Enterprise Edition " -"Licence (Par exemple: LGPL, MIT ou d'autres licenses propriétaires " -"similaires à celle-ci)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:503 -msgid "" -"Vous êtes autorisé à utiliser des modules Odoo publiés sous n'importe quelle" -" licence, pour autant que leur licence soit compatible avec les conditions " -"de la licence Odoo Enterprise Edition License (Notamment tous les modules " -"publiés sur l'Odoo Apps Store sur odoo.com/apps)." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:508 -msgid "" -"Il est interdit de publier, distribuer, accorder des sous-licences, ou " -"vendre tout copie du Logiciel ou toute copie modifiée du Logiciel." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:511 -msgid "" -"Toute copie du Logiciel ou d'une partie substantielle de celui-ci doit " -"inclure l'avis de droit d'auteur original ainsi que le texte de la présente " -"licence." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:514 -msgid "" -"LE LOGICIEL EST FOURNI \"EN L'ETAT\", SANS AUCUNE GARANTIE DE QUELQUE NATURE" -" QUE CE SOIT, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS Y ETRE LIMITE, LES" -" GARANTIES IMPLICITES DE COMMERCIABILITE, DE CONFORMITE A UNE UTILISATION " -"PARTICULIERE, OU DE NON INFRACTION AUX DROITS D'UN TIERS." -msgstr "" - -#: ../../legal/terms/i18n/enterprise_fr.rst:519 -msgid "" -"EN AUCUN CAS LES AUTEURS OU TITULAIRES DE DROITS D'AUTEUR NE POURRONT ETRE " -"TENUS POUR RESPONSABLE A VOTRE EGARD DE RECLAMATIONS, DOMMAGES OU AUTRES " -"RESPONSABILITES, EN VERTU D'UN CONTRAT, DÉLIT OU AUTREMENT, RELATIVEMENT AU " -"LOGICIEL, A L'UTILISATION DU LOGICIEL, OU A TOUTE AUTRE MANIPULATION " -"RELATIVE AU LOGICIEL." -msgstr "" - -#: ../../legal/terms/online.rst:3 -msgid "Odoo Online Terms & Conditions" -msgstr "" - -#: ../../legal/terms/partnership.rst:6 -msgid "Odoo Partnership Agreement - Under Revision!" -msgstr "" - -#: ../../legal/terms/partnership.rst:8 -msgid "Version 5_work-in-progress - Last revision: March 02, 2016." -msgstr "" - -#: ../../legal/terms/partnership.rst:11 -msgid "BETWEEN:" -msgstr "" - -#: ../../legal/terms/partnership.rst:13 -msgid "" -"ODOO SA registered at the Trade and Companies Register of Nivelles under " -"number RCN 95656, having its registered office at Chaussée de Namur, 40 - " -"1367 Grand-Rosière, Belgium." -msgstr "" - -#: ../../legal/terms/partnership.rst:16 -msgid "" -"AND ________________________________, a company having its registered office" -" at _____________________ (Hereinafter referred to as “PARTNER”)" -msgstr "" - -#: ../../legal/terms/partnership.rst:22 -msgid "1 Purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:23 -msgid "" -"The purpose of this agreement is to set forth the conditions under which " -"ODOO provides services to PARTNER, and access to Odoo Enterprise Edition " -"software, and PARTNER complies with the obligations set out hereafter." -msgstr "" - -#: ../../legal/terms/partnership.rst:27 -msgid "" -"ODOO hereby appoints PARTNER, and PARTNER hereby accepts appointment, to be " -"a non-exclusive partner promoting and selling the Odoo Enterprise " -"Subscriptions to clients. PARTNER commits to do its best effort to sell Odoo" -" Enterprise Subscriptions to its clients. To support that, PARTNER will " -"market in priority the ‘Odoo Enterprise Edition’ version to prospects and " -"clients. PARTNER still has the option to sell services on other versions of " -"the software, like \"Odoo Community Edition\", should it be needed." -msgstr "" - -#: ../../legal/terms/partnership.rst:35 -msgid "2 Term of the Agreement" -msgstr "" - -#: ../../legal/terms/partnership.rst:36 -msgid "" -"The duration of this Agreement (the “Term”) shall be one year beginning on " -"the date of the signature. It is automatically renewed for an equal Term, " -"unless either party provides a written notice of termination minimum 30 days" -" before the end of the Term to the other party." -msgstr "" - -#: ../../legal/terms/partnership.rst:45 -msgid "3.1 Project platform access" -msgstr "" - -#: ../../legal/terms/partnership.rst:46 -msgid "" -"To help PARTNER promoting Odoo Enterprise, ODOO grants access to its Github " -"code repository to PARTNER for all ‘Enterprise Edition’ modules, under the " -"terms set forth in Exhibit A and the conditions restricted under this " -"agreement. This access will be granted as of the signature of this agreement" -" and be revoked should the partnership contract be revoked." -msgstr "" - -#: ../../legal/terms/partnership.rst:50 -msgid "3.2 Restrictions" -msgstr "" - -#: ../../legal/terms/partnership.rst:51 -msgid "" -"PARTNER commits to keep confidentiality of the source code of Odoo " -"Enterprise edition modules licensed under restricted rights (labelled as " -"‘Enterprise Edition’) within its staff. The access to clients is governed by" -" the Odoo Enterprise Contract (version 4.0 and above). PARTNER agrees to NOT" -" redistribute this code to 3rd parties without the explicit agreement of " -"ODOO. Notwithstanding the above, PARTNER commits to wholly preserve the " -"integrity of the Odoo Enterprise edition code that is required to verify the" -" validity of usage of Odoo Enterprise edition, collects statistics that are " -"needed for that purpose and enforce the payment of the subscription." -msgstr "" - -#: ../../legal/terms/partnership.rst:56 -msgid "4 Partnership Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:59 -msgid "4.1 Partnership levels" -msgstr "" - -#: ../../legal/terms/partnership.rst:60 -msgid "" -"The ODOO partner program consists of three partnership levels; Ready, Silver" -" and Gold with specific requirements and benefits for each level. " -"Partnership level granted to PARTNER depends on the annual new Odoo " -"Enterprise revenues generated for ODOO. Renewals of existing contracts does " -"not account for the partnership level, but the partner still get his " -"commission on these contracts as stated in 5.2 The table below summarizes " -"the requirement for each partnership level." -msgstr "" - -#: ../../legal/terms/partnership.rst:64 -msgid "" -"Ready Silver Gold Annual New Net Odoo Enterprise Revenues 1.000 € 12.000 € " -"25.000 €" -msgstr "" - -#: ../../legal/terms/partnership.rst:72 -msgid "" -"The level of partnerships will be reviewed quarterly by ODOO based on Odoo " -"Enterprise contracts sold by partners, over the preceeding 12 months. " -"Partners may be upgraded automatically to a higher level once they reach the" -" requirements for a higher level. Silver and Gold partners which are not " -"complying with their partnerships requirements will be assigned to a lower " -"level of partnership if they have not met their requirement at the end of " -"the annual period. For new partners, the initial partner level is granted " -"for one year." -msgstr "" - -#: ../../legal/terms/partnership.rst:77 -msgid "4.2 Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:78 -msgid "" -"The details of the benefits for each level of partnership are described in " -"the table below:" -msgstr "" - -#: ../../legal/terms/partnership.rst:81 -msgid "" -"Ready Silver Gold Recognition Visibility on odoo.com Ready Partner Silver " -"Partner Gold Partner Rights to use the Odoo trademark Ready logo Silver logo" -" Gold logo Learning benefits Yearly upgrades seminars Yes Yes Yes Sales " -"Training Yes Yes Yes Weekly functional training webinars Yes Yes Yes " -"Software Benefits Access to Odoo Enterprise source code Yes Yes Yes Sales " -"benefits Discount on all ODOO services 10% 15% 20% Discount on ODOO " -"Enterprise (Minimum 10 users per contract, applied then for all users). 10% " -"15% 20% Access to an Account Manager Yes Yes Yes Marketing Benefits Access " -"to marketing materials Yes Yes Yes Partner EVENT – ODOO Support & Promotion " -"No Yes Yes" -msgstr "" - -#: ../../legal/terms/partnership.rst:135 -msgid "4.3 Partner Recognition" -msgstr "" - -#: ../../legal/terms/partnership.rst:136 -msgid "" -"ODOO will promote PARTNER as an official partner on its website (odoo.com) " -"for agreed countries. ODOO grants to PARTNER, on a non-exclusive basis, the " -"right to use and reproduce only the ODOO Partner’s logo, and the Odoo name " -"in connection with this Agreement. Each Party undertakes to respect all the " -"rights of the other Party in all the items referred to in the previous " -"paragraph and, more particularly, each Party shall refrain from causing any " -"analogy or creating any confusion between their respective company in the " -"mind of the general public, for any reason whatsoever and by any means " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:141 -msgid "4.4 Learning Benefits" -msgstr "" - -#: ../../legal/terms/partnership.rst:142 -msgid "" -"In order to train PARTNER, ODOO will organize online training sessions once " -"a week. Sessions are organized into discovery and advanced topics. A session" -" is usually 2 hours and cover an application of the Odoo Enterprise " -"software: sales and CRM, inventory management, project management, " -"eCommerce, human resources, manufacturing, advanced customizations, etc. " -"PARTNER can attend these training sessions at no additional cost and commit " -"to attend at least 20 sessions per year. ODOO will organize at least four " -"sales training session per year of a duration of one week. Each sales " -"training session is organized in one of the ODOO office. PARTNER can send " -"any employee to these training session. Once a new version of Odoo " -"Enterprise is released, ODOO must organize upgrade training session for " -"partners." -msgstr "" - -#: ../../legal/terms/partnership.rst:148 -msgid "4.5 Commission on Odoo Services" -msgstr "" - -#: ../../legal/terms/partnership.rst:149 -msgid "" -"For every ODOO services directly purchased by a customer through PARTNER, " -"PARTNER shall receive retribution as follows For “ODOO Enterprise” contracts" -" sold to CUSTOMER: ODOO will invoice directly the CUSTOMER based on final " -"pricing agreed between ODOO, the PARTNER & the CUSTOMER. Then, PARTNER will " -"invoice his commission to ODOO based on Odoo Enteprise price, net of " -"possible rebates, and based on his current partnership level at the time of " -"signature. For Other Services; Partner invoice directly the CLIENT and ODOO " -"will invoice the PARTNER directly commission included. (as a discount) For " -"“ODOO Enterprise” contracts; PARTNER get a commission as long as the PARTNER" -" maintains a contractual relationship with the CUSTOMER." -msgstr "" - -#: ../../legal/terms/partnership.rst:156 -msgid "5 Miscellaneous" -msgstr "" - -#: ../../legal/terms/partnership.rst:159 -msgid "5.1 Communications" -msgstr "" - -#: ../../legal/terms/partnership.rst:160 -msgid "" -"No communications from either party to the other shall have any validity " -"under this Agreement unless made in writing by or on behalf of PARTNER or " -"ODOO, as the case may be, in accordance with the provisions of this " -"Agreement. Any notice whatsoever which either party hereto is required or " -"authorised by this Agreement to give or make to the other shall be given or " -"made either by post in a prepaid letter, or by hand delivery or facsimile " -"transmission or E-mail." -msgstr "" - -#: ../../legal/terms/partnership.rst:164 -msgid "5.2 BRAND IMAGE" -msgstr "" - -#: ../../legal/terms/partnership.rst:165 -msgid "" -"Both Parties shall refrain from harming the brand image and reputation of " -"the other Party, in any way whatsoever, in the performance of this " -"Agreement. Non-compliance to this provision shall be a cause for termination" -" of this Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:168 -msgid "5.3 Publicity" -msgstr "" - -#: ../../legal/terms/partnership.rst:169 -msgid "" -"ODOO shall publish any press release, advertisement or other public " -"announcement using the PARTNER’s name or trademarks without its prior " -"written consent. In particular, PARTNER accepts to be mentioned, and that " -"its logo and trademark is used for this purpose only, in the list of the " -"partners of ODOO." -msgstr "" - -#: ../../legal/terms/partnership.rst:172 -msgid "5.4 No SOLICITING" -msgstr "" - -#: ../../legal/terms/partnership.rst:173 -msgid "" -"Each party, its subsidiaries and any entity controlled indirectly agrees not" -" to solicit, offer employment to, or use the services of any employee of the" -" other party who is involved in performing the Services for the duration of " -"the Agreement and for a period of twenty four (24) Months from the date of " -"termination of this Agreement, except as expressly provided for in the " -"Agreement or where the other party gives its consent in writing to this. In " -"case of any breach of the terms of this article, the defaulting Party shall " -"pay an indemnity equivalent to 12 months of the gross salary of the employee" -" sought or dismissed, or to at least a minimum of € 30,000." -msgstr "" - -#: ../../legal/terms/partnership.rst:177 -msgid "5.5 Independent Contractor" -msgstr "" - -#: ../../legal/terms/partnership.rst:178 -msgid "" -"The Parties are independent contractors, and this Agreement shall not be " -"construed as constituting either Party as partner, joint venture or " -"fiduciary of the other, as creating any other form of legal association that" -" would impose liability on one Party for the act or failure to act of the " -"other or as providing either Party with the right, power or authority " -"(express or implied) to create any duty or obligation of the other." -msgstr "" - -#: ../../legal/terms/partnership.rst:181 -msgid "6 FEES AND CHARGES" -msgstr "" - -#: ../../legal/terms/partnership.rst:182 -msgid "" -"PARTNER shall pay the charges and the annual fee immediately upon receipt of" -" the invoice sent by ODOO.The annual partnership fees is 2950€. PARTNER " -"shall automatically pay a late payment interest at the rate equivalent to " -"the applicable interest rate of the principal instrument of re-financing of " -"the European Central Bank increased by 7% per year, which shall accrue on a " -"daily basis from the due date of payment; it not being necessary for such " -"accrual that ODOO request or claims the unpaid amount in any manner " -"whatsoever." -msgstr "" - -#: ../../legal/terms/partnership.rst:186 -msgid "7 Termination" -msgstr "" - -#: ../../legal/terms/partnership.rst:187 -msgid "" -"In the event that either Party fails to fulfil one or more of its " -"obligations arising hereunder, and if such breach has not been remedied " -"within thirty (30) calendar days from the first presentation of a letter, " -"sent by the injured Party by registered letter with advice of receipt, " -"giving notice of the breaches, this Agreement may be terminated immediately " -"as of right at the request of the injured Party, without prejudice to any " -"damages that may be claimed from the defaulting Party." -msgstr "" - -#: ../../legal/terms/partnership.rst:189 -msgid "" -"On expiry or termination of this Agreement, PARTNER: shall not use anymore " -"the materials and/or the Odoo brand name or claim the existence of any " -"partnership or link with ODOO, shall during any notice period prior to such " -"termination comply with its obligations. shall not use Odoo Enterprise " -"anymore, for development, test or production purpose" -msgstr "" - -#: ../../legal/terms/partnership.rst:195 -msgid "8 Liability AND Indemnities" -msgstr "" - -#: ../../legal/terms/partnership.rst:196 -msgid "" -"Both Parties are bound by a best endeavours obligation hereunder. To the " -"maximum extent permitted by law, ODOO’s liability for any and all claims, " -"losses, damages or expenses from any cause whatsoever and howsoever arising " -"under this Agreement will be limited to the direct damages proven, but will " -"in no event exceed for all damage causing event or series of connected " -"events causing damages the total amount for the charges paid by PARTNER in " -"the course of the six (6) months immediately preceding the date of the event" -" giving rise to such claim. In no event will ODOO be liable for any indirect" -" or consequential damages, including but not limited third parties or " -"Customer claims, loss of revenue, profits, savings, loss of business or " -"other financial loss, costs of standstill or delay, lost or corrupted data " -"arising out of or in connection with the performance of its obligations. " -"PARTNER acknowledges that he has no expectation and has received no " -"assurances that any investment made in execution of this Agreement and the " -"ODOO Partners Program will be recovered or recouped or that he shall obtain " -"any anticipated amount of profits by virtue of this Agreement. Partner " -"waives any commitment whatsoever on behalf of ODOO regarding the evolution " -"of Software." -msgstr "" - -#: ../../legal/terms/partnership.rst:202 -msgid "" -"According to the terms of the Software license, ODOO will not be liable for " -"any bug or for the quality and the performance of the Software, ODOO’s " -"commitment being limited to the correction of bugs as defined in this " -"Agreement." -msgstr "" - -#: ../../legal/terms/partnership.rst:205 -msgid "9 Governing Law and Jurisdiction" -msgstr "" - -#: ../../legal/terms/partnership.rst:206 -msgid "" -"This Agreement will be governed by and construed in accordance with the laws" -" of Belgium. All disputes arising in connection with the Agreement for which" -" no amicable settlement can be found shall be finally settled by the Courts " -"of Belgium in Nivelles." -msgstr "" - -#: ../../legal/terms/partnership.rst:208 -msgid "For Odoo SA," -msgstr "" - -#: ../../legal/terms/partnership.rst:213 -msgid "For _____________," -msgstr "" - -#: ../../legal/terms/partnership.rst:220 -msgid "10 Appendix A: Odoo Enterprise Edition License" -msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/point_of_sale.po b/locale/zh_CN/LC_MESSAGES/point_of_sale.po index bfa8f7420..46b07e9dd 100644 --- a/locale/zh_CN/LC_MESSAGES/point_of_sale.po +++ b/locale/zh_CN/LC_MESSAGES/point_of_sale.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Martin Trigaux <mat@odoo.com>, 2017\n" +"Last-Translator: Talway <9010446@qq.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2016,136 +2016,252 @@ msgid "" "location,..." msgstr "你可以根据硬件，位置等条件配置ＰＯＳ" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Point of Sale Name" +msgstr "POS名称" + #: ../../point_of_sale/overview/start.rst:0 msgid "An internal identification of the point of sale" msgstr "这个一个ＰＯＳ的内部识别" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Journal" +msgstr "销售日记账" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to post sales entries." msgstr "会计日记账用来登录销售分录。" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoice Journal" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "Accounting journal used to create invoices." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Group Journal Items" +msgstr "分组日记账项目" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Check this if you want to group the Journal Items by Product while closing a" " Session" msgstr "如果您想在关闭一个会话时，按产品来对分类账项目进行分组，请勾选此项。" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcodes" +msgstr "条码" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "Defines what kind of barcodes are available and how they are assigned to " "products, customers and cashiers" msgstr "定义并分配相关的条码给商品，客户和收银员" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Order IDs Sequence" +msgstr "订单号序列" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "This sequence is automatically created by Odoo but you can change it to " "customize the reference numbers of your orders." msgstr "这个序列号是由Odoo自动产生的，不过您可以自己定义订单的序列号。" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Sales Channel" +msgstr "" + #: ../../point_of_sale/overview/start.rst:0 msgid "This Point of sale's sales will be related to this Sales Channel." msgstr "" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Virtual KeyBoard" +msgstr "虚拟键盘" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables an integrated Virtual Keyboard" msgstr "允许集成虚拟键盘" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Invoicing" +msgstr "开票" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables invoice generation from the Point of Sale" msgstr "启用POS生成发票" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Prefill Cash Payment" +msgstr "预先填好现金付款" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The payment input will behave similarily to bank payment input, and will be " "prefilled with the exact due amount" msgstr "付款输入和银行凭证输入类似，将事先录入到期金额" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Start Category" +msgstr "开始类别" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The point of sale will display this product category by default. If no " "category is specified, all available products will be shown" msgstr "ＰＯＳ会默认显示属于该类别的商品，如果没有指定，所有商品将显示。" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Tip Product" +msgstr "提示产品" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The product used to encode the customer tip. Leave empty if you do not " "accept tips." msgstr "该商品通常含有小费，如果不接受小费，请留空" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Include Taxes in Prices" +msgstr "含税价" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The displayed prices will always include all taxes, even if the taxes have " "been setup differently" msgstr "显示的价格总是包含所有的税，即使税被不同的设置" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Large Scrollbars" +msgstr "大滚动条" + #: ../../point_of_sale/overview/start.rst:0 msgid "For imprecise industrial touchscreens" msgstr "用于非工业级触摸屏" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Display Category Pictures" +msgstr "展示类别图片" + #: ../../point_of_sale/overview/start.rst:0 msgid "The product categories will be displayed with pictures." msgstr "在图片上会显示商品类别" +#: ../../point_of_sale/overview/start.rst:0 +msgid "IP Address" +msgstr "IP地址" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The hostname or ip address of the hardware proxy, Will be autodetected if " "left empty" msgstr "如果保持为空，硬件代理服务器的主机名或ＩＰ地址会被自动识别到" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Barcode Scanner" +msgstr "条码扫描器" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enable barcode scanning with a remotely connected barcode scanner" msgstr "允许通过远程连接的条码枪进行扫描" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Electronic Scale" +msgstr "电子秤" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Electronic Scale integration" msgstr "允许电子秤集成" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cashdrawer" +msgstr "收银机" + #: ../../point_of_sale/overview/start.rst:0 msgid "Automatically open the cashdrawer" msgstr "自动打开钱箱" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Receipt Printer" +msgstr "票据打印机" + #: ../../point_of_sale/overview/start.rst:0 msgid "Bypass browser printing and prints via the hardware proxy" msgstr "通过浏览器打印和通过硬件代理打印" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Automatic Receipt Printing" +msgstr "自动收据打印" + #: ../../point_of_sale/overview/start.rst:0 msgid "The receipt will automatically be printed at the end of each order" msgstr "每张订单的最后会自动的打印出收据" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Skip Receipt Screen" +msgstr "跳过收据屏幕" + #: ../../point_of_sale/overview/start.rst:0 msgid "" "The receipt screen will be skipped if the receipt can be printed " "automatically." msgstr "小票预览将被略过如果小票是设置成自动打印" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Header" +msgstr "页眉" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a header in the printed receipt" msgstr "短文本会作为表头插入到打印的销售小票上" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Footer" +msgstr "页脚" + #: ../../point_of_sale/overview/start.rst:0 msgid "A short text that will be inserted as a footer in the printed receipt" msgstr "短文本会作为结尾插入到打印的销售小票上" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Cash Control" +msgstr "现金管理" + #: ../../point_of_sale/overview/start.rst:0 msgid "Check the amount of the cashbox at opening and closing." msgstr "在开业和关闭检查钱箱的总额" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Splitting" +msgstr "账单拆分" + #: ../../point_of_sale/overview/start.rst:0 msgid "Enables Bill Splitting in the Point of Sale" msgstr "允许在ＰＯＳ中进行销售付款拆分" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Bill Printing" +msgstr "账单打印" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allows to print the Bill before payment" msgstr "允许在付款前打印销售发票" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Orderline Notes" +msgstr "订单行批注" + #: ../../point_of_sale/overview/start.rst:0 msgid "Allow custom notes on Orderlines" msgstr "允许在订单行中自定义" +#: ../../point_of_sale/overview/start.rst:0 +msgid "Restaurant Floors" +msgstr "餐馆楼层" + #: ../../point_of_sale/overview/start.rst:0 msgid "The restaurant floors served by this point of sale" msgstr "该ＰＯＳ对应的餐馆层" @@ -2906,11 +3022,19 @@ msgid "" "all products or only on specific ones. Click on **Add an item**." msgstr "为你的ＰＯＳ建一个价格列表，每个价格列表可以包含多个不同价格和日期的商品，可以选择所有商品或者指定的商品。点击××增加一个项目××" +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Active" +msgstr "有效" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "" "If unchecked, it will allow you to hide the pricelist without removing it." msgstr "如果不选中，允许您隐藏价格表而无需删除" +#: ../../point_of_sale/shop/seasonal_discount.rst:0 +msgid "Selectable" +msgstr "可选" + #: ../../point_of_sale/shop/seasonal_discount.rst:0 msgid "Allow the end user to choose this price list" msgstr "允许最终用户选择此价格表" diff --git a/locale/zh_CN/LC_MESSAGES/purchase.po b/locale/zh_CN/LC_MESSAGES/purchase.po index 263eacdb9..3a88482f1 100644 --- a/locale/zh_CN/LC_MESSAGES/purchase.po +++ b/locale/zh_CN/LC_MESSAGES/purchase.po @@ -8,9 +8,9 @@ msgid "" msgstr "" "Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-04-20 15:45+0200\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: max_xu <wangzhanwh@163.com>, 2017\n" +"Last-Translator: Yuan Xulei <hi@yxl.name>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1687,10 +1687,18 @@ msgid "" msgstr "" "在 **供应商** 菜单选择你的供应商, 或者通过点击 **创建并编辑** 来创建。在 **订单日期** 字段, 选择你实际希望处理的日期。" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Shipment" +msgstr "送货" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Incoming Shipments" msgstr "入向送货" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "供应商单号" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the sales order or bid sent by the vendor. It's used to do the " @@ -1698,32 +1706,56 @@ msgid "" "on the delivery order sent by your vendor." msgstr "供应商会发送销售订单或投标的有关信息。这些信息是你收到货物后用来核对的." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "订购日期" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Depicts the date where the Quotation should be validated and converted into " "a purchase order." msgstr "当确认报价, 并将之转成订单时, 填入相关日期." +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "源单据" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Reference of the document that generated this purchase order request (e.g. a" " sales order or an internal procurement request)" msgstr "" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "交货到" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "This will determine picking type of incoming shipment" msgstr "这将确定入向送货的拣货类型" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "直运地址" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "Put an address if you want to deliver directly from the vendor to the " "customer. Otherwise, keep empty to deliver to your own company." msgstr "输入地址,如果你想直接把货直接从供应商发给客户。空着就是发自己公司。" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "目标位置类型" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "Technical field used to display the Drop Ship Address" msgstr "字段用于显示直接发运地址" +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "贸易条款" + #: ../../purchase/purchases/rfq/create.rst:0 msgid "" "International Commercial Terms are a series of predefined commercial terms " diff --git a/locale/zh_CN/LC_MESSAGES/sales.po b/locale/zh_CN/LC_MESSAGES/sales.po index 88a0bf54b..2a1451213 100644 --- a/locale/zh_CN/LC_MESSAGES/sales.po +++ b/locale/zh_CN/LC_MESSAGES/sales.po @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 9.0\n" +"Project-Id-Version: Odoo Business 10.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-03-23 15:39+0100\n" +"POT-Creation-Date: 2017-05-09 14:24+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: waveyeung <waveyeung@qq.com>, 2017\n" "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n" @@ -781,13 +781,11 @@ msgstr " **追踪服务**: 合同上的记工单。一个分析科目会被自 #: ../../sales/invoicing/services/support.rst:66 msgid "" -"There are different ways to track the service related to a sale order or " +"There are different ways to track the service related to a sales order or " "product sold. With the above configuration, you can only sell one support " "contract per order. If your customer orders several service contracts on " "timesheet, you will have to split the quotation into several orders." msgstr "" -"有不同的方式来追踪和销售订单相关或者和产品相关的服务, 根据上面的配置, 只能够在一个订单上销售一个支持合同。如果客户同时订购不同的记工单的服务, " -"就必须要把询价单分成不同的订单" #: ../../sales/invoicing/services/support.rst:72 msgid "" @@ -804,17 +802,16 @@ msgid "Managing support contract" msgstr "管理支持合同" #: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sale Orders" +msgid "Quotations and Sales Orders" msgstr "报价单和销售订单" #: ../../sales/invoicing/services/support.rst:83 msgid "" -"Once the product is created, you can create a quotation or a sale order with" -" the related product. Once the quotation is confirmed and transformed into a" -" sale order, your users will be able to record services related to this " -"support contract using the timesheet application." +"Once the product is created, you can create a quotation or a sales order " +"with the related product. Once the quotation is confirmed and transformed " +"into a sales order, your users will be able to record services related to " +"this support contract using the timesheet application." msgstr "" -"一旦创建了产品, 你就可以用该产品创建报价单或者销售订单。一旦报价单被确认掉并且转为小昂首订单, 你的用户就可以使用记工单应用记录和支持合同相关的服务。" #: ../../sales/invoicing/services/support.rst:93 msgid "Timesheets" @@ -831,8 +828,8 @@ msgstr "" "\"), 然后只要服务被销售掉就可以对之进行跟踪。" #: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sale order" -msgstr "在销售订单上控制已交付的支持" +msgid "Control delivered support on the sales order" +msgstr "" #: ../../sales/invoicing/services/support.rst:106 msgid "" @@ -852,71 +849,56 @@ msgstr "向上销售和更新" #: ../../sales/invoicing/services/support.rst:118 msgid "" "If the number of hours you performed on the support contract is bigger or " -"equal to the number of hours the customer purchased, the sale order " -"**Invoicing Status** is automatically set to **Upselling**. This means you " -"have an opportunity to sell an extra contract to the customer since he used " -"all his quota of service." +"equal to the number of hours the customer purchased, you are suggested to " +"sell an extra contract to the customer since they used all their quota of " +"service. Periodically (ideally once every two weeks), you should check the " +"sales order that are in such a case. To do so, go to :menuselection:`Sales " +"--> Invoicing --> Orders to Upsell`." msgstr "" -"如果在销售合同上记录的小时数大于或者等于客户采购的数量, 销售订单的 **开票状态** 就会自动的被设置为 **向上销售** " -"。这样意味着你有一个额外合同的新的商机可以卖给该客户, 因为他已经使用完了所购的服务" -#: ../../sales/invoicing/services/support.rst:124 -msgid "" -"Periodically (ideally once every two weeks), you should check the sales " -"order that are in an upselling status. To do this, go to the " -":menuselection:`Sales --> Sales Order` menu and use the **Upselling** filter" -" to get all orders that are in upselling." -msgstr "" -"定期地(最好每两周一次), 你可以检查在向上销售状态的销售订单。要这样做的话, 进入菜单项 :menuselection:`销售(Sales) --> " -"销售订单(Sales Orders)` 菜单并使用 **向上销售** 过滤器收集所有在向上销售状态的订单。" - -#: ../../sales/invoicing/services/support.rst:130 +#: ../../sales/invoicing/services/support.rst:127 msgid "" "If you use Odoo CRM, a good practice is to create an opportunity for every " "sale order in upselling invoice status so that you easily track your " "upselling effort." msgstr "如果你使用Odoo CRM, 最好的联系就是为每个在向上销售开票状态的销售订单创建一个商机, 这样你就可以容易追踪向上销售" -#: ../../sales/invoicing/services/support.rst:134 +#: ../../sales/invoicing/services/support.rst:131 msgid "" "If you sell an extra support contract, you can either add a new line on the " -"existing sale order (thus, you continue to timesheet on the same order) or " +"existing sales order (thus, you continue to timesheet on the same order) or " "create a new order (thus, people will timesheet their hours on the new " -"contract). To unmark the sale order as **Upselling**, you can set the sale " -"order as done and it will disappear from your upselling list." +"contract). To unmark the sales order as **Upselling**, you can set the sales" +" order as done and it will disappear from your upselling list." msgstr "" -"如果你销售额外的支持合同, 你还可以在目前的销售订单中添加新的订单行(因此, 你可以继续在同一张合同上记工单)或者创建一个新的订单(这样, " -"就需要在新建的合同上记工单)。取消标记销售订单的 **向上销售** 状态, 并把销售订单设置完成状态, 然后该订单就从向上销售列表中消失" -#: ../../sales/invoicing/services/support.rst:141 +#: ../../sales/invoicing/services/support.rst:138 msgid "Special Configuration" msgstr "特殊配置" -#: ../../sales/invoicing/services/support.rst:143 +#: ../../sales/invoicing/services/support.rst:140 msgid "" "When creating the product form, you may set a different approach to track " "the service:" msgstr "在创建产品表单的时候, 选择不同方式跟踪该服务" -#: ../../sales/invoicing/services/support.rst:146 +#: ../../sales/invoicing/services/support.rst:143 msgid "" "**Create task and track hours**: in this mode, a task is created for every " -"sale order line. Then when you do the timesheet, you don't record hours on a" -" sale order/contract, but you record hours on a task (that represents the " +"sales order line. Then when you do the timesheet, you don't record hours on " +"a sales order/contract, but you record hours on a task (that represents the " "contract). The advantage of this solution is that it allows to sell several " -"service contracts within the same sale order." +"service contracts within the same sales order." msgstr "" -" **创建任务并追踪小时数**: 在该模式下, 每个订单行都会创建一个任务。然后在你记录记工单的时候, " -"不需要在销售订单／合同上输入。而是在每个任务(代表合同)上记录记工单。该方案的优点是能够在同一张销售订单上销售不同服务合同。" -#: ../../sales/invoicing/services/support.rst:153 +#: ../../sales/invoicing/services/support.rst:150 msgid "" "**Manually**: you can use this mode if you don't record timesheets in Odoo. " "The number of hours you worked on a specific contract can be recorded " -"manually on the sale order line directly, in the delivered quantity field." -msgstr " **手工地**: 如果你不在Odoo中记录记工单就可以使用该种模式。特定合同的工作时间手工地在销售订单行的交货数量字段直接记录。" +"manually on the sales order line directly, in the delivered quantity field." +msgstr "" -#: ../../sales/invoicing/services/support.rst:159 +#: ../../sales/invoicing/services/support.rst:156 msgid ":doc:`../../../inventory/settings/products/uom`" msgstr ":doc:`../../../inventory/settings/products/uom` " @@ -1132,11 +1114,11 @@ msgstr ":menuselection:`电商订单(eCommerce Order) --> 开票(Invoice)` " #: ../../sales/overview/main_concepts/invoicing.rst:69 msgid "" -"An eCommerce order will also trigger the creation of the order when it is " +"An eCommerce order will also trigger the creation of the invoice when it is " "fully paid. If you allow paying orders by check or wire transfer, Odoo only " "creates an order and the invoice will be triggered once the payment is " "received." -msgstr "在全部付款完成后, 电商订单也会触发订单的创建, 如果允许通过支票和电汇付款, Odoo只会创建一张订单并且一旦付款完成发票会触发。" +msgstr "" #: ../../sales/overview/main_concepts/invoicing.rst:75 msgid "Creating an invoice manually" @@ -1440,140 +1422,76 @@ msgid "Manage your products" msgstr "" #: ../../sales/products_prices/products/import.rst:3 -msgid "How to import my products" +msgid "How to import products with categories and variants" msgstr "" -#: ../../sales/products_prices/products/import.rst:6 -msgid "How to start" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:8 -msgid "Download the following import templates:" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:10 +#: ../../sales/products_prices/products/import.rst:5 msgid "" -"Partners: customers, vendors (no relation field, can be imported as is)" +"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 "Products (no relation field, can be imported as is)" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:12 -msgid "Product Website Categories" +msgid "How to customize the file" msgstr "" #: ../../sales/products_prices/products/import.rst:13 -msgid "Product Attributes & Values" +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:14 -msgid "Products with Categories & Attributes (3 & 4 must be imported first)" +#: ../../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 "" -"Download link: " -"https://drive.google.com/drive/folders/0B1uIL9E_zXrrTEp5eGI2dXJSUjg?usp=sharing" +"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 "" -"You can open them with any spreadsheets software (Microsoft Office, " -"OpenOffice, Google Drive, etc.)." +"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:21 -msgid "How to customize the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:23 -msgid "" -"Remove columns you don't need. Don't remove the first one (called *ID*, see " -"why here below)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:25 -msgid "" -"Don't change labels of columns you want to import. Otherwse Odoo won't match" -" the columns automatically." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:27 -msgid "" -"Feel free to add new columns but the fields need to exist in Odoo. If Odoo " -"fails in matching the column name with a field, you can make it manually " -"when importing by browsing a list of available fields." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:30 -msgid "Once modified, keep your file in .csv format." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:33 -msgid "How to import the file" -msgstr "" - -#: ../../sales/products_prices/products/import.rst:35 -msgid "Go to the Products menu in Sales, Purchase, Website Admin, etc." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:36 -msgid "Switch to list view (top-right corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:37 -msgid "Click the *Import* button (top-left corner)." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:38 -msgid "" -"Make sure all the columns match an existing field. If not select it manually" -" from the drop-down list." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:40 -msgid "Press * Validate* to test the import." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:41 -msgid "" -"If you get \"Everything seems valid.\" as result message, press *Import* to " -"process the real import. Otherwise correct the issues spotted during the " -"test." -msgstr "" - -#: ../../sales/products_prices/products/import.rst:45 +#: ../../sales/products_prices/products/import.rst:24 msgid "Why an “ID” column" msgstr "" -#: ../../sales/products_prices/products/import.rst:47 +#: ../../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:50 +#: ../../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:52 +#: ../../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:53 +#: ../../sales/products_prices/products/import.rst:32 msgid "Import relation fields (see here below)." msgstr "" -#: ../../sales/products_prices/products/import.rst:56 +#: ../../sales/products_prices/products/import.rst:35 msgid "How to import relation fields" msgstr "" -#: ../../sales/products_prices/products/import.rst:58 +#: ../../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 " @@ -1581,7 +1499,7 @@ msgid "" "their own list menu." msgstr "" -#: ../../sales/products_prices/products/import.rst:62 +#: ../../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 \" / " diff --git a/sales/invoicing/services/support.rst b/sales/invoicing/services/support.rst index 925f5cbf8..57b968cb0 100644 --- a/sales/invoicing/services/support.rst +++ b/sales/invoicing/services/support.rst @@ -78,7 +78,7 @@ Managing support contract ========================= Quotations and Sales Orders --------------------------- +--------------------------- Once the product is created, you can create a quotation or a sales order with the related product. Once the quotation is confirmed and @@ -101,7 +101,7 @@ above), so you can start tracking services as soon as it has been sold. :align: center Control delivered support on the sales order -------------------------------------------- +-------------------------------------------- From the **Sales** application, use the menu :menuselection:`Sales --> Sales Orders` to control diff --git a/website/optimize/google_analytics_dashboard.rst b/website/optimize/google_analytics_dashboard.rst index 49b6f5865..93d944a9a 100644 --- a/website/optimize/google_analytics_dashboard.rst +++ b/website/optimize/google_analytics_dashboard.rst @@ -1,8 +1,8 @@ -============================================================ -How to track your website's traffic from your Odoo Dashboard -============================================================ +========================================================== +How to track your website traffic from your Odoo Dashboard +========================================================== -You can follow your traffic's statistics straight from your Odoo Website +You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics. - A preliminary step is creating a Google Analytics account and entering the @@ -13,35 +13,39 @@ Dashboard thanks to Google Analytics. - Select Analytics API. - .. image:: media/google_analytics_api.png - :align: center +.. image:: media/google_analytics_api.png + :align: center -- Create a new project and give it a name (e.g. Google Analytics in Odoo). +- Create a new project and give it a name (e.g. Odoo). + This project is needed to store your API credentials. - .. image:: media/google_analytics_create_project.png - :align: center +.. image:: media/google_analytics_create_project.png + :align: center - Enable the API. - .. image:: media/google_analytics_enable.png - :align: center +.. image:: media/google_analytics_enable.png + :align: center -- Create credentials to use in Odoo. Select *Web browser (Javascript)* +- Create credentials to use in Odoo. + +.. image:: media/google_analytics_create_credentials.png + :align: center + +- Select *Web browser (Javascript)* as calling source and *User data* as kind of data. - .. image:: media/google_analytics_create_credentials.png - :align: center +.. image:: media/google_analytics_get_credentials.png + :align: center - .. image:: media/google_analytics_get_credentials.png - :align: center - -- Then enter the name of the application (e.g. Odoo) and the allowed pages on +- Then you can create a Client ID. + Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance - URL followed by /google_account/authentication. + URL followed by '/google_account/authentication'. - .. image:: media/google_analytics_authorization.png - :align: center +.. image:: media/google_analytics_authorization.png + :align: center - Go through the Consent Screen step by entering a product name @@ -51,16 +55,16 @@ Dashboard thanks to Google Analytics. - Finally you are provided with your Client ID. Copy and paste it in Odoo. - .. image:: media/google_analytics_client_id.png - :align: center +.. image:: media/google_analytics_client_id.png + :align: center - Open your Website Dashboard in Odoo and link your Analytics account. to past your Client ID. - .. image:: media/google_analytics_start.png - :align: center +.. image:: media/google_analytics_start.png + :align: center - As a last step, authorize Odoo to access Google API. - .. image:: media/google_analytics_login.png - :align: center +.. image:: media/google_analytics_login.png + :align: center diff --git a/website/optimize/media/google_analytics_client_id.png b/website/optimize/media/google_analytics_client_id.png index a76a26ba5..c78ee713f 100644 Binary files a/website/optimize/media/google_analytics_client_id.png and b/website/optimize/media/google_analytics_client_id.png differ