diff --git a/locale/es/LC_MESSAGES/accounting.po b/locale/es/LC_MESSAGES/accounting.po index 4793748ad..c9c51d256 100644 --- a/locale/es/LC_MESSAGES/accounting.po +++ b/locale/es/LC_MESSAGES/accounting.po @@ -46,6 +46,8 @@ # Jon Perez , 2019 # Gabriel Umana , 2019 # Jesse Garza , 2019 +# Angel Moya - PESOL , 2019 +# Vivian Montana , 2019 # #, fuzzy msgid "" @@ -54,7 +56,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2018-11-07 15:38+0100\n" "PO-Revision-Date: 2018-10-19 08:14+0000\n" -"Last-Translator: Jesse Garza , 2019\n" +"Last-Translator: Vivian Montana , 2019\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" @@ -2288,7 +2290,7 @@ msgstr "La divisa utilizada para introducir asientos." #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Defines how the bank statements will be registered" -msgstr "" +msgstr "Define como se registrarán los extractos bancarios" #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Creation of Bank Statements" @@ -2296,7 +2298,7 @@ msgstr "Creación de extracto bancario" #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Defines when a new bank statement" -msgstr "" +msgstr "Define cuándo un nuevo extracto bancario" #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "will be created when fetching new transactions" @@ -2699,12 +2701,16 @@ msgid "" "These fields can be found in :menuselection:`Partner --> Sales & Purchase " "Tab --> Fiscal Information`" msgstr "" +"Estos campos se pueden encontrar en :seleccion de menu: `Socio--> Lengüeta " +"de Ventas & Compras ---> Información Fiscal" #: ../../accounting/localizations/colombia.rst:104 msgid "" "Additionally two booleans fields were added in order to specify the fiscal " "regimen of the partner." msgstr "" +"Adicionalmente se agregaron dos campos booleanos para especificar el régimen" +" fiscal del socio." #: ../../accounting/localizations/colombia.rst:108 msgid "4.2 Taxes" diff --git a/locale/es/LC_MESSAGES/discuss.po b/locale/es/LC_MESSAGES/discuss.po index d0825a250..539315f85 100644 --- a/locale/es/LC_MESSAGES/discuss.po +++ b/locale/es/LC_MESSAGES/discuss.po @@ -3,14 +3,21 @@ # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # +# Translators: +# Martin Trigaux, 2018 +# Lina Maria Avendaño Carvajal , 2018 +# Pablo Rojas , 2018 +# Fairuoz Hussein Naranjo , 2018 +# Vivian Montana , 2019 +# #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2018-10-19 10:03+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: Fairuoz Hussein Naranjo , 2018\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Vivian Montana , 2019\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" @@ -25,6 +32,8 @@ msgstr "Debates" #: ../../discuss/email_servers.rst:3 msgid "How to use my mail server to send and receive emails in Odoo" msgstr "" +"Cómo usar mi servidor de correo para enviar y recibir correos electrónicos " +"en Odoo" #: ../../discuss/email_servers.rst:5 msgid "" @@ -60,7 +69,7 @@ msgstr "" #: ../../discuss/email_servers.rst:24 msgid "How to manage outbound messages" -msgstr "" +msgstr "Cómo administrar mensajes de correo salientes" #: ../../discuss/email_servers.rst:26 msgid "" @@ -72,7 +81,7 @@ msgstr "" #: ../../discuss/email_servers.rst:31 msgid "Here is a typical configuration for a G Suite server." -msgstr "" +msgstr "Esta es una configuración típica del servidor G Suite." #: ../../discuss/email_servers.rst:36 msgid "Then set your email domain name in the General Settings." @@ -80,7 +89,7 @@ msgstr "" #: ../../discuss/email_servers.rst:39 msgid "Can I use an Office 365 server" -msgstr "" +msgstr "¿Puedo usar un servidor de Office 365?" #: ../../discuss/email_servers.rst:40 msgid "" @@ -98,7 +107,7 @@ msgstr "" #: ../../discuss/email_servers.rst:47 msgid "How to use a G Suite server" -msgstr "" +msgstr "Cómo usar un servidor de G Suite" #: ../../discuss/email_servers.rst:48 msgid "" @@ -153,7 +162,7 @@ msgstr "" #: ../../discuss/email_servers.rst:78 msgid "Allow DKIM" -msgstr "" +msgstr "Permitir DKIM" #: ../../discuss/email_servers.rst:79 msgid "" @@ -167,7 +176,7 @@ msgstr "" #: ../../discuss/email_servers.rst:87 msgid "How to manage inbound messages" -msgstr "" +msgstr "¿Cómo administrar los mensajes de correo entrantes?" #: ../../discuss/email_servers.rst:89 msgid "Odoo relies on generic email aliases to fetch incoming messages." @@ -305,7 +314,7 @@ msgstr "" #: ../../discuss/mail_twitter.rst:19 msgid "Name: this is the name of the application on Twitter" -msgstr "" +msgstr "Nombre: Este es el nombre de la aplicación en Twitter" #: ../../discuss/mail_twitter.rst:21 msgid "" @@ -347,6 +356,8 @@ msgstr "" #: ../../discuss/mentions.rst:3 msgid "How to grab attention of other users in my messages" msgstr "" +"¿Cómo llamar la atención de otros usuarios en mis mensajes.Cómo llamar la " +"atención de otros usuarios en mis mensajes?" #: ../../discuss/mentions.rst:5 msgid "" @@ -422,7 +433,7 @@ msgstr "" #: ../../discuss/monitoring.rst:13 msgid "You can keep an eye on your **Inbox** from any screen." -msgstr "" +msgstr "Puedes vigilar tu ** Bandeja de entrada ** desde cualquier pantalla." #: ../../discuss/monitoring.rst:18 msgid "" @@ -435,7 +446,7 @@ msgstr "" #: ../../discuss/overview.rst:3 msgid "Why use Odoo Discuss" -msgstr "" +msgstr "¿Por qué usar Odoo Discuss?" #: ../../discuss/overview.rst:5 msgid "" @@ -458,7 +469,7 @@ msgstr "" #: ../../discuss/plan_activities.rst:3 msgid "Get organized by planning activities" -msgstr "" +msgstr "Organízate planeando actividades" #: ../../discuss/plan_activities.rst:5 msgid "" @@ -481,7 +492,7 @@ msgstr "" #: ../../discuss/plan_activities.rst:22 msgid "Set your activity types" -msgstr "" +msgstr "Establece tus tipos de actividad" #: ../../discuss/plan_activities.rst:24 msgid "" @@ -492,7 +503,7 @@ msgstr "" #: ../../discuss/plan_activities.rst:29 msgid "Schedule meetings" -msgstr "" +msgstr "Programar reuniones" #: ../../discuss/plan_activities.rst:31 msgid "" @@ -509,7 +520,7 @@ msgstr "" #: ../../discuss/plan_activities.rst:40 msgid "Schedule a chain of activities to follow" -msgstr "" +msgstr "Programar una cadena de actividades a seguir" #: ../../discuss/plan_activities.rst:42 msgid "" diff --git a/locale/it/LC_MESSAGES/accounting.po b/locale/it/LC_MESSAGES/accounting.po new file mode 100644 index 000000000..2b1435bb6 --- /dev/null +++ b/locale/it/LC_MESSAGES/accounting.po @@ -0,0 +1,12401 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Davide Corio , 2019 +# Luigi Di Naro , 2019 +# Marco Calcagni , 2019 +# Rosario Savarese , 2019 +# mymage , 2019 +# Francesco Garganese , 2019 +# David Minneci , 2019 +# Francesco Arillotta , 2019 +# Martin Trigaux, 2019 +# Simone Bernini , 2019 +# Giacomo Grasso , 2019 +# Paolo Valier, 2019 +# Léonie Bouchat , 2019 +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:14+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../accounting.rst:5 ../../accounting/localizations/mexico.rst:283 +msgid "Accounting" +msgstr "Contabilità" + +#: ../../accounting/bank.rst:3 +msgid "Bank & Cash" +msgstr "Banca e cassa" + +#: ../../accounting/bank/feeds.rst:3 +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Bank Feeds" +msgstr "Feed bancari" + +#: ../../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/localizations/colombia.rst:25 +#: ../../accounting/localizations/mexico.rst:33 +#: ../../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_rounding.rst:19 +#: ../../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/customer_payments/payment_sepa.rst:19 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../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/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 "Panoramica" + +#: ../../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 "Come sincronizzare il conto PayPal con Odoo?" + +#: ../../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 "Come sincronizzare Odoo con la banca?" + +#: ../../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/feeds/synchronize.rst:73 +#: ../../accounting/localizations/mexico.rst:533 +msgid "FAQ" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:76 +msgid "The synchronization is not working in real time, is it normal?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:78 +msgid "" +"Yodlee tries to get the data from a bank account once a day. However, this " +"doesn't always happen at the same time. And sometimes the process can fail. " +"In that case, Yodlee retries one hour or two later. This is why in Odoo " +"there is a cron that is running every 4 hours to fetch the information from " +"Yodlee." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:83 +msgid "" +"You can however force this synchronization by clicking on the button " +"\"Synchronize now\" from the accounting dashboard." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:86 +msgid "" +"Moreover, a transaction can be visible in your bank account but not being " +"fetched by Yodlee. Indeed, the transaction in your bank account can have the" +" status \"pending\" and not the status \"posted\". In that case, Yodlee " +"won't import it, you will have to wait that the status changes." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:91 +msgid "" +"What is important to remember is that Yodlee is not a service fetching " +"transactions in real time. This is a service to facilitate the import of the" +" bank statement in the database." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:95 +msgid "Is the Yodlee feature included in my contract?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:97 +msgid "" +"Enterprise Version: Yes, if you have a valid enterprise contract linked to " +"your database." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:98 +msgid "" +"Community Version: No, this feature is not included in the Community " +"Version." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:99 +msgid "" +"Online Version: Yes, even if you benefit from the One App Free contract." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:102 +msgid "Some banks have a status \"Beta\", what does it mean?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:104 +msgid "" +"This means that Yodlee is only currently working on developing the " +"synchronization with this bank. The synchronization could already work or it" +" may need a bit more time to have a 100% working synchronization. " +"Unfortunately, there is not much to do about except being patient." +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:110 +msgid "All my past transactions are not in Odoo, why?" +msgstr "" + +#: ../../accounting/bank/feeds/synchronize.rst:112 +msgid "Yodlee only allows to fetch up transactions to 3 months in the past." +msgstr "" + +#: ../../accounting/bank/misc.rst:3 ../../accounting/payables/misc.rst:3 +#: ../../accounting/payables/misc/employee_expense.rst:187 +msgid "Miscellaneous" +msgstr "Varie" + +#: ../../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 "Risoluzione problemi" + +#: ../../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 +msgid "Bank Reconciliation" +msgstr "Riconciliazione bancaria" + +#: ../../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 "Use 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 "Impostazione" + +#: ../../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 "Creare un conto bancario" + +#: ../../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:0 +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Type" +msgstr "Tipo" + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "" +"Bank account type: Normal or IBAN. Inferred from the bank account number." +msgstr "" +"Tipo di conto corrente: normale o IBAN. Dedotto dal numero di conto " +"corrente." + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "ABA/Routing" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "American Bankers Association Routing Number" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "Account Holder Name" +msgstr "Nome del titolare del conto" + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "" +"Account holder name, in case it is different than the name of the Account " +"Holder" +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 +msgid "Active" +msgstr "Attivo" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Set active to false to hide the Journal without removing it." +msgstr "" +"Impostare «Attivo» a falso per nascondere il registro senza rimuoverlo." + +#: ../../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 "Use in Point of Sale" +msgstr "Usare nel punto vendita" + +#: ../../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 "" +"Selezionare la casella se il registro indica un metodo di pagamento che può " +"essere usato nel punto vendita." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company" +msgstr "Azienda" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Company related to this journal" +msgstr "Azienda collegata a questo registro" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Short Code" +msgstr "Codice breve" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The journal entries of this journal will be named using this prefix." +msgstr "" +"Le registrazioni contabili di questo registro verranno identificate usando " +"questo prefisso." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Number" +msgstr "Numero successivo" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The next sequence number will be used for the next invoice." +msgstr "Per la prossima fattura verrà usato il successivo numero di sequenza." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Entry Sequence" +msgstr "Sequenza registrazione" + +#: ../../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 "" +"Questo campo contiene informazioni sulla numerazione delle registrazioni " +"contabili per questo registro." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Dedicated Credit Note Sequence" +msgstr "Sequenza dedicata per note di credito" + +#: ../../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" +" credit notes made from this journal" +msgstr "" +"Selezionare questa casella per non usare la stessa sequenza per fatture e " +"note di credito di questo registro" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Credit Notes: Next Number" +msgstr "Note di credito: numero successivo" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "The next sequence number will be used for the next credit note." +msgstr "" +"Per la prossima nota di credito verrà utilizzato il seguente numero di " +"sequenza." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Credit Note Entry Sequence" +msgstr "Sequenza registrazione nota di credito" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"This field contains the information related to the numbering of the credit " +"note entries of this journal." +msgstr "" +"Questo campo contiene informazioni sulla numerazione delle registrazioni " +"contabili per le note di credito." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Debit Account" +msgstr "Conto dare predefinito" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for debit amount" +msgstr "Opera come conto predefinito per l'importo in dare" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Default Credit Account" +msgstr "Conto avere predefinito" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It acts as a default account for credit amount" +msgstr "Opera come conto predefinito per l'importo in avere" + +#: ../../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 "La valuta utilizzata per inserire l'estratto conto" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Defines how the bank statements will be registered" +msgstr "Definisce come verrà registrato l'estratto conto bancario" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Creation of Bank Statements" +msgstr "Creazione estratti conto bancari" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Defines when a new bank statement" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "will be created when fetching new transactions" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "from your bank account." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "For Incoming Payments" +msgstr "Per pagamenti in entrata" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual: Get paid by cash, check or any other method outside of Odoo." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Electronic: Get paid automatically through a payment acquirer by requesting " +"a transaction on a card saved by the customer when buying or subscribing " +"online (payment token)." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Batch Deposit: Encase several customer checks at once by generating a batch " +"deposit to submit to your bank. When encoding the bank statement in Odoo,you" +" are suggested to reconcile the transaction with the batch deposit. Enable " +"this option from the settings." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "For Outgoing Payments" +msgstr "Per pagamenti in uscita" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Manual:Pay bill by cash or any other method outside of Odoo." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check:Pay bill by check and print it from Odoo." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit " +"to your bank. Enable this option from the settings." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "Conto utili" + +#: ../../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 "" +"Usato per registrare un utile quando il saldo finale di un registratore di " +"cassa è diverso da quanto calcolato dal sistema" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "Conto perdite" + +#: ../../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 "" +"Usato per registrare una perdita quando il saldo finale di un registratore " +"di cassa è diverso da quanto calcolato dal sistema" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Group Invoice Lines" +msgstr "Raggruppare le righe fattura" + +#: ../../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 "" +"Se la casella è selezionata, il sistema proverà a raggruppare le righe " +"contabili quando vengono generate dalle fatture." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Post At Bank Reconciliation" +msgstr "Generare con riconciliazione bancaria" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Whether or not the payments made in this journal should be generated in " +"draft state, so that the related journal entries are only posted when " +"performing bank reconciliation." +msgstr "" +"Indica se impostare a bozza i pagamenti creati in questo registro, in modo " +"che le relative registrazioni contabili vengano generate solo con la " +"riconciliazione bancaria." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Alias Name for Vendor Bills" +msgstr "Pseudonimo per fatture fornitore" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It creates draft vendor bill by sending an email." +msgstr "Crea una fattura fornitore in bozza inviando una e-mail." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Printing Payment Method Selected" +msgstr "Metodo di pagamento di stampa degli assegni selezionato" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "" +"Technical feature used to know whether check printing was enabled as payment" +" method." +msgstr "" +"Funzionalità tecnica utilizzata per sapere se la stampa degli assegni è " +"stata abilitata come metodo di pagamento. " + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Check Sequence" +msgstr "Sequenza assegno" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Checks numbering sequence." +msgstr "Sequenza di numerazione degli assegni. " + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 +msgid "Manual Numbering" +msgstr "Numerazione manuale" + +#: ../../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 "" +"Selezionare questa opzione se gli assegni prestampati non sono numerati." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Next Check Number" +msgstr "Prossimo numero di assegno" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Sequence number of the next printed check." +msgstr "Numero di sequenza del prossimo assegno stampato." + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Amount Authorized Difference" +msgstr "Differenza di importo autorizzata" + +#: ../../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 "Utilizzo" + +#: ../../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/localizations.rst:3 +msgid "Localizations" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:3 +msgid "Colombia" +msgstr "Colombia" + +#: ../../accounting/localizations/colombia.rst:6 +#: ../../accounting/localizations/mexico.rst:14 +#: ../../accounting/others/taxes/B2B_B2C.rst:63 +msgid "Introduction" +msgstr "Introduzione" + +#: ../../accounting/localizations/colombia.rst:8 +msgid "" +"Electronic invoicing for Colombia is available from Odoo 12 and requires the" +" next modules:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:11 +msgid "" +"**l11n_co**: All the basic data to manage the accounting module, contains " +"the default setup for: chart of accounts, taxes, retentions, identification " +"document types" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:14 +msgid "" +"**l10n_co_edi**: This module includes all the extra fields that are required" +" for the Integration with Carvajal T&S and generate the electronic invoice, " +"based on the DIAN legal requirements." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:19 +msgid "Workflow" +msgstr "Flusso di lavoro" + +#: ../../accounting/localizations/colombia.rst:28 +msgid "1. Install the Colombian localization modules" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:30 +msgid "" +"For this, go in Apps and search for Colombia. Then click Install for the " +"first two modules." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:37 +msgid "2. Configure credentials for Carvajal T&S web service" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:39 +msgid "" +"Once that the modules are installed, in order to be able to connect with " +"Carvajal T&S Web Service, it's necessary to configure the user and " +"credentials, this information will be provided by Carvajal T&S." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:43 +#: ../../accounting/localizations/colombia.rst:64 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and look " +"for the *Colombian Electronic Invoice* section." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:49 +msgid "" +"Using the Testing mode it is possible to connect with a Carvajal T&S testing" +" environment. This allows users to test the complete workflow and " +"integration with the CEN Financiero portal, which is accessible here: " +"https://cenfinancierolab.cen.biz" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:54 +msgid "" +"Once that Odoo and Carvajal T&S is fully configured and ready for production" +" the testing environment can be disabled." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:58 +msgid "3. Configure your report data" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:60 +msgid "" +"As part of the configurable information that is sent in the XML, you can " +"define the data for the fiscal section and the bank information in the PDF." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:71 +msgid "4. Configure data required in the XML" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:74 +msgid "4.1 Partner" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:77 +msgid "4.1.1 Identification" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:79 +msgid "" +"As part of the Colombian Localization, the document types defined by the " +"DIAN are now available on the Partner form. Colombian partners have to have " +"their identification number and document type set:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:86 +msgid "" +"When the document type is RUT the identification number needs to be " +"configured in Odoo including the verification digit, Odoo will split this " +"number when the data to the third party vendor is sent." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:92 +msgid "4.1.2 Fiscal structure (RUT)" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:94 +msgid "" +"The partner's responsibility codes (section 53 in the RUT document) are " +"included as part of the electronic invoice module given that is part of the " +"information required by the DIAN ." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:98 +msgid "" +"These fields can be found in :menuselection:`Partner --> Sales & Purchase " +"Tab --> Fiscal Information`" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:104 +msgid "" +"Additionally two booleans fields were added in order to specify the fiscal " +"regimen of the partner." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:108 +msgid "4.2 Taxes" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:110 +msgid "" +"If your sales transactions include products with taxes, it's important to " +"consider that an extra field *Value Type* needs to be configured per tax. " +"This option is located in the Advanced Options tab." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:117 +msgid "" +"Retention tax types (ICA, IVA, Fuente) are also included in the options to " +"configure your taxes. This configuration is used in order to correctly " +"display taxes in the invoice PDF." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:125 +msgid "4.3 Journals" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:127 +msgid "" +"Once the DIAN has assigned the official sequence and prefix for the " +"electronic invoice resolution, the Sales journals related to your invoice " +"documents need to be updated in Odoo. The sequence can be accessed using " +"developer mode: :menuselection:`Accounting --> Settings --> Configuration " +"Setting --> Journals`." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:136 +msgid "" +"Once that the sequence is opened, the Prefix and Next Number fields should " +"be configured and synchronized with the CEN Financiero." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:143 +msgid "4.4 Users" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:145 +msgid "" +"The default template that is used by Odoo on the invoice PDF includes the " +"job position of the salesperson, so these fields should be configured:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:153 +#: ../../accounting/localizations/mexico.rst:196 +msgid "Usage and testing" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:156 +msgid "1. Invoice" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:158 +msgid "" +"When all your master data and credentials has been configured, it's possible" +" to start testing the electronic invoice workflow." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:162 +msgid "1.1 Invoice creation" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:164 +msgid "" +"The functional workflow that takes place before an invoice validation " +"doesn't change. The main changes that are introduced with the electronic " +"invoice are the next fields:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:171 +msgid "There are three types of documents:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:173 +msgid "" +"**Factura Electronica**: This is the regular type of document and its " +"applicable for Invoices, Credit Notes and Debit Notes." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:175 +msgid "" +"**Factura de Importación**: This should be selected for importation " +"transactions." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:177 +msgid "" +"**Factura de contingencia**: This is an exceptional type that is used as a " +"manual backup in case that the company is not able to use the ERP and it's " +"necessary to generate the invoice manually, when this invoice is added to " +"the ERP, this invoice type should be selected." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:184 +msgid "1.2 Invoice validation" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:186 +msgid "" +"After the invoice is validated an XML file is created and sent automatically" +" to Carvajal, this file is displayed in the chatter." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:192 +msgid "" +"An extra field is now displayed in \"Other Info\" tab with the name of the " +"XML file. Additionally there is a second extra field that is displayed with " +"the Electronic Invoice status, with the initial value \"In progress\":" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:201 +msgid "1.3 Reception of legal XML and PDF" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:203 +msgid "" +"The electronic invoice vendor receives the XML file and proceeds to validate" +" the structure and the information in it, if everything is correct the " +"invoice status changes to \"Validated\" after using the \"Check Carvajal " +"Status\" button in the Action dropdown. They then proceed to generate a " +"Legal XML which includes a digital signature and a unique code (CUFE), a PDF" +" invoice that includes a QR code and the CUFE is also generated." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:211 +msgid "After this:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:213 +msgid "" +"A ZIP containing the legal XML and the PDF is downloaded and displayed in " +"the invoice chatter:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:222 +msgid "The Electronic Invoice status changes to \"Accepted\"" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:225 +msgid "1.4 Common errors" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:227 +msgid "" +"During the XML validation the most common errors are usually related to " +"missing master data. In such cases, error messages are shown in the chatter " +"after updating the electronic invoice status." +msgstr "" + +#: ../../accounting/localizations/colombia.rst:234 +msgid "" +"After the master data is corrected, it's possible to reprocess the XML with " +"the new data and send the updated version, using the following button:" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:245 +msgid "2. Additional use cases" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:247 +msgid "" +"The process for credit and debit notes is exactly the same as the invoice, " +"the functional workflow remains the same as well." +msgstr "" + +#: ../../accounting/localizations/france.rst:3 +msgid "France" +msgstr "Francia" + +#: ../../accounting/localizations/france.rst:6 +msgid "FEC" +msgstr "" + +#: ../../accounting/localizations/france.rst:8 +msgid "" +"If you have installed the French Accounting, you will be able to download " +"the FEC. For this, go in :menuselection:`Accounting --> Reporting --> France" +" --> FEC`." +msgstr "" + +#: ../../accounting/localizations/france.rst:12 +msgid "" +"If you do not see the submenu **FEC**, go in **Apps** and search for the " +"module called **France-FEC** and verify if it is well installed." +msgstr "" + +#: ../../accounting/localizations/france.rst:16 +msgid "French Accounting Reports" +msgstr "" + +#: ../../accounting/localizations/france.rst:18 +msgid "" +"If you have installed the French Accounting, you will have access to some " +"accounting reports specific to France:" +msgstr "" + +#: ../../accounting/localizations/france.rst:20 +msgid "Bilan comptable" +msgstr "" + +#: ../../accounting/localizations/france.rst:21 +msgid "Compte de résultats" +msgstr "" + +#: ../../accounting/localizations/france.rst:22 +msgid "Plan de Taxes France" +msgstr "" + +#: ../../accounting/localizations/france.rst:25 +msgid "Get the VAT anti-fraud certification with Odoo" +msgstr "" + +#: ../../accounting/localizations/france.rst:27 +msgid "" +"As of January 1st 2018, a new anti-fraud legislation comes into effect in " +"France and DOM-TOM. This new legislation stipulates certain criteria " +"concerning the inalterability, security, storage and archiving of sales " +"data. These legal requirements are implemented in Odoo, version 9 onward, " +"through a module and a certificate of conformity to download." +msgstr "" + +#: ../../accounting/localizations/france.rst:34 +msgid "Is my company required to use an anti-fraud software?" +msgstr "" + +#: ../../accounting/localizations/france.rst:36 +msgid "" +"Your company is required to use an anti-fraud cash register software like " +"Odoo (CGI art. 286, I. 3° bis) if:" +msgstr "" + +#: ../../accounting/localizations/france.rst:39 +msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," +msgstr "" + +#: ../../accounting/localizations/france.rst:40 +msgid "Some of your customers are private individuals (B2C)." +msgstr "" + +#: ../../accounting/localizations/france.rst:42 +msgid "" +"This rule applies to any company size. Auto-entrepreneurs are exempted from " +"VAT and therefore are not affected." +msgstr "" + +#: ../../accounting/localizations/france.rst:46 +msgid "Get certified with Odoo" +msgstr "" + +#: ../../accounting/localizations/france.rst:48 +msgid "Getting compliant with Odoo is very easy." +msgstr "" + +#: ../../accounting/localizations/france.rst:50 +msgid "" +"Your company is requested by the tax administration to deliver a certificate" +" of conformity testifying that your software complies with the anti-fraud " +"legislation. This certificate is granted by Odoo SA to Odoo Enterprise users" +" `here `__. If you " +"use Odoo Community, you should `upgrade to Odoo Enterprise " +"`__ or " +"contact your Odoo service provider." +msgstr "" + +#: ../../accounting/localizations/france.rst:58 +msgid "In case of non-conformity, your company risks a fine of €7,500." +msgstr "" + +#: ../../accounting/localizations/france.rst:60 +msgid "To get the certification just follow the following steps:" +msgstr "" + +#: ../../accounting/localizations/france.rst:62 +msgid "" +"Install the anti-fraud module fitting your Odoo environment from the *Apps* " +"menu:" +msgstr "" + +#: ../../accounting/localizations/france.rst:65 +msgid "" +"if you use Odoo Point of Sale: *l10n_fr_pos_cert*: France - VAT Anti-Fraud " +"Certification for Point of Sale (CGI 286 I-3 bis)" +msgstr "" + +#: ../../accounting/localizations/france.rst:67 +msgid "" +"in any other case: *l10n_fr_certification*: France - VAT Anti-Fraud " +"Certification (CGI 286 I-3 bis)" +msgstr "" + +#: ../../accounting/localizations/france.rst:68 +msgid "" +"Make sure a country is set on your company, otherwise your entries won’t be " +"encrypted for the inalterability check. To edit your company’s data, go to " +":menuselection:`Settings --> Users & Companies --> Companies`. Select a " +"country from the list; Do not create a new country." +msgstr "" + +#: ../../accounting/localizations/france.rst:72 +msgid "" +"Download the mandatory certificate of conformity delivered by Odoo SA `here " +"`__." +msgstr "" + +#: ../../accounting/localizations/france.rst:74 +msgid "" +"To install the module in any system created before December 18th 2017, you " +"should update the modules list. To do so, activate the developer mode from " +"the *Settings* menu. Then go to the *Apps* menu and press *Update Modules " +"List* in the top-menu." +msgstr "" + +#: ../../accounting/localizations/france.rst:78 +msgid "" +"In case you run Odoo on-premise, you need to update your installation and " +"restart your server beforehand." +msgstr "" + +#: ../../accounting/localizations/france.rst:80 +msgid "" +"If you have installed the initial version of the anti-fraud module (prior to" +" December 18th 2017), you need to update it. The module's name was *France -" +" Accounting - Certified CGI 286 I-3 bis*. After an update of the modules " +"list, search for the updated module in *Apps*, select it and click " +"*Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is" +" installed." +msgstr "" + +#: ../../accounting/localizations/france.rst:89 +msgid "Anti-fraud features" +msgstr "" + +#: ../../accounting/localizations/france.rst:91 +msgid "The anti-fraud module introduces the following features:" +msgstr "" + +#: ../../accounting/localizations/france.rst:93 +msgid "" +"**Inalterability**: deactivation of all the ways to cancel or modify key " +"data of POS orders, invoices and journal entries;" +msgstr "" + +#: ../../accounting/localizations/france.rst:95 +msgid "**Security**: chaining algorithm to verify the inalterability;" +msgstr "" + +#: ../../accounting/localizations/france.rst:96 +msgid "" +"**Storage**: automatic sales closings with computation of both period and " +"cumulative totals (daily, monthly, annually)." +msgstr "" + +#: ../../accounting/localizations/france.rst:100 +msgid "Inalterability" +msgstr "" + +#: ../../accounting/localizations/france.rst:102 +msgid "" +"All the possible ways to cancel and modify key data of paid POS orders, " +"confirmed invoices and journal entries are deactivated, if the company is " +"located in France or in any DOM-TOM." +msgstr "" + +#: ../../accounting/localizations/france.rst:106 +msgid "" +"If you run a multi-companies environment, only the documents of such " +"companies are impacted." +msgstr "" + +#: ../../accounting/localizations/france.rst:110 +msgid "Security" +msgstr "Sicurezza" + +#: ../../accounting/localizations/france.rst:112 +msgid "" +"To ensure the inalterability, every order or journal entry is encrypted upon" +" validation. This number (or hash) is calculated from the key data of the " +"document as well as from the hash of the precedent documents." +msgstr "" + +#: ../../accounting/localizations/france.rst:117 +msgid "" +"The module introduces an interface to test the data inalterability. If any " +"information is modified on a document after its validation, the test will " +"fail. The algorithm recomputes all the hashes and compares them against the " +"initial ones. In case of failure, the system points out the first corrupted " +"document recorded in the system." +msgstr "" + +#: ../../accounting/localizations/france.rst:123 +msgid "" +"Users with *Manager* access rights can launch the inalterability check. For " +"POS orders, go to :menuselection:`Point of Sales --> Reporting --> French " +"Statements`. For invoices or journal entries, go to " +":menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." +msgstr "" + +#: ../../accounting/localizations/france.rst:130 +msgid "Storage" +msgstr "Stoccaggio" + +#: ../../accounting/localizations/france.rst:132 +msgid "" +"The system also processes automatic sales closings on a daily, monthly and " +"annual basis. Such closings distinctly compute the sales total of the period" +" as well as the cumulative grand totals from the very first sales entry " +"recorded in the system." +msgstr "" + +#: ../../accounting/localizations/france.rst:138 +msgid "" +"Closings can be found in the *French Statements* menu of Point of Sale, " +"Invoicing and Accounting apps." +msgstr "" + +#: ../../accounting/localizations/france.rst:142 +msgid "" +"Closings compute the totals for journal entries of sales journals (Journal " +"Type = Sales)." +msgstr "" + +#: ../../accounting/localizations/france.rst:144 +msgid "" +"For multi-companies environments, such closings are performed by company." +msgstr "" + +#: ../../accounting/localizations/france.rst:146 +msgid "" +"POS orders are posted as journal entries at the closing of the POS session. " +"Closing a POS session can be done anytime. To prompt users to do it on a " +"daily basis, the module prevents from resuming a session opened more than 24" +" hours ago. Such a session must be closed before selling again." +msgstr "" + +#: ../../accounting/localizations/france.rst:152 +msgid "" +"A period’s total is computed from all the journal entries posted after the " +"previous closing of the same type, regardless of their posting date. If you " +"record a new sales transaction for a period already closed, it will be " +"counted in the very next closing." +msgstr "" + +#: ../../accounting/localizations/france.rst:157 +msgid "" +"For test & audit purposes such closings can be manually generated in the " +"developer mode. Go to :menuselection:`Settings --> Technical --> Automation " +"--> Scheduled Actions` to do so." +msgstr "" + +#: ../../accounting/localizations/france.rst:164 +msgid "Responsibilities" +msgstr "Responsabilità" + +#: ../../accounting/localizations/france.rst:166 +msgid "" +"Do not uninstall the module! If you do so, the hashes will be reset and none" +" of your past data will be longer guaranteed as being inalterable." +msgstr "" + +#: ../../accounting/localizations/france.rst:169 +msgid "" +"Users remain responsible for their Odoo instance and must use it with due " +"diligence. It is not permitted to modify the source code which guarantees " +"the inalterability of data." +msgstr "" + +#: ../../accounting/localizations/france.rst:173 +msgid "" +"Odoo absolves itself of all and any responsibility in case of changes in the" +" module’s functions caused by 3rd party applications not certified by Odoo." +msgstr "" + +#: ../../accounting/localizations/france.rst:178 +msgid "More Information" +msgstr "" + +#: ../../accounting/localizations/france.rst:180 +msgid "" +"You will find more information about this legislation in the official " +"documents:" +msgstr "" + +#: ../../accounting/localizations/france.rst:182 +msgid "" +"`Frequently Asked Questions " +"`__" +msgstr "" + +#: ../../accounting/localizations/france.rst:183 +msgid "" +"`Official Statement " +"`__" +msgstr "" + +#: ../../accounting/localizations/france.rst:184 +msgid "" +"`Item 88 of Finance Law 2016 " +"`__" +msgstr "" + +#: ../../accounting/localizations/germany.rst:3 +msgid "Germany" +msgstr "Germania" + +#: ../../accounting/localizations/germany.rst:6 +msgid "German Chart of Accounts" +msgstr "" + +#: ../../accounting/localizations/germany.rst:8 +msgid "" +"The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can " +"choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the Fiscal Localization " +"section." +msgstr "" + +#: ../../accounting/localizations/germany.rst:12 +#: ../../accounting/localizations/spain.rst:17 +msgid "" +"Be careful, you can only change the accounting package as long as you have " +"not created any accounting entry." +msgstr "" + +#: ../../accounting/localizations/germany.rst:16 +msgid "" +"When you create a new SaaS database, the SKR03 is installed by default." +msgstr "" + +#: ../../accounting/localizations/germany.rst:19 +msgid "German Accounting Reports" +msgstr "" + +#: ../../accounting/localizations/germany.rst:21 +msgid "" +"Here is the list of German-specific reports available on Odoo Enterprise:" +msgstr "" + +#: ../../accounting/localizations/germany.rst:23 +#: ../../accounting/localizations/spain.rst:27 +#: ../../accounting/others/reporting/main_reports.rst:30 +msgid "Balance Sheet" +msgstr "Stato patrimoniale" + +#: ../../accounting/localizations/germany.rst:24 +#: ../../accounting/localizations/nederlands.rst:19 +msgid "Profit & Loss" +msgstr "" + +#: ../../accounting/localizations/germany.rst:25 +msgid "Tax Report (Umsatzsteuervoranmeldung)" +msgstr "" + +#: ../../accounting/localizations/germany.rst:26 +msgid "Partner VAT Intra" +msgstr "" + +#: ../../accounting/localizations/germany.rst:29 +msgid "Export from Odoo to Datev" +msgstr "" + +#: ../../accounting/localizations/germany.rst:31 +msgid "" +"It is possible to export your accounting entries from Odoo to Datev. To be " +"able to use this feature, the german accounting localization needs to be " +"installed on your Odoo Enterprise database. Then you can go in " +":menuselection:`Accounting --> Reporting --> General Ledger` then click on " +"the **Export Datev (csv)** button." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:3 +msgid "Mexico" +msgstr "Messico" + +#: ../../accounting/localizations/mexico.rst:6 +msgid "" +"This documentation is written assuming that you follow and know the official" +" documentation regarding Invoicing, Sales and Accounting and that you have " +"experience working with odoo on such areas, we are not intended to put here " +"procedures that are already explained on those documents, just the " +"information necessary to allow you use odoo in a Company with the country " +"\"Mexico\" set." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:16 +msgid "The mexican localization is a group of 3 modules:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:18 +msgid "" +"**l10n_mx:** All the basic data to manage the accounting, taxes and the " +"chart of account, this proposed chart of account installed is a intended " +"copy of the list of group codes offered by the `SAT`_." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:21 +msgid "" +"**l10n_mx_edi**: All regarding to electronic transactions, CFDI 3.2 and 3.3," +" payment complement, invoice addendum." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:23 +msgid "" +"**l10n_mx_reports**: All mandatory electronic reports for electronic " +"accounting are here (Accounting app required)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:26 +msgid "" +"With the Mexican localization in Odoo you will be able not just to comply " +"with the required features by law in México but to use it as your accounting" +" and invoicing system due to all the set of normal requirements for this " +"market, becoming your Odoo in the perfect solution to administer your " +"company in Mexico." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:36 +msgid "" +"After the configuration we will give you the process to test everything, try" +" to follow step by step in order to allow you to avoid expend time on fix " +"debugging problems. In any step you can recall the step and try again." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:41 +msgid "1. Install the Mexican Accounting Localization" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:43 +msgid "For this, go in Apps and search for Mexico. Then click on *Install*." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:49 +msgid "" +"When creating a database from www.odoo.com, if you choose Mexico as country " +"when creating your account, the mexican localization will be automatically " +"installed." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:54 +msgid "2. Electronic Invoices (CDFI 3.2 and 3.3 format)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:56 +msgid "" +"To enable this requirement in Mexico go to configuration in accounting Go in" +" :menuselection:`Accounting --> Settings` and enable the option on the image" +" with this you will be able to generate the signed invoice (CFDI 3.2 and " +"3.3) and generate the payment complement signed as well (3.3 only) all fully" +" integrate with the normal invoicing flow in Odoo." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:68 +msgid "3. Set you legal information in the company" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:70 +msgid "" +"First, make sure that your company is configured with the correct data. Go " +"in :menuselection:`Settings --> Users --> Companies` and enter a valid " +"address and VAT for your company. Don’t forget to define a mexican fiscal " +"position on your company’s contact." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:77 +msgid "" +"If you want use the Mexican localization on test mode, you can put any known" +" address inside Mexico with all fields for the company address and set the " +"vat to **TCM970625MB1**." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:85 +msgid "" +"4. Set the proper \"Fiscal Position\" on the partner that represent the " +"company" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:87 +msgid "" +"Go In the same form where you are editing the company save the record in " +"order to set this form as a readonly and on readonly view click on the " +"partner link, then edit it and set in the *Invoicing* tab the proper Fiscal " +"Information (for the **Test Environment** this must be *601 - General de Ley" +" Personas Morales*, just search it as a normal Odoo field if you can't see " +"the option)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:94 +msgid "5. Enabling CFDI Version 3.3" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:97 +msgid "" +"This steps are only necessary when you will enable the CFDI 3.3 (only " +"available for V11.0 and above) if you do not have Version 11.0 or above on " +"your SaaS instance please ask for an upgrade sending a ticket to support in " +"https://www.odoo.com/help." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:102 +msgid "Enable debug mode:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:107 +msgid "" +"Go and look the following technical parameter, on :menuselection:`Settings " +"--> Technical --> Parameters --> System Parameters` and set the parameter " +"called *l10n_mx_edi_cfdi_version* to 3.3 (Create it if the entry with this " +"name does not exist)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:113 +msgid "" +"The CFDI 3.2 will be legally possible until November 30th 2017 enable the " +"3.3 version will be a mandatory step to comply with the new `SAT " +"resolution`_ in any new database created since v11.0 released CFDI 3.3 is " +"the default behavior." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:122 +msgid "Important considerations when yo enable the CFDI 3.3" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:124 +#: ../../accounting/localizations/mexico.rst:613 +msgid "" +"Your tax which represent the VAT 16% and 0% must have the \"Factor Type\" " +"field set to \"Tasa\"." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:132 +msgid "" +"You must go to the Fiscal Position configuration and set the proper code (it" +" is the first 3 numbers in the name) for example for the test one you should" +" set 601, it will look like the image." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:139 +msgid "" +"All products must have for CFDI 3.3 the \"SAT code\" and the field " +"\"Reference\" properly set, you can export them and re import them to do it " +"faster." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:146 +msgid "6. Configure the PAC in order to sign properly the invoices" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:148 +msgid "" +"To configure the EDI with the **PACs**, you can go in " +":menuselection:`Accounting --> Settings --> Electronic Invoicing (MX)`. You " +"can choose a PAC within the **List of supported PACs** on the *PAC field* " +"and then enter your PAC username and PAC password." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:154 +msgid "" +"Remember you must sign up in the refereed PAC before hand, that process can " +"be done with the PAC itself on this case we will have two (2) availables " +"`Finkok`_ and `Solución Factible`_." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:158 +msgid "" +"You must process your **Private Key (CSD)** with the SAT institution before " +"follow this steps, if you do not have such information please try all the " +"\"Steps for Test\" and come back to this process when you finish the process" +" proposed for the SAT in order to set this information for your production " +"environment with real transactions." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:168 +msgid "" +"If you ticked the box *MX PAC test environment* there is no need to enter a " +"PAC username or password." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:175 +msgid "" +"Here is a SAT certificate you can use if you want to use the *Test " +"Environment* for the Mexican Accounting Localization." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:178 +msgid "`Certificate`_" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:179 +msgid "`Certificate Key`_" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:180 +msgid "**Password :** 12345678a" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:183 +msgid "7. Configure the tag in sales taxes" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:185 +msgid "" +"This tag is used to set the tax type code, transferred or withhold, " +"applicable to the concept in the CFDI. So, if the tax is a sale tax the " +"\"Tag\" field should be \"IVA\", \"ISR\" or \"IEPS\"." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:192 +msgid "" +"Note that the default taxes already has a tag assigned, but when you create " +"a new tax you should choose a tag." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:199 +msgid "Invoicing" +msgstr "Fatturazione" + +#: ../../accounting/localizations/mexico.rst:201 +msgid "" +"To use the mexican invoicing you just need to do a normal invoice following " +"the normal Odoo's behaviour." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:204 +msgid "" +"Once you validate your first invoice a correctly signed invoice should look " +"like this:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:211 +msgid "" +"You can generate the PDF just clicking on the Print button on the invoice or" +" sending it by email following the normal process on odoo to send your " +"invoice by email." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:218 +msgid "" +"Once you send the electronic invoice by email this is the way it should " +"looks like." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:225 +msgid "Cancelling invoices" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:227 +msgid "" +"The cancellation process is completely linked to the normal cancellation in " +"Odoo." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:229 +msgid "If the invoice is not paid." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:231 +msgid "Go to to the customer invoice journal where the invoice belong to" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:239 +msgid "Check the \"Allow cancelling entries\" field" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:244 +msgid "Go back to your invoice and click on the button \"Cancel Invoice\"" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:249 +msgid "" +"For security reasons it is recommendable return the check on the to allow " +"cancelling to false again, then go to the journal and un check such field." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:252 +msgid "**Legal considerations**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:254 +msgid "A cancelled invoice will automatically cancelled on the SAT." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:255 +msgid "" +"If you retry to use the same invoice after cancelled, you will have as much " +"cancelled CFDI as you tried, then all those xml are important to maintain a " +"good control of the cancellation reasons." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:258 +msgid "" +"You must unlink all related payment done to an invoice on odoo before cancel" +" such document, this payments must be cancelled to following the same " +"approach but setting the \"Allow Cancel Entries\" in the payment itself." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:263 +msgid "Payments (Just available for CFDI 3.3)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:265 +msgid "" +"To generate the payment complement you just must to follow the normal " +"payment process in Odoo, this considerations to understand the behavior are " +"important." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:268 +msgid "" +"All payment done in the same day of the invoice will be considered as It " +"will not be signed, because It is the expected behavior legally required for" +" \"Cash payment\"." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:271 +msgid "" +"To test a regular signed payment just create an invoice for the day before " +"today and then pay it today." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:273 +msgid "You must print the payment in order to retrieve the PDF properly." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:274 +msgid "" +"Regarding the \"Payments in Advance\" you must create a proper invoice with " +"the payment in advance itself as a product line setting the proper SAT code " +"following the procedure on the official documentation `given by the SAT`_ in" +" the section **Apéndice 2 Procedimiento para la emisión de los CFDI en el " +"caso de anticipos recibidos**." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:279 +msgid "" +"Related to topic 4 it is blocked the possibility to create a Customer " +"Payment without a proper invoice." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:284 +msgid "The accounting for Mexico in odoo is composed by 3 reports:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:286 +msgid "Chart of Account (Called and shown as COA)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:287 +msgid "Electronic Trial Balance." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:288 +msgid "DIOT report." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:290 +msgid "" +"1 and 2 are considered as the electronic accounting, and the DIOT is a " +"report only available on the context of the accounting." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:293 +msgid "" +"You can find all those reports in the original report menu on Accounting " +"app." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:299 +msgid "Electronic Accounting (Requires Accounting App)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:302 +msgid "Electronic Chart of account CoA" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:304 +msgid "" +"The electronic accounting never has been easier, just go to " +":menuselection:`Accounting --> Reporting --> Mexico --> COA` and click on " +"the button **Export for SAT (XML)**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:311 +msgid "**How to add new accounts?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:313 +msgid "" +"If you add an account with the coding convention NNN.YY.ZZ where NNN.YY is a" +" SAT coding group then your account will be automatically configured." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:316 +msgid "" +"Example to add an Account for a new Bank account go to " +":menuselection:`Accounting --> Settings --> Chart of Account` and then " +"create a new account on the button \"Create\" and try to create an account " +"with the number 102.01.99 once you change to set the name you will see a tag" +" automatically set, the tags set are the one picked to be used in the COA on" +" xml." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:326 +msgid "**What is the meaning of the tag?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:328 +msgid "" +"To know all possible tags you can read the `Anexo 24`_ in the SAT website on" +" the section called **Código agrupador de cuentas del SAT**." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:332 +msgid "" +"When you install the module l10n_mx and yous Chart of Account rely on it " +"(this happen automatically when you install setting Mexico as country on " +"your database) then you will have the more common tags if the tag you need " +"is not created you can create one on the fly." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:338 +msgid "Electronic Trial Balance" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:340 +msgid "" +"Exactly as the COA but with Initial balance debit and credit, once you have " +"your coa properly set you can go to :menuselection:`Accounting --> Reports " +"--> Mexico --> Trial Balance` this is automatically generated, and can be " +"exported to XML using the button in the top **Export for SAT (XML)** with " +"the previous selection of the period you want to export." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:349 +msgid "" +"All the normal auditory and analysis features are available here also as any" +" regular Odoo Report." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:353 +msgid "DIOT Report (Requires Accounting App)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:355 +msgid "**What is the DIOT and the importance of presenting it SAT**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:357 +msgid "" +"When it comes to procedures with the SAT Administration Service we know that" +" we should not neglect what we present. So that things should not happen in " +"Odoo." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:360 +msgid "" +"The DIOT is the Informational Statement of Operations with Third Parties " +"(DIOT), which is an an additional obligation with the VAT, where we must " +"give the status of our operations to third parties, or what is considered " +"the same, with our providers." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:365 +msgid "" +"This applies both to individuals and to the moral as well, so if we have VAT" +" for submitting to the SAT and also dealing with suppliers it is necessary " +"to. submit the DIOT:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:369 +msgid "**When to file the DIOT and in what format?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:371 +msgid "" +"It is simple to present the DIOT, since like all format this you can obtain " +"it in the page of the SAT, it is the electronic format A-29 that you can " +"find in the SAT website." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:375 +msgid "" +"Every month if you have operations with third parties it is necessary to " +"present the DIOT, just as we do with VAT, so that if in January we have " +"deals with suppliers, by February we must present the information pertinent " +"to said data." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:380 +msgid "**Where the DIOT is presented?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:382 +msgid "" +"You can present DIOT in different ways, it is up to you which one you will " +"choose and which will be more comfortable for you than you will present " +"every month or every time you have dealings with suppliers." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:386 +msgid "" +"The A-29 format is electronic so you can present it on the SAT page, but " +"this after having made up to 500 records." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:389 +msgid "" +"Once these 500 records are entered in the SAT, you must present them to the " +"Local Taxpayer Services Administration (ALSC) with correspondence to your " +"tax address, these records can be presented in a digital storage medium such" +" as a CD or USB, which once validated you will be returned, so do not doubt " +"that you will still have these records and of course, your CD or USB." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:395 +msgid "**One more fact to know: the Batch load?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:397 +msgid "" +"When reviewing the official SAT documents on DIOT, you will find the Batch " +"load, and of course the first thing we think is what is that ?, and " +"according to the SAT site is:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:401 +msgid "" +"The \"batch upload\" is the conversion of records databases of transactions " +"with suppliers made by taxpayers in text files (.txt). These files have the " +"necessary structure for their application and importation into the system of" +" the Informative Declaration of Operations with third parties, avoiding the " +"direct capture and consequently, optimizing the time invested in its " +"integration for the presentation in time and form to the SAT." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:408 +msgid "" +"You can use it to present the DIOT, since it is allowed, which will make " +"this operation easier for you, so that it does not exist to avoid being in " +"line with the SAT in regard to the Information Statement of Operations with " +"Third Parties." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:413 +msgid "You can find the `official information here`_." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:415 +msgid "**How Generate this report in odoo?**" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:417 +msgid "" +"Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions " +"with third partied (DIOT)`." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:422 +msgid "" +"A report view is shown, select last month to report the immediate before " +"month you are or left the current month if it suits to you." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:428 +msgid "Click on \"Export (TXT)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:433 +msgid "" +"Save in a secure place the downloaded file and go to SAT website and follow " +"the necessary steps to declare it." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:437 +msgid "Important considerations on your Supplier and Invice data for the DIOT" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:439 +msgid "" +"All suppliers must have set the fields on the accounting tab called \"DIOT " +"Information\", the *L10N Mx Nationality* field is filled with just select " +"the proper country in the address, you do not need to do anything else " +"there, but the *L10N Mx Type Of Operation* must be filled by you in all your" +" suppliers." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:447 +msgid "" +"There are 3 options of VAT for this report, 16%, 0% and exempt, an invoice " +"line in odoo is considered exempt if no tax on it, the other 2 taxes are " +"properly configured already." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:450 +msgid "" +"Remember to pay an invoice which represent a payment in advance you must ask" +" for the invoice first and then pay it and reconcile properly the payment " +"following standard odoo procedure." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:453 +msgid "" +"You do not need all you data on partners filled to try to generate the " +"supplier invoice, you can fix this information when you generate the report " +"itself." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:456 +msgid "" +"Remember this report only shows the Supplier Invoices that were actually " +"paid." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:458 +msgid "" +"If some of this considerations are not taken into account a message like " +"this will appear when generate the DIOT on TXT with all the partners you " +"need to check on this particular report, this is the reason we recommend use" +" this report not just to export your legal obligation but to generate it " +"before the end of the month and use it as your auditory process to see all " +"your partners are correctly set." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:469 +msgid "Extra Recommended features" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:472 +msgid "Contact Module (Free)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:474 +msgid "" +"If you want to administer properly your customers, suppliers and addresses " +"this module even if it is not a technical need, it is highly recommended to " +"install." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:479 +msgid "Multi currency (Requires Accounting App)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:481 +msgid "" +"In Mexico almost all companies send and receive payments in different " +"currencies if you want to manage such capability you should enable the multi" +" currency feature and you should enable the synchronization with " +"**Banxico**, such feature allow you retrieve the proper exchange rate " +"automatically retrieved from SAT and not being worried of put such " +"information daily in the system manually." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:488 +msgid "Go to settings and enable the multi currency feature." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:494 +msgid "" +"Enabling Explicit errors on the CFDI using the XSD local validator (CFDI " +"3.3)" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:496 +msgid "" +"Frequently you want receive explicit errors from the fields incorrectly set " +"on the xml, those errors are better informed to the user if the check is " +"enable, to enable the Check with xsd feature follow the next steps (with " +"debug mode enabled)." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:501 +msgid "" +"Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:502 +msgid "Look for the Action called \"Download XSD files to CFDI\"" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:503 +msgid "Click on button \"Create Contextual Action\"" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:504 +msgid "" +"Go to the company form :menuselection:`Settings --> Users&Companies --> " +"Companies`" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:505 +msgid "Open any company you have." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:506 +#: ../../accounting/localizations/mexico.rst:529 +msgid "Click on \"Action\" and then on \"Download XSD file to CFDI\"." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:511 +msgid "" +"Now you can make an invoice with any error (for example a product without " +"code which is pretty common) and an explicit error will be shown instead a " +"generic one with no explanation." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:516 +msgid "If you see an error like this:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:518 +msgid "The cfdi generated is not valid" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:520 +msgid "" +"attribute decl. 'TipoRelacion', attribute 'type': The QName value " +"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_TipoRelacion' does " +"not resolve to a(n) simple type definition., line 36" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:524 +msgid "" +"This can be caused because of a database backup restored in anothe server, " +"or when the XSD files are not correctly downloaded. Follow the same steps as" +" above but:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:528 +msgid "Go to the company in which the error occurs." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:535 +msgid "**Error message** (Only applicable on CFDI 3.3):" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:537 +msgid "" +":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_MINLENGTH_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': " +"[facet 'minLength'] The value '' has a length of '0'; this underruns the " +"allowed minimum length of '1'." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:539 +msgid "" +":9:0:ERROR:SCHEMASV:SCHEMAV_CVC_PATTERN_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Concepto', attribute 'NoIdentificacion': " +"[facet 'pattern'] The value '' is not accepted by the pattern '[^|]{1,100}'." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:542 +msgid "" +"**Solution:** You forget to set the proper \"Reference\" field in the " +"product, please go to the product form and set your internal reference " +"properly." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:545 +#: ../../accounting/localizations/mexico.rst:570 +#: ../../accounting/localizations/mexico.rst:580 +#: ../../accounting/localizations/mexico.rst:593 +#: ../../accounting/localizations/mexico.rst:604 +msgid "**Error message**:" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:547 +msgid "" +":6:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}RegimenFiscal': The attribute 'Regimen' is " +"required but missing." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:549 +msgid "" +":5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'RegimenFiscal' is " +"required but missing." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:552 +msgid "" +"**Solution:** You forget to set the proper \"Fiscal Position\" on the " +"partner of the company, go to customers, remove the customer filter and look" +" for the partner called as your company and set the proper fiscal position " +"which is the kind of business you company does related to SAT list of " +"possible values, antoher option can be that you forgot follow the " +"considerations about fiscal positions." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:559 +msgid "" +"Yo must go to the Fiscal Position configuration and set the proper code (it " +"is the first 3 numbers in the name) for example for the test one you should " +"set 601, it will look like the image." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:567 +msgid "" +"For testing purposes this value must be *601 - General de Ley Personas " +"Morales* which is the one required for the demo VAT." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:572 +msgid "" +":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'FormaPago': [facet " +"'enumeration'] The value '' is not an element of the set {'01', '02', '03', " +"'04', '05', '06', '08', '12', '13', '14', '15', '17', '23', '24', '25', " +"'26', '27', '28', '29', '30', '99'}" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:575 +msgid "**Solution:** The payment method is required on your invoice." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:582 +msgid "" +":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_ENUMERATION_VALID: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': " +"[facet 'enumeration'] The value '' is not an element of the set {'00 " +":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' " +"is not a valid value of the atomic type " +"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'. " +":5:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Emisor': The attribute 'Rfc' is required but " +"missing." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:587 +msgid "" +"**Solution:** You must set the address on your company properly, this is a " +"mandatory group of fields, you can go to your company configuration on " +":menuselection:`Settings --> Users & Companies --> Companies` and fill all " +"the required fields for your address following the step :ref:`mx-legal-" +"info`." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:595 +msgid "" +":2:0:ERROR:SCHEMASV:SCHEMAV_CVC_DATATYPE_VALID_1_2_1: Element " +"'{http://www.sat.gob.mx/cfd/3}Comprobante', attribute 'LugarExpedicion': '' " +"is not a valid value of the atomic type " +"'{http://www.sat.gob.mx/sitio_internet/cfd/catalogos}c_CodigoPostal'." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:598 +msgid "" +"**Solution:** The postal code on your company address is not a valid one for" +" Mexico, fix it." +msgstr "" + +#: ../../accounting/localizations/mexico.rst:606 +msgid "" +":18:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: Element " +"'{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' is " +"required but missing. :34:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_4: " +"Element '{http://www.sat.gob.mx/cfd/3}Traslado': The attribute 'TipoFactor' " +"is required but missing.\", '')" +msgstr "" + +#: ../../accounting/localizations/mexico.rst:610 +msgid "" +"**Solution:** Set the mexican name for the tax 0% and 16% in your system and" +" used on the invoice." +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:2 +msgid "Netherlands" +msgstr "Olanda" + +#: ../../accounting/localizations/nederlands.rst:5 +msgid "XAF Export" +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:7 +msgid "" +"With the Dutch accounting localization installed, you will be able to export" +" all your accounting entries in XAF format. For this, you have to go in " +":menuselection:`Accounting --> Reporting --> General Ledger`, you define the" +" entries you want to export using the filters (period, journals, ...) and " +"then you click on the button **EXPORT (XAF)**." +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:14 +msgid "Dutch Accounting Reports" +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:16 +msgid "" +"If you install the Dutch accounting localization, you will have access to " +"some reports that are specific to the Netherlands such as :" +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:21 +msgid "Tax Report (Aangifte omzetbelasting)" +msgstr "" + +#: ../../accounting/localizations/nederlands.rst:23 +msgid "Intrastat Report (ICP)" +msgstr "" + +#: ../../accounting/localizations/spain.rst:3 +msgid "Spain" +msgstr "Spagna" + +#: ../../accounting/localizations/spain.rst:6 +msgid "Spanish Chart of Accounts" +msgstr "" + +#: ../../accounting/localizations/spain.rst:8 +msgid "" +"In Odoo, there are several Spanish Chart of Accounts that are available by " +"default:" +msgstr "" + +#: ../../accounting/localizations/spain.rst:10 +msgid "PGCE PYMEs 2008" +msgstr "" + +#: ../../accounting/localizations/spain.rst:11 +msgid "PGCE Completo 2008" +msgstr "" + +#: ../../accounting/localizations/spain.rst:12 +msgid "PGCE Entitades" +msgstr "" + +#: ../../accounting/localizations/spain.rst:14 +msgid "" +"You can choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the **Fiscal " +"Localization** section." +msgstr "" + +#: ../../accounting/localizations/spain.rst:20 +msgid "" +"When you create a new SaaS database, the PGCE PYMEs 2008 is installed by " +"default." +msgstr "" + +#: ../../accounting/localizations/spain.rst:23 +msgid "Spanish Accounting Reports" +msgstr "" + +#: ../../accounting/localizations/spain.rst:25 +msgid "" +"If the Spanish Accounting Localization is installed, you will have access to" +" accounting reports specific to Spain:" +msgstr "" + +#: ../../accounting/localizations/spain.rst:28 +msgid "Tax Report (Modelo 111)" +msgstr "" + +#: ../../accounting/localizations/spain.rst:29 +msgid "Tax Report (Modelo 115)" +msgstr "" + +#: ../../accounting/localizations/spain.rst:30 +msgid "Tax Report (Modelo 303)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:3 +msgid "Switzerland" +msgstr "Svizzera" + +#: ../../accounting/localizations/switzerland.rst:6 +msgid "ISR (In-payment Slip with Reference number)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:8 +msgid "" +"The ISRs are payment slips used in Switzerland. You can print them directly " +"from Odoo. On the customer invoices, there is a new button called *Print " +"ISR*." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:16 +msgid "" +"The button *Print ISR* only appears there is well a bank account defined on " +"the invoice. You can use CH6309000000250097798 as bank account number and " +"010391391 as CHF ISR reference." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:23 +msgid "Then you open a pdf with the ISR." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:28 +msgid "" +"There exists two layouts for ISR: one with, and one without the bank " +"coordinates. To choose which one to use, there is an option to print the " +"bank information on the ISR. To activate it, go in " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Reports` and tick this box :" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:38 +msgid "Currency Rate Live Update" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:40 +msgid "" +"You can update automatically your currencies rates based on the Federal Tax " +"Administration from Switzerland. For this, go in :menuselection:`Accounting " +"--> Settings`, activate the multi-currencies setting and choose the service " +"you want." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:49 +msgid "Updated VAT for January 2018" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:51 +msgid "" +"Starting from the 1st January 2018, new reduced VAT rates will be applied in" +" Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate" +" for the hotel sector will switch from 3.8% to 3.7%." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:56 +msgid "How to update your taxes in Odoo Enterprise (SaaS or On Premise)?" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:58 +msgid "" +"If you have the V11.1 version, all the work is already been done, you don't " +"have to do anything." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:61 +msgid "" +"If you have started on an earlier version, you first have to update the " +"module \"Switzerland - Accounting Reports\". For this, you go in " +":menuselection:`Apps --> remove the filter \"Apps\" --> search for " +"\"Switzerland - Accounting Reports\" --> open the module --> click on " +"\"upgrade\"`." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:68 +msgid "" +"Once it has been done, you can work on creating new taxes for the updated " +"rates." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:72 +msgid "" +"**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want " +"to keep them since you may have to use both rates for a short period of " +"time. Instead, remember to archive them once you have encoded all your 2017 " +"transactions." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:77 +msgid "The creation of such taxes should be done in the following manner:" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:79 +msgid "" +"**Purchase taxes**: copy the origin tax, change its name, label on invoice, " +"rate and tax group (effective from v10 only)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:82 +msgid "" +"**Sale taxes**: copy the origin tax, change its name, label on invoice, rate" +" and tax group (effective from v10 only). Since the vat report now shows the" +" details for old and new rates, you should also set the tags accordingly to" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:87 +msgid "" +"For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: " +"grid 302 tax" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:90 +msgid "" +"For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: " +"grid 342 tax" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:93 +msgid "" +"You'll find below, as examples, the correct configuration for all taxes " +"included in Odoo by default" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Tax Name**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Rate**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Label on Invoice**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Tax Group (effective from V10)**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Tax Scope**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:97 +msgid "**Tag**" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:99 +msgid "TVA 7.7% sur achat B&S (TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/localizations/switzerland.rst:117 +msgid "7.7%" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:99 +msgid "7.7% achat" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/localizations/switzerland.rst:117 +msgid "TVA 7.7%" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/localizations/switzerland.rst:113 +msgid "Purchases" +msgstr "Acquisti" + +#: ../../accounting/localizations/switzerland.rst:99 +#: ../../accounting/localizations/switzerland.rst:101 +#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/localizations/switzerland.rst:109 +msgid "Switzerland VAT Form: grid 400" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:101 +msgid "TVA 7.7% sur achat B&S (Incl. TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:101 +msgid "7.7% achat Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:103 +msgid "TVA 7.7% sur invest. et autres ch. (TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:103 +msgid "7.7% invest." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:103 +#: ../../accounting/localizations/switzerland.rst:105 +#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/localizations/switzerland.rst:113 +msgid "Switzerland VAT Form: grid 405" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:105 +msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:105 +msgid "7.7% invest. Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:107 +msgid "TVA 3.7% sur achat B&S (TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/localizations/switzerland.rst:121 +msgid "3.7%" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:107 +msgid "3.7% achat" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:107 +#: ../../accounting/localizations/switzerland.rst:109 +#: ../../accounting/localizations/switzerland.rst:111 +#: ../../accounting/localizations/switzerland.rst:113 +#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/localizations/switzerland.rst:121 +msgid "TVA 3.7%" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:109 +msgid "TVA 3.7% sur achat B&S (Incl. TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:109 +msgid "3.7% achat Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:111 +msgid "TVA 3.7% sur invest. et autres ch. (TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:111 +msgid "3.7% invest" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:113 +msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:113 +msgid "3.7% invest Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:115 +msgid "TVA due a 7.7% (TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/localizations/switzerland.rst:117 +#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/localizations/switzerland.rst:121 +#: ../../accounting/overview/process_overview/customer_invoice.rst:113 +#: ../../accounting/receivables/customer_invoices/overview.rst:16 +msgid "Sales" +msgstr "Vendite" + +#: ../../accounting/localizations/switzerland.rst:115 +#: ../../accounting/localizations/switzerland.rst:117 +msgid "" +"Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:117 +msgid "TVA due à 7.7% (Incl. TN)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:117 +msgid "7.7% Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:119 +msgid "TVA due à 3.7% (TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:119 +#: ../../accounting/localizations/switzerland.rst:121 +msgid "" +"Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:121 +msgid "TVA due a 3.7% (Incl. TS)" +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:121 +msgid "3.7% Incl." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:124 +msgid "" +"If you have questions or remarks, please contact our support using " +"odoo.com/help." +msgstr "" + +#: ../../accounting/localizations/switzerland.rst:128 +msgid "" +"Don't forget to update your fiscal positions. If you have a version 11.1 (or" +" higher), there is nothing to do. Otherwise, you will also have to update " +"your fiscal positions accordingly." +msgstr "" + +#: ../../accounting/others.rst:3 +#: ../../accounting/receivables/customer_invoices/overview.rst:108 +msgid "Others" +msgstr "Altri" + +#: ../../accounting/others/adviser.rst:3 +msgid "Adviser" +msgstr "Operazioni contabili" + +#: ../../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 "Stato" + +#: ../../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 "Asset Category" +msgstr "Categoria Immobilizzazione" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Category of asset" +msgstr "Categoria del bene" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date" +msgstr "Data" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Date of asset" +msgstr "Data del bene" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Depreciation Dates" +msgstr "Date di ammortamento" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The way to compute the date of the first depreciation." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Based on last day of purchase period: The depreciation dates will be based" +" on the last day of the purchase month or the purchase year (depending on " +"the periodicity of the depreciations)." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Based on purchase date: The depreciation dates will be based on the " +"purchase date." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "First Depreciation Date" +msgstr "Prima data di ammortamento" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Note that this date does not alter the computation of the first journal " +"entry in case of prorata temporis assets. It simply changes its accounting " +"date" +msgstr "" +"Questa data non modifica il calcolo della prima registrazione contabile in " +"caso di immobilizzazione prorata temporis; cambia semplicemente la data di " +"contabilità." + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross Value" +msgstr "Valore Iniziale" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Gross value of asset" +msgstr "Valore lordo del bene" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Salvage Value" +msgstr "Valore di Realizzo" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "It is the amount you plan to have that you cannot depreciate." +msgstr "È l'ammontare che si prevede di non poter ammortizzare." + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Computation Method" +msgstr "Metodo di calcolo" + +#: ../../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 "Metodo temporale basato su" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Choose the method to use to compute the dates and number of entries." +msgstr "" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"* Number of Entries: Fix the number of entries 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 "Prorata Temporis" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "" +"Indicates that the first depreciation entry for this asset have to be done " +"from the asset date (purchase date) instead of the first January / Start " +"date of fiscal year" +msgstr "" +"Indica che il primo ammortamento di questa immobilizzazione deve essere " +"calcolato dalla data di acquisto e non dal primo gennaio/dalla data di " +"inizio dell'anno fiscale." + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Depreciations" +msgstr "Numero di ammortamenti" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The number of depreciations needed to depreciate your asset" +msgstr "" +"Il numero di ammortamenti necessari per ammortizzare l'immobilizzazione" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "Number of Months in a Period" +msgstr "Numero di mesi in un periodo" + +#: ../../accounting/others/adviser/assets.rst:0 +msgid "The amount of time between two depreciations, in months" +msgstr "Il periodo tra due ammortamenti, in mesi" + +#: ../../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 depreciate 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:35 +msgid "Budgetary Positions" +msgstr "Posizioni di Bilancio" + +#: ../../accounting/others/adviser/budget.rst:37 +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:43 +msgid "" +"To define the positions enter the :menuselection:`Accounting module --> " +"Configuration --> Budgetary Positions`." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:46 +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:52 +msgid "" +"In this case we select the three relevant accounts used wherein we will book" +" our expenses." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:58 +msgid "Click on *Select*." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:63 +msgid "Save the changes to confirm your Budgetary position." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:65 +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:69 +msgid "Analytical account" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:71 +msgid "" +"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:82 +msgid "Set a budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:84 +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:88 +msgid "" +"To set those targets, enter the accounting app, select " +":menuselection:`Advisers --> Budgets` and create a new Budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:91 +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:98 +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:108 +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:111 +msgid "You'll need to **Confirm** and **Approve** the budget." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:114 +msgid "Check your budget" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:116 +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:121 +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:125 +msgid "for more information about booking invoices and purchase orders see:" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:127 +msgid ":doc:`../../receivables/customer_invoices/overview`" +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:129 +msgid "Go back in the budget list and find the Smith Project." +msgstr "" + +#: ../../accounting/others/adviser/budget.rst:131 +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:140 +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/adviser/fiscalyear.rst:93 +msgid ":doc:`../configuration/fiscal_year`" +msgstr "" + +#: ../../accounting/others/adviser/reverse_entry.rst:3 +msgid "Reverse an accounting entry automatically" +msgstr "" + +#: ../../accounting/others/adviser/reverse_entry.rst:5 +msgid "" +"You may want to automatically reverse an accounting entry at a specific " +"date." +msgstr "" + +#: ../../accounting/others/adviser/reverse_entry.rst:8 +msgid "" +"This is, for example, used when you make a provision (e.g. provision for bad" +" debt). When making the accounting entry for the provision, the amount you " +"entered is only an estimated amount. You will only be sure of the amount at " +"the end of the fiscal year. That's why, at that point, you want the " +"accounting entry to be reversed to be able to enter the real loss that " +"occurred." +msgstr "" + +#: ../../accounting/others/adviser/reverse_entry.rst:15 +msgid "" +"For this, you just have to tick the box \"Reverse Automatically\" on the " +"journal entry and to define a reversal date. The accounting entry will be " +"reversed at that date." +msgstr "" + +#: ../../accounting/others/analytic.rst:3 +msgid "Analytic" +msgstr "Analitico" + +#: ../../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. 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:113 +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:117 +msgid "Subcontracting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:119 +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:127 +msgid "You can also track cost with timesheets, see: :doc:`timesheets`" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:130 +msgid "Track costs in accounting" +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:132 +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:135 +msgid "" +"Enter the accounting module, click on :menuselection:`Advisers --> Analytic " +"Accounts --> Open Charts`." +msgstr "" + +#: ../../accounting/others/analytic/purchases_expenses.rst:138 +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:146 +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 "Contabilità analitica" + +#: ../../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 "Reparto marketing" + +#: ../../accounting/others/analytic/usage.rst:43 +msgid "Commercial Department" +msgstr "Reparto commerciale" + +#: ../../accounting/others/analytic/usage.rst:45 +msgid "Administration Department" +msgstr "Reparto amministrativo" + +#: ../../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/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**" +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**" +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 "Marketing" + +#: ../../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 "Commerciale" + +#: ../../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 "Amministrativo" + +#: ../../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 "Credito" + +#: ../../accounting/others/configuration/account_type.rst:29 +msgid "Payable" +msgstr "Debito" + +#: ../../accounting/others/configuration/account_type.rst:31 +msgid "Bank and Cash" +msgstr "Banca e cassa" + +#: ../../accounting/others/configuration/account_type.rst:33 +msgid "Current Assets" +msgstr "Attività correnti" + +#: ../../accounting/others/configuration/account_type.rst:35 +msgid "Non-current Assets" +msgstr "Attività non correnti" + +#: ../../accounting/others/configuration/account_type.rst:37 +msgid "Prepayments" +msgstr "Risconti attivi" + +#: ../../accounting/others/configuration/account_type.rst:39 +msgid "Fixed Assets" +msgstr "Immobilizzazioni" + +#: ../../accounting/others/configuration/account_type.rst:41 +msgid "Current Liabilities" +msgstr "Passività correnti" + +#: ../../accounting/others/configuration/account_type.rst:43 +msgid "Non-current Liabilities" +msgstr "Passività non correnti" + +#: ../../accounting/others/configuration/account_type.rst:45 +msgid "Equity" +msgstr "Patrimonio netto" + +#: ../../accounting/others/configuration/account_type.rst:47 +msgid "Current Year Earnings" +msgstr "Ricavi anno corrente" + +#: ../../accounting/others/configuration/account_type.rst:49 +msgid "Other Income" +msgstr "Altri ricavi" + +#: ../../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 "Ricavi" + +#: ../../accounting/others/configuration/account_type.rst:53 +msgid "Depreciation" +msgstr "Ammortamenti" + +#: ../../accounting/others/configuration/account_type.rst:55 +msgid "Expenses" +msgstr "Costi" + +#: ../../accounting/others/configuration/account_type.rst:57 +msgid "Direct Costs" +msgstr "Costi diretti" + +#: ../../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:86 +msgid "View *Create Account* in our Online Demonstration" +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:3 +msgid "Manage Fiscal Years" +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:5 +msgid "" +"In most cases, the fiscal years last 12 months. If it is your case, you just" +" have to define what is the last day of your fiscal year in the accounting " +"settings. By default, it is set on the 31st December." +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:12 +msgid "" +"However, there might be some exceptions. For example, if it is the first " +"fiscal year of your business, it could last more or less than 12 months. In " +"this case, some additional configuration is required." +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:16 +msgid "" +"Go in :menuselection:`accounting --> configuration --> settings` and " +"activate the fiscal years." +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:22 +msgid "" +"You can then configure your fiscal years in :menuselection:`accounting --> " +"configuration --> fiscal years`." +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:29 +msgid "" +"You only have to create fiscal years if they last more or less than 12 " +"months." +msgstr "" + +#: ../../accounting/others/configuration/fiscal_year.rst:34 +msgid ":doc:`../adviser/fiscalyear`" +msgstr "" + +#: ../../accounting/others/inventory.rst:3 +msgid "Inventory" +msgstr "Magazzino" + +#: ../../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 "Operazione" + +#: ../../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 "Valore di magazzino" + +#: ../../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 "12" + +#: ../../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.rst:3 +msgid "Multicurrency" +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 +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:68 +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 "Tassi di cambio dal vivo" + +#: ../../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 "Estratti conto bancari" + +#: ../../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 "Fatture" + +#: ../../accounting/others/multicurrencies/invoices_payments.rst:64 +#: ../../accounting/payables/supplier_bills.rst:3 +msgid "Vendor Bills" +msgstr "Fatture fornitore" + +#: ../../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 "Rendicontazione" + +#: ../../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 "Attiva la modalità sviluppatore" + +#: ../../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: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 "Conto economico" + +#: ../../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 "Dati di Sintesi" + +#: ../../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 "Libro mastro" + +#: ../../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 "Debiti scaduti" + +#: ../../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 "Crediti esigibili" + +#: ../../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 "Rendiconto finanziario" + +#: ../../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 "Resoconto fiscale" + +#: ../../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 "Imposte" + +#: ../../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: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€ tax excluded" +msgstr "" + +#: ../../accounting/others/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, tax 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 tax 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 tax " +"included or tax 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:80 +msgid "The fiscal positions are not applied on assets and deferred revenues." +msgstr "" + +#: ../../accounting/others/taxes/application.rst:84 +#: ../../accounting/others/taxes/default_taxes.rst:27 +#: ../../accounting/others/taxes/retention.rst:70 +msgid ":doc:`create`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:85 +#: ../../accounting/others/taxes/default_taxes.rst:29 +msgid ":doc:`taxcloud`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:86 +#: ../../accounting/others/taxes/create.rst:70 +#: ../../accounting/others/taxes/default_taxes.rst:31 +msgid ":doc:`tax_included`" +msgstr "" + +#: ../../accounting/others/taxes/application.rst:87 +#: ../../accounting/others/taxes/default_taxes.rst:30 +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 "Registro banca" + +#: ../../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 "Registro imposte criterio di cassa" + +#: ../../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 "Come creare nuove imposte" + +#: ../../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 "Come gestire le ritenute d'acconto?" + +#: ../../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 each of your sales taxes in " +":menuselection:`Accounting --> Configuration --> Accounting --> 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 "La guida implementativa fornirà supporto per i seguenti passi: " + +#: ../../accounting/overview/getting_started/setup.rst:19 +msgid "Completing your company settings" +msgstr "Completamento impostazioni dell'azienda" + +#: ../../accounting/overview/getting_started/setup.rst:20 +msgid "Entering in your bank accounts" +msgstr "Inserimento dei conti bancari" + +#: ../../accounting/overview/getting_started/setup.rst:21 +msgid "Selecting your chart of accounts" +msgstr "Scelta del piano dei conti" + +#: ../../accounting/overview/getting_started/setup.rst:22 +msgid "Confirming your usual tax rates" +msgstr "Conferma delle proprie aliquote fiscali" + +#: ../../accounting/overview/getting_started/setup.rst:23 +msgid "Setting up any foreign currencies" +msgstr "Impostazione di eventuali valute estere" + +#: ../../accounting/overview/getting_started/setup.rst:24 +msgid "Importing your customers" +msgstr "Importazione dei propri clienti" + +#: ../../accounting/overview/getting_started/setup.rst:25 +msgid "Importing your suppliers" +msgstr "Importazione dei propri fornitori" + +#: ../../accounting/overview/getting_started/setup.rst:26 +msgid "Importing your products" +msgstr "Importazione dei propri prodotti" + +#: ../../accounting/overview/getting_started/setup.rst:27 +msgid "Importing your outstanding transactions" +msgstr "Importazione delle operazioni in corso" + +#: ../../accounting/overview/getting_started/setup.rst:28 +msgid "Importing your starting balances" +msgstr "Importazione dei saldi di apertura" + +#: ../../accounting/overview/getting_started/setup.rst:29 +msgid "Define the users for accounting" +msgstr "Definizione degli utenti per la contabilità" + +#: ../../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 "Concetti principali" + +#: ../../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 supports 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 "Multi azienda" + +#: ../../accounting/overview/main_concepts/in_odoo.rst:32 +msgid "" +"Odoo allows one 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 supports more than 50 countries. The Odoo core accounting " +"implements accounting standards that are common to all countries. Specific " +"modules exist 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 costs 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 "Calculate 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 "Valorizzazione inventario" + +#: ../../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 are 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 "Introduzione alla contabilità Odoo" + +#: ../../accounting/overview/main_concepts/intro.rst:11 +msgid "Transcript" +msgstr "Transcript" + +#: ../../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 "Piano dei conti" + +#: ../../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 "Registrazioni contabili" + +#: ../../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 +msgid "Reconciliation" +msgstr "Riconciliazione" + +#: ../../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 "Dare" + +#: ../../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 "Avere" + +#: ../../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 "Conto" + +#: ../../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 "Conto di credito" + +#: ../../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 "Banca" + +#: ../../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 "Estratto conto bancario" + +#: ../../accounting/overview/main_concepts/memento.rst:246 +msgid "Statement XYZ" +msgstr "" + +#: ../../accounting/overview/process_overview.rst:3 +msgid "Process overview" +msgstr "" + +#: ../../accounting/overview/process_overview/customer_invoice.rst:3 +msgid "From Customer Invoice to Payments 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:117 +msgid "Payment" +msgstr "Pagamento" + +#: ../../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 "Riconcilia" + +#: ../../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 +#: ../../accounting/overview/process_overview/supplier_bill.rst:15 +msgid "From Vendor Bill to Payment" +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:18 +msgid "Record a new vendor bill" +msgstr "Registra una nuova fattura fornitore" + +#: ../../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/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 "Vendor Payments" +msgstr "Pagamenti fornitore" + +#: ../../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 "Stati Uniti" + +#: ../../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 --> Vendor 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 "Contiene fatture" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field used for usability purposes" +msgstr "Campo tecnico utilizzato a fini di usabilità" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Hide Payment Method" +msgstr "Nascondere il metodo di pagamento" + +#: ../../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 "" +"Campo tecnico usato per nascondere il metodo di pagamento se il registro " +"selezionato ne ha disponibile solo uno \"manuale\"" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check: Pay bill by check and print it from Odoo." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Batch Deposit: Encase several customer checks at once by generating a batch " +"deposit to submit to your bank. When encoding the bank statement in Odoo, " +"you are suggested to reconcile the transaction with the batch deposit.To " +"enable batch deposit, module account_batch_payment must be installed." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit " +"to your bank. To enable sepa credit transfer, module account_sepa must be " +"installed" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Show Partner Bank Account" +msgstr "Mostrare conto bancario partner" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to know whether the field `partner_bank_account_id` " +"needs to be displayed or not in the payments form views" +msgstr "" +"Campo tecnico usato per sapere se il campo \"partner_bank_account_id\" deve " +"essere visualizzato nelle viste modulo dei pagamenti" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Code" +msgstr "Codice" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "" +"Technical field used to adapt the interface to the payment type selected." +msgstr "" +"Campo tecnico usato per adeguare l'interfaccia al tipo di pagamento " +"selezionato." + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Check Number" +msgstr "Numero assegno" + +#: ../../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 "" +"Il registro selezionato è configurato per stampare i numeri di assegno. Se " +"l'assegno prestampato ha già un numero o se la numerazione esistente è " +"sbagliata, è possibile cambiarla nella pagina di configurazione del " +"registro." + +#: ../../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 +#: ../../accounting/receivables/customer_payments/payment_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/recording.rst:129 +msgid ":doc:`check`" +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 "Come gestire le fatture fornitore?" + +#: ../../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 "Quantità ordinate" + +#: ../../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 +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:53 +msgid "Customer Invoices" +msgstr "Fatture cliente" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3 +msgid "Offer cash discounts" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5 +msgid "" +"Cash discounts are incentives you can offer to customers to motivate them to" +" pay within a specific time frame. For instance, you offer a 2% discount if " +"the customer pays you within the first 5 days of the invoice, when it is due" +" in 30 days. This approach can greatly improve your average collection " +"period." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:12 +msgid "Set up a cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:14 +msgid "" +"To set up a cash discount, go to :menuselection:`Accounting --> " +"Configuration --> Management --> Payment Terms` and click on *Create*. Add a" +" *Percent* type of term with a corresponding value (e.g. 98% of the total " +"price for a 2% discount) and the number of days during which the offer is " +"valid. You can also change the default balance term if needed." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:25 +msgid "Start offering the cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27 +msgid "" +"Now, you can create a customer invoice and select the cash discount payment " +"term you added. Once the invoice is validated, Odoo will automatically split" +" the account receivables part of the journal entry into two installments " +"having different due dates. Since the discounted price is already " +"calculated, your payment controls will be simplified." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:37 +msgid "Grant the cash discount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:39 +msgid "" +"The customer fulfilled the payment terms and therefore benefits from the " +"cash discount. When you process the bank statement, match the payment with " +"the related journal entry. Then, select the remaining cash discount and " +"click on *Create Write-off* to reconcile it." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:48 +msgid "" +"You can also create a dedicated reconciliation model to make the process " +"easier. In this case, you should add a tax to the model based on the taxes " +"applied to your invoices. This means that if you handle multiple tax rates, " +"you need to create several reconciliation models. Note that depending on " +"your localisation, you might already have a Cash Discount model available by" +" default." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:56 +msgid "Register the full payment" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58 +msgid "" +"In this case, the customer has not fulfilled the payment term and cannot " +"benefit from the cash discount. When you process the bank statement, match " +"the payment with the two related journal entries." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:67 +msgid ":doc:`../../receivables/customer_invoices/payment_terms`" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:2 +msgid "Set up cash roundings" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:4 +msgid "" +"In some currencies, the smallest coins do not exist. For example, in " +"Switzerland, there is no coin for 0.01 CHF. For this reason, if invoices are" +" paid in cash, you have to round their total amount to the smallest coin " +"that exist in the currency. For the CHF, the smallest coin is 0.05 CHF." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:10 +msgid "There are two strategies for the rounding:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:12 +msgid "Add a line on the invoice for the rounding" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:14 +msgid "Add the rounding in the tax amount" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:16 +msgid "Both strategies are applicable in Odoo." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:21 +msgid "" +"First, you have to activate the feature. For this, go in " +":menuselection:`Accounting --> Configuration --> Settings` and activate the " +"Cash Rounding." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:28 +msgid "" +"There is a new menu to manage cash roundings in :menuselection:`Accounting " +"--> Configuration --> Management --> Cash roundings`." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:31 +msgid "" +"Now, you can create cash roundings. You can choose between two rounding " +"strategies:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:34 +msgid "" +"**Add a rounding line**: if a rounding is necessary, Odoo will add a line on" +" your customer invoice to take this rounding into account. You also have to " +"define the account in which the rounding will go." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:39 +msgid "" +"**Modify tax amount:** Odoo will add the rounding to the amount of the " +"highest tax." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:46 +msgid "Apply roundings" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/cash_rounding.rst:48 +msgid "" +"Once your roundings are created, you can apply them on customer invoices. On" +" the customer invoices, there is a new field called **Cash Rounding Method**" +" where you can simply choose one of the rounding methods created previously." +" If needed, a rounding will be applied to the invoice." +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 "Prodotto" + +#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:69 +msgid "Deferred Revenue Type" +msgstr "Tipo ricavi differiti" + +#: ../../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/deferred_revenues.rst:116 +#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 +msgid ":doc:`overview`" +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 (eg: 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 "Data di scadenza" + +#: ../../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/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 "Contratti" + +#: ../../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 "Pagamenti cliente" + +#: ../../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 "" +"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 +#: ../../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 "Carte di credito" + +#: ../../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 +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 "Follow-up on invoices and get paid faster" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:5 +msgid "" +"It is essential for your business to collect payments when they are overdue." +" Odoo will help you identify payments that are late and will allow you to " +"send the appropriate reminders." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:10 +msgid "Manage your follow-ups" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:13 +msgid "" +"We recommend that you reconcile your bank statements before launching your " +"follow-up process. It will avoid you the trouble of sending a statement to a" +" customer that has already paid you." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:17 +msgid "" +"The overdue invoices you need to follow-up on are available by default in " +":menuselection:`Accounting --> Sales --> Follow-up Reports`. There, you can " +"easily send a reminder by email or print it as a letter. Then, you can click" +" on the *Done* button to view the next follow-up that needs your attention." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:23 +msgid "" +"Otherwise, if now is not the time for a reminder, click on *Remind me " +"later*. You will get the next report according to the *Next Reminder Date* " +"set on the statement." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:28 +msgid "" +"To avoid sending too many reminders in a short period of time, change the " +"number of days calculated between each report by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Payment " +"Follow-up`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:33 +msgid "" +"You can also set a trust level for your customers by marking them as bad, " +"normal or good debtors on the follow-up reports." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:40 +msgid "Send reminders in batch" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:42 +msgid "" +"To get your follow-up process easier, you can send reminder emails in batch " +"from your follow-up reports page. Select all the reports you would like to " +"process, click on *Action* and then on *Process Follow-ups*. A pdf document " +"containing all of the follow-up letters for you to print will also be " +"automatically generated." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:52 +msgid "Plan a follow-up process" +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:54 +msgid "" +"To plan a follow-up process, go to :menuselection:`Accounting --> " +"Configuration --> Settings` and activate the *Follow-up Levels* feature " +"under the *Customer Payments* section. Then, click on the new *Follow-up " +"Levels* button that has appeared on your settings page." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:59 +msgid "" +"A follow-up plan with several actions is available by default in Odoo, but " +"you can customize it any way you want. Depending on a specific number of " +"overdue days, plan to send an email, a letter or to undertake a manual " +"action. You can also edit the template used for the statement according to " +"the stage of the process." +msgstr "" + +#: ../../accounting/receivables/customer_payments/followup.rst:69 +msgid "" +"If you would like to get a reminder before the actual due date, set a " +"negative number of due days." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:3 +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:29 +msgid "Get paid with SEPA" +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_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 Direct Debit allows you to withdraw money from the bank accounts of " +"your customers with their approval." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:13 +msgid "" +"With Odoo, you can record customer mandates, generate an SDD XML file " +"containing customer payments and upload it in your bank interface. The file " +"follows the SEPA Direct Debit PAIN.008.001.02 specifications. This is a " +"well-defined standard that makes consensus among banks." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:21 +msgid "" +"Go in :menuselection:`Accounting --> Configuration --> Settings` and " +"activate the SEPA Direct Debit (SDD) Feature. Enter the Creditor Identifier " +"of your company. This number is provided by your bank." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:32 +msgid "Direct Debit Mandates" +msgstr "Mandati di addebito diretto" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:34 +msgid "" +"Before withdrawing money from a customer bank account, your customer has to " +"sign a mandate. Go in :menuselection:`Accounting --> Sales --> Direct Debit " +"Mandates` and create a new mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:41 +msgid "SEPA Direct Debit only works between IBAN Bank Accounts." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:43 +msgid "" +"Once you have entered all the information in the customer mandate, you can " +"print it and ask your customer to sign it. Once it is done, you can upload " +"the mandate signed by your customer on the mandate in Odoo." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:50 +msgid "You can now validate the mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:55 +msgid "Let's create an invoice for that customer." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:57 +msgid "" +"When you will validate this invoice, the payment will be automatically " +"generated and your invoice will be directly marked as paid." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:61 +msgid "" +"If you already had some invoices for that customer that could be paid using " +"that mandate, it's still possible to do it. Go on the invoice, click on " +"register payment and choose the Sepa Direct Debit as payment method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:67 +msgid "Generate SDD Files" +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:69 +msgid "" +"You can generate the SDD File with all the customer payments to send to your" +" bank directly from the accounting dashboard :" +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:75 +msgid "" +"You select the payments in the list that you want to include in your SDD " +"File, click on action and select \"Generate Direct Debit XML\"." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:81 +msgid "" +"You can now download the XML file generated by Odoo and upload it in your " +"bank interface." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:85 +msgid "" +"You can retrieve all the generated XML by activating the developer mode and " +"going in :menuselection:`Accounting --> Configuration --> Payments --> SDD " +"Payment File`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:89 +msgid "Close or revoke a mandate" +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:91 +msgid "" +"The Direct Debit mandate will be closed automatically once the end date " +"defined on it is reached. However, you can **close** a mandate earlier than " +"initially planned. To do that, simply go on the mandate and click on the " +"\"Close\" button.The end date of the mandate will be updated to today's " +"date. This means you will not be able to pay invoices with an invoice date " +"superior to this end date. Be careful, once a mandate is closed, it cannot " +"be reopened." +msgstr "" + +#: ../../accounting/receivables/customer_payments/payment_sepa.rst:99 +msgid "" +"You can also **revoke** a mandate. In that case, you won't be able to pay " +"any invoice using that mandate anymore, no matter the invoice date.To do " +"that, simply go on the mandate and click on the \"Revoke\" button." +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 "" diff --git a/locale/it/LC_MESSAGES/applications.po b/locale/it/LC_MESSAGES/applications.po new file mode 100644 index 000000000..3d0a39fd7 --- /dev/null +++ b/locale/it/LC_MESSAGES/applications.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:14+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../applications.rst:3 +msgid "Applications" +msgstr "Applicazioni" diff --git a/locale/it/LC_MESSAGES/crm.po b/locale/it/LC_MESSAGES/crm.po new file mode 100644 index 000000000..f6cfa411f --- /dev/null +++ b/locale/it/LC_MESSAGES/crm.po @@ -0,0 +1,1161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# Luigi Di Naro , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-07-23 12:10+0200\n" +"PO-Revision-Date: 2018-10-19 08:14+0000\n" +"Last-Translator: Luigi Di Naro , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../crm.rst:5 +msgid "CRM" +msgstr "CRM" + +#: ../../crm/acquire_leads.rst:3 +msgid "Acquire leads" +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:3 +msgid "Convert leads into opportunities" +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:5 +msgid "" +"The system can generate leads instead of opportunities, in order to add a " +"qualification step before converting a *Lead* into an *Opportunity* and " +"assigning to the right sales people. You can activate this mode from the CRM" +" Settings. It applies to all your sales channels by default. But you can " +"make it specific for specific channels from their configuration form." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:13 +#: ../../crm/acquire_leads/generate_from_website.rst:41 +#: ../../crm/optimize/onsip.rst:13 ../../crm/track_leads/lead_scoring.rst:12 +#: ../../crm/track_leads/prospect_visits.rst:12 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../crm/acquire_leads/convert.rst:15 +msgid "" +"For this feature to work, go to :menuselection:`CRM --> Configuration --> " +"Settings` and activate the *Leads* feature." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:21 +msgid "" +"You will now have a new submenu *Leads* under *Pipeline* where they will " +"aggregate." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:28 +msgid "Convert a lead into an opportunity" +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:30 +msgid "" +"When you click on a *Lead* you will have the option to convert it to an " +"opportunity and decide if it should still be assigned to the same " +"channel/person and if you need to create a new customer." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:37 +msgid "" +"If you already have an opportunity with that customer Odoo will " +"automatically offer you to merge with that opportunity. In the same manner, " +"Odoo will automatically offer you to link to an existing customer if that " +"customer already exists." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_email.rst:3 +msgid "Generate leads/opportunities from emails" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_email.rst:5 +msgid "" +"Automating the lead/opportunity generation will considerably improve your " +"efficiency. By default, any email sent to *sales@database\\_domain.ext* will" +" create an opportunity in the pipeline of the default sales channel." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_email.rst:11 +msgid "Configure email aliases" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_email.rst:13 +msgid "" +"Each sales channel can have its own email alias, to generate " +"leads/opportunities automatically assigned to it. It is useful if you manage" +" several sales teams with specific business processes. You will find the " +"configuration of sales channels under :menuselection:`Configuration --> " +"Sales Channels`." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:3 +msgid "Generate leads/opportunities from your website contact page" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:5 +msgid "" +"Automating the lead/opportunity generation will considerably improve your " +"efficiency. Any visitor using the contact form on your website will create a" +" lead/opportunity in the pipeline." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:10 +msgid "Use the contact us on your website" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:12 +msgid "You should first go to your website app." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:14 +msgid "|image0|\\ |image1|" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:16 +msgid "" +"With the CRM app installed, you benefit from ready-to-use contact form on " +"your Odoo website that will generate leads/opportunities automatically." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:23 +msgid "" +"To change to a specific sales channel, go to :menuselection:`Website --> " +"Configuration --> Settings` under *Communication* you will find the Contact " +"Form info and where to change the *Sales Channel* or *Salesperson*." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:32 +#: ../../crm/acquire_leads/generate_from_website.rst:50 +msgid "Create a custom contact form" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:34 +msgid "" +"You may want to know more from your visitor when they use they want to " +"contact you. You will then need to build a custom contact form on your " +"website. Those contact forms can generate multiple types of records in the " +"system (emails, leads/opportunities, project tasks, helpdesk tickets, " +"etc...)" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:43 +msgid "" +"You will need to install the free *Form Builder* module. Only available in " +"Odoo Enterprise." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:52 +msgid "" +"From any page you want your contact form to be in, in edit mode, drag the " +"form builder in the page and you will be able to add all the fields you " +"wish." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:59 +msgid "" +"By default any new contact form will send an email, you can switch to " +"lead/opportunity generation in *Change Form Parameters*." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:63 +msgid "" +"If the same visitors uses the contact form twice, the second information " +"will be added to the first lead/opportunity in the chatter." +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:67 +msgid "Generate leads instead of opportunities" +msgstr "" + +#: ../../crm/acquire_leads/generate_from_website.rst:69 +msgid "" +"When using a contact form, it is advised to use a qualification step before " +"assigning to the right sales people. To do so, activate *Leads* in CRM " +"settings and refer to :doc:`convert`." +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:3 +msgid "Send quotations" +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:5 +msgid "" +"When you qualified one of your lead into an opportunity you will most likely" +" need to them send a quotation. You can directly do this in the CRM App with" +" Odoo." +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:13 +msgid "Create a new quotation" +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:15 +msgid "" +"By clicking on any opportunity or lead, you will see a *New Quotation* " +"button, it will bring you into a new menu where you can manage your quote." +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:22 +msgid "" +"You will find all your quotes to that specific opportunity under the " +"*Quotations* menu on that page." +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:29 +msgid "Mark them won/lost" +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:31 +msgid "" +"Now you will need to mark your opportunity as won or lost to move the " +"process along." +msgstr "" + +#: ../../crm/acquire_leads/send_quotes.rst:34 +msgid "" +"If you mark them as won, they will move to your *Won* column in your Kanban " +"view. If you however mark them as *Lost* they will be archived." +msgstr "" + +#: ../../crm/optimize.rst:3 +msgid "Optimize your Day-to-Day work" +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:3 +msgid "Synchronize Google Calendar with Odoo" +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:5 +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 "" +"Odoo è perfettamente integrato con i calendari di Google, è possibile " +"visionare e gestire le riunioni da entrambe le piattaforme (gli " +"aggiornamenti sono bidirezionali)." + +#: ../../crm/optimize/google_calendar_credentials.rst:10 +msgid "Setup in Google" +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:11 +msgid "" +"Go to `Google APIs platform `__ to " +"generate Google Calendar API credentials. Log in with your Google account." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:14 +msgid "Go to the API & Services page." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:19 +msgid "Search for *Google Calendar API* and select it." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:27 +msgid "Enable the API." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:32 +msgid "" +"Select or create an API project to store the credentials if not yet done " +"before. Give it an explicit name (e.g. Odoo Sync)." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:35 +msgid "Create credentials." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:40 +msgid "" +"Select *Web browser (Javascript)* as calling source and *User data* as kind " +"of data." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:46 +msgid "" +"Then you can create a Client ID. Enter the name of the application (e.g. " +"Odoo Calendar) 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/optimize/google_calendar_credentials.rst:55 +msgid "" +"Go through the Consent Screen step by entering a product name (e.g. Odoo " +"Calendar). 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/optimize/google_calendar_credentials.rst:60 +msgid "" +"Finally you are provided with your **Client ID**. Go to *Credentials* to get" +" the **Client Secret** as well. Both of them are required in Odoo." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:67 +msgid "Setup in Odoo" +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:69 +msgid "" +"Install the **Google Calendar** App from the *Apps* menu or by checking the " +"option in :menuselection:`Settings --> General Settings`." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:75 +msgid "" +"Go to :menuselection:`Settings --> General Settings` and enter your **Client" +" ID** and **Client Secret** in Google Calendar option." +msgstr "" + +#: ../../crm/optimize/google_calendar_credentials.rst:81 +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/optimize/google_calendar_credentials.rst:89 +msgid "As of now you no longer have excuses to miss a meeting!" +msgstr "" + +#: ../../crm/optimize/onsip.rst:3 +msgid "Use VOIP services in Odoo with OnSIP" +msgstr "" + +#: ../../crm/optimize/onsip.rst:6 +msgid "Introduction" +msgstr "Introduzione" + +#: ../../crm/optimize/onsip.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with OnSIP (www.onsip.com). In that" +" case, the installation and setup of an Asterisk server is not necessary as " +"the whole infrastructure is hosted and managed by OnSIP." +msgstr "" + +#: ../../crm/optimize/onsip.rst:10 +msgid "" +"You will need to open an account with OnSIP to use this service. Before " +"doing so, make sure that your area and the areas you wish to call are " +"covered by the service. After opening an OnSIP account, follow the " +"configuration procedure below." +msgstr "" + +#: ../../crm/optimize/onsip.rst:15 +msgid "Go to Apps and install the module **VoIP OnSIP**." +msgstr "" + +#: ../../crm/optimize/onsip.rst:20 +msgid "" +"Go to Settings/General Settings. In the section Integrations/Asterisk " +"(VoIP), fill in the 3 fields:" +msgstr "" + +#: ../../crm/optimize/onsip.rst:22 +msgid "" +"**OnSIP Domain** is the domain you chose when creating an account on " +"www.onsip.com. If you don't know it, log in to https://admin.onsip.com/ and " +"you will see it in the top right corner of the screen." +msgstr "" + +#: ../../crm/optimize/onsip.rst:23 +msgid "**WebSocket** should contain wss://edge.sip.onsip.com" +msgstr "" + +#: ../../crm/optimize/onsip.rst:24 +msgid "**Mode** should be Production" +msgstr "" + +#: ../../crm/optimize/onsip.rst:29 +msgid "" +"Go to **Settings/Users**. In the form view of each VoIP user, in the " +"Preferences tab, fill in the section **PBX Configuration**:" +msgstr "" + +#: ../../crm/optimize/onsip.rst:31 +msgid "**SIP Login / Browser's Extension**: the OnSIP 'Username'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:32 +msgid "**OnSIP authorization User**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:33 +msgid "**SIP Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:34 +msgid "**Handset Extension**: the OnSIP 'Extension'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:36 +msgid "" +"You can find all this information by logging in at " +"https://admin.onsip.com/users, then select the user you want to configure " +"and refer to the fields as pictured below." +msgstr "" + +#: ../../crm/optimize/onsip.rst:41 +msgid "" +"You can now make phone calls by clicking the phone icon in the top right " +"corner of Odoo (make sure you are logged in as a user properly configured in" +" Odoo and in OnSIP)." +msgstr "" + +#: ../../crm/optimize/onsip.rst:45 +msgid "" +"If you see a *Missing Parameters* message in the Odoo softphone, make sure " +"to refresh your Odoo window and try again." +msgstr "" + +#: ../../crm/optimize/onsip.rst:52 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g.: +16506913277 (where +1 is the " +"international prefix for the United States)." +msgstr "" + +#: ../../crm/optimize/onsip.rst:57 +msgid "" +"You can now also receive phone calls. Your number is the one provided by " +"OnSIP. Odoo will ring and display a notification." +msgstr "" + +#: ../../crm/optimize/onsip.rst:63 +msgid "OnSIP on Your Cell Phone" +msgstr "" + +#: ../../crm/optimize/onsip.rst:65 +msgid "" +"In order to make and receive phone calls when you are not in front of your " +"computer, you can use a softphone app on your cell phone in parallel of Odoo" +" VoIP. This is useful for on-the-go calls, but also to make sure to hear " +"incoming calls, or simply for convenience. Any SIP softphone will work." +msgstr "" + +#: ../../crm/optimize/onsip.rst:67 +msgid "" +"On Android and iOS, OnSIP has been successfully tested with `Grandstream " +"Wave `_." +" When creating an account, select OnSIP in the list of carriers. You will " +"then have to configure it as follows:" +msgstr "" + +#: ../../crm/optimize/onsip.rst:69 +msgid "**Account name**: OnSIP" +msgstr "" + +#: ../../crm/optimize/onsip.rst:70 +msgid "**SIP Server**: the OnSIP 'Domain'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:71 +msgid "**SIP User ID**: the OnSIP 'Username'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:72 +msgid "**SIP Authentication ID**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:73 +msgid "**Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../crm/optimize/onsip.rst:75 +msgid "" +"Aside from initiating calls from Grandstream Wave on your phone, you can " +"also initiate calls by clicking phone numbers in your browser on your PC. " +"This will make Grandstream Wave ring and route the call via your phone to " +"the other party. This approach is useful to avoid wasting time dialing phone" +" numbers. In order to do so, you will need the Chrome extension `OnSIP Call " +"Assistant `_." +msgstr "" + +#: ../../crm/optimize/onsip.rst:79 +msgid "" +"The downside of using a softphone on your cell phone is that your calls will" +" not be logged in Odoo as the softphone acts as an independent separate app." +msgstr "" + +#: ../../crm/optimize/setup.rst:3 +msgid "Configure your VOIP Asterisk server for Odoo" +msgstr "" + +#: ../../crm/optimize/setup.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../crm/optimize/setup.rst:9 +msgid "Dependencies" +msgstr "Dipendenze" + +#: ../../crm/optimize/setup.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../crm/optimize/setup.rst:13 +msgid "wget" +msgstr "" + +#: ../../crm/optimize/setup.rst:14 +msgid "gcc" +msgstr "" + +#: ../../crm/optimize/setup.rst:15 +msgid "g++" +msgstr "" + +#: ../../crm/optimize/setup.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../crm/optimize/setup.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../crm/optimize/setup.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../crm/optimize/setup.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../crm/optimize/setup.rst:37 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:43 +msgid "**run:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:49 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:57 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:63 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:69 +msgid "**The result should be:**" +msgstr "" + +#: ../../crm/optimize/setup.rst:86 +msgid "Asterisk" +msgstr "" + +#: ../../crm/optimize/setup.rst:88 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there `_." +msgstr "" + +#: ../../crm/optimize/setup.rst:90 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../crm/optimize/setup.rst:96 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../crm/optimize/setup.rst:102 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../crm/optimize/setup.rst:108 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../crm/optimize/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/optimize/setup.rst:116 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../crm/optimize/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/optimize/setup.rst:125 +msgid "DTLS Certificates" +msgstr "" + +#: ../../crm/optimize/setup.rst:127 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../crm/optimize/setup.rst:133 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../crm/optimize/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/optimize/setup.rst:146 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../crm/optimize/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/optimize/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/optimize/setup.rst:186 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../crm/optimize/setup.rst:193 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../crm/optimize/setup.rst:202 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../crm/optimize/setup.rst:204 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../crm/optimize/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/optimize/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/performance.rst:3 +msgid "Analyze performance" +msgstr "" + +#: ../../crm/performance/turnover.rst:3 +msgid "Get an accurate probable turnover" +msgstr "" + +#: ../../crm/performance/turnover.rst:5 +msgid "" +"As you progress in your sales cycle, and move from one stage to another, you" +" can expect to have more precise information about a given opportunity " +"giving you an better idea of the probability of closing it, this is " +"important to see your expected turnover in your various reports." +msgstr "" + +#: ../../crm/performance/turnover.rst:11 +msgid "Configure your kanban stages" +msgstr "" + +#: ../../crm/performance/turnover.rst:13 +msgid "" +"By default, Odoo Kanban view has four stages: New, Qualified, Proposition, " +"Won. Respectively with a 10, 30, 70 and 100% probability of success. You can" +" add stages as well as edit them. By refining default probability of success" +" for your business on stages, you can make your probable turnover more and " +"more accurate." +msgstr "" + +#: ../../crm/performance/turnover.rst:25 +msgid "" +"Every one of your opportunities will have the probability set by default but" +" you can modify them manually of course." +msgstr "" + +#: ../../crm/performance/turnover.rst:29 +msgid "Set your opportunity expected revenue & closing date" +msgstr "" + +#: ../../crm/performance/turnover.rst:31 +msgid "" +"When you get information on a prospect, it is important to set an expected " +"revenue and expected closing date. This will let you see your total expected" +" revenue by stage as well as give a more accurate probable turnover." +msgstr "" + +#: ../../crm/performance/turnover.rst:40 +msgid "See the overdue or closing soon opportunities" +msgstr "" + +#: ../../crm/performance/turnover.rst:42 +msgid "" +"In your pipeline, you can filter opportunities by how soon they will be " +"closing, letting you prioritize." +msgstr "" + +#: ../../crm/performance/turnover.rst:48 +msgid "" +"As a sales manager, this tool can also help you see potential ways to " +"improve your sale process, for example a lot of opportunities in early " +"stages but with near closing date might indicate an issue." +msgstr "" + +#: ../../crm/performance/turnover.rst:53 +msgid "View your total expected revenue and probable turnover" +msgstr "" + +#: ../../crm/performance/turnover.rst:55 +msgid "" +"While in your Kanban view you can see the expected revenue for each of your " +"stages. This is based on each opportunity expected revenue that you set." +msgstr "" + +#: ../../crm/performance/turnover.rst:62 +msgid "" +"As a manager you can go to :menuselection:`CRM --> Reporting --> Pipeline " +"Analysis` by default *Probable Turnover* is set as a measure. This report " +"will take into account the revenue you set on each opportunity but also the " +"probability they will close. This gives you a much better idea of your " +"expected revenue allowing you to make plans and set targets." +msgstr "" + +#: ../../crm/performance/win_loss.rst:3 +msgid "Check your Win/Loss Ratio" +msgstr "" + +#: ../../crm/performance/win_loss.rst:5 +msgid "" +"To see how well you are doing with your pipeline, take a look at the " +"Win/Loss ratio." +msgstr "" + +#: ../../crm/performance/win_loss.rst:8 +msgid "" +"To access this report, go to your *Pipeline* view under the *Reporting* tab." +msgstr "" + +#: ../../crm/performance/win_loss.rst:11 +msgid "" +"From there you can filter to which opportunities you wish to see, yours, the" +" ones from your sales channel, your whole company, etc. You can then click " +"on filter and check Won/Lost." +msgstr "" + +#: ../../crm/performance/win_loss.rst:18 +msgid "You can also change the *Measures* to *Total Revenue*." +msgstr "" + +#: ../../crm/performance/win_loss.rst:23 +msgid "You also have the ability to switch to a pie chart view." +msgstr "" + +#: ../../crm/pipeline.rst:3 +msgid "Organize the pipeline" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:3 +msgid "Manage lost opportunities" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:5 +msgid "" +"While working with your opportunities, you might lose some of them. You will" +" want to keep track of the reasons you lost them and also which ways Odoo " +"can help you recover them in the future." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:10 +msgid "Mark a lead as lost" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:12 +msgid "" +"While in your pipeline, select any opportunity you want and you will see a " +"*Mark Lost* button." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:15 +msgid "" +"You can then select an existing *Lost Reason* or create a new one right " +"there." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:22 +msgid "Manage & create lost reasons" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:24 +msgid "" +"You will find your *Lost Reasons* under :menuselection:`Configuration --> " +"Lost Reasons`." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:26 +msgid "" +"You can select & rename any of them as well as create a new one from there." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:30 +msgid "Retrieve lost opportunities" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:32 +msgid "" +"To retrieve lost opportunities and do actions on them (send an email, make a" +" feedback call, etc.), select the *Lost* filter in the search bar." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:39 +msgid "You will then see all your lost opportunities." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:41 +msgid "" +"If you want to refine them further, you can add a filter on the *Lost " +"Reason*." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:44 +msgid "For Example, *Too Expensive*." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:50 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:52 +msgid "" +"From the Kanban view with the filter(s) in place, you can select any " +"opportunity you wish and work on it as usual. You can also restore it by " +"clicking on *Archived*." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:59 +msgid "" +"You can also restore items in batch from the Kanban view when they belong to" +" the same stage. Select *Restore Records* in the column options. You can " +"also archive the same way." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:66 +msgid "To select specific opportunities, you should switch to the list view." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:71 +msgid "" +"Then you can select as many or all opportunities and select the actions you " +"want to take." +msgstr "" + +#: ../../crm/pipeline/lost_opportunities.rst:78 +msgid ":doc:`../performance/win_loss`" +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:3 +msgid "Manage multiple sales teams" +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:5 +msgid "" +"In Odoo, you can manage several sales teams, departments or channels with " +"specific sales processes. To do so, we use the concept of *Sales Channel*." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:10 +msgid "Create a new sales channel" +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:12 +msgid "" +"To create a new *Sales Channel*, go to :menuselection:`Configuration --> " +"Sales Channels`." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:14 +msgid "" +"There you can set an email alias to it. Every message sent to that email " +"address will create a lead/opportunity." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:21 +msgid "Add members to your sales channel" +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:23 +msgid "" +"You can add members to any channel; that way those members will see the " +"pipeline structure of the sales channel when opening it. Any " +"lead/opportunity assigned to them will link to the sales channel. Therefore," +" you can only be a member of one channel." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:28 +msgid "This will ease the process review of the team manager." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:33 +msgid "" +"If you now filter on this specific channel in your pipeline, you will find " +"all of its opportunities." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:40 +msgid "Sales channel dashboard" +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:42 +msgid "" +"To see the operations and results of any sales channel at a glance, the " +"sales manager also has access to the *Sales Channel Dashboard* under " +"*Reporting*." +msgstr "" + +#: ../../crm/pipeline/multi_sales_team.rst:46 +msgid "" +"It is shared with the whole ecosystem so every revenue stream is included in" +" it: Sales, eCommerce, PoS, etc." +msgstr "" + +#: ../../crm/track_leads.rst:3 +msgid "Assign and track leads" +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:3 +msgid "Assign leads based on scoring" +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:5 +msgid "" +"With *Leads Scoring* you can automatically rank your leads based on selected" +" criterias." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:8 +msgid "" +"For example you could score customers from your country higher or the ones " +"that visited specific pages on your website." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:14 +msgid "" +"To use scoring, install the free module *Lead Scoring* under your *Apps* " +"page (only available in Odoo Enterprise)." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:21 +msgid "Create scoring rules" +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:23 +msgid "" +"You now have a new tab in your *CRM* app called *Leads Management* where you" +" can manage your scoring rules." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:26 +msgid "" +"Here's an example for a Canadian lead, you can modify for whatever criteria " +"you wish to score your leads on. You can add as many criterias as you wish." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:33 +msgid "" +"Every hour every lead without a score will be automatically scanned and " +"assigned their right score according to your scoring rules." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:40 +msgid "Assign leads" +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:42 +msgid "" +"Once the scores computed, leads can be assigned to specific teams using the " +"same domain mechanism. To do so go to :menuselection:`CRM --> Leads " +"Management --> Team Assignation` and apply a specific domain on each team. " +"This domain can include scores." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:49 +msgid "" +"Further on, you can assign to a specific vendor in the team with an even " +"more refined domain." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:52 +msgid "" +"To do so go to :menuselection:`CRM --> Leads Management --> Leads " +"Assignation`." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:58 +msgid "" +"The team & leads assignation will assign the unassigned leads once a day." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:62 +msgid "Evaluate & use the unassigned leads" +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:64 +msgid "" +"Once your scoring rules are in place you will most likely still have some " +"unassigned leads. Some of them could still lead to an opportunity so it is " +"useful to do something with them." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:68 +msgid "" +"In your leads page you can place a filter to find your unassigned leads." +msgstr "" + +#: ../../crm/track_leads/lead_scoring.rst:73 +msgid "" +"Why not using :menuselection:`Email Marketing` or :menuselection:`Marketing " +"Automation` apps to send a mass email to them? You can also easily find such" +" unassigned leads from there." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:3 +msgid "Track your prospects visits" +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:5 +msgid "" +"Tracking your website pages will give you much more information about the " +"interests of your website visitors." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:8 +msgid "" +"Every tracked page they visit will be recorded on your lead/opportunity if " +"they use the contact form on your website." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:14 +msgid "" +"To use this feature, install the free module *Lead Scoring* under your " +"*Apps* page (only available in Odoo Enterprise)." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:21 +msgid "Track a webpage" +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:23 +msgid "" +"Go to any static page you want to track on your website and under the " +"*Promote* tab you will find *Optimize SEO*" +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:29 +msgid "There you will see a *Track Page* checkbox to track this page." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:35 +msgid "See visited pages in your leads/opportunities" +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:37 +msgid "" +"Now each time a lead is created from the contact form it will keep track of " +"the pages visited by that visitor. You have two ways to see those pages, on " +"the top right corner of your lead/opportunity you can see a *Page Views* " +"button but also further down you will see them in the chatter." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:43 +msgid "" +"Both will update if the viewers comes back to your website and visits more " +"pages." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:52 +msgid "" +"The feature will not repeat multiple viewings of the same pages in the " +"chatter." +msgstr "" + +#: ../../crm/track_leads/prospect_visits.rst:55 +msgid "Your customers will no longer be able to keep any secrets from you!" +msgstr "" diff --git a/locale/it/LC_MESSAGES/db_management.po b/locale/it/LC_MESSAGES/db_management.po new file mode 100644 index 000000000..374679f96 --- /dev/null +++ b/locale/it/LC_MESSAGES/db_management.po @@ -0,0 +1,730 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Luigi Di Naro , 2019 +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-07-27 11:08+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../db_management/db_online.rst:8 +msgid "Online Database management" +msgstr "Gestione database online" + +#: ../../db_management/db_online.rst:10 +msgid "" +"To manage your databases, access the `database management page " +"`__ (you will have to sign in). Then " +"click on the `Manage Your Databases " +"`__ button." +msgstr "" +"Per gestire i propri database, visitare la `pagina di gestione database " +"`__ (è necessario effettuare l'accesso). " +"Quindi fare clic sul pulsante `«Gestisci database» " +"`__ ." + +#: ../../db_management/db_online.rst:18 +msgid "" +"Make sure you are connected as the administrator of the database you want to" +" manage - many operations depends on indentifying you remotely to that " +"database." +msgstr "" + +#: ../../db_management/db_online.rst:22 +msgid "Several actions are available:" +msgstr "" + +#: ../../db_management/db_online.rst:28 +msgid ":ref:`Upgrade `" +msgstr "" + +#: ../../db_management/db_online.rst:28 +msgid "" +"Upgrade your database to the latest Odoo version to enjoy cutting-edge " +"features" +msgstr "" + +#: ../../db_management/db_online.rst:32 +msgid ":ref:`Duplicate `" +msgstr "" + +#: ../../db_management/db_online.rst:31 +msgid "" +"Make an exact copy of your database, if you want to try out new apps or new " +"flows without compromising your daily operations" +msgstr "" + +#: ../../db_management/db_online.rst:34 +msgid ":ref:`Rename `" +msgstr "" + +#: ../../db_management/db_online.rst:35 +msgid "Rename your database (and its URL)" +msgstr "" + +#: ../../db_management/db_online.rst:37 +msgid "**Backup**" +msgstr "" + +#: ../../db_management/db_online.rst:37 +msgid "" +"Download an instant backup of your database; note that we back up databases " +"daily according to our Odoo Cloud SLA" +msgstr "" + +#: ../../db_management/db_online.rst:40 +msgid ":ref:`Domains `" +msgstr "" + +#: ../../db_management/db_online.rst:40 +msgid "Configure custom domains to access your database via another URL" +msgstr "" + +#: ../../db_management/db_online.rst:42 +msgid ":ref:`Delete `" +msgstr "" + +#: ../../db_management/db_online.rst:43 +msgid "Delete a database instantly" +msgstr "" + +#: ../../db_management/db_online.rst:46 +msgid "Contact Support" +msgstr "" + +#: ../../db_management/db_online.rst:45 +msgid "" +"Access our `support page `__ with the correct " +"database already selected" +msgstr "" + +#: ../../db_management/db_online.rst:51 +msgid "Upgrade" +msgstr "Aggiorna" + +#: ../../db_management/db_online.rst:53 +msgid "" +"Make sure to be connected to the database you want to upgrade and access the" +" database management page. On the line of the database you want to upgrade, " +"click on the \"Upgrade\" button." +msgstr "" + +#: ../../db_management/db_online.rst:60 +msgid "" +"You have the possibility to choose the target version of the upgrade. By " +"default, we select the highest available version available for your " +"database; if you were already in the process of testing a migration, we will" +" automatically select the version you were already testing (even if we " +"released a more recent version during your tests)." +msgstr "" + +#: ../../db_management/db_online.rst:66 +msgid "" +"By clicking on the \"Test upgrade\" button an upgrade request will be " +"generated. If our automated system does not encounter any problem, you will " +"receive a \"Test\" version of your upgraded database." +msgstr "" + +#: ../../db_management/db_online.rst:73 +msgid "" +"If our automatic system detect an issue during the creation of your test " +"database, our dedicated team will have to work on it. You will be notified " +"by email and the process will take up to 4 weeks." +msgstr "" + +#: ../../db_management/db_online.rst:77 +msgid "" +"You will have the possibility to test it for 1 month. Inspect your data " +"(e.g. accounting reports, stock valuation, etc.), check that all your usual " +"flows work correctly (CRM flow, Sales flow, etc.)." +msgstr "" + +#: ../../db_management/db_online.rst:81 +msgid "" +"Once you are ready and that everything is correct in your test migration, " +"you can click again on the Upgrade button, and confirm by clicking on " +"Upgrade (the button with the little rocket!) to switch your production " +"database to the new version." +msgstr "" + +#: ../../db_management/db_online.rst:89 +msgid "" +"Your database will be taken offline during the upgrade (usually between " +"30min up to several hours for big databases), so make sure to plan your " +"migration during non-business hours." +msgstr "" + +#: ../../db_management/db_online.rst:96 +msgid "Duplicating a database" +msgstr "" + +#: ../../db_management/db_online.rst:98 +msgid "" +"Database duplication, renaming, custom DNS, etc. is not available for trial " +"databases on our Online platform. Paid Databases and \"One App Free\" " +"database can duplicate without problem." +msgstr "" + +#: ../../db_management/db_online.rst:103 +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:110 +msgid "" +"If you do not check the \"For testing purposes\" checkbox when duplicating a" +" database, all external communication will remain active:" +msgstr "" + +#: ../../db_management/db_online.rst:113 +msgid "Emails are sent" +msgstr "" + +#: ../../db_management/db_online.rst:115 +msgid "" +"Payments are processed (in the e-commerce or Subscriptions apps, for " +"example)" +msgstr "" + +#: ../../db_management/db_online.rst:118 +msgid "Delivery orders (shipping providers) are sent" +msgstr "" + +#: ../../db_management/db_online.rst:120 +msgid "Etc." +msgstr "" + +#: ../../db_management/db_online.rst:122 +msgid "" +"Make sure to check the checkbox \"For testing purposes\" if you want these " +"behaviours to be disabled." +msgstr "" + +#: ../../db_management/db_online.rst:125 +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:129 +msgid "Duplicate databases expire automatically after 15 days." +msgstr "" + +#: ../../db_management/db_online.rst:137 +msgid "Rename a Database" +msgstr "" + +#: ../../db_management/db_online.rst:139 +msgid "" +"To rename your database, make sure you are connected to the database you " +"want to rename, access the `database management page " +"`__ and click **Rename**. You will have " +"to give a new name to your database, then click **Rename Database**." +msgstr "" + +#: ../../db_management/db_online.rst:150 +msgid "Deleting a Database" +msgstr "" + +#: ../../db_management/db_online.rst:152 +msgid "You can only delete databases of which you are the administrator." +msgstr "" + +#: ../../db_management/db_online.rst:154 +msgid "" +"When you delete your database all the data will be permanently lost. The " +"deletion is instant and for all the Users. We advise you to do an instant " +"backup of your database before deleting it, since the last automated daily " +"backup may be several hours old at that point." +msgstr "" + +#: ../../db_management/db_online.rst:160 +msgid "" +"From the `database management page `__, " +"on the line of the database you want to delete, click on the \"Delete\" " +"button." +msgstr "" + +#: ../../db_management/db_online.rst:167 +msgid "" +"Read carefully the warning message that will appear and proceed only if you " +"fully understand the implications of deleting a database:" +msgstr "" + +#: ../../db_management/db_online.rst:173 +msgid "" +"After a few seconds, the database will be deleted and the page will reload " +"automatically." +msgstr "" + +#: ../../db_management/db_online.rst:177 +msgid "" +"If you need to re-use this database name, it will be immediately available." +msgstr "" + +#: ../../db_management/db_online.rst:179 +msgid "" +"It is not possible to delete a database if it is expired or linked to a " +"Subscription. In these cases contact `Odoo Support " +"`__" +msgstr "" + +#: ../../db_management/db_online.rst:183 +msgid "" +"If you want to delete your Account, please contact `Odoo Support " +"`__" +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 "Error message due to too many users" +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 "o" + +#: ../../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/it/LC_MESSAGES/discuss.po b/locale/it/LC_MESSAGES/discuss.po new file mode 100644 index 000000000..521dedb1a --- /dev/null +++ b/locale/it/LC_MESSAGES/discuss.po @@ -0,0 +1,662 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../discuss.rst:5 +msgid "Discuss" +msgstr "Comunicazioni" + +#: ../../discuss/email_servers.rst:3 +msgid "How to use my mail server to send and receive emails in Odoo" +msgstr "" + +#: ../../discuss/email_servers.rst:5 +msgid "" +"This document is mainly dedicated to Odoo on-premise users who don't benefit" +" from an out-of-the-box solution to send and receive emails in Odoo, unlike " +"`Odoo Online `__ & `Odoo.sh " +"`__." +msgstr "" + +#: ../../discuss/email_servers.rst:9 +msgid "" +"If no one in your company is used to manage email servers, we strongly " +"recommend that you opt for those Odoo hosting solutions. Their email system " +"works instantly and is monitored by professionals. Nevertheless you can " +"still use your own email servers if you want to manage your email server's " +"reputation yourself." +msgstr "" + +#: ../../discuss/email_servers.rst:15 +msgid "" +"You will find here below some useful information on how to integrate your " +"own email solution with Odoo." +msgstr "" + +#: ../../discuss/email_servers.rst:18 +msgid "" +"Office 365 email servers don't allow easiliy to send external emails from " +"hosts like Odoo. Refer to the `Microsoft's documentation " +"`__ to make it work." +msgstr "" + +#: ../../discuss/email_servers.rst:24 +msgid "How to manage outbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:26 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings` and " +"check *External Email Servers*. Then, click *Outgoing Mail Servers* to " +"create one and reference the SMTP data of your email server. Once all the " +"information has been filled out, click on *Test Connection*." +msgstr "" + +#: ../../discuss/email_servers.rst:31 +msgid "Here is a typical configuration for a G Suite server." +msgstr "" + +#: ../../discuss/email_servers.rst:36 +msgid "Then set your email domain name in the General Settings." +msgstr "" + +#: ../../discuss/email_servers.rst:39 +msgid "Can I use an Office 365 server" +msgstr "" + +#: ../../discuss/email_servers.rst:40 +msgid "" +"You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP" +" relays are not compatible with Odoo Online." +msgstr "" + +#: ../../discuss/email_servers.rst:43 +msgid "" +"Please refer to `Microsoft's documentation `__ to configure" +" a SMTP relay for your Odoo's IP address." +msgstr "" + +#: ../../discuss/email_servers.rst:47 +msgid "How to use a G Suite server" +msgstr "" + +#: ../../discuss/email_servers.rst:48 +msgid "" +"You can use an G Suite server for any Odoo hosting type. To do so you need " +"to enable a SMTP relay and to allow *Any addresses* in the *Allowed senders*" +" section. The configuration steps are explained in `Google documentation " +"`__." +msgstr "" + +#: ../../discuss/email_servers.rst:56 +msgid "Be SPF-compliant" +msgstr "" + +#: ../../discuss/email_servers.rst:57 +msgid "" +"In case you use SPF (Sender Policy Framework) to increase the deliverability" +" of your outgoing emails, don't forget to authorize Odoo as a sending host " +"in your domain name settings. Here is the configuration for Odoo Online:" +msgstr "" + +#: ../../discuss/email_servers.rst:61 +msgid "" +"If no TXT record is set for SPF, create one with following definition: " +"v=spf1 include:_spf.odoo.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:63 +msgid "" +"In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g." +" for a domain name that sends emails via Odoo Online and via G Suite it " +"could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all" +msgstr "" + +#: ../../discuss/email_servers.rst:67 +msgid "" +"Find `here `__ the exact procedure to " +"create or modify TXT records in your own domain registrar." +msgstr "" + +#: ../../discuss/email_servers.rst:70 +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:73 +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:78 +msgid "Allow DKIM" +msgstr "" + +#: ../../discuss/email_servers.rst:79 +msgid "" +"You should do the same thing if DKIM (Domain Keys Identified Mail) is " +"enabled on your email server. In the case of Odoo Online & Odoo.sh, you " +"should add a DNS \"odoo._domainkey\" CNAME record to " +"\"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have " +"a record \"odoo._domainkey.foo.com\" that is a CNAME with the value " +"\"odoo._domainkey.odoo.com\"." +msgstr "" + +#: ../../discuss/email_servers.rst:87 +msgid "How to manage inbound messages" +msgstr "" + +#: ../../discuss/email_servers.rst:89 +msgid "Odoo relies on generic email aliases to fetch incoming messages." +msgstr "" + +#: ../../discuss/email_servers.rst:91 +msgid "" +"**Reply messages** of messages sent from Odoo are routed to their original " +"discussion thread (and to the inbox of all its followers) by the catchall " +"alias (**catchall@**)." +msgstr "" + +#: ../../discuss/email_servers.rst:95 +msgid "" +"**Bounced messages** are routed to **bounce@** in order to track them in " +"Odoo. This is especially used in `Odoo Email Marketing " +"`__ to opt-out invalid " +"recipients." +msgstr "" + +#: ../../discuss/email_servers.rst:99 +msgid "" +"**Original messages**: Several business objects have their own alias to " +"create new records in Odoo from incoming emails:" +msgstr "" + +#: ../../discuss/email_servers.rst:102 +msgid "" +"Sales Channel (to create Leads or Opportunities in `Odoo CRM " +"`__)," +msgstr "" + +#: ../../discuss/email_servers.rst:104 +msgid "" +"Support Channel (to create Tickets in `Odoo Helpdesk " +"`__)," +msgstr "" + +#: ../../discuss/email_servers.rst:106 +msgid "" +"Projects (to create new Tasks in `Odoo Project `__)," +msgstr "" + +#: ../../discuss/email_servers.rst:108 +msgid "" +"Job Positions (to create Applicants in `Odoo Recruitment " +"`__)," +msgstr "" + +#: ../../discuss/email_servers.rst:110 +msgid "etc." +msgstr "" + +#: ../../discuss/email_servers.rst:112 +msgid "" +"Depending on your mail server, there might be several methods to fetch " +"emails. The easiest and most recommended method is to manage one email " +"address per Odoo alias in your mail server." +msgstr "" + +#: ../../discuss/email_servers.rst:116 +msgid "" +"Create the corresponding email addresses in your mail server (catchall@, " +"bounce@, sales@, etc.)." +msgstr "" + +#: ../../discuss/email_servers.rst:118 +msgid "Set your domain name in the General Settings." +msgstr "" + +#: ../../discuss/email_servers.rst:123 +msgid "" +"If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for " +"each alias. You can do it from the General Settings as well. 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:132 +msgid "" +"If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming " +"messages to Odoo's domain name rather than exclusively use your own email " +"server. That way you will receive incoming messages without delay. Indeed, " +"Odoo Online is fetching incoming messages of external servers once per hour " +"only. You should set redirections for all the email addresses to Odoo's " +"domain name in your email server (e.g. *catchall@mydomain.ext* to " +"*catchall@mycompany.odoo.com*)." +msgstr "" + +#: ../../discuss/email_servers.rst:139 +msgid "" +"All the aliases are customizable in Odoo. Object aliases can be edited from " +"their respective configuration view. To edit catchall and bounce aliases, " +"you first need to activate the developer mode from the Settings Dashboard." +msgstr "" + +#: ../../discuss/email_servers.rst:147 +msgid "" +"Then refresh your screen and go to :menuselection:`Settings --> Technical " +"--> Parameters --> System Parameters` to customize the aliases " +"(*mail.catchall.alias* & * mail.bounce.alias*)." +msgstr "" + +#: ../../discuss/email_servers.rst:154 +msgid "" +"By default inbound messages are fetched every 5 minutes in Odoo on-premise. " +"You can change this value in developer mode. Go to :menuselection:`Settings " +"--> Technical --> Automation --> Scheduled Actions` and look for *Mail: " +"Fetchmail Service*." +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 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/plan_activities.rst:3 +msgid "Get organized by planning activities" +msgstr "" + +#: ../../discuss/plan_activities.rst:5 +msgid "" +"Planning activities is the perfect way to keep on track with your work. Get " +"reminded of what needs to be done and schedule the next activities to " +"undertake." +msgstr "" + +#: ../../discuss/plan_activities.rst:9 +msgid "" +"Your activities are available wherever you are in Odoo. It is easy to manage" +" your priorities." +msgstr "" + +#: ../../discuss/plan_activities.rst:15 +msgid "" +"Activities can be planned and managed from the chatters or in the kanban " +"views. Here is an example for opportunities :" +msgstr "" + +#: ../../discuss/plan_activities.rst:22 +msgid "Set your activity types" +msgstr "" + +#: ../../discuss/plan_activities.rst:24 +msgid "" +"A number of generic activities types are available by default in Odoo (e.g. " +"call, email, meeting, etc.). If you would like to set new ones, go to " +":menuselection:`Settings --> General settings --> Activity types`." +msgstr "" + +#: ../../discuss/plan_activities.rst:29 +msgid "Schedule meetings" +msgstr "" + +#: ../../discuss/plan_activities.rst:31 +msgid "" +"Activities are planned for specific days. If you need to set hours, go with " +"the *Meeting* activity type. When scheduling one, the calendar will simply " +"open to let you select a time slot." +msgstr "" + +#: ../../discuss/plan_activities.rst:36 +msgid "" +"If you need to use other activity types with a calendar planning, make sure " +"their *Category* is set as *Meeting*." +msgstr "" + +#: ../../discuss/plan_activities.rst:40 +msgid "Schedule a chain of activities to follow" +msgstr "" + +#: ../../discuss/plan_activities.rst:42 +msgid "" +"Odoo helps you easily plan your usual flow of activities. Go to " +":menuselection:`Configuration --> Activity Types` and set the common " +"following steps as *Recommended next activities*." +msgstr "" + +#: ../../discuss/plan_activities.rst:49 +msgid "" +"Now, when an activity is completed, you can select *Done & schedule next*. " +"The next steps will automatically be suggested to you." +msgstr "" + +#: ../../discuss/plan_activities.rst:55 +msgid "Have fun getting better organized by planning activities !" +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/it/LC_MESSAGES/ecommerce.po b/locale/it/LC_MESSAGES/ecommerce.po new file mode 100644 index 000000000..7528354cc --- /dev/null +++ b/locale/it/LC_MESSAGES/ecommerce.po @@ -0,0 +1,1360 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Martin Trigaux, 2019 +# Sebastiano Pistore , 2019 +# Sergio Zanchetta , 2019 +# Paolo Valier, 2019 +# mymage , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: mymage , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../ecommerce.rst:5 +msgid "eCommerce" +msgstr "E-commerce" + +#: ../../ecommerce/getting_started.rst:3 +msgid "Get started" +msgstr "Cominciare" + +#: ../../ecommerce/getting_started/catalog.rst:3 +msgid "How to customize my catalog page" +msgstr "" + +#: ../../ecommerce/getting_started/catalog.rst:6 +msgid "Product Catalog" +msgstr "Catalogo prodotto" + +#: ../../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. 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:20 +msgid "Select a product from the Products list, go to the *Variants* tab." +msgstr "" + +#: ../../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:30 +msgid "How to edit variants" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:32 +msgid "See all the variants from the product template detail form." +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:40 +msgid "You can edit following data:" +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:42 +msgid "Picture (will update in real time on the website)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:43 +msgid "Barcode," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:44 +msgid "Internal Reference (SKU #)," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:45 +msgid "Volume," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:46 +msgid "Weight," +msgstr "" + +#: ../../ecommerce/managing_products/variants.rst:47 +msgid "Active (available in quotes & website)." +msgstr "" + +#: ../../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: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:58 +msgid "How to set specific prices per variant" +msgstr "" + +#: ../../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:66 +msgid "" +"The Price Extra is added to the product price whenever the corresponding " +"attribute value is selected." +msgstr "" + +#: ../../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:80 +msgid "How to disable/archive variants" +msgstr "" + +#: ../../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:88 +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 "Impostazione" + +#: ../../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 "Panoramica" + +#: ../../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 "Tariffa" + +#: ../../ecommerce/overview/introduction.rst:16 +msgid "Taxes" +msgstr "Imposte" + +#: ../../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 "Pagamento" + +#: ../../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/authorize.rst:3 +msgid "How to get paid with Authorize.Net" +msgstr "Come essere pagati con Authorize.Net" + +#: ../../ecommerce/shopper_experience/authorize.rst:5 +msgid "" +"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." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:12 +msgid "Create an Authorize.Net account" +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:14 +msgid "" +"Create an `Authorize.Net account `__ by clicking " +"'Get Started'." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:16 +msgid "" +"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." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:23 +msgid "Go through the registration steps." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:24 +msgid "" +"The account is set as a test account by default. You can use this test " +"account to process a test transaction from Odoo." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:26 +msgid "Once ready, switch to **Production** mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:30 +#: ../../ecommerce/shopper_experience/paypal.rst:74 +msgid "Set up Odoo" +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:31 +msgid "" +"Activate Authorize.Net in Odoo from :menuselection:`Website or Sales or " +"Accounting --> Settings --> Payment Acquirers`." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:33 +msgid "Enter both your **Login ID** and your **API Transaction Key**." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:39 +msgid "" +"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." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:47 +#: ../../ecommerce/shopper_experience/paypal.rst:102 +msgid "Go live" +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:48 +msgid "" +"Your configuration is now ready! You can make Authorize.Net visible on your " +"merchant interface and activate the **Production** mode." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:55 +msgid "" +"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." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:61 +msgid "Assess Authorize.Net as payment solution" +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:62 +msgid "" +"You can test and assess Authorize.Net for free by creating a `developer " +"account `__." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:64 +msgid "" +"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." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:68 +msgid "" +"You can also log in to `Authorize.Net sandbox platform " +"`__ to configure your sandbox account." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:71 +msgid "" +"To perform ficticious transactions you can use fake card numbers provided in" +" the `Authorize.Net Testing Guide " +"`__." +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:76 +#: ../../ecommerce/shopper_experience/paypal.rst:154 +msgid ":doc:`payment`" +msgstr "" + +#: ../../ecommerce/shopper_experience/authorize.rst:77 +#: ../../ecommerce/shopper_experience/payment.rst:111 +#: ../../ecommerce/shopper_experience/paypal.rst:155 +msgid ":doc:`payment_acquirer`" +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 "Ingenico" + +#: ../../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 "PayUmoney" + +#: ../../ecommerce/shopper_experience/payment.rst:33 +msgid "Sips" +msgstr "Sips" + +#: ../../ecommerce/shopper_experience/payment.rst:34 +msgid "Stripe" +msgstr "Stripe" + +#: ../../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_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 acquirer 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 "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: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: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/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 "Registrati" + +#: ../../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/it/LC_MESSAGES/expenses.po b/locale/it/LC_MESSAGES/expenses.po new file mode 100644 index 000000000..345aa1bf2 --- /dev/null +++ b/locale/it/LC_MESSAGES/expenses.po @@ -0,0 +1,26 @@ +# 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. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, 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: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../expenses.rst:5 +msgid "Expenses" +msgstr "Spese" diff --git a/locale/it/LC_MESSAGES/general.po b/locale/it/LC_MESSAGES/general.po new file mode 100644 index 000000000..19fd9b991 --- /dev/null +++ b/locale/it/LC_MESSAGES/general.po @@ -0,0 +1,915 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Martin Trigaux, 2019 +# Cécile Collart , 2019 +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../general.rst:5 +msgid "General" +msgstr "Generale" + +#: ../../general/auth.rst:3 +msgid "Authentication" +msgstr "Autenticazione" + +#: ../../general/auth/google.rst:3 +msgid "How to allow users to sign in with their Google account" +msgstr "Come consentire agli utenti di accedere con il loro account Google" + +#: ../../general/auth/google.rst:5 +msgid "" +"Connect to your Google account and go to " +"`https://console.developers.google.com/ " +"`_." +msgstr "" +"Accedere al proprio account Google e andare su " +"`https://console.developers.google.com/ " +"`_." + +#: ../../general/auth/google.rst:7 +msgid "" +"Click on **Create Project** and enter the project name and other details." +msgstr "" +"Fare clic su **Crea progetto** e inserire il nome e altri dettagli del " +"progetto." + +#: ../../general/auth/google.rst:15 +msgid "Click on **Use Google APIs**" +msgstr "Fare clic su **Use API Google**" + +#: ../../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 "" +"Dal menù a sinistra selezionare il sottomenù **Credenziali** (da **Gestore " +"API**), quindi selezionare **Schermata di consenso OAuth**." + +#: ../../general/auth/google.rst:25 +msgid "" +"Fill in your address, email and the product name (for example odoo) and then" +" save." +msgstr "" +"Compilare indirizzo, e-mail e nome del prodotto (ad esempio Odoo), quindi " +"salvare." + +#: ../../general/auth/google.rst:30 +msgid "" +"Then click on **Add Credentials** and select the second option (OAuth 2.0 " +"Client ID)." +msgstr "" +"Poi fare clic su **Aggiungi credenziali** e selezionare la seconda opzione " +"(ID cliente OAuth 2.0)." + +#: ../../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 "" +"Verificare di aver impostato il tipo di applicazione in **Applicazione " +"web**. Configurare ora le pagine autorizzate alle quali si verrà " +"ridirezionati." + +#: ../../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 "Nazione: il nome o il codice della nazione" + +#: ../../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 "Nazione: Belgio" + +#: ../../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 "Cosa fare in presenza di un campo con corrispondenze multiple?" + +#: ../../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 "È possibile importare più volte lo stesso record?" + +#: ../../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/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 "" + +#: ../../general/unsplash.rst:3 +msgid "Unsplash" +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:3 +msgid "How to generate an Unsplash access key" +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:5 +msgid "Create an account on `Unsplash.com `_." +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:7 +msgid "" +"Go to your `applications dashboard " +"`_ and click on **New " +"Application**." +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:12 +msgid "Accept the conditions and click on **Accept terms**." +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:17 +msgid "" +"You will be prompted to insert an **Application name** and a " +"**Description**. Once done, click on **Create application**." +msgstr "" + +#: ../../general/unsplash/unsplash_access_key.rst:22 +msgid "" +"You should be redirected to your application details page. Scroll down a bit" +" to find your **access key**." +msgstr "" + +#: ../../general/unsplash/unsplash_application_id.rst:3 +msgid "How to generate an Unsplash application ID" +msgstr "" + +#: ../../general/unsplash/unsplash_application_id.rst:5 +msgid "" +"You should first create and set up your Unsplash application with this " +"tutorial: `How to generate an Unsplash access key " +"`_." +msgstr "" + +#: ../../general/unsplash/unsplash_application_id.rst:7 +msgid "" +"Go to your `applications dashboard " +"`_ and click on your newly created " +"Unsplash application under **Your applications**." +msgstr "" + +#: ../../general/unsplash/unsplash_application_id.rst:12 +msgid "" +"You will be redirected to your application details page. The **application " +"ID** will be visible in your browser's URL. The URL should be something like" +" ``https://unsplash.com/oauth/applications/application_id``" +msgstr "" + +#: ../../general/unsplash/unsplash_application_id.rst:17 +msgid "" +"Note that if you `apply for a production account " +"`_ and it " +"got approved, your will also find your application ID in the UI. It will be " +"listed next to your **Access Key** on your application details page." +msgstr "" diff --git a/locale/it/LC_MESSAGES/getting_started.po b/locale/it/LC_MESSAGES/getting_started.po new file mode 100644 index 000000000..6b16ad93a --- /dev/null +++ b/locale/it/LC_MESSAGES/getting_started.po @@ -0,0 +1,472 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../getting_started/documentation.rst:5 +msgid "Basics of the QuickStart Methodology" +msgstr "" + +#: ../../getting_started/documentation.rst:7 +msgid "" +"This document summarizes Odoo Online's services, our Success Pack " +"implementation methodology, and best practices to get started with our " +"product." +msgstr "" + +#: ../../getting_started/documentation.rst:12 +msgid "1. The SPoC (*Single Point of Contact*) and the Consultant" +msgstr "" + +#: ../../getting_started/documentation.rst:14 +msgid "" +"Within the context of your project, it is highly recommended to designate " +"and maintain on both sides (your side and ours) **one and only single person" +" of contact** who will take charge and assume responsibilities regarding the" +" project. He also has to have **the authority** in terms of decision making." +msgstr "" + +#: ../../getting_started/documentation.rst:20 +msgid "" +"**The Odoo Consultant ensures the project implementation from A to Z**: From" +" the beginning to the end of the project, he ensures the overall consistency" +" of the implementation in Odoo and shares his expertise in terms of good " +"practices." +msgstr "" + +#: ../../getting_started/documentation.rst:25 +msgid "" +"**One and only decision maker on the client side (SPoC)**: He is responsible" +" for the business knowledge transmission (coordinate key users intervention " +"if necessary) and the consistency of the implementation from a business " +"point of view (decision making, change management, etc.)" +msgstr "" + +#: ../../getting_started/documentation.rst:31 +msgid "" +"**Meetings optimization**: The Odoo consultant is not involved in the " +"process of decision making from a business point of view nor to precise " +"processes and company's internal procedures (unless a specific request or an" +" exception). Project meetings, who will take place once or twice a week, are" +" meant to align on the business needs (SPoC) and to define the way those " +"needs will be implemented in Odoo (Consultant)." +msgstr "" + +#: ../../getting_started/documentation.rst:39 +msgid "" +"**Train the Trainer approach**: The Odoo consultant provides functional " +"training to the SPoC so that he can pass on this knowledge to his " +"collaborators. In order for this approach to be successful, it is necessary " +"that the SPoC is also involved in its own rise in skills through self-" +"learning via the `Odoo documentation " +"`__, `The elearning " +"platform `__ and the " +"testing of functionalities." +msgstr "" + +#: ../../getting_started/documentation.rst:47 +msgid "2. Project Scope" +msgstr "" + +#: ../../getting_started/documentation.rst:49 +msgid "" +"To make sure all the stakeholders involved are always aligned, it is " +"necessary to define and to make the project scope evolve as long as the " +"project implementation is pursuing." +msgstr "" + +#: ../../getting_started/documentation.rst:53 +msgid "" +"**A clear definition of the initial project scope**: A clear definition of " +"the initial needs is crucial to ensure the project is running smoothly. " +"Indeed, when all the stakeholders share the same vision, the evolution of " +"the needs and the resulting decision-making process are more simple and more" +" clear." +msgstr "" + +#: ../../getting_started/documentation.rst:59 +msgid "" +"**Phasing the project**: Favoring an implementation in several coherent " +"phases allowing regular production releases and an evolving takeover of Odoo" +" by the end users have demonstrated its effectiveness over time. This " +"approach also helps to identify gaps and apply corrective actions early in " +"the implementation." +msgstr "" + +#: ../../getting_started/documentation.rst:66 +msgid "" +"**Adopting standard features as a priority**: Odoo offers a great " +"environment to implement slight improvements (customizations) or more " +"important ones (developments). Nevertheless, adoption of the standard " +"solution will be preferred as often as possible in order to optimize project" +" delivery times and provide the user with a long-term stability and fluid " +"scalability of his new tool. Ideally, if an improvement of the software " +"should still be realized, its implementation will be carried out after an " +"experiment of the standard in production." +msgstr "" + +#: ../../getting_started/documentation.rst:80 +msgid "3. Managing expectations" +msgstr "" + +#: ../../getting_started/documentation.rst:82 +msgid "" +"The gap between the reality of an implementation and the expectations of " +"future users is a crucial factor. Three important aspects must be taken into" +" account from the beginning of the project:" +msgstr "" + +#: ../../getting_started/documentation.rst:86 +msgid "" +"**Align with the project approach**: Both a clear division of roles and " +"responsibilities and a clear description of the operating modes (validation," +" problem-solving, etc.) are crucial to the success of an Odoo " +"implementation. It is therefore strongly advised to take the necessary time " +"at the beginning of the project to align with these topics and regularly " +"check that this is still the case." +msgstr "" + +#: ../../getting_started/documentation.rst:94 +msgid "" +"**Focus on the project success, not on the ideal solution**: The main goal " +"of the SPoC and the Consultant is to carry out the project entrusted to them" +" in order to provide the most effective solution to meet the needs " +"expressed. This goal can sometimes conflict with the end user's vision of an" +" ideal solution. In that case, the SPoC and the consultant will apply the " +"80-20 rule: focus on 80% of the expressed needs and take out the remaining " +"20% of the most disadvantageous objectives in terms of cost/benefit ratio " +"(those proportions can of course change over time). Therefore, it will be " +"considered acceptable to integrate a more time-consuming manipulation if a " +"global relief is noted. Changes in business processes may also be proposed " +"to pursue this same objective." +msgstr "" + +#: ../../getting_started/documentation.rst:108 +msgid "" +"**Specifications are always EXPLICIT**: Gaps between what is expected and " +"what is delivered are often a source of conflict in a project. In order to " +"avoid being in this delicate situation, we recommend using several types of " +"tools\\* :" +msgstr "" + +#: ../../getting_started/documentation.rst:113 +msgid "" +"**The GAP Analysis**: The comparison of the request with the standard " +"features proposed by Odoo will make it possible to identify the gap to be " +"filled by developments/customizations or changes in business processes." +msgstr "" + +#: ../../getting_started/documentation.rst:118 +msgid "" +"`The User Story `__: " +"This technique clearly separates the responsibilities between the SPoC, " +"responsible for explaining the WHAT, the WHY and the WHO, and the Consultant" +" who will provide a response to the HOW." +msgstr "" + +#: ../../getting_started/documentation.rst:126 +msgid "" +"`The Proof of Concept `__ A " +"simplified version, a prototype of what is expected to agree on the main " +"lines of expected changes." +msgstr "" + +#: ../../getting_started/documentation.rst:130 +msgid "" +"**The Mockup**: In the same idea as the Proof of Concept, it will align with" +" the changes related to the interface." +msgstr "" + +#: ../../getting_started/documentation.rst:133 +msgid "" +"To these tools will be added complete transparency on the possibilities and " +"limitations of the software and/or its environment so that all project " +"stakeholders have a clear idea of what can be expected/achieved in the " +"project. We will, therefore, avoid basing our work on hypotheses without " +"verifying its veracity beforehand." +msgstr "" + +#: ../../getting_started/documentation.rst:139 +msgid "" +"*This list can, of course, be completed by other tools that would more " +"adequately meet the realities and needs of your project*" +msgstr "" + +#: ../../getting_started/documentation.rst:143 +msgid "4. Communication Strategy" +msgstr "" + +#: ../../getting_started/documentation.rst:145 +msgid "" +"The purpose of the QuickStart methodology is to ensure quick ownership of " +"the tool for end users. Effective communication is therefore crucial to the " +"success of this approach. Its optimization will, therefore, lead us to " +"follow those principles:" +msgstr "" + +#: ../../getting_started/documentation.rst:150 +msgid "" +"**Sharing the project management documentation**: The best way to ensure " +"that all stakeholders in a project have the same level of knowledge is to " +"provide direct access to the project's tracking document (Project " +"Organizer). This document will contain at least a list of tasks to be " +"performed as part of the implementation for which the priority level and the" +" manager are clearly defined." +msgstr "" + +#: ../../getting_started/documentation.rst:158 +msgid "" +"The Project Organizer is a shared project tracking tool that allows both " +"detailed tracking of ongoing tasks and the overall progress of the project." +msgstr "" + +#: ../../getting_started/documentation.rst:162 +msgid "" +"**Report essential information**: In order to minimize the documentation " +"time to the essentials, we will follow the following good practices:" +msgstr "" + +#: ../../getting_started/documentation.rst:166 +msgid "Meeting minutes will be limited to decisions and validations;" +msgstr "" + +#: ../../getting_started/documentation.rst:168 +msgid "" +"Project statuses will only be established when an important milestone is " +"reached;" +msgstr "" + +#: ../../getting_started/documentation.rst:171 +msgid "" +"Training sessions on the standard or customized solution will be organized." +msgstr "" + +#: ../../getting_started/documentation.rst:175 +msgid "5. Customizations and Development" +msgstr "" + +#: ../../getting_started/documentation.rst:177 +msgid "" +"Odoo is a software known for its flexibility and its important evolution " +"capacity. However, a significant amount of development contradicts a fast " +"and sustainable implementation. This is the reason why it is recommended to:" +msgstr "" + +#: ../../getting_started/documentation.rst:182 +msgid "" +"**Develop only for a good reason**: The decision to develop must always be " +"taken when the cost-benefit ratio is positive (saving time on a daily basis," +" etc.). For example, it will be preferable to realize a significant " +"development in order to reduce the time of a daily operation, rather than an" +" operation to be performed only once a quarter. It is generally accepted " +"that the closer the solution is to the standard, the lighter and more fluid " +"the migration process, and the lower the maintenance costs for both parties." +" In addition, experience has shown us that 60% of initial development " +"requests are dropped after a few weeks of using standard Odoo (see " +"\"Adopting the standard as a priority\")." +msgstr "" + +#: ../../getting_started/documentation.rst:194 +msgid "" +"**Replace, without replicate**: There is a good reason for the decision to " +"change the management software has been made. In this context, the moment of" +" implementation is THE right moment to accept and even be a change initiator" +" both in terms of how the software will be used and at the level of the " +"business processes of the company." +msgstr "" + +#: ../../getting_started/documentation.rst:202 +msgid "6. Testing and Validation principles" +msgstr "" + +#: ../../getting_started/documentation.rst:204 +msgid "" +"Whether developments are made or not in the implementation, it is crucial to" +" test and validate the correspondence of the solution with the operational " +"needs of the company." +msgstr "" + +#: ../../getting_started/documentation.rst:208 +msgid "" +"**Role distribution**: In this context, the Consultant will be responsible " +"for delivering a solution corresponding to the defined specifications; the " +"SPoC will have to test and validate that the solution delivered meets the " +"requirements of the operational reality." +msgstr "" + +#: ../../getting_started/documentation.rst:214 +msgid "" +"**Change management**: When a change needs to be made to the solution, the " +"noted gap is caused by:" +msgstr "" + +#: ../../getting_started/documentation.rst:218 +msgid "" +"A difference between the specification and the delivered solution - This is " +"a correction for which the Consultant is responsible" +msgstr "" + +#: ../../getting_started/documentation.rst:220 +msgid "**or**" +msgstr "" + +#: ../../getting_started/documentation.rst:222 +msgid "" +"A difference between the specification and the imperatives of operational " +"reality - This is a change that is the responsibility of SPoC." +msgstr "" + +#: ../../getting_started/documentation.rst:226 +msgid "7. Data Imports" +msgstr "" + +#: ../../getting_started/documentation.rst:228 +msgid "" +"Importing the history of transactional data is an important issue and must " +"be answered appropriately to allow the project running smoothly. Indeed, " +"this task can be time-consuming and, if its priority is not well defined, " +"prevent production from happening in time. To do this as soon as possible, " +"it will be decided :" +msgstr "" + +#: ../../getting_started/documentation.rst:234 +msgid "" +"**Not to import anything**: It often happens that after reflection, " +"importing data history is not considered necessary, these data being, " +"moreover, kept outside Odoo and consolidated for later reporting." +msgstr "" + +#: ../../getting_started/documentation.rst:239 +msgid "" +"**To import a limited amount of data before going into production**: When " +"the data history relates to information being processed (purchase orders, " +"invoices, open projects, for example), the need to have this information " +"available from the first day of use in production is real. In this case, the" +" import will be made before the production launch." +msgstr "" + +#: ../../getting_started/documentation.rst:246 +msgid "" +"**To import after production launch**: When the data history needs to be " +"integrated with Odoo mainly for reporting purposes, it is clear that these " +"can be integrated into the software retrospectively. In this case, the " +"production launch of the solution will precede the required imports." +msgstr "" + +#: ../../getting_started/documentation.rst:253 +msgid "8. Support" +msgstr "" + +#: ../../getting_started/documentation.rst:255 +msgid "" +"Your Odoo Online subscription includes **unlimited 24hr support at no extra " +"cost, Monday to Friday**. Our teams are located around the world to ensure " +"you have support, no matter your location. Your support representative could" +" be communicating to you from San Francisco, Belgium, or India!" +msgstr "" + +#: ../../getting_started/documentation.rst:260 +msgid "What kind of support is included?" +msgstr "" + +#: ../../getting_started/documentation.rst:262 +msgid "" +"Providing you with relevant material (guidelines, product documentation, " +"etc...)" +msgstr "" + +#: ../../getting_started/documentation.rst:264 +msgid "" +"Answers to issues that you may encounter in your standard Odoo database (eg." +" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)" +msgstr "" + +#: ../../getting_started/documentation.rst:266 +msgid "Questions related to your account, subscription, or billing" +msgstr "" + +#: ../../getting_started/documentation.rst:267 +msgid "" +"Bug resolution (blocking issues or unexpected behaviour not due to " +"misconfiguration or customization)" +msgstr "" + +#: ../../getting_started/documentation.rst:269 +msgid "" +"Issues that might occur in a test database after upgrading to a newer " +"version" +msgstr "" + +#: ../../getting_started/documentation.rst:271 +msgid "" +"*Odoo Support does not make changes to your production database, but gives " +"you the material and knowledge to do it yourself!*" +msgstr "" + +#: ../../getting_started/documentation.rst:274 +msgid "What kind of support is not included?" +msgstr "" + +#: ../../getting_started/documentation.rst:276 +msgid "" +"Questions that require us to understand your business processes in order to " +"help you implement your database" +msgstr "" + +#: ../../getting_started/documentation.rst:278 +msgid "" +"Training on how to use our software (we will direct you to our many " +"resources)" +msgstr "" + +#: ../../getting_started/documentation.rst:279 +msgid "Importation of documents into your database" +msgstr "" + +#: ../../getting_started/documentation.rst:280 +msgid "" +"Guidance on which configurations to apply inside of an application or the " +"database" +msgstr "" + +#: ../../getting_started/documentation.rst:281 +msgid "" +"How to set up configuration models (Examples include: Inventory Routes, " +"Payment Terms, Warehouses, etc)" +msgstr "" + +#: ../../getting_started/documentation.rst:283 +msgid "" +"Questions or issues related to specific developments or customizations done " +"either by Odoo or a third party (this is specific only to your database or " +"involving code)" +msgstr "" + +#: ../../getting_started/documentation.rst:287 +msgid "" +"You can get this type of support with a `Success Pack `__. With a pack, one of our consultants will analyze the way" +" your business runs and tell you how you can get the most out of your Odoo " +"Database. We will handle all configurations and coach you on how to use " +"Odoo." +msgstr "" + +#: ../../getting_started/documentation.rst:292 +msgid "" +"Our support team can be contacted through our `online support form " +"`__." +msgstr "" diff --git a/locale/it/LC_MESSAGES/helpdesk.po b/locale/it/LC_MESSAGES/helpdesk.po new file mode 100644 index 000000000..de3ca24d5 --- /dev/null +++ b/locale/it/LC_MESSAGES/helpdesk.po @@ -0,0 +1,398 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Martin Trigaux, 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../helpdesk.rst:5 +msgid "Helpdesk" +msgstr "Helpdesk" + +#: ../../helpdesk/getting_started.rst:3 +msgid "Get started with Odoo Helpdesk" +msgstr "" + +#: ../../helpdesk/getting_started.rst:6 +msgid "Overview" +msgstr "Panoramica" + +#: ../../helpdesk/getting_started.rst:9 +msgid "Getting started with Odoo Helpdesk" +msgstr "" + +#: ../../helpdesk/getting_started.rst:11 +msgid "Installing Odoo Helpdesk:" +msgstr "" + +#: ../../helpdesk/getting_started.rst:13 +msgid "Open the Apps module, search for \"Helpdesk\", and click install" +msgstr "" + +#: ../../helpdesk/getting_started.rst:19 +msgid "Set up Helpdesk teams" +msgstr "" + +#: ../../helpdesk/getting_started.rst:21 +msgid "By default, Odoo Helpdesk comes with a team installed called \"Support\"" +msgstr "" + +#: ../../helpdesk/getting_started.rst:26 +msgid "" +"To modify this team, or create additional teams, select \"Configuration\" in" +" the purple bar and select \"Settings\"" +msgstr "" + +#: ../../helpdesk/getting_started.rst:32 +msgid "" +"Here you can create new teams, decide what team members to add to this team," +" how your customers can submit tickets and set up SLA policies and ratings. " +"For the assignation method you can have tickets assigned randomly, balanced," +" or manually." +msgstr "" + +#: ../../helpdesk/getting_started.rst:38 +msgid "How to set up different stages for each team" +msgstr "" + +#: ../../helpdesk/getting_started.rst:40 +msgid "" +"First you will need to activate the developer mode. To do this go to your " +"settings module, and select the link for \"Activate the developer mode\" on " +"the lower right-hand side." +msgstr "" + +#: ../../helpdesk/getting_started.rst:47 +msgid "" +"Now, when you return to your Helpdesk module and select \"Configuration\" in" +" the purple bar you will find additional options, like \"Stages\". Here you " +"can create new stages and assign those stages to 1 or multiple teams " +"allowing for customizable stages for each team!" +msgstr "" + +#: ../../helpdesk/getting_started.rst:53 +msgid "Start receiving tickets" +msgstr "" + +#: ../../helpdesk/getting_started.rst:56 +msgid "How can my customers submit tickets?" +msgstr "" + +#: ../../helpdesk/getting_started.rst:58 +msgid "" +"Select \"Configuration\" in the purple bar and select \"Settings\", select " +"your Helpdesk team. Under \"Channels you will find 4 options:" +msgstr "" + +#: ../../helpdesk/getting_started.rst:64 +msgid "" +"Email Alias allows for customers to email the alias you choose to create a " +"ticket. The subject line of the email with become the Subject on the ticket." +msgstr "" + +#: ../../helpdesk/getting_started.rst:71 +msgid "" +"Website Form allows your customer to go to " +"yourwebsite.com/helpdesk/support-1/submit and submit a ticket via a website " +"form - much like odoo.com/help!" +msgstr "" + +#: ../../helpdesk/getting_started.rst:78 +msgid "" +"Live Chat allows your customers to submit a ticket via Live Chat on your " +"website. Your customer will begin the live chat and your Live Chat Operator " +"can create the ticket by using the command /helpdesk Subject of Ticket." +msgstr "" + +#: ../../helpdesk/getting_started.rst:86 +msgid "" +"The final option to submit tickets is thru an API connection. View the " +"documentation `*here* " +"`__." +msgstr "" + +#: ../../helpdesk/getting_started.rst:91 +msgid "Tickets have been created, now what?" +msgstr "" + +#: ../../helpdesk/getting_started.rst:93 +msgid "" +"Now your employees can start working on them! If you have selecting a manual" +" assignation method then your employees will need to assign themselves to " +"tickets using the \"Assign To Me\" button on the top left of a ticket or by " +"adding themselves to the \"Assigned to\" field." +msgstr "" + +#: ../../helpdesk/getting_started.rst:101 +msgid "" +"If you have selected \"Random\" or \"Balanced\" assignation method, your " +"tickets will be assigned to a member of that Helpdesk team." +msgstr "" + +#: ../../helpdesk/getting_started.rst:104 +msgid "" +"From there they will begin working on resolving the tickets! When they are " +"completed, they will move the ticket to the solved stage." +msgstr "" + +#: ../../helpdesk/getting_started.rst:108 +msgid "How do I mark this ticket as urgent?" +msgstr "" + +#: ../../helpdesk/getting_started.rst:110 +msgid "" +"On your tickets you will see stars. You can determine how urgent a ticket is" +" but selecting one or more stars on the ticket. You can do this in the " +"Kanban view or on the ticket form." +msgstr "" + +#: ../../helpdesk/getting_started.rst:117 +msgid "" +"To set up a Service Level Agreement Policy for your employees, first " +"activate the setting under \"Settings\"" +msgstr "" + +#: ../../helpdesk/getting_started.rst:123 +msgid "From here, select \"Configure SLA Policies\" and click \"Create\"." +msgstr "" + +#: ../../helpdesk/getting_started.rst:125 +msgid "" +"You will fill in information like the Helpdesk team, what the minimum " +"priority is on the ticket (the stars) and the targets for the ticket." +msgstr "" + +#: ../../helpdesk/getting_started.rst:132 +msgid "What if a ticket is blocked or is ready to be worked on?" +msgstr "" + +#: ../../helpdesk/getting_started.rst:134 +msgid "" +"If a ticket cannot be resolved or is blocked, you can adjust the \"Kanban " +"State\" on the ticket. You have 3 options:" +msgstr "" + +#: ../../helpdesk/getting_started.rst:137 +msgid "Grey - Normal State" +msgstr "" + +#: ../../helpdesk/getting_started.rst:139 +msgid "Red - Blocked" +msgstr "" + +#: ../../helpdesk/getting_started.rst:141 +msgid "Green - Ready for next stage" +msgstr "" + +#: ../../helpdesk/getting_started.rst:143 +msgid "" +"Like the urgency stars you can adjust the state in the Kanban or on the " +"Ticket form." +msgstr "" + +#: ../../helpdesk/getting_started.rst:150 +msgid "How can my employees log time against a ticket?" +msgstr "" + +#: ../../helpdesk/getting_started.rst:152 +msgid "" +"First, head over to \"Settings\" and select the option for \"Timesheet on " +"Ticket\". You will see a field appear where you can select the project the " +"timesheets will log against." +msgstr "" + +#: ../../helpdesk/getting_started.rst:159 +msgid "" +"Now that you have selected a project, you can save. If you move back to your" +" tickets, you will see a new tab called \"Timesheets\"" +msgstr "" + +#: ../../helpdesk/getting_started.rst:165 +msgid "" +"Here you employees can add a line to add work they have done for this " +"ticket." +msgstr "" + +#: ../../helpdesk/getting_started.rst:169 +msgid "How to allow your customers to rate the service they received" +msgstr "" + +#: ../../helpdesk/getting_started.rst:171 +msgid "First, you will need to activate the ratings setting under \"Settings\"" +msgstr "" + +#: ../../helpdesk/getting_started.rst:176 +msgid "" +"Now, when a ticket is moved to its solved or completed stage, it will send " +"an email to the customer asking how their service went." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:3 +msgid "Record and invoice time for tickets" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:5 +msgid "" +"You may have service contracts with your clients to provide them assistance " +"in case of a problem. For this purpose, Odoo will help you record the time " +"spent fixing the issue and most importantly, to invoice it to your clients." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:11 +msgid "The modules needed" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:13 +msgid "" +"In order to record and invoice time for tickets, the following modules are " +"needed : Helpdesk, Project, Timesheets, Sales. If you are missing one of " +"them, go to the Apps module, search for it and then click on *Install*." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:19 +msgid "Get started to offer the helpdesk service" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:22 +msgid "Step 1 : start a helpdesk project" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:24 +msgid "" +"To start a dedicated project for the helpdesk service, first go to " +":menuselection:`Project --> Configuration --> Settings` and make sure that " +"the *Timesheets* feature is activated." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:31 +msgid "" +"Then, go to your dashboard, create the new project and allow timesheets for " +"it." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:35 +msgid "Step 2 : gather a helpdesk team" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:37 +msgid "" +"To set a team in charge of the helpdesk, go to :menuselection:`Helpdesk --> " +"Configuration --> Helpdesk Teams` and create a new team or select an " +"existing one. On the form, tick the box in front of *Timesheet on Ticket* to" +" activate the feature. Make sure to select the helpdesk project you have " +"previously created as well." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:47 +msgid "Step 3 : launch the helpdesk service" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:49 +msgid "" +"Finally, to launch the new helpdesk service, first go to " +":menuselection:`Sales --> Configuration --> Settings` and make sure that the" +" *Units of Measure* feature is activated." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:56 +msgid "" +"Then, go to :menuselection:`Products --> Products` and create a new one. " +"Make sure that the product is set as a service." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:63 +msgid "" +"Here, we suggest that you set the *Unit of Measure* as *Hour(s)*, but any " +"unit will do." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:66 +msgid "" +"Finally, select the invoicing management you would like to have under the " +"*Sales* tab of the product form. Here, we recommend the following " +"configuration :" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:73 +msgid "Now, you are ready to start receiving tickets !" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:76 +msgid "Solve issues and record time spent" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:79 +msgid "Step 1 : place an order" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:81 +msgid "" +"You are now in the Helpdesk module and you have just received a ticket from " +"a client. To place a new order, go to :menuselection:`Sales --> Orders --> " +"Orders` and create one for the help desk service product you have previously" +" recorded. Set the number of hours needed to assist the client and confirm " +"the sale." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:91 +msgid "Step 2 : link the task to the ticket" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:93 +msgid "" +"If you access the dedicated helpdesk project, you will notice that a new " +"task has automatically been generated with the order. To link this task with" +" the client ticket, go to the Helpdesk module, access the ticket in question" +" and select the task on its form." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:102 +msgid "Step 3 : record the time spent to help the client" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:104 +msgid "" +"The job is done and the client's issue is sorted out. To record the hours " +"performed for this task, go back to the ticket form and add them under the " +"*Timesheets* tab." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:112 +msgid "" +"The hours recorded on the ticket will also automatically appear in the " +"Timesheet module and on the dedicated task." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:116 +msgid "Step 4 : invoice the client" +msgstr "" + +#: ../../helpdesk/invoice_time.rst:118 +msgid "" +"To invoice the client, go back to the Sales module and select the order that" +" had been placed. Notice that the hours recorded on the ticket form now " +"appear as the delivered quantity." +msgstr "" + +#: ../../helpdesk/invoice_time.rst:125 +msgid "" +"All that is left to do, is to create the invoice from the order and then " +"validate it. Now you just have to wait for the client's payment !" +msgstr "" diff --git a/locale/it/LC_MESSAGES/index.po b/locale/it/LC_MESSAGES/index.po new file mode 100644 index 000000000..1e674db6b --- /dev/null +++ b/locale/it/LC_MESSAGES/index.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../index.rst:3 +msgid "Odoo User Documentation" +msgstr "Documentazione utente Odoo" diff --git a/locale/it/LC_MESSAGES/inventory.po b/locale/it/LC_MESSAGES/inventory.po new file mode 100644 index 000000000..08a4c7886 --- /dev/null +++ b/locale/it/LC_MESSAGES/inventory.po @@ -0,0 +1,7718 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# mymage , 2019 +# Simone Bernini , 2019 +# Cesare Cugnasco , 2019 +# Luigi Di Naro , 2019 +# Davide Corio , 2019 +# Paolo Valier, 2019 +# Martin Trigaux, 2019 +# David Minneci , 2019 +# Léonie Bouchat , 2019 +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../inventory.rst:5 ../../inventory/overview/concepts/double-entry.rst:64 +msgid "Inventory" +msgstr "Magazzino" + +#: ../../inventory/barcode.rst:3 +msgid "Barcodes" +msgstr "Codici a barre" + +#: ../../inventory/barcode/operations.rst:3 +msgid "Daily Operations" +msgstr "Operazioni giornaliere" + +#: ../../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 "Impostazione" + +#: ../../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 "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 :menuselection:`Operations --> Barcode Scanner`. Click Save, and " +"go back into the previous screen to click Configure Product Barcodes. This " +"interface can also be accessed via the planner." +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:39 +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:44 +msgid "Set locations barcodes" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:49 +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:58 +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:65 +msgid "Barcode formats" +msgstr "" + +#: ../../inventory/barcode/setup/software.rst:67 +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:72 +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 "Gestione Magazzino" + +#: ../../inventory/management/adjustment.rst:3 +msgid "Inventory Adjustment" +msgstr "Rettifica di inventario" + +#: ../../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 "Rendicontazione" + +#: ../../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 +#: ../../inventory/settings/products/strategies.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:13 +#: ../../inventory/settings/products/strategies.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 +#: ../../inventory/settings/products/strategies.rst:22 +#: ../../inventory/settings/products/strategies.rst:58 +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/strategies.rst:30 +#: ../../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 "Configurazione" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:33 +#: ../../inventory/settings/products/strategies.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 "Attivo" + +#: ../../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 "" +"Se il campo attivo è impostato su False, ti permetterà di nascondere il " +"punto di ordine senza rimuoverlo." + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Product Unit of Measure" +msgstr "Unità di misura prodotto" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Default unit of measure used for all stock operations." +msgstr "Unità di misura predefinita per ogni operazione di stoccaggio." + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Procurement Group" +msgstr "Gruppo di Approvvigionamento" + +#: ../../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 stock rules will be grouped into " +"one big picking." +msgstr "" +"I movimenti creati attraverso questo punto di riordino saranno inseriti in " +"questo gruppo di approvvigionamento. Se non ne viene dato nessuno, i " +"movimenti generati dalle regole di magazzino saranno raggruppati in un unico" +" prelievo." + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Minimum Quantity" +msgstr "Quantità minima" + +#: ../../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 "" +"Quando le scorte virtuali scendono al di sotto della quantità minima " +"indicata per questo campo, Odoo genera un approvvigionamento per portare la " +"quantità prevista alla quantità massima." + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Maximum Quantity" +msgstr "Quantità massima" + +#: ../../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 "" +"Quando le scorte virtuali scendono al di sotto della quantità minima, Odoo " +"genera un approvvigionamento per portare la quantità prevista alla quantità " +"indicata come quantità massima." + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Quantity Multiple" +msgstr "Multiplo Quantità" + +#: ../../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 "" +"La quantità di approvvigionamento sarà arrotondata a questo multiplo. Se il " +"multiplo è 0, verrà utilizzata la quantità esatta. " + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 +msgid "Lead Time" +msgstr "Tempi di consegna" + +#: ../../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 "" +"Numero di giorni dopo che l’ordine è stato attivato per ricevere i prodotti " +"o per ordinare al fornitore" + +#: ../../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 +#: ../../inventory/settings/products/strategies.rst:70 +msgid "Choice between the two options" +msgstr "" + +#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:70 +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/management/delivery.rst:3 +msgid "Delivery Orders" +msgstr "Ordini di consegna" + +#: ../../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/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 "Panoramica" + +#: ../../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 "Creare un ordine di vendita" + +#: ../../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 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 +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 "Spedizioni in Ingresso" + +#: ../../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 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 "Lotti e numeri di serie" + +#: ../../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 "Introduzione" + +#: ../../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 "Trasferimenti" + +#: ../../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 "Rettifica di inventario" + +#: ../../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 "Operazioni varie" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:2 +msgid "Immediate & Planned Transfers" +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:4 +msgid "" +"In Odoo, you can create two types of transfers: immediate or planned " +"transfers." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:8 +msgid "Immediate Transfers" +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:10 +msgid "" +"When you create a transfer manually, it is by default an immediate transfer." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:13 +msgid "" +"In the case of an immediate transfer, you directly encode the products and " +"quantities you are processing, there is no reservation that applies. This is" +" why the column \"Initial Demand\" is not editable. You only fill in the " +"column \"Done\" for the quantities." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:18 +msgid "" +"This is for example used when you are transferring goods from a location A " +"to a location B and that this is not planned (you are processing the " +"transfer right now)." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:23 +msgid "Planned Transfers" +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:25 +msgid "" +"When a transfer is generated automatically (from a sales order or purchase " +"order for example), it is a planned transfer. This means that there is an " +"initial demand and that reservation applies on this initial demand." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:30 +msgid "" +"If you want to create a planned transfer manually, you can do it from the " +"inventory dashboard." +msgstr "" + +#: ../../inventory/management/misc/immediate_planned_transfers.rst:36 +msgid "" +"In that case, you will have to enter the initial demand first (how many " +"units are you supposed to proceed), then to mark your transfer as to do. " +"Once this is done, you will be able to reserve the products and to process " +"the transfer." +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 --> Settings` 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 --> Internal Transfers`" +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 --> Settings`" +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 "Metodo di valorizzazione" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:63 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:64 +msgid "Standard Price" +msgstr "Prezzo Standard" + +#: ../../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 "Operazione" + +#: ../../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 "Costo unitario" + +#: ../../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 "Valore di magazzino" + +#: ../../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 "12" + +#: ../../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 "20 €" + +#: ../../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 "Prezzo medio" + +#: ../../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 "Fattura fornitore" + +#: ../../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 "Dare" + +#: ../../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 "Avere" + +#: ../../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 "Fattura cliente" + +#: ../../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 "Ordini di produzione" + +#: ../../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: defined on the product category as a default, or specifically to a" +" specific product." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:350 +msgid "" +"Expenses: this is where you should set the \"Cost of Goods Sold\" account. " +"Defined on the product category as a default value, or specifically on the " +"product form." +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:354 +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:357 +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:360 +#: ../../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:362 +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:367 +#: ../../inventory/management/reporting/valuation_methods_continental.rst:356 +msgid ":doc:`../../routes/strategies/removal`" +msgstr "" + +#: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:368 +#: ../../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:369 +#: ../../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 "Concetti principali" + +#: ../../inventory/overview/concepts/double-entry.rst:5 +msgid "Introduction to 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 "Operazioni" + +#: ../../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 "Ordine di produzione" + +#: ../../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 "Pick" + +#: ../../inventory/overview/concepts/double-entry.rst:40 +msgid "1 Bicycle: Stock → Packing Zone" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:41 +msgid "Pack" +msgstr "Collo" + +#: ../../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 "Spedizione" + +#: ../../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 "Analisi" + +#: ../../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 "Regole minime dello stock" + +#: ../../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 "Rotte" + +#: ../../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 "Magazzini" + +#: ../../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 "Categoria prodotto" + +#: ../../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 "Consegna:" + +#: ../../inventory/overview/concepts/double-entry.rst:222 +msgid "Output → Customer" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:227 +msgid "Sale Order Line" +msgstr "Riga ordine di vendita" + +#: ../../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 "Forzare le Regole" + +#: ../../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 "Controllo qualità" + +#: ../../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 "Prelievo" + +#: ../../inventory/overview/concepts/double-entry.rst:253 +msgid "Packing" +msgstr "" + +#: ../../inventory/overview/concepts/double-entry.rst:254 +msgid "Delivery Order" +msgstr "Ordine di consegna" + +#: ../../inventory/overview/concepts/double-entry.rst:255 +msgid "Purchase Order" +msgstr "Ordine di acquisto" + +#: ../../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 "Gestire le catene di produzione del prodotto" + +#: ../../inventory/routes/concepts/use_routes.rst:13 +msgid "Manage default locations per product" +msgstr "Gestisci locations predefinite per prodotto" + +#: ../../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 "" +"Aiutare la gestione degli affitti, generando spostamenti di ritorno " +"automatizzati per i prodotti noleggiati" + +#: ../../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 "Tipi di costo allo sbarco" + +#: ../../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:50 +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:55 +msgid "Link landed costs to a transfer" +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:57 +msgid "" +"To calculate landed costs, go to :menuselection:`Inventory --> Inventory " +"Control --> Landed Costs`." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:60 +msgid "" +"Click on the **Create** button and select the picking(s) you want to " +"attribute landed costs." +msgstr "" + +#: ../../inventory/routes/costing/landed_costs.rst:66 +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:73 +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:79 +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 "Gelato" + +#: ../../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 "Impostazioni" + +#: ../../inventory/settings/products.rst:3 +msgid "Products" +msgstr "Prodotti" + +#: ../../inventory/settings/products/strategies.rst:3 +msgid "How to select the right replenishment strategy" +msgstr "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/strategies.rst:44 +msgid "" +"Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity " +"multiple\" fields" +msgstr "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/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 "" + +#: ../../inventory/settings/products/strategies.rst:64 +msgid "On the product form, under Inventory, click on \"Make To Order\"." +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 "Approvvigionamento" + +#: ../../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 "Colli" + +#: ../../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/usage.rst:38 +msgid "Packaging" +msgstr "Imballaggio" + +#: ../../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:70 +msgid ":doc:`../../overview/start/setup`" +msgstr "" + +#: ../../inventory/settings/products/usage.rst:71 +msgid ":doc:`uom`" +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:23 +msgid "Click on **Apply** when you are done." +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: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/shipping/operation/multipack.rst:56 +msgid "It will automatically create a pack with the requested quantity." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:58 +msgid "Do the same steps for the other pieces you want to pack in." +msgstr "" + +#: ../../inventory/shipping/operation/multipack.rst:63 +msgid "Click on **Validate** when you are done." +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 "Consegna" + +#: ../../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/it/LC_MESSAGES/iot.po b/locale/it/LC_MESSAGES/iot.po new file mode 100644 index 000000000..046ae840d --- /dev/null +++ b/locale/it/LC_MESSAGES/iot.po @@ -0,0 +1,370 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Paolo Valier, 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Paolo Valier, 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../iot.rst:5 +msgid "Internet of Things (IoT)" +msgstr "" + +#: ../../iot/connect.rst:3 +msgid "Connect an IoT Box to your database" +msgstr "" + +#: ../../iot/connect.rst:5 +msgid "Install the Internet of Things (IoT) App on your Odoo Database." +msgstr "" + +#: ../../iot/connect.rst:10 +msgid "Go in the IoT App and click on Connect on the IoT Boxes page." +msgstr "" + +#: ../../iot/connect.rst:15 +msgid "Follow the steps to connect your IoT Box." +msgstr "" + +#: ../../iot/connect.rst:21 +msgid "Ethernet Connection" +msgstr "" + +#: ../../iot/connect.rst:23 +msgid "" +"Connect to the IoT Box all the devices that have to be connected with cables" +" (ethernet, usb devices, etc.)." +msgstr "" + +#: ../../iot/connect.rst:26 +msgid "Power on the IoT Box." +msgstr "" + +#: ../../iot/connect.rst:28 +msgid "Then click on the Scan button." +msgstr "" + +#: ../../iot/connect.rst:34 +msgid "WiFi Connection" +msgstr "" + +#: ../../iot/connect.rst:36 +msgid "Power on the IoT Box" +msgstr "" + +#: ../../iot/connect.rst:38 +msgid "Copy the token" +msgstr "" + +#: ../../iot/connect.rst:43 +msgid "" +"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable " +"plugged in your computer)." +msgstr "" + +#: ../../iot/connect.rst:49 +msgid "" +"You will be redirected to the IoT Box Homepage (if it doesn't work, connect " +"to the IP address of the box). Give a name to your IoT Box (not required) " +"and paste the token, then click on next." +msgstr "" + +#: ../../iot/connect.rst:57 +msgid "" +"If you are on Runbot, do not forget to add the -all or -base in the token " +"(e.g. this token **http://375228-saas-11-5-iot-" +"f3f920.runbot16.odoo.com\\|4957098401** should become " +"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)." +msgstr "" + +#: ../../iot/connect.rst:63 +msgid "" +"Choose the WiFi network you want to connect with (enter the password if " +"there is one) and click on Submit. Wait a few seconds before being " +"redirected to your database." +msgstr "" + +#: ../../iot/connect.rst:70 +msgid "You should now see the IoT Box." +msgstr "" + +#: ../../iot/connect.rst:76 +msgid "IoT Box Schema" +msgstr "" + +#: ../../iot/pos.rst:3 +msgid "Use the IoT Box for the PoS" +msgstr "" + +#: ../../iot/pos.rst:9 +msgid "Prerequisites" +msgstr "" + +#: ../../iot/pos.rst:11 +msgid "Before starting, make sure you have the following:" +msgstr "" + +#: ../../iot/pos.rst:13 +msgid "An IoT Box" +msgstr "" + +#: ../../iot/pos.rst:15 +msgid "A 2A Power adapter with pi 3 b+ 2.5 A" +msgstr "" + +#: ../../iot/pos.rst:17 +msgid "A computer or tablet with an up-to-date web browser" +msgstr "" + +#: ../../iot/pos.rst:19 +msgid "" +"A running SaaS or Odoo instance with the Point of Sale and IoT apps " +"installed" +msgstr "" + +#: ../../iot/pos.rst:22 +msgid "A local network setup with DHCP (this is the default setting)" +msgstr "" + +#: ../../iot/pos.rst:24 +msgid "" +"An Epson USB TM-T20 Printer or another ESC/POS compatible printer " +"(officially supported printers are listed at the `POS Hardware page " +"`__)" +msgstr "" + +#: ../../iot/pos.rst:28 +msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" +msgstr "" + +#: ../../iot/pos.rst:30 +msgid "An Epson compatible cash drawer" +msgstr "" + +#: ../../iot/pos.rst:32 +msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)" +msgstr "" + +#: ../../iot/pos.rst:35 +msgid "Set Up" +msgstr "Imposta" + +#: ../../iot/pos.rst:37 +msgid "" +"To connect hardware to the PoS, the first step is to connect an IoT Box to " +"your database. For this, follow this `documentation " +"`__." +msgstr "" + +#: ../../iot/pos.rst:44 +msgid "Then, you have to connect the peripheral devices to your IoT Box." +msgstr "" + +#: ../../iot/pos.rst:46 +msgid "" +"Officially supported hardware is listed on `the POS Hardware page " +"`__, but other hardware" +" might work as well." +msgstr "" + +#: ../../iot/pos.rst:50 +msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." +msgstr "" + +#: ../../iot/pos.rst:53 +msgid "" +"**Cash drawer**: The cash drawer should be connected to the printer with an " +"RJ25 cable." +msgstr "" + +#: ../../iot/pos.rst:56 +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 "" + +#: ../../iot/pos.rst:62 +msgid "**Scale**: Connect your scale and power it on." +msgstr "" + +#: ../../iot/pos.rst:64 +msgid "" +"**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. " +"Make sure this will connect the IoT Box to the same network as your POS " +"device." +msgstr "" + +#: ../../iot/pos.rst:68 +msgid "" +"**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make sure " +"not to plug in an Ethernet cable when booting, because all Wi-Fi " +"functionality will be bypassed when a wired network connection is available " +"on boot." +msgstr "" + +#: ../../iot/pos.rst:73 +msgid "" +"Once it's done, you can connect the IoT Box to your PoS. For this, go in " +"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the" +" IoT Box you want to connect with. Save the changes." +msgstr "" + +#: ../../iot/pos.rst:77 +msgid "Set up is done, you can launch a new PoS Session." +msgstr "" + +#: ../../iot/pos.rst:80 +msgid "Troubleshoot" +msgstr "" + +#: ../../iot/pos.rst:83 +msgid "The PoS cannot connect to the IoT Box" +msgstr "" + +#: ../../iot/pos.rst:85 +msgid "" +"The easiest way to make sure the IoT Box 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 IoT Box's IP address in case of success. If no " +"receipt is printed, check the following steps:" +msgstr "" + +#: ../../iot/pos.rst:91 +msgid "" +"Make sure the IoT Box is powered on, indicated by a brightly lit red status " +"LED." +msgstr "" + +#: ../../iot/pos.rst:94 +msgid "" +"Make sure the IoT Box is ready, this is indicated by a brightly lit green " +"status LED just next to the red power status LED. The IoT Box should be " +"ready ~2 minutes after it is started." +msgstr "" + +#: ../../iot/pos.rst:98 +msgid "" +"Make sure the IoT Box is connected to the same network as your POS device. " +"Both the device and the IoT Box should be visible in the list of connected " +"devices on your network router." +msgstr "" + +#: ../../iot/pos.rst:102 +msgid "" +"If you specified the IoT Box's IP address in the configuration, make sure it" +" corresponds to the ip address printed on the IoT Box's status receipt." +msgstr "" + +#: ../../iot/pos.rst:106 +msgid "Make sure that the POS is not loaded over HTTPS." +msgstr "" + +#: ../../iot/pos.rst:108 +msgid "" +"A bug in Firefox's HTTP implementation might prevent the autodiscovery from " +"working reliably. You could also manually set up the IoT Box's IP address in" +" the POS configuration." +msgstr "" + +#: ../../iot/pos.rst:113 +msgid "The Barcode Scanner is not working" +msgstr "" + +#: ../../iot/pos.rst:115 +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 "" + +#: ../../iot/pos.rst:120 +msgid "" +"The IoT Box 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 "" + +#: ../../iot/pos.rst:124 +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 "" + +#: ../../iot/pos.rst:129 +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 " +"IoT Box." +msgstr "" + +#: ../../iot/pos.rst:134 +msgid "The Barcode Scanner is not working reliably" +msgstr "" + +#: ../../iot/pos.rst:136 +msgid "" +"Make sure that no more than one device with 'Scan via Proxy'/'Barcode " +"Scanner' enabled are connected to the IoT Box at the same time." +msgstr "" + +#: ../../iot/pos.rst:140 +msgid "Printing the receipt takes too much time" +msgstr "" + +#: ../../iot/pos.rst:142 +msgid "" +"A small delay before the first print is expected, as the IoT Box 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 IoT Box." +msgstr "" + +#: ../../iot/pos.rst:148 +msgid "Some characters are not correctly printed on the receipt" +msgstr "" + +#: ../../iot/pos.rst:150 +msgid "" +"The IoT Box does not support all languages and characters. It currently " +"supports Latin and Cyrillic based scripts, with basic Japanese support." +msgstr "" + +#: ../../iot/pos.rst:155 +msgid "The printer is offline" +msgstr "" + +#: ../../iot/pos.rst:157 +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 "" + +#: ../../iot/pos.rst:162 +msgid "The cashdrawer does not open" +msgstr "" + +#: ../../iot/pos.rst:164 +msgid "" +"The cashdrawer should be connected to the printer and should be activated in" +" the POS configuration." +msgstr "" diff --git a/locale/it/LC_MESSAGES/livechat.po b/locale/it/LC_MESSAGES/livechat.po new file mode 100644 index 000000000..e4072da60 --- /dev/null +++ b/locale/it/LC_MESSAGES/livechat.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# mymage , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-07-23 12:10+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: mymage , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../livechat/livechat.rst:5 +msgid "Live Chat" +msgstr "Livechat" + +#: ../../livechat/livechat.rst:8 +msgid "Chat in live with website visitors" +msgstr "" + +#: ../../livechat/livechat.rst:10 +msgid "" +"With Odoo Live Chat, you can establish a direct contact with your website " +"visitors. A simple dialog box will be available on their screen and will " +"allow them to get in touch with one of your sales representatives. This way," +" you can easily turn prospects into potential business opportunities. You " +"will also be able to provide assistance to your customers. Overall, this is " +"the perfect tool to improve customer satisfaction." +msgstr "" + +#: ../../livechat/livechat.rst:19 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../livechat/livechat.rst:21 +msgid "" +"To get the Live Chat feature, open the Apps module, search for \"Live Chat\"" +" and then click on install." +msgstr "" + +#: ../../livechat/livechat.rst:27 +msgid "" +"The Live Chat module provides you a direct access to your channels. There, " +"operators can easily join and leave the chat." +msgstr "" + +#: ../../livechat/livechat.rst:34 +msgid "Add the live chat to an Odoo website" +msgstr "" + +#: ../../livechat/livechat.rst:36 +msgid "" +"If your website was created with Odoo, then the live chat is automatically " +"added to it. All that is left to do, is to go to :menuselection:`Website -->" +" Configuration --> Settings` to select the channel to be linked to the " +"website." +msgstr "" + +#: ../../livechat/livechat.rst:45 +msgid "Add the live chat to an external website" +msgstr "" + +#: ../../livechat/livechat.rst:47 +msgid "" +"If your website was not created with Odoo, go to the Live Chat module and " +"then select the channel to be linked. There, you can simply copy paste the " +"code available into your website. A specific url you can send to customers " +"or suppliers for them to access the live chat is also provided." +msgstr "" + +#: ../../livechat/livechat.rst:54 +msgid "Hide / display the live chat according to rules" +msgstr "" + +#: ../../livechat/livechat.rst:56 +msgid "" +"Rules for the live chat can be defined on the channel form. For instance, " +"you can choose to display the chat in the countries you speak the language " +"of. On the contrary, you are able to hide the chat in countries your company" +" does not sell in. If you select *Auto popup*, you can also set the length " +"of time it takes for the chat to appear." +msgstr "" + +#: ../../livechat/livechat.rst:66 +msgid "Prepare automatic messages" +msgstr "" + +#: ../../livechat/livechat.rst:68 +msgid "" +"On the channel form, in the *Options* section, several messages can be typed" +" to appear automatically on the chat. This will entice visitors to reach you" +" through the live chat." +msgstr "" + +#: ../../livechat/livechat.rst:76 +msgid "Start chatting with customers" +msgstr "" + +#: ../../livechat/livechat.rst:78 +msgid "" +"In order to start chatting with customers, first make sure that the channel " +"is published on your website. To do so, select *Unpublished on Website* on " +"the top right corner of the channel form to toggle the *Published* setting. " +"Then, the live chat can begin once an operator has joined the channel." +msgstr "" + +#: ../../livechat/livechat.rst:88 +msgid "" +"If no operator is available and/or if the channel is unpublished on the " +"website, then the live chat button will not appear to visitors." +msgstr "" + +#: ../../livechat/livechat.rst:92 +msgid "" +"In practice, the conversations initiated by the visitors will appear in the " +"Discuss module and will also pop up as a direct message. Therefore, " +"inquiries can be answered wherever you are in Odoo." +msgstr "" + +#: ../../livechat/livechat.rst:96 +msgid "" +"If there several operators in charge of a channel, the system will dispatch " +"sessions randomly between them." +msgstr "" + +#: ../../livechat/livechat.rst:100 +msgid "Use commands" +msgstr "" + +#: ../../livechat/livechat.rst:102 +msgid "" +"Commands are useful shortcuts for completing certain actions or to access " +"information you might need. To use this feature, simply type the commands " +"into the chat. The following actions are available :" +msgstr "" + +#: ../../livechat/livechat.rst:106 +msgid "**/help** : show a helper message." +msgstr "" + +#: ../../livechat/livechat.rst:108 +msgid "**/helpdesk** : create a helpdesk ticket." +msgstr "" + +#: ../../livechat/livechat.rst:110 +msgid "**/helpdesk\\_search** : search for a helpdesk ticket." +msgstr "" + +#: ../../livechat/livechat.rst:112 +msgid "**/history** : see 15 last visited pages." +msgstr "" + +#: ../../livechat/livechat.rst:114 +msgid "**/lead** : create a new lead." +msgstr "" + +#: ../../livechat/livechat.rst:116 +msgid "**/leave** : leave the channel." +msgstr "" + +#: ../../livechat/livechat.rst:119 +msgid "" +"If a helpdesk ticket is created from the chat, then the conversation it was " +"generated from will automatically appear as the description of the ticket. " +"The same goes for the creation of a lead." +msgstr "" + +#: ../../livechat/livechat.rst:124 +msgid "Send canned responses" +msgstr "" + +#: ../../livechat/livechat.rst:126 +msgid "" +"Canned responses allow you to create substitutes to generic sentences you " +"frequently use. Typing a word instead of several will save you a lot of " +"time. To add canned responses, go to :menuselection:`LIVE CHAT --> " +"Configuration --> Canned Responses` and create as many as you need to. Then," +" to use them during a chat, simply type \":\" followed by the shortcut you " +"assigned." +msgstr "" + +#: ../../livechat/livechat.rst:136 +msgid "" +"You now have all of the tools needed to chat in live with your website " +"visitors, enjoy !" +msgstr "" diff --git a/locale/it/LC_MESSAGES/manufacturing.po b/locale/it/LC_MESSAGES/manufacturing.po new file mode 100644 index 000000000..36c90d1fb --- /dev/null +++ b/locale/it/LC_MESSAGES/manufacturing.po @@ -0,0 +1,523 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# Paolo Valier, 2019 +# Léonie Bouchat , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Léonie Bouchat , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../manufacturing.rst:5 +msgid "Manufacturing" +msgstr "Produzione" + +#: ../../manufacturing/management.rst:5 +msgid "Manufacturing Management" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:3 +msgid "How to create a Bill of Materials" +msgstr "" + +#: ../../manufacturing/management/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/management/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/management/bill_configuration.rst:14 +msgid "Setting up a Basic BoM" +msgstr "" + +#: ../../manufacturing/management/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." +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:19 +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/management/bill_configuration.rst:29 +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/management/bill_configuration.rst:35 +msgid "Adding a Routing to a BoM" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:37 +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/management/bill_configuration.rst:43 +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/management/bill_configuration.rst:47 +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/management/bill_configuration.rst:58 +msgid "Adding Byproducts to a BoM" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:60 +msgid "" +"In Odoo, a byproduct is any product produced by a BoM in addition to the " +"primary product." +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:63 +msgid "" +"To add byproducts to a BoM, you will first need to enable them from " +":menuselection:`Configuration --> Settings`." +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:69 +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/management/bill_configuration.rst:78 +msgid "Setting up a BoM for a Product With Sub-Assemblies" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:80 +#: ../../manufacturing/management/sub_assemblies.rst:5 +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/management/bill_configuration.rst:87 +#: ../../manufacturing/management/sub_assemblies.rst:12 +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/management/bill_configuration.rst:94 +msgid "Configure the Top-Level Product BoM" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:96 +#: ../../manufacturing/management/sub_assemblies.rst:21 +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/management/bill_configuration.rst:104 +#: ../../manufacturing/management/sub_assemblies.rst:29 +msgid "Configure the Subassembly Product Data" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:106 +#: ../../manufacturing/management/sub_assemblies.rst:31 +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/management/bill_configuration.rst:114 +#: ../../manufacturing/management/sub_assemblies.rst:39 +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/management/bill_configuration.rst:120 +msgid "Using a Single BoM to Describe Several Variants of a Single Product" +msgstr "" + +#: ../../manufacturing/management/bill_configuration.rst:122 +#: ../../manufacturing/management/product_variants.rst:5 +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/management/bill_configuration.rst:129 +#: ../../manufacturing/management/product_variants.rst:12 +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/management/bill_configuration.rst:134 +#: ../../manufacturing/management/product_variants.rst:17 +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/management/kit_shipping.rst:3 +msgid "How to Sell a Set of Products as a Kit" +msgstr "" + +#: ../../manufacturing/management/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/management/kit_shipping.rst:12 +msgid "Manage Stock of Component Products" +msgstr "" + +#: ../../manufacturing/management/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/management/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/management/kit_shipping.rst:24 +msgid "|image0|\\ |image1|" +msgstr "" + +#: ../../manufacturing/management/kit_shipping.rst:27 +#: ../../manufacturing/management/kit_shipping.rst:62 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../manufacturing/management/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/management/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/management/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/management/kit_shipping.rst:53 +msgid "Manage Stock of Kit Product and Component Products" +msgstr "" + +#: ../../manufacturing/management/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/management/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/management/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/management/manufacturing_order.rst:3 +msgid "How to process a manufacturing order" +msgstr "" + +#: ../../manufacturing/management/manufacturing_order.rst:6 +msgid "Introduction" +msgstr "Introduzione" + +#: ../../manufacturing/management/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/management/manufacturing_order.rst:17 +msgid "How to manage manufacturing without routings" +msgstr "" + +#: ../../manufacturing/management/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/management/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/management/manufacturing_order.rst:27 +#: ../../manufacturing/management/manufacturing_order.rst:52 +msgid "Create manufacturing orders" +msgstr "" + +#: ../../manufacturing/management/manufacturing_order.rst:29 +msgid "Record Production" +msgstr "Registrare la produzione" + +#: ../../manufacturing/management/manufacturing_order.rst:32 +msgid "How to manage manufacturing with routings and work orders" +msgstr "" + +#: ../../manufacturing/management/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/management/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/management/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/management/manufacturing_order.rst:50 +msgid "The workflow is thus divided into three basic phases, as follows:" +msgstr "" + +#: ../../manufacturing/management/manufacturing_order.rst:54 +msgid "Schedule the associated work orders." +msgstr "" + +#: ../../manufacturing/management/manufacturing_order.rst:56 +msgid "Perform the scheduled work and record production." +msgstr "" + +#: ../../manufacturing/management/product_variants.rst:3 +msgid "How to manage BoMs for product variants" +msgstr "" + +#: ../../manufacturing/management/sub_assemblies.rst:3 +msgid "How to manage semi-finished products" +msgstr "" + +#: ../../manufacturing/management/sub_assemblies.rst:19 +msgid "Configure the Top -Level Product BoM" +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:3 +msgid "Unbuild a product" +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:5 +msgid "" +"In Odoo Manufacturing App, you can *Unbuild* products. Two use cases can be " +"managed: (1) you can unbuild products you have built yourself or (2) you can" +" unbuild products you have received." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:9 +msgid "" +"Let's take the first case, you are manufacturing products yourself. If one " +"of your product presents some defect, you might want to unbuild it instead " +"of scrapping it completely, allowing you to reuse some components of the " +"product." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:14 +msgid "" +"In the second case, you are buying products for the sole purpose of " +"unbuilding them and recycling them." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:18 +msgid "Unbuild Order" +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:20 +msgid "" +"While in the Manufacturing App, under the *Operations* tab you will find the" +" menu *Unbuild Orders*." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:26 +msgid "" +"When creating a new one, you can either select a MO if you are unbuilding " +"something you manufactured or only select a product if you are unbuilding " +"something you received." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:33 +msgid "When you are done, just click unbuild and the process will be over." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:35 +msgid "" +"If you unbuild a product that you manufactured before, you will get the " +"components from the MO back in stock." +msgstr "" + +#: ../../manufacturing/management/unbuild.rst:38 +msgid "" +"If you unbuild a product you bought, you will get the components from the " +"BoM back in stock." +msgstr "" + +#: ../../manufacturing/overview.rst:5 +msgid "Overview" +msgstr "Panoramica" + +#: ../../manufacturing/repair.rst:5 +msgid "Repair Management" +msgstr "" + +#: ../../manufacturing/repair/repair.rst:3 +msgid "Repair products" +msgstr "" + +#: ../../manufacturing/repair/repair.rst:5 +msgid "" +"The Odoo *Repair* app allows you to manage a complete after sales process " +"but also to simply repair products you have manufactured, if they present a " +"defect." +msgstr "" + +#: ../../manufacturing/repair/repair.rst:10 +msgid "Create a Repair Order" +msgstr "" + +#: ../../manufacturing/repair/repair.rst:12 +msgid "" +"Once in the app, you can access your existing *Repair Orders* and create a " +"new one." +msgstr "" + +#: ../../manufacturing/repair/repair.rst:19 +msgid "Manage a repair" +msgstr "" + +#: ../../manufacturing/repair/repair.rst:21 +msgid "" +"When a customer sends you a product for repair, create a new *Repair Order*." +" Fill it in with all the information you may need such as the product, the " +"customer, if it has to be invoiced after or before the repair, the parts you" +" might need, etc." +msgstr "" + +#: ../../manufacturing/repair/repair.rst:29 +msgid "" +"Once everything is done, you can then send the repair quotation to your " +"customer. If it is approved, you can confirm the repair. You will then be " +"able to start & end the repair when it is completed." +msgstr "" + +#: ../../manufacturing/repair/repair.rst:36 +msgid "You can now invoice the repair." +msgstr "" diff --git a/locale/it/LC_MESSAGES/mobile.po b/locale/it/LC_MESSAGES/mobile.po new file mode 100644 index 000000000..9607e9282 --- /dev/null +++ b/locale/it/LC_MESSAGES/mobile.po @@ -0,0 +1,120 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../mobile/firebase.rst:5 +msgid "Mobile" +msgstr "Dispositivo mobile" + +#: ../../mobile/firebase.rst:8 +msgid "Setup your Firebase Cloud Messaging" +msgstr "" + +#: ../../mobile/firebase.rst:10 +msgid "" +"In order to have mobile notifications in our Android app, you need an API " +"key." +msgstr "" + +#: ../../mobile/firebase.rst:13 +msgid "" +"If it is not automatically configured (for instance for On-premise or " +"Odoo.sh) please follow these steps below to get an API key for the android " +"app." +msgstr "" + +#: ../../mobile/firebase.rst:18 +msgid "" +"The iOS app doesn't support mobile notifications for Odoo versions < 12." +msgstr "" + +#: ../../mobile/firebase.rst:22 +msgid "Firebase Settings" +msgstr "" + +#: ../../mobile/firebase.rst:25 +msgid "Create a new project" +msgstr "Creazione di un nuovo progetto" + +#: ../../mobile/firebase.rst:27 +msgid "" +"First, make sure you to sign in to your Google Account. Then, go to " +"`https://console.firebase.google.com " +"`__ and create a new project." +msgstr "" + +#: ../../mobile/firebase.rst:34 +msgid "" +"Choose a project name, click on **Continue**, then click on **Create " +"project**." +msgstr "" + +#: ../../mobile/firebase.rst:37 +msgid "When you project is ready, click on **Continue**." +msgstr "" + +#: ../../mobile/firebase.rst:39 +msgid "" +"You will be redirected to the overview project page (see next screenshot)." +msgstr "" + +#: ../../mobile/firebase.rst:43 +msgid "Add an app" +msgstr "" + +#: ../../mobile/firebase.rst:45 +msgid "In the overview page, click on the Android icon." +msgstr "" + +#: ../../mobile/firebase.rst:50 +msgid "" +"You must use \"com.odoo.com\" as Android package name. Otherwise, it will " +"not work." +msgstr "" + +#: ../../mobile/firebase.rst:56 +msgid "" +"No need to download the config file, you can click on **Next** twice and " +"skip the fourth step." +msgstr "" + +#: ../../mobile/firebase.rst:60 +msgid "Get generated API key" +msgstr "" + +#: ../../mobile/firebase.rst:62 +msgid "On the overview page, go to Project settings:" +msgstr "" + +#: ../../mobile/firebase.rst:67 +msgid "" +"In **Cloud Messaging**, you will see the **API key** and the **Sender ID** " +"that you need to set in Odoo General Settings." +msgstr "" + +#: ../../mobile/firebase.rst:74 +msgid "Settings in Odoo" +msgstr "" + +#: ../../mobile/firebase.rst:76 +msgid "Simply paste the API key and the Sender ID from Cloud Messaging." +msgstr "" diff --git a/locale/it/LC_MESSAGES/point_of_sale.po b/locale/it/LC_MESSAGES/point_of_sale.po new file mode 100644 index 000000000..27f8683e1 --- /dev/null +++ b/locale/it/LC_MESSAGES/point_of_sale.po @@ -0,0 +1,1369 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# mymage , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: mymage , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../point_of_sale.rst:5 +msgid "Point of Sale" +msgstr "Punto vendita" + +#: ../../point_of_sale/advanced.rst:3 +msgid "Advanced topics" +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:3 +msgid "Using barcodes in PoS" +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:5 +msgid "" +"Using a barcode scanner to process point of sale orders improves your " +"efficiency and helps you to save time for you and your customers." +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:9 +#: ../../point_of_sale/advanced/loyalty.rst:9 +#: ../../point_of_sale/advanced/mercury.rst:25 +#: ../../point_of_sale/advanced/reprint.rst:8 +#: ../../point_of_sale/overview/start.rst:22 +#: ../../point_of_sale/restaurant/setup.rst:9 +#: ../../point_of_sale/restaurant/split.rst:10 +#: ../../point_of_sale/shop/seasonal_discount.rst:10 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../point_of_sale/advanced/barcode.rst:11 +msgid "" +"To use a barcode scanner, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:14 +msgid "" +"Under the IoT Box / Hardware category, you will find *Barcode Scanner* " +"select it." +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:21 +msgid "You can find more about Barcode Nomenclature here (ADD HYPERLINK)" +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:25 +msgid "Add barcodes to product" +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:27 +msgid "" +"Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a " +"product." +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:30 +msgid "" +"Under the general information tab, you can find a barcode field where you " +"can input any barcode." +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:37 +msgid "Scanning products" +msgstr "" + +#: ../../point_of_sale/advanced/barcode.rst:39 +msgid "" +"From your PoS interface, scan any barcode with your barcode scanner. The " +"product will be added, you can scan the same product to add it multiple " +"times or change the quantity manually on the screen." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:3 +msgid "Using discount tags with a barcode scanner" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:5 +msgid "" +"If you want to sell your products with a discount, for a product getting " +"close to its expiration date for example, you can use discount tags. They " +"allow you to scan discount barcodes." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:10 +msgid "" +"To use discount tags you will need to use a barcode scanner, you can see the" +" documentation about it `here `__" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:15 +msgid "Barcode Nomenclature" +msgstr "Nomenclatura codice a barre" + +#: ../../point_of_sale/advanced/discount_tags.rst:17 +msgid "To use discounts tags, we need to learn about barcode nomenclature." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:19 +msgid "" +"Let's say you want to have a discount for the product with the following " +"barcode:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:25 +msgid "" +"You can find the *Default Nomenclature* under the settings of your PoS " +"interface." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:34 +msgid "" +"Let's say you want 50% discount on a product you have to start your barcode " +"with 22 (for the discount barcode nomenclature) and then 50 (for the %) " +"before adding the product barcode. In our example, the barcode would be:" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:43 +msgid "Scan the products & tags" +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:45 +msgid "You first have to scan the desired product (in our case, a lemon)." +msgstr "" + +#: ../../point_of_sale/advanced/discount_tags.rst:50 +msgid "" +"And then scan the discount tag. The discount will be applied and you can " +"finish the transaction." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:3 +msgid "Manage a loyalty program" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:5 +msgid "" +"Encourage your customers to continue to shop at your point of sale with a " +"*Loyalty Program*." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:11 +msgid "" +"To activate the *Loyalty Program* feature, go to :menuselection:`Point of " +"Sale --> Configuration --> Point of sale` and select your PoS interface. " +"Under the Pricing features, select *Loyalty Program*" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:19 +msgid "From there you can create and edit your loyalty programs." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:24 +msgid "" +"You can decide what type of program you wish to use, if the reward is a " +"discount or a gift, make it specific to some products or cover your whole " +"range. Apply rules so that it is only valid in specific situation and " +"everything in between." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:30 +msgid "Use the loyalty program in your PoS interface" +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:32 +msgid "" +"When a customer is set, you will now see the points they will get for the " +"transaction and they will accumulate until they are spent. They are spent " +"using the button *Rewards* when they have enough points according to the " +"rules defined in the loyalty program." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:40 +#: ../../point_of_sale/shop/seasonal_discount.rst:45 +msgid "" +"You can see the price is instantly updated to reflect the pricelist. You can" +" finalize the order in your usual way." +msgstr "" + +#: ../../point_of_sale/advanced/loyalty.rst:44 +#: ../../point_of_sale/shop/seasonal_discount.rst:49 +msgid "" +"If you select a customer with a default pricelist, it will be applied. You " +"can of course change it." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:3 +msgid "Apply manual discounts" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:5 +msgid "" +"If you seldom use discounts, applying manual discounts might be the easiest " +"solution for your Point of Sale." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:8 +msgid "" +"You can either apply a discount on the whole order or on specific products." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:12 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:14 +msgid "From your session interface, use *Disc* button." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:19 +msgid "" +"You can then input a discount (in percentage) over the product that is " +"currently selected and the discount will be applied." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:23 +msgid "Apply a global discount" +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:25 +msgid "" +"To apply a discount on the whole order, go to :menuselection:`Point of Sales" +" --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:28 +msgid "" +"Under the *Pricing* category, you will find *Global Discounts* select it." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:34 +msgid "You now have a new *Discount* button in your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:39 +msgid "" +"Once clicked you can then enter your desired discount (in percentages)." +msgstr "" + +#: ../../point_of_sale/advanced/manual_discount.rst:44 +msgid "" +"On this example, you can see a global discount of 50% as well as a specific " +"product discount also at 50%." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:3 +msgid "Accept credit card payment using Mercury" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:5 +msgid "" +"A MercuryPay account (see `*MercuryPay website* " +"`__) is required to accept credit card payments" +" in Odoo 11 PoS with an integrated card reader. MercuryPay only operates " +"with US and Canadian banks making this procedure only suitable for North " +"American businesses." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:11 +msgid "" +"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:16 +msgid "Install Mercury" +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:18 +msgid "" +"To install Mercury go to :menuselection:`Apps` and search for the *Mercury* " +"module." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:27 +msgid "" +"To configure mercury, you need to activate the developer mode. To do so go " +"to :menuselection:`Apps --> Settings` and select *Activate the developer " +"mode*." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:34 +msgid "" +"While in developer mode, go to :menuselection:`Point of Sale --> " +"Configuration --> Mercury Configurations`." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:37 +msgid "" +"Create a new configuration for credit cards and enter your Mercury " +"credentials." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:43 +msgid "" +"Then go to :menuselection:`Point of Sale --> Configuration --> Payment " +"Methods` and create a new one." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:46 +msgid "" +"Under *Point of Sale* when you select *Use in Point of Sale* you can then " +"select your Mercury credentials that you just created." +msgstr "" + +#: ../../point_of_sale/advanced/mercury.rst:52 +msgid "" +"You now have a new option to pay by credit card when validating a payment." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:3 +msgid "Manage multiple cashiers" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:5 +msgid "" +"With Odoo Point of Sale, you can easily manage multiple cashiers. This " +"allows you to keep track on who is working in the Point of Sale and when." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:9 +msgid "" +"There are three different ways of switching between cashiers in Odoo. They " +"are all explained below." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:13 +msgid "" +"To manage multiple cashiers, you need to have several users (at least two)." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:17 +msgid "Switch without pin codes" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:19 +msgid "" +"The easiest way to switch cashiers is without a code. Simply press on the " +"name of the current cashier in your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:25 +msgid "You will then be able to change between different users." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:30 +msgid "And the cashier will be changed." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:33 +msgid "Switch cashiers with pin codes" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:35 +msgid "" +"You can also set a pin code on each user. To do so, go to " +":menuselection:`Settings --> Manage Access rights` and select the user." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:41 +msgid "" +"On the user page, under the *Point of Sale* tab you can add a Security PIN." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:47 +msgid "Now when you switch users you will be asked to input a PIN password." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:53 +msgid "Switch cashiers with barcodes" +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:55 +msgid "You can also ask your cashiers to log themselves in with their badges." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:57 +msgid "Back where you put a security PIN code, you could also put a barcode." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:62 +msgid "" +"When they scan their barcode, the cashier will be switched to that user." +msgstr "" + +#: ../../point_of_sale/advanced/multi_cashiers.rst:64 +msgid "Barcode nomenclature link later on" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:3 +msgid "Reprint Receipts" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:5 +msgid "" +"Use the *Reprint receipt* feature if you have the need to reprint a ticket." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:10 +msgid "" +"To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:13 +msgid "" +"Under the Bills & Receipts category, you will find *Reprint Receipt* option." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:20 +msgid "Reprint a receipt" +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:22 +msgid "On your PoS interface, you now have a *Reprint receipt* button." +msgstr "" + +#: ../../point_of_sale/advanced/reprint.rst:27 +msgid "When you use it, you can then reprint your last receipt." +msgstr "" + +#: ../../point_of_sale/analyze.rst:3 +msgid "Analyze sales" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:3 +msgid "View your Point of Sale statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:5 +msgid "" +"Keeping track of your sales is key for any business. That's why Odoo " +"provides you a practical view to analyze your sales and get meaningful " +"statistics." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:10 +msgid "View your statistics" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:12 +msgid "" +"To access your statistics go to :menuselection:`Point of Sale --> Reporting " +"--> Orders`" +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:15 +msgid "You can then see your various statistics in graph or pivot form." +msgstr "" + +#: ../../point_of_sale/analyze/statistics.rst:21 +msgid "You can also access the stats views by clicking here" +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 "Introduzione" + +#: ../../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 IoT Box per POS configuration" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:35 +msgid "Setup" +msgstr "Impostazione" + +#: ../../point_of_sale/belgian_fdm/setup.rst:38 +msgid "IoT Box" +msgstr "Box IoT" + +#: ../../point_of_sale/belgian_fdm/setup.rst:40 +msgid "" +"In order to use a Fiscal Data Module, you will need a registered IoT Box. " +"These IoT Boxes are similar to the regular IoT Boxes we sell, but they are " +"registered with the Belgian government. This is required by law. Attempting " +"to use a Fiscal Data Module on a non-registered IoT Box will not work. You " +"can verify that the Fiscal Data Module is recognized by the IoT Box by going" +" to the *Hardware status page* via the IoT Box homepage." +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:52 +msgid "Odoo" +msgstr "Odoo" + +#: ../../point_of_sale/belgian_fdm/setup.rst:54 +msgid "" +"An Odoo POS app can be given certified POS capabilities by installing the " +"**Belgian Registered Cash Register** app (technical name: " +"``pos_blackbox_be``). Because of government restrictions imposed on us, this" +" installation cannot be undone. After this, you will have to ensure that " +"each POS configuration has a unique registered IoT Box associated with it " +"(:menuselection:`Point of Sale --> Configuration --> Point of Sale` and " +"ensure Hardware Proxy / IoT Box and the serial number of your IoT Box is " +"set). The first time you open the Point of Sale and attempt to do a " +"transaction, you will be asked to input the PIN that you received with your " +"VAT signing card." +msgstr "" + +#: ../../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 IoT Box are not allowed" +msgstr "" + +#: ../../point_of_sale/belgian_fdm/setup.rst:91 +msgid "Using the POS without a connection to the IoT Box (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.rst:3 ../../point_of_sale/overview/start.rst:6 +msgid "Overview" +msgstr "Panoramica" + +#: ../../point_of_sale/overview/register.rst:3 +msgid "Register customers" +msgstr "" + +#: ../../point_of_sale/overview/register.rst:5 +msgid "" +"Registering your customers will give you the ability to grant them various " +"privileges such as discounts, loyalty program, specific communication. It " +"will also be required if they want an invoice and registering them will make" +" any future interaction with them faster." +msgstr "" + +#: ../../point_of_sale/overview/register.rst:11 +msgid "Create a customer" +msgstr "" + +#: ../../point_of_sale/overview/register.rst:13 +msgid "From your session interface, use the customer button." +msgstr "" + +#: ../../point_of_sale/overview/register.rst:18 +msgid "Create a new one by using this button." +msgstr "" + +#: ../../point_of_sale/overview/register.rst:23 +msgid "" +"You will be invited to fill out the customer form with their information." +msgstr "" + +#: ../../point_of_sale/overview/register.rst:29 +msgid "" +"Use the save button when you are done. You can then select that customer in " +"any future transactions." +msgstr "" + +#: ../../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 Accounting " +"applications. Any transaction in your point of sale will be automatically " +"registered in your stock and accounting entries but also 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 "Go to Apps and install the Point of Sale application." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:33 +msgid "" +"If you are using Odoo Accounting, do not forget to install a chart of " +"accounts if it's not already done. This can be achieved in the accounting " +"settings." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:38 +msgid "Make products available in the Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:40 +msgid "" +"To make products available for sale in the Point of Sale, open a product, go" +" in the tab Sales and tick the box \"Available in Point of Sale\"." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:48 +msgid "" +"You can also define there if the product has to be weighted with a scale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:52 +msgid "Configure your payment methods" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:54 +msgid "" +"To add a new payment method for a Point of Sale, go to :menuselection:`Point" +" of Sale --> Configuration --> Point of Sale --> Choose a Point of Sale --> " +"Go to the Payments section` and click on the link \"Payment Methods\"." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:62 +msgid "" +"Now, you can create new payment methods. Do not forget to tick the box \"Use" +" in Point of Sale\"." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:68 +msgid "" +"Once your payment methods are created, you can decide in which Point of Sale" +" you want to make them available in the Point of Sale configuration." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:75 +msgid "Configure your Point of Sale" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:77 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" +" select the Point of Sale you want to configure. From this menu, you can " +"edit all the settings of your Point of Sale." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:82 +msgid "Create your first PoS session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:85 +msgid "Your first order" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:87 +msgid "" +"You are now ready to make your first sales through the PoS. From the PoS " +"dashboard, you see all your points of sale and you can start a new session." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:94 +msgid "You now arrive on the PoS interface." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:99 +msgid "" +"Once an order is completed, you can register the payment. All the available " +"payment methods appear on the left of the screen. Select the payment method " +"and enter the received amount. You can then validate the payment." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:104 +msgid "You can register the next orders." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:107 +msgid "Close the PoS session" +msgstr "" + +#: ../../point_of_sale/overview/start.rst:109 +msgid "" +"At the end of the day, you will close your PoS session. For this, click on " +"the close button that appears on the top right corner and confirm. You can " +"now close the session from the dashboard." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:117 +msgid "" +"It's strongly advised to close your PoS session at the end of each day." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:119 +msgid "You will then see a summary of all transactions per payment method." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:124 +msgid "" +"You can click on a line of that summary to see all the orders that have been" +" paid by this payment method during that PoS session." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:127 +msgid "" +"If everything is correct, you can validate the PoS session and post the " +"closing entries." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:130 +msgid "It's done, you have now closed your first PoS session." +msgstr "" + +#: ../../point_of_sale/overview/start.rst:133 +msgid "" +"To connect the PoS to hardware with an Odoo IoT Box, please see the section " +":doc:`../../../iot/connect` and :doc:`../../../iot/pos`" +msgstr "" + +#: ../../point_of_sale/restaurant.rst:3 +msgid "Advanced Restaurant Features" +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:3 +msgid "Print the Bill" +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:5 +msgid "" +"Use the *Bill Printing* feature to print the bill before the payment. This " +"is useful if the bill is still subject to evolve and is thus not the " +"definitive ticket." +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:10 +msgid "Configure Bill Printing" +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:12 +msgid "" +"To activate *Bill Printing*, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:15 +msgid "" +"Under the Bills & Receipts category, you will find *Bill Printing* option." +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:22 +msgid "Split a Bill" +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:24 +msgid "On your PoS interface, you now have a *Bill* button." +msgstr "" + +#: ../../point_of_sale/restaurant/bill_printing.rst:29 +msgid "When you use it, you can then print the bill." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:3 +msgid "Print orders at the kitchen or bar" +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:5 +msgid "" +"To ease the workflow between the front of house and the back of the house, " +"printing the orders taken on the PoS interface right in the kitchen or bar " +"can be a tremendous help." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:10 +msgid "Activate the bar/kitchen printer" +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:12 +msgid "" +"To activate the *Order printing* feature, go to :menuselection:`Point of " +"Sales --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:16 +msgid "" +"Under the IoT Box / Hardware Proxy category, you will find *Order Printers*." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:19 +msgid "Add a printer" +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:21 +msgid "" +"In your configuration menu you will now have a *Order Printers* option where" +" you can add the printer." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:28 +msgid "Print a kitchen/bar order" +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:33 +msgid "Select or create a printer." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:36 +msgid "Print the order in the kitchen/bar" +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:38 +msgid "On your PoS interface, you now have a *Order* button." +msgstr "" + +#: ../../point_of_sale/restaurant/kitchen_printing.rst:43 +msgid "" +"When you press it, it will print the order on your kitchen/bar printer." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:3 +msgid "Register multiple orders" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:5 +msgid "" +"The Odoo Point of Sale App allows you to register multiple orders " +"simultaneously giving you all the flexibility you need." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:9 +msgid "Register an additional order" +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:11 +msgid "" +"When you are registering any order, you can use the *+* button to add a new " +"order." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:14 +msgid "" +"You can then move between each of your orders and process the payment when " +"needed." +msgstr "" + +#: ../../point_of_sale/restaurant/multi_orders.rst:20 +msgid "" +"By using the *-* button, you can remove the order you are currently on." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:3 +msgid "Setup PoS Restaurant/Bar" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:5 +msgid "" +"Food and drink businesses have very specific needs that the Odoo Point of " +"Sale application can help you to fulfill." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:11 +msgid "" +"To activate the *Bar/Restaurant* features, go to :menuselection:`Point of " +"Sale --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:15 +msgid "Select *Is a Bar/Restaurant*" +msgstr "" + +#: ../../point_of_sale/restaurant/setup.rst:20 +msgid "" +"You now have various specific options to help you setup your point of sale. " +"You can see those options have a small knife and fork logo next to them." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:3 +msgid "Offer a bill-splitting option" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:5 +msgid "" +"Offering an easy bill splitting solution to your customers will leave them " +"with a positive experience. That's why this feature is available out-of-the-" +"box in the Odoo Point of Sale application." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:12 +msgid "" +"To activate the *Bill Splitting* feature, go to :menuselection:`Point of " +"Sales --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:16 +msgid "" +"Under the Bills & Receipts category, you will find the Bill Splitting " +"option." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:23 +msgid "Split a bill" +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:25 +msgid "In your PoS interface, you now have a *Split* button." +msgstr "" + +#: ../../point_of_sale/restaurant/split.rst:30 +msgid "" +"When you use it, you will be able to select what that guest should had and " +"process the payment, repeating the process for each guest." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:3 +msgid "Configure your table management" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:5 +msgid "" +"Once your point of sale has been configured for bar/restaurant usage, select" +" *Table Management* in :menuselection:`Point of Sale --> Configuration --> " +"Point of sale`.." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:9 +msgid "Add a floor" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:11 +msgid "" +"When you select *Table management* you can manage your floors by clicking on" +" *Floors*" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:18 +msgid "Add tables" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:20 +msgid "From your PoS interface, you will now see your floor(s)." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:25 +msgid "" +"When you click on the pencil you will enter into edit mode, which will allow" +" you to create tables, move them, modify them, ..." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:31 +msgid "" +"In this example I have 2 round tables for six and 2 square tables for four, " +"I color coded them to make them easier to find, you can also rename them, " +"change their shape, size, the number of people they hold as well as " +"duplicate them with the handy tool bar." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:36 +msgid "Once your floor plan is set, you can close the edit mode." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:39 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:41 +msgid "" +"When you select a table, you will be brought to your usual interface to " +"register an order and payment." +msgstr "" + +#: ../../point_of_sale/restaurant/table.rst:44 +msgid "" +"You can quickly go back to your floor plan by selecting the floor button and" +" you can also transfer the order to another table." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:3 +msgid "Integrate a tip option into payment" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:5 +msgid "" +"As it is customary to tip in many countries all over the world, it is " +"important to have the option in your PoS interface." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:9 +msgid "Configure Tipping" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:11 +msgid "" +"To activate the *Tips* feature, go to :menuselection:`Point of Sale --> " +"Configuration --> Point of sale` and select your PoS." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:14 +msgid "" +"Under the Bills & Receipts category, you will find *Tips*. Select it and " +"create a *Tip Product* such as *Tips* in this case." +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:21 +msgid "Add Tips to the bill" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:23 +msgid "Once on the payment interface, you now have a new *Tip* button" +msgstr "" + +#: ../../point_of_sale/restaurant/tips.rst:31 +msgid "Add the tip your customer wants to leave and process to the payment." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:3 +msgid "Transfer customers between tables" +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:5 +msgid "" +"If your customer(s) want to change table after they have already placed an " +"order, Odoo can help you to transfer the customers and their order to their " +"new table, keeping your customers happy without making it complicated for " +"you." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:11 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:13 +msgid "Select the table your customer(s) is/are currently on." +msgstr "" + +#: ../../point_of_sale/restaurant/transfer.rst:18 +msgid "" +"You can now transfer the customers, simply use the transfer button and " +"select the new table" +msgstr "" + +#: ../../point_of_sale/shop.rst:3 +msgid "Advanced Shop Features" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:3 +msgid "Set-up Cash Control in Point of Sale" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:5 +msgid "" +"Cash control allows you to check the amount of the cashbox at the opening " +"and closing. You can thus make sure no error has been made and that no cash " +"is missing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:10 +msgid "Activate Cash Control" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:12 +msgid "" +"To activate the *Cash Control* feature, go to :menuselection:`Point of Sales" +" --> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:16 +msgid "Under the payments category, you will find the cash control setting." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:21 +msgid "" +"In this example, you can see I want to have 275$ in various denomination at " +"the opening and closing." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:24 +msgid "" +"When clicking on **Opening/Closing Values** you will be able to create those" +" values." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:31 +msgid "Start a session" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:33 +msgid "" +"You now have a new button added when you open a session, *Set opening " +"Balance*" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:42 +msgid "" +"By default it will use the values you added before, but you can always " +"modify it." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:46 +msgid "Close a session" +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:48 +msgid "" +"When you want to close your session, you now have a *Set Closing Balance* " +"button as well." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:51 +msgid "" +"You can then see the theoretical balance, the real closing balance (what you" +" have just counted) and the difference between the two." +msgstr "" + +#: ../../point_of_sale/shop/cash_control.rst:57 +msgid "" +"If you use the *Take Money Out* option to take out your transactions for " +"this session, you now have a zero-sum difference and the same closing " +"balance as your opening balance. You cashbox is ready for the next session." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:3 +msgid "Invoice from the PoS interface" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:5 +msgid "" +"Some of your customers might request an invoice when buying from your Point " +"of Sale, you can easily manage it directly from the PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:9 +msgid "Activate invoicing" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:11 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and" +" select your Point of Sale:" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:17 +msgid "" +"Under the *Bills & Receipts* you will see the invoicing option, tick it. " +"Don't forget to choose in which journal the invoices should be created." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:25 +msgid "Select a customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:27 +msgid "From your session interface, use the customer button" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:32 +msgid "" +"You can then either select an existing customer and set it as your customer " +"or create a new one by using this button." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:38 +msgid "" +"You will be invited to fill out the customer form with its information." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:41 +msgid "Invoice your customer" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:43 +msgid "" +"From the payment screen, you now have an invoice option, use the button to " +"select it and validate." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:49 +msgid "You can then print the invoice and move on to your next order." +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:52 +msgid "Retrieve invoices" +msgstr "" + +#: ../../point_of_sale/shop/invoice.rst:54 +msgid "" +"Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top" +" right corner) you will find all your orders in :menuselection:`Point of " +"Sale --> Orders --> Orders` and under the status tab you will see which ones" +" have been invoiced. When clicking on a order you can then access the " +"invoice." +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:3 +msgid "Accept returns and refund products" +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:5 +msgid "" +"Having a well-thought-out return policy is key to attract - and keep - your " +"customers. Making it easy for you to accept and refund those returns is " +"therefore also a key aspect of your *Point of Sale* interface." +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:10 +msgid "" +"From your *Point of Sale* interface, select the product your customer wants " +"to return, use the +/- button and enter the quantity they need to return. If" +" they need to return multiple products, repeat the process." +msgstr "" + +#: ../../point_of_sale/shop/refund.rst:17 +msgid "" +"As you can see, the total is in negative, to end the refund you simply have " +"to process the payment." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:3 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:5 +msgid "" +"Entice your customers and increase your revenue by offering time-limited or " +"seasonal discounts. Odoo has a powerful pricelist feature to support a " +"pricing strategy tailored to your business." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:12 +msgid "" +"To activate the *Pricelists* feature, go to :menuselection:`Point of Sales " +"--> Configuration --> Point of sale` and select your PoS interface." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:18 +msgid "" +"Choose the pricelists you want to make available in this Point of Sale and " +"define the default pricelist. You can access all your pricelists by clicking" +" on *Pricelists*." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:23 +msgid "Create a pricelist" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:25 +msgid "" +"By default, you have a *Public Pricelist* to create more, go to " +":menuselection:`Point of Sale --> Catalog --> Pricelists`" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:31 +msgid "" +"You can set several criterias to use a specific price: periods, min. " +"quantity (meet a minimum ordered quantity and get a price break), etc. You " +"can also chose to only apply that pricelist on specific products or on the " +"whole range." +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:37 +msgid "Using a pricelist in the PoS interface" +msgstr "" + +#: ../../point_of_sale/shop/seasonal_discount.rst:39 +msgid "" +"You now have a new button above the *Customer* one, use it to instantly " +"select the right pricelist." +msgstr "" diff --git a/locale/it/LC_MESSAGES/portal.po b/locale/it/LC_MESSAGES/portal.po new file mode 100644 index 000000000..112e216d2 --- /dev/null +++ b/locale/it/LC_MESSAGES/portal.po @@ -0,0 +1,179 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Francesco Garganese , 2019 +# Martin Trigaux, 2019 +# Sergio Zanchetta , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-07-23 12:10+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../portal/my_odoo_portal.rst:6 +msgid "My Odoo Portal" +msgstr "Portale Odoo" + +#: ../../portal/my_odoo_portal.rst:8 +msgid "" +"In this section of the portal you will find all the communications between " +"you and Odoo, documents such Quotations, Sales Orders, Invoices and your " +"Subscriptions." +msgstr "" +"In questa sezione del portale saranno presenti tutte le comunicazioni " +"personali con Odoo, documenti come i preventivi, ordini di vendita, fatture " +"e iscrizioni." + +#: ../../portal/my_odoo_portal.rst:11 +msgid "" +"To access this section you have to log with your username and password to " +"`Odoo `__ . If you are already logged-in just " +"click on your name on the top-right corner and select \"My Account\"." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:20 +msgid "Quotations" +msgstr "Preventivi" + +#: ../../portal/my_odoo_portal.rst:22 +msgid "" +"Here you will find all the quotations sent to you by Odoo. For example, a " +"quotation can be generated for you after adding an Application or a User to " +"your database or if your contract has to be renewed." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:29 +msgid "" +"The *Valid Until* column shows until when the quotation is valid; after that" +" date the quotation will be \"Expired\". By clicking on the quotation you " +"will see all the details of the offer, the pricing and other useful " +"information." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:36 +msgid "" +"If you want to accept the quotation just click \"Accept & Pay\" and the " +"quote will get confirmed. If you don't want to accept it, or you need to ask" +" for some modifications, click on \"Ask Changes Reject\"." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:41 +msgid "Sales Orders" +msgstr "Ordini di vendita" + +#: ../../portal/my_odoo_portal.rst:43 +msgid "" +"All your purchases within Odoo such as Upsells, Themes, Applications, etc. " +"will be registered under this section." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:49 +msgid "" +"By clicking on the sale order you can review the details of the products " +"purchased and process the payment." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:53 +msgid "Invoices" +msgstr "Fatture" + +#: ../../portal/my_odoo_portal.rst:55 +msgid "" +"All the invoices of your subscription(s), or generated by a sales order, " +"will be shown in this section. The tag before the Amount Due will indicate " +"you if the invoice has been paid." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:62 +msgid "" +"Just click on the Invoice if you wish to see more information, pay the " +"invoice or download a PDF version of the document." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:66 +msgid "Tickets" +msgstr "Biglietti" + +#: ../../portal/my_odoo_portal.rst:68 +msgid "" +"When you submit a ticket through `Odoo Support " +"`__ a ticket will be created. Here you can find " +"all the tickets that you have opened, the conversation between you and our " +"Agents, the Status of the ticket and the ID (# Ref)." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:77 +msgid "Subscriptions" +msgstr "Iscrizioni" + +#: ../../portal/my_odoo_portal.rst:79 +msgid "" +"You can access to your Subscription with Odoo from this section. The first " +"page shows you the subscriptions that you have and their status." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:85 +msgid "" +"By clicking on the Subscription you will access to all the details regarding" +" your plan: this includes the number of applications purchased, the billing " +"information and the payment method." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:89 +msgid "" +"To change the payment method click on \"Change Payment Method\" and enter " +"the new credit card details." +msgstr "" +"Per cambiare il metodo di pagamento fare clic su \"Cambia metodo di " +"pagamento\" e inserire i dettagli della nuova carta di credito." + +#: ../../portal/my_odoo_portal.rst:95 +msgid "" +"If you want to remove the credit cards saved, you can do it by clicking on " +"\"Manage you payment methods\" at the bottom of the page. Click then on " +"\"Delete\" to delete the payment method." +msgstr "" +"Per rimuovere le carte di credito salvate, fare clic su \"Gestire i metodi " +"di pagamento\" in fondo alla pagina. Quindi fare clic su «Elimina» per " +"eliminare il metodo di pagamento." + +#: ../../portal/my_odoo_portal.rst:102 +msgid "" +"At the date of the next invoice, if there is no payment information provided" +" or if your credit card has expired, the status of your subscription will " +"change to \"To Renew\". You will then have 7 days to provide a valid method" +" of payment. After this delay, the subscription will be closed and you will " +"no longer be able to access the database." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:109 +msgid "Success Packs" +msgstr "" + +#: ../../portal/my_odoo_portal.rst:110 +msgid "" +"With a Success Pack/Partner Success Pack, you are assigned an expert to " +"provide unique personalized assistance to help you customize your solution " +"and optimize your workflows as part of your initial implementation. These " +"hours never expire allowing you to utilize them whenever you need support." +msgstr "" + +#: ../../portal/my_odoo_portal.rst:116 +msgid "" +"If you need information about how to manage your database see " +":ref:`db_online`" +msgstr "" +"Per informazioni su come gestire il database consultare :ref:`db_online`" diff --git a/locale/it/LC_MESSAGES/practical.po b/locale/it/LC_MESSAGES/practical.po new file mode 100644 index 000000000..6df798dac --- /dev/null +++ b/locale/it/LC_MESSAGES/practical.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Federico Castellano , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Federico Castellano , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../practical.rst:3 +msgid "Practical Information" +msgstr "Informazioni pratiche" diff --git a/locale/it/LC_MESSAGES/project.po b/locale/it/LC_MESSAGES/project.po new file mode 100644 index 000000000..d7e8ffa4b --- /dev/null +++ b/locale/it/LC_MESSAGES/project.po @@ -0,0 +1,1601 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Francesco Garganese , 2019 +# Paolo Valier, 2019 +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# Alessandro Forte , 2019 +# David Minneci , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: David Minneci , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../project.rst:5 +msgid "Project" +msgstr "Progetto" + +#: ../../project/advanced.rst:3 +msgid "Advanced" +msgstr "Avanzato" + +#: ../../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 "Panoramica" + +#: ../../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 "Modello e-mail" + +#: ../../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 "Rendicontazione" + +#: ../../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/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:24 +#: ../../project/configuration/time_record.rst:12 +#: ../../project/planning/assignments.rst:10 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../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:113 +#: ../../project/planning/assignments.rst:137 +msgid ":doc:`../configuration/setup`" +msgstr "" + +#: ../../project/advanced/so_to_task.rst:114 +msgid ":doc:`../../sales/invoicing/subscriptions`" +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 "Transcript" + +#: ../../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 "Responsabilità" + +#: ../../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 "Follower" + +#: ../../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 "Visualize a project's tasks" +msgstr "" + +#: ../../project/configuration/visualization.rst:5 +msgid "" +"In day to day business, your company might struggle due to the important " +"amount of tasks to fulfill. Those tasks already are complex enough. Having " +"to remember them all and follow up on them can be a burden. Luckily, Odoo " +"enables you to efficiently visualize and organize the different tasks you " +"have to cope with." +msgstr "" + +#: ../../project/configuration/visualization.rst:12 +msgid "Create a task" +msgstr "" + +#: ../../project/configuration/visualization.rst:14 +msgid "" +"While in the project app, select an existing project or create a new one." +msgstr "" + +#: ../../project/configuration/visualization.rst:17 +msgid "In the project, create a new task." +msgstr "" + +#: ../../project/configuration/visualization.rst:22 +msgid "" +"In that task you can then assigned it to the right person, add tags, a " +"deadline, descriptions… and anything else you might need for that task." +msgstr "" + +#: ../../project/configuration/visualization.rst:29 +msgid "View your tasks with the Kanban view" +msgstr "" + +#: ../../project/configuration/visualization.rst:31 +msgid "" +"Once you created several tasks, they can be managed and followed up thanks " +"to the Kanban view." +msgstr "" + +#: ../../project/configuration/visualization.rst:34 +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:38 +#: ../../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:45 +msgid "" +"You can also notify your colleagues about the status of a task right from " +"the Kanban view by using the little dot, it will notify follower of the task" +" and indicate if the task is ready." +msgstr "" + +#: ../../project/configuration/visualization.rst:53 +msgid "Sort tasks in your Kanban view" +msgstr "" + +#: ../../project/configuration/visualization.rst:55 +msgid "" +"Tasks are ordered by priority, which you can give by clicking on the star " +"next to the clock and then by sequence, meaning if you manually move them " +"using drag & drop, they will be in that order and finally by their ID linked" +" to their creation date." +msgstr "" + +#: ../../project/configuration/visualization.rst:63 +msgid "" +"Tasks that are past their deadline will appear in red in your Kanban view." +msgstr "" + +#: ../../project/configuration/visualization.rst:67 +msgid "" +"If you put a low priority task on top, when you go back to your dashboard " +"the next time, it will have moved back below the high priority tasks." +msgstr "" + +#: ../../project/configuration/visualization.rst:72 +msgid "Manage deadlines with the Calendar view" +msgstr "" + +#: ../../project/configuration/visualization.rst:74 +msgid "" +"You also have the option to switch from a Kanban view to a calendar view, " +"allowing you to see every deadline for every task that has a deadline set " +"easily in a single window." +msgstr "" + +#: ../../project/configuration/visualization.rst:78 +msgid "" +"Tasks are color coded to the employee they are assigned to and you can " +"filter deadlines by employees by selecting who's deadline you wish to see." +msgstr "" + +#: ../../project/configuration/visualization.rst:86 +#: ../../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:47 +msgid "Get an overview of activities with the kanban view" +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 "" +"Crea una colonna per fase nel tuo processo di lavoro. Per esempio, in un " +"progetto di sviluppo, fasi potrebbero essere: Caratteristiche Tecniche, " +"Sviluppo, Test, Fatto" + +#: ../../project/planning/assignments.rst:80 +msgid "Sort tasks by priority" +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:119 +msgid "Keep an eye on deadlines with the Calendar view" +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: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/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/it/LC_MESSAGES/purchase.po b/locale/it/LC_MESSAGES/purchase.po new file mode 100644 index 000000000..e830fabce --- /dev/null +++ b/locale/it/LC_MESSAGES/purchase.po @@ -0,0 +1,2011 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Francesco Garganese , 2019 +# Martin Trigaux, 2019 +# Paolo Valier, 2019 +# Tiziano Zambelli , 2019 +# maiolif , 2019 +# Léonie Bouchat , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 12.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-11-07 15:38+0100\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Léonie Bouchat , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../purchase.rst:5 +msgid "Purchase" +msgstr "Acquisto" + +#: ../../purchase/purchases.rst:3 +msgid "Purchases" +msgstr "Acquisti" + +#: ../../purchase/purchases/master.rst:3 +msgid "Master Data" +msgstr "Anagrafiche" + +#: ../../purchase/purchases/master/import.rst:3 +msgid "Import vendors pricelists" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:5 +msgid "" +"It is key for companies to be able to import vendors pricelists to stay up " +"to date on products pricing." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:9 +#: ../../purchase/purchases/master/uom.rst:22 +#: ../../purchase/purchases/rfq/3_way_matching.rst:18 +#: ../../purchase/purchases/rfq/analyze.rst:24 +#: ../../purchase/purchases/rfq/approvals.rst:9 +#: ../../purchase/purchases/rfq/bills.rst:31 +#: ../../purchase/purchases/rfq/create.rst:13 +#: ../../purchase/purchases/rfq/lock_orders.rst:9 +#: ../../purchase/purchases/rfq/reception.rst:14 +#: ../../purchase/purchases/rfq/warning.rst:14 +#: ../../purchase/purchases/tender/blanket_orders.rst:10 +#: ../../purchase/purchases/tender/call_for_tender.rst:9 +#: ../../purchase/replenishment/flows/dropshipping.rst:13 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../purchase/purchases/master/import.rst:11 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and tick the box in front of \"Vendor Pricelists\"." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:15 +msgid "Don't forget to save your settings in the top left corner." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:21 +msgid "Import a pricelist" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:23 +msgid "To import go to :menuselection:`Purchase --> Vendor Pricelists`" +msgstr "" + +#: ../../purchase/purchases/master/import.rst:25 +msgid "" +"Load your file, then you can check if everything is correct before clicking " +"import." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:28 +msgid "See below a template of the columns used." +msgstr "" + +#: ../../purchase/purchases/master/import.rst:33 +msgid "" +"`Template download " +"`__" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:3 +msgid "Set multiple vendors on a product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:5 +msgid "" +"If you find yourself with the need to buy from multiple vendors for one " +"product, Odoo can let you directly link them with a single product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:9 +msgid "Add vendors in a product" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:11 +msgid "" +"To use this feature, go to :menuselection:`Purchases --> Products`, then " +"select a product." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:14 +msgid "" +"From there you can add existing vendors to your product or create a new one " +"on the fly." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:17 +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:24 +msgid "Add price & quantity as well as a validity period" +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:26 +msgid "" +"When you're adding a vendor to a product, you're able to add the vendor " +"product name & code as well as set the minimal quantity, price and validity " +"period." +msgstr "" + +#: ../../purchase/purchases/master/suppliers.rst:34 +msgid "" +"This Odoo feature also works with variants of your products, such as one " +"t-shirt in different sizes!" +msgstr "" + +#: ../../purchase/purchases/master/uom.rst:3 +msgid "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 Quotation and Purchase Orders" +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:3 +msgid "Determine when to pay a vendor bill with 3-way matching" +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:5 +msgid "" +"In some industries, you may receive a bill from a vendor before receiving " +"the ordered products. However, you might not want to pay it until the " +"products have been received." +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:9 +msgid "" +"To define whether the vendor bill should be paid or not, you can use what we" +" call *3-way matching*. It refers to the comparaison of the information " +"appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*." +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:14 +msgid "" +"The 3-way matching helps you avoid paying incorrect or fraudulent vendor " +"bills." +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:20 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *3-way matching* feature" +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:27 +msgid "Should I pay the vendor bill?" +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:29 +msgid "" +"With the feature activated you will have a new *Should be paid* line appear " +"on the vendor bill under the *Other info* tab." +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:32 +msgid "" +"That way Odoo let's you easily know if you should pay the vendor bill or " +"not." +msgstr "" + +#: ../../purchase/purchases/rfq/3_way_matching.rst:39 +msgid "" +"The status is defined automatically by Odoo. However, if you want to define " +"this status manually, you can tick the box Force Status and then you will be" +" able to set manually whether the vendor bill should be paid or not." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:3 +msgid "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 +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**." +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:43 +msgid "Analyzing your vendors" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:46 +msgid "Generate flexible reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:48 +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:59 +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:66 +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:76 +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:80 +msgid "Customize reports" +msgstr "" + +#: ../../purchase/purchases/rfq/analyze.rst:82 +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:96 +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/approvals.rst:3 +msgid "Request managers approval for expensive orders" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:5 +msgid "" +"In case of expensive purchases you may want a manager approval to validate " +"the orders, Odoo let's you easily set that up." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:11 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *Order Approval* feature. From there you can " +"also set the minimum amount required to activate this feature." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:20 +msgid "Create a new Request for Quotation" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:22 +msgid "" +"While working on a new RfQ, if the order is made by a user and not a manager" +" and the amount of the order is above the minimum amount you specified, a " +"new *To Approve* status will be introduced in the process." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:31 +msgid "Approve the order" +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:33 +msgid "" +"If you are a purchase manager, you can now go to the purchase order and " +"approve the order if everything is alright with it. Giving you full control " +"of what your users can or can't do." +msgstr "" + +#: ../../purchase/purchases/rfq/approvals.rst:37 +msgid "Once approved, the purchase order follows the normal process." +msgstr "" + +#: ../../purchase/purchases/rfq/bills.rst:3 +msgid "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 "Quantità ordinate" + +#: ../../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 "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 "Cancel your Purchase Order" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:28 +msgid "Use case 1 : you didn't receive your goods yet" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:30 +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:36 +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:43 +msgid "Use case 2 : partially delivered goods" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:45 +msgid "" +"In this case, **2** of the **3 iPad Mini** arrived before you needed to " +"cancel the PO." +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:49 +msgid "Register good received and cancel backorder" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:51 +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:61 +msgid "To learn more, see :doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:63 +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:70 +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:78 +msgid "Create reverse transfer" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:80 +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:88 +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:94 +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:99 +#: ../../purchase/purchases/rfq/reception.rst:116 +msgid ":doc:`bills`" +msgstr "" + +#: ../../purchase/purchases/rfq/cancel.rst:100 +msgid ":doc:`reception`" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:3 +msgid "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:16 +msgid "Creating a Request for Quotation" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:18 +msgid "" +"In the Purchases module, open :menuselection:`Purchase --> Requests for " +"Quotation` and click on **Create**." +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:24 +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 "Receipt" +msgstr "Ricevuta" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoming Shipments" +msgstr "Spedizioni in Ingresso" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor" +msgstr "Fornitore" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "You can find a vendor by its Name, TIN, Email or Internal Reference." +msgstr "" +"È possibile trovare un fornitore per nome, codice fiscale, e-mail o " +"riferimento interno." + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Vendor Reference" +msgstr "Riferimento fornitore" + +#: ../../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 "" +"Riferimento all'ordine di vednita o all'offerta inviata dal Fornitore. E " +"utilizzato per controllare quando ricevi i prodotti ed è riportato " +"solitamente sul buono di consegna del fonitore" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Order Date" +msgstr "Data ordine" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Depicts the date where the Quotation should be validated and converted into " +"a purchase order." +msgstr "" +"Rappresenta la data di quando la quotazione sarà validata e convertita in un" +" ordine d'acquisto." + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Source Document" +msgstr "Documento origine" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"Reference of the document that generated this purchase order request (e.g. a" +" sales order)" +msgstr "" +"Riferimento al documento che ha creato questa richiesta di ordine di " +"acquisto (es. un ordine di vendita)" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Deliver To" +msgstr "Consegna a" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "This will determine operation type of incoming shipment" +msgstr "Questo determinerà il tipo di operazione dei ricevimenti" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Drop Ship Address" +msgstr "Indirizzo dropshipping" + +#: ../../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 "" +"Inserisci un indirizzo se vuoi spedire dal fornitore a cliente . Altrimenti " +", continua senza inserire l'indirizzo per consegnare alla tua azienda" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Destination Location Type" +msgstr "Tipo di Location di Destinazione" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Technical field used to display the Drop Ship Address" +msgstr "Campo tecnico utilizzato per visualizzare l'indirizzo Drop Ship" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "Incoterm" +msgstr "Termine di resa" + +#: ../../purchase/purchases/rfq/create.rst:0 +msgid "" +"International Commercial Terms are a series of predefined commercial terms " +"used in international transactions." +msgstr "" +"Gli Incoterm sono una serie di termini commerciali predefiniti usati nelle " +"transazioni internazionali" + +#: ../../purchase/purchases/rfq/create.rst:32 +msgid "View *Request for Quotation* in our Online Demonstration" +msgstr "" + +#: ../../purchase/purchases/rfq/create.rst:34 +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:48 +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:54 +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:59 +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:65 +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/dropshipping.rst:3 +msgid "Dropship products" +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:5 +msgid "" +"Dropshipping is a method in which the vendor does not keep products in stock" +" but instead transfers the products directly from the supplier to the " +"customer." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:10 +msgid "" +"You need the *Sales*, *Inventory* and *Purchases* modules for this feature " +"to work." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:14 +msgid "Activate the dropshipping feature" +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:16 +msgid "" +"Go to :menuselection:`Purchases --> Configuration --> Settings` and select " +"*Dropshipping*." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:22 +msgid "" +"A new route *Dropshipping* has been created. You can go on a product and " +"tick the dropshipping route. You also need to define to which vendor you " +"will buy the product. Now, each time this product will be sold, it will be " +"drop shipped." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:30 +msgid "" +"If you don't always dropship that product, you can go to " +":menuselection:`Sales --> Configuration --> Settings` and tick the box in " +"front of *Order-Specific Routes*." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:37 +msgid "" +"When you create a quotation or sales order, you can now decide, order line " +"per order line, which products should be drop shipped by selecting the " +"dropship route on the SO line." +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:45 +msgid "Drop ship a product" +msgstr "" + +#: ../../purchase/purchases/rfq/dropshipping.rst:47 +msgid "" +"Once a sale order with products to dropship is confirmed, a request for " +"quotation is generated by Odoo to buy the product to the vendor. If you " +"confirm that request for quotation into a purchase order, it will create a " +"transfer from your vendor directly to your customer. The products doesn't go" +" through your own stock." +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:3 +msgid "Lock a purchase order" +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:5 +msgid "" +"Once an order is confirmed, you can lock it preventing any further editing." +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:11 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *Lock Confirmed Orders* feature" +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:19 +msgid "Lock an order" +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:21 +msgid "" +"While working on a purchase order, when you confirm it, you can then lock " +"the order preventing any further modification on the document." +msgstr "" + +#: ../../purchase/purchases/rfq/lock_orders.rst:28 +msgid "You can unlock the document if you need to make additional changes" +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:3 +msgid "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 "Receive Products" +msgstr "Ricevi Prodotti" + +#: ../../purchase/purchases/rfq/reception.rst:69 +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:77 +msgid "" +"Click on this button and you access a list of all awaiting orders for this " +"warehouse." +msgstr "" + +#: ../../purchase/purchases/rfq/reception.rst:83 +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:92 +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:99 +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:103 +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:110 +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:117 +msgid ":doc:`cancel`" +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:3 +msgid "Raise warnings on purchase orders" +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:5 +msgid "" +"The *Warnings* feature allows you to raise warnings or blocking messages on " +"purchase orders based on a vendor or a product." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:8 +msgid "" +"For example, if you often have a problem with a vendor, you might want to " +"raise a warning when purchasing from that vendor. If a product is about to " +"be discontinued, you may want to raise a blocking message on the purchase " +"order." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:16 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *Warnings* feature." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:24 +msgid "Add a warning on a vendor" +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:26 +msgid "" +"When you activate the feature, you get a new option under the *Internal " +"Notes* tab on vendors. You can decide to write a simple warning or a " +"blocking message." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:34 +msgid "Add a warning on a product" +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:36 +msgid "" +"When you activate the feature, you get a new option under the *Purchase* tab" +" on the product page where you can add a warning or a blocking message." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:44 +msgid "Trying to buy with warnings or blocking messages" +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:46 +msgid "" +"If you try to validate a *Purchase Order* from a vendor or with a product " +"with a warning, a message will be raised. You can ignore it by clicking ok." +msgstr "" + +#: ../../purchase/purchases/rfq/warning.rst:53 +msgid "However, if it is a blocking message, you can not ignore it." +msgstr "" + +#: ../../purchase/purchases/tender.rst:3 +msgid "Purchase Agreements" +msgstr "Contratti di acquisto" + +#: ../../purchase/purchases/tender/blanket_orders.rst:3 +msgid "Manage Blanket Orders" +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:5 +msgid "" +"A Blanket Order is a purchase order which a customer places with its " +"supplier to allow multiple delivery dates over a period of time, often " +"negotiated to take advantage of predetermined pricing." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:12 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *Purchase Agreements* feature" +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:20 +msgid "Start a Blanket Order" +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:22 +#: ../../purchase/purchases/tender/call_for_tender.rst:21 +msgid "" +"To use this feature go to :menuselection:`Purchases --> Purchase " +"Agreements`." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:24 +msgid "" +"Once you are creating the purchase agreement, access the *Agreement Type* " +"drop down menu and select *Blanket Order*." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:30 +msgid "" +"You can then create your new blanket order, select your vendor, the " +"product(s), agreement deadline, ordering date and delivery date." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:33 +msgid "" +"When you are satisfied with your purchase agreement, confirm it. Its status " +"will change from*Draft* to *Ongoing* and a new *RFQs/Orders* will appear in " +"the top right corner of the document." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:41 +msgid "RFQ from the Blanket Order" +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:43 +msgid "" +"From your blanket order you can create a new quotation, Odoo will auto-fill " +"the document with the product(s) from your blanket order, you only have to " +"choose the quantity and confirm the order." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:47 +msgid "" +"When you will go back on the blanket order, you will see how many quantities" +" you have already ordered from your blanket order." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:51 +msgid "Vendors prices on your product" +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:53 +msgid "" +"When a blanket order is validated, a new vendor line is added in your " +"product. You can see which one are linked to a blanket order and give " +"priority to the ones you want with the arrows on the left of the vendor " +"name." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:58 +msgid "" +"Thanks to this, a blanket order can be used for automated replenishment " +"(using *reordering rules* or *made to order* configuration)." +msgstr "" + +#: ../../purchase/purchases/tender/blanket_orders.rst:65 +msgid "" +"You can also create a *Request for Quotation* from the classic RFQ Menu and " +"link them with an existing *Blanket Order*" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:3 +msgid "Manage Call for Tender" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:5 +msgid "" +"A Call for Tender is a special procedure to request offers from multiple " +"vendors to obtain the most interesting price." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:11 +msgid "" +"For this feature to work, go to :menuselection:`Purchases --> Configuration " +"--> Settings` and activate the *Purchase Agreements* feature." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:19 +msgid "Create a Call for Tender" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:23 +msgid "" +"Create a new purchase agreement, access the *Agreement Type* drop down menu " +"and select *Call for Tender*." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:26 +msgid "" +"When you are satisfied with your purchase agreement, confirm it will move " +"from *Draft* to *Confirmed* and a new *RFQs/Orders* appeared in the top " +"right corner of the document." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:34 +msgid "Request new quotations from the Call for Tender" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:36 +msgid "" +"From the Call for Tender, Odoo will auto-fill the RFQ with the product(s) " +"from your Call for Tender." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:40 +msgid "Select the best offer" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:42 +msgid "" +"The various RFQs and orders linked to the Call for Tenders will be under the" +" *RFQs/Orders* button where you can select and confirm the best offer." +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:50 +msgid "Close the Call for Tender" +msgstr "" + +#: ../../purchase/purchases/tender/call_for_tender.rst:52 +msgid "Once you're done with your *Call for Tender* don't forget to close it." +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 "Schedule your receipts and deliveries" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:5 +msgid "" +"To manage your supply chain scheduling, you will need to use Odoo *Lead " +"Times*." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:8 +msgid "" +"*Lead Times* are the expected times needed to receive, deliver or " +"manufacture products." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:12 +msgid "Configure Lead Times" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:15 +msgid "Vendor Lead Time" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:17 +msgid "" +"The vendor lead time is the time needed by your vendor to deliver the " +"product to you." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:20 +msgid "" +"To configure your vendor lead times, go to a product page, under the " +"purchase tab, click on a *Vendor* once there you can change the delivery " +"lead time for that Vendor & Product." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:28 +msgid "Customer Lead Time" +msgstr "Tempi di consegna Cliente" + +#: ../../purchase/replenishment/flows/compute_date.rst:30 +msgid "" +"The customer lead time, on the other hand, is the time you need to deliver " +"the product to your customer." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:33 +msgid "" +"To configure your customer lead time open a product and go under the " +"*Inventory* tab. You can then add how many days you need." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:40 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:42 +msgid "" +"The manufacturing lead time is the time you need to manufacture the product." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:45 +msgid "" +"To configure your manufacturing lead time open a product and go under the " +"*Inventory* tab. You can then add how many days you need." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:52 +msgid "Configure Security Lead Times" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:54 +msgid "" +"Odoo also lets you configure *Security Days* allowing you to cope with " +"potential delays along the supply chain and make sure you meet your " +"engagements." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:58 +msgid "" +"The easiest way is to go to *Settings* from any module and type **Lead " +"Time** in the search bar. From there, tick each box and configure your " +"various *Security Lead Time* for your needs." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:65 +msgid "" +"Alternatively, you can go in the settings of the *Inventory* module and " +"*Manufacturing* module to configure those settings." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:69 +msgid "Lead & security times in a use case" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:71 +msgid "" +"For example you sell a car today (January 1st), that is purchased on order, " +"and you promise to deliver your customer within 20 days (January 20). Here " +"is your product’s configuration:" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:75 +msgid "Security lead time for sales : 1 day" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:77 +msgid "Security lead time for purchase : 1 day" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:79 +msgid "Vendor delivery lead time : 9 days" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:81 +msgid "" +"In such a scenario, the scheduler will trigger the following events based on" +" your configuration." +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:84 +msgid "" +"January 19: scheduled delivery date (20th January - 1 day of security lead " +"time for Sales)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:87 +msgid "" +"January 18: scheduled receipt date (19th January - 1 day of security lead " +"time for Purchase)" +msgstr "" + +#: ../../purchase/replenishment/flows/compute_date.rst:90 +msgid "" +"January 10: order date = deadline to order from your vendor (19th January - " +"9 days of vendor lead time)" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:3 +msgid "Setup drop-shipping" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:6 +#: ../../purchase/replenishment/multicompany/setup.rst:6 +msgid "Overview" +msgstr "Panoramica" + +#: ../../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 "Trigger purchase of products based on sales (Make to Order)" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:5 +msgid "" +"If you don't keep stock of your products, you may need to trigger purchase " +"orders on each sale you make." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:8 +msgid "" +"Thanks to being a fully integrated solution, Odoo lets you do that easily in" +" just one step." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:12 +msgid "Configure the product" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:14 +msgid "" +"Open a product form and, under the inventory tab, tick the routes *Buy* and " +"*Make To Order*." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:20 +msgid "Don't forget to also set a vendor under the *Purchase* tab." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:23 +msgid "" +"The *Inventory*, *Sales* and *Purchases* modules have to be installed in " +"Odoo for this feature to work." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:27 +msgid "Create a sales order using Buy & MTO" +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:29 +msgid "" +"Create a new sales order with your product. When you confirm the order, a " +"delivery order is created with the status *Waiting for another operation*." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:33 +msgid "" +"A new RfQ will automatically be created in your *Purchases* module. Note " +"that you can see for which SO this RfQ has been created thanks to the " +"*Source Document* field, visible on the RfQ." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:40 +msgid "" +"When you confirm the RfQ into a purchase order, a receipt is automatically " +"created and directly accessible from your purchase order with the use of the" +" *Shipment* button." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:47 +msgid "" +"You can validate the receipt of your products. When you will go back to the " +"delivery order, you will see that the products are now ready to be shipped." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:52 +msgid "" +"As long as your RfQ is not confirmed, Odoo will keep adding PO Lines " +"automatically under it." +msgstr "" + +#: ../../purchase/replenishment/flows/purchase_triggering.rst:57 +msgid ":doc:`../../../purchase/replenishment/flows/setup_stock_rule`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:3 +msgid "Don’t run out of stock thanks to Reordering Rules" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:5 +msgid "" +"To make sure you never run out of stock, you might want to define " +"*Reordering Rules* on products. Thanks to reordering rules, Odoo will help " +"you to replenish your stock when it reaches a minimum stock level." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:10 +msgid "Set a reordering rule" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:12 +msgid "Open a stockable product, you'll find the *Reordering Rules* tab." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:15 +msgid "" +"You can also access all your reordering rules from :menuselection:`Inventory" +" --> Master Data --> Reordering Rules`." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:21 +msgid "" +"Once in the next menu, you can create the reordering rules linked to your " +"product. From now on, every time this product reaches the minimum quantity " +"it will replenish your stock to your **maximum quantity**." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:29 +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:33 +msgid "See also: :doc:`../../../inventory/management/misc/schedulers`" +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:35 +msgid "" +"From now on, every time a product with a reordering rule reaches the minimum" +" stock, the system will automatically see how to fulfill that need based on " +"the product configuration (e.g create an RfQ, create an MO, etc.)." +msgstr "" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:41 +msgid "Troubleshooting" +msgstr "Risoluzione problemi" + +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:43 +msgid "" +"For your reordering rules to work, your product needs to be correctly " +"configured. If you are using *Buy* route, you need a vendor on the product. " +"If you are using *Manufacturing* route you will been a BoM on the product. " +"If the product is not fully configured or there is a mistake in your routes," +" a next activity will be logged on the product informing you there is an " +"issue with the configuration." +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 "" diff --git a/locale/it/LC_MESSAGES/recruitment.po b/locale/it/LC_MESSAGES/recruitment.po new file mode 100644 index 000000000..b95f2fc0f --- /dev/null +++ b/locale/it/LC_MESSAGES/recruitment.po @@ -0,0 +1,26 @@ +# 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. +# +# Translators: +# Sergio Zanchetta , 2019 +# +#, 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: 2018-10-19 08:15+0000\n" +"Last-Translator: Sergio Zanchetta , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../recruitment.rst:5 +msgid "Recruitment" +msgstr "Selezione del personale" diff --git a/locale/it/LC_MESSAGES/sales.po b/locale/it/LC_MESSAGES/sales.po new file mode 100644 index 000000000..4c874b356 --- /dev/null +++ b/locale/it/LC_MESSAGES/sales.po @@ -0,0 +1,1401 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Sergio Zanchetta , 2019 +# Léonie Bouchat , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"PO-Revision-Date: 2018-10-19 08:15+0000\n" +"Last-Translator: Léonie Bouchat , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../sales.rst:5 +msgid "Sales" +msgstr "Vendite" + +#: ../../sales/advanced.rst:3 +msgid "Advanced Topics" +msgstr "" + +#: ../../sales/advanced/portal.rst:3 +msgid "How to give portal access rights to my customers?" +msgstr "" + +#: ../../sales/advanced/portal.rst:6 +msgid "What is Portal access/Who is a portal user?" +msgstr "" + +#: ../../sales/advanced/portal.rst:8 +msgid "" +"A portal access is given to a user who has the necessity to have access to " +"Odoo instance, to view certain documents or information in the system." +msgstr "" + +#: ../../sales/advanced/portal.rst:12 +msgid "For Example, a long term client who needs to view online quotations." +msgstr "" + +#: ../../sales/advanced/portal.rst:14 +msgid "" +"A portal user has only read/view access. He or she will not be able to edit " +"any document in the system." +msgstr "" + +#: ../../sales/advanced/portal.rst:18 +msgid "How to give portal access to customers?" +msgstr "" + +#: ../../sales/advanced/portal.rst:21 +msgid "From Contacts Module" +msgstr "" + +#: ../../sales/advanced/portal.rst:23 +msgid "" +"From the main menu, select **Contacts** menu. If the contact is not yet " +"created in the system, click on the create button to create new contact. " +"Enter details of the contact and click \"save\"." +msgstr "" + +#: ../../sales/advanced/portal.rst:33 +msgid "" +"Choose a contact, click on the **Action** menu in the top-center of the " +"interface and from the drop down." +msgstr "" + +#: ../../sales/advanced/portal.rst:36 +msgid "Select **Portal Access Management**. A pop up window appears." +msgstr "" + +#: ../../sales/advanced/portal.rst:41 +msgid "" +"Enter the login **email ID**, check the box under **In Portal** and add the " +"content to be included in the email in the text field box below. Click on " +"**Apply** when you're done." +msgstr "" + +#: ../../sales/advanced/portal.rst:47 +msgid "" +"An email will be sent to the specified email address, indicating that the " +"contact is now a portal user of the respective instance." +msgstr "" + +#: ../../sales/ebay/manage.rst:3 +msgid "How to list a product?" +msgstr "" + +#: ../../sales/ebay/manage.rst:6 +msgid "Listing without variation" +msgstr "" + +#: ../../sales/ebay/manage.rst:8 +msgid "" +"In order to list a product, you need to check the **use eBay** field on a " +"product form. The eBay tab will be available." +msgstr "" + +#: ../../sales/ebay/manage.rst:14 +msgid "" +"When the **Use Stock Quantity** field is checked, the quantity sets on eBay " +"will be the Odoo **Forecast Quantity**." +msgstr "" + +#: ../../sales/ebay/manage.rst:17 +msgid "" +"The **Description Template** allows you to use templates for your listings. " +"The default template only use the **eBay Description** field of the product." +" You can use html inside the **Description Template** and in the **eBay " +"Description**." +msgstr "" + +#: ../../sales/ebay/manage.rst:21 +msgid "" +"To use pictures in your listing, you need to add them as **Attachments** on " +"the product template." +msgstr "" + +#: ../../sales/ebay/manage.rst:24 +msgid "Listing with variations" +msgstr "" + +#: ../../sales/ebay/manage.rst:26 +msgid "" +"When the **use eBay** on a product with variations is checked and with " +"**Fixed Price** as **Listing Type**, the eBay form is sligthly different. In" +" the variants array, you can choose which variant will be listed on eBay as " +"well as set the price and the quantity for each variant." +msgstr "" + +#: ../../sales/ebay/manage.rst:35 +msgid "Listing with item specifics" +msgstr "" + +#: ../../sales/ebay/manage.rst:37 +msgid "" +"In order to add item specifics, you should create a product attribute with " +"one value in the **Variants** tab on the product form." +msgstr "" + +#: ../../sales/ebay/manage.rst:44 +msgid "Product Identifiers" +msgstr "" + +#: ../../sales/ebay/manage.rst:46 +msgid "" +"Products identifiers such as EAN, UPC, Brand or MPN are required in most of " +"the eBay category. The module manages the EAN and UPC identifiers with the " +"**Barcode** field of the product variant. If the **Barcode** field is empty " +"or is value is not valid, the EAN and UPC values will be set as 'Does not " +"apply' as recommended by eBay. The Brand and MPN values are working as item " +"specifics and should be define in the **Variants** tab on the product form. " +"If theses values are not set, 'Does not apply' will be used for the eBay " +"listing." +msgstr "" + +#: ../../sales/ebay/setup.rst:3 +msgid "How to configure eBay in Odoo?" +msgstr "" + +#: ../../sales/ebay/setup.rst:6 +msgid "Create eBay tokens" +msgstr "" + +#: ../../sales/ebay/setup.rst:8 +msgid "" +"In order to create your tokens, you need to create a developer account on " +"the `developer portal `_. Once you are " +"logged in, you can create **Sandbox Keys** and **Production Keys** by " +"clicking on the adequate buttons." +msgstr "" + +#: ../../sales/ebay/setup.rst:16 +msgid "" +"After the creation of the keys, you can get the user token. To do so, click " +"on the **Get a User Token** link in the bottom of the page. Go through the " +"form, log in with you eBay account and you will get the keys and token " +"needed to configure the module in Odoo." +msgstr "" + +#: ../../sales/ebay/setup.rst:22 +msgid "Set up tokens in Odoo?" +msgstr "" + +#: ../../sales/ebay/setup.rst:24 +msgid "" +"To set up the eBay integration, go to :menuselection:`Sales --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../sales/ebay/setup.rst:29 +msgid "" +"First choose if you want to use the production or the sandbox eBay Site. " +"Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert " +"Key**. Apply the changes." +msgstr "" + +#: ../../sales/ebay/setup.rst:33 +msgid "" +"Once the page is reloaded, you need to synchronize information from eBay. " +"Push on **Sync countries and currencies**, then you can fill in all the " +"other fields." +msgstr "" + +#: ../../sales/ebay/setup.rst:36 +msgid "" +"When all the fields are filled in, you can synchronize the categories and " +"the policies by clicking on the adequate buttons." +msgstr "" + +#: ../../sales/invoicing.rst:3 +msgid "Invoicing Method" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:3 +msgid "Request a down payment" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:5 +msgid "" +"A down payment is an initial, partial payment, with the agreement that the " +"rest will be paid later. For expensive orders or projects, it is a way to " +"protect yourself and make sure your customer is serious." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:10 +msgid "First time you request a down payment" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:12 +msgid "" +"When you confirm a sale, you can create an invoice and select a down payment" +" option. It can either be a fixed amount or a percentage of the total " +"amount." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:16 +msgid "" +"The first time you request a down payment you can select an income account " +"and a tax setting that will be reused for next down payments." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:22 +msgid "You will then see the invoice for the down payment." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:27 +msgid "" +"On the subsequent or final invoice, any prepayment made will be " +"automatically deducted." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:34 +msgid "Modify the income account and customer taxes" +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:36 +msgid "From the products list, search for *Down Payment*." +msgstr "" + +#: ../../sales/invoicing/down_payment.rst:41 +msgid "" +"You can then edit it, under the invoicing tab you will be able to change the" +" income account & customer taxes." +msgstr "" + +#: ../../sales/invoicing/expense.rst:3 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../sales/invoicing/expense.rst:5 +msgid "" +"It often happens that your employees have to spend their personal money " +"while working on a project for your client. Let's take the example of an " +"consultant paying an hotel to work on the site of your client. As a company," +" you would like to be able to invoice that expense to your client." +msgstr "" + +#: ../../sales/invoicing/expense.rst:12 +#: ../../sales/invoicing/time_materials.rst:64 +msgid "Expenses configuration" +msgstr "" + +#: ../../sales/invoicing/expense.rst:14 +#: ../../sales/invoicing/time_materials.rst:66 +msgid "" +"To track & invoice expenses, you will need the expenses app. Go to " +":menuselection:`Apps --> Expenses` to install it." +msgstr "" + +#: ../../sales/invoicing/expense.rst:17 +#: ../../sales/invoicing/time_materials.rst:69 +msgid "" +"You should also activate the analytic accounts feature to link expenses to " +"the sales order, to do so, go to :menuselection:`Invoicing --> Configuration" +" --> Settings` and activate *Analytic Accounting*." +msgstr "" + +#: ../../sales/invoicing/expense.rst:22 +#: ../../sales/invoicing/time_materials.rst:74 +msgid "Add expenses to your sales order" +msgstr "" + +#: ../../sales/invoicing/expense.rst:24 +#: ../../sales/invoicing/time_materials.rst:76 +msgid "" +"From the expense app, you or your consultant can create a new one, e.g. the " +"hotel for the first week on the site of your customer." +msgstr "" + +#: ../../sales/invoicing/expense.rst:27 +#: ../../sales/invoicing/time_materials.rst:79 +msgid "" +"You can then enter a relevant description and select an existing product or " +"create a new one from right there." +msgstr "" + +#: ../../sales/invoicing/expense.rst:33 +#: ../../sales/invoicing/time_materials.rst:85 +msgid "Here, we are creating a *Hotel* product:" +msgstr "" + +#: ../../sales/invoicing/expense.rst:38 +msgid "" +"Under the invoicing tab, select *Delivered quantities* and either *At cost* " +"or *Sales price* as well depending if you want to invoice the cost of your " +"expense or a previously agreed on sales price." +msgstr "" + +#: ../../sales/invoicing/expense.rst:45 +#: ../../sales/invoicing/time_materials.rst:97 +msgid "" +"To modify or create more products go to :menuselection:`Expenses --> " +"Configuration --> Expense products`." +msgstr "" + +#: ../../sales/invoicing/expense.rst:48 +#: ../../sales/invoicing/time_materials.rst:100 +msgid "" +"Back on the expense, add the original sale order in the expense to submit." +msgstr "" + +#: ../../sales/invoicing/expense.rst:54 +#: ../../sales/invoicing/time_materials.rst:106 +msgid "It can then be submitted to the manager, approved and finally posted." +msgstr "" + +#: ../../sales/invoicing/expense.rst:65 +#: ../../sales/invoicing/time_materials.rst:117 +msgid "It will then be in the sales order and ready to be invoiced." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:3 +msgid "Invoice based on delivered or ordered quantities" +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:5 +msgid "" +"Depending on your business and what you sell, you have two options for " +"invoicing:" +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:8 +msgid "" +"Invoice on ordered quantity: invoice the full order as soon as the sales " +"order is confirmed." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:10 +msgid "" +"Invoice on delivered quantity: invoice on what you delivered even if it's a " +"partial delivery." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:13 +msgid "Invoice on ordered quantity is the default mode." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:15 +msgid "" +"The benefits of using *Invoice on delivered quantity* depends on your type " +"of business, when you sell material, liquids or food in large quantities the" +" quantity might diverge a little bit and it is therefore better to invoice " +"the actual delivered quantity." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:21 +msgid "" +"You also have the ability to invoice manually, letting you control every " +"options: invoice ready to invoice lines, invoice a percentage (advance), " +"invoice a fixed advance." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:26 +msgid "Decide the policy on a product page" +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:28 +msgid "" +"From any products page, under the invoicing tab you will find the invoicing " +"policy and select the one you want." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:35 +msgid "Send the invoice" +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:37 +msgid "" +"Once you confirm the sale, you can see your delivered and invoiced " +"quantities." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:43 +msgid "" +"If you set it in ordered quantities, you can invoice as soon as the sale is " +"confirmed. If however you selected delivered quantities, you will first have" +" to validate the delivery." +msgstr "" + +#: ../../sales/invoicing/invoicing_policy.rst:47 +msgid "" +"Once the products are delivered, you can invoice your customer. Odoo will " +"automatically add the quantities to invoiced based on how many you delivered" +" if you did a partial delivery." +msgstr "" + +#: ../../sales/invoicing/milestone.rst:3 +msgid "Invoice project milestones" +msgstr "" + +#: ../../sales/invoicing/milestone.rst:5 +msgid "" +"Milestone invoicing can be used for expensive or large-scale projects, with " +"each milestone representing a clear sequence of work that will incrementally" +" build up to the completion of the contract. This invoicing method is " +"comfortable both for the company which is ensured to get a steady cash flow " +"throughout the project lifetime and for the client who can monitor the " +"project's progress and pay in several installments." +msgstr "" + +#: ../../sales/invoicing/milestone.rst:13 +msgid "Create milestone products" +msgstr "" + +#: ../../sales/invoicing/milestone.rst:15 +msgid "" +"In Odoo, each milestone of your project is considered as a product. To " +"configure products to work this way, go to any product form." +msgstr "" + +#: ../../sales/invoicing/milestone.rst:18 +msgid "" +"You have to set the product type as *Service* under general information and " +"select *Milestones* in the sales tab." +msgstr "" + +#: ../../sales/invoicing/milestone.rst:25 +msgid "Invoice milestones" +msgstr "" + +#: ../../sales/invoicing/milestone.rst:27 +msgid "" +"From the sales order, you can manually edit the quantity delivered as you " +"complete a milestone." +msgstr "" + +#: ../../sales/invoicing/milestone.rst:33 +msgid "You can then invoice that first milestone." +msgstr "" + +#: ../../sales/invoicing/proforma.rst:3 ../../sales/invoicing/proforma.rst:22 +msgid "Send a pro-forma invoice" +msgstr "" + +#: ../../sales/invoicing/proforma.rst:5 +msgid "" +"A pro-forma invoice is an abridged or estimated invoice in advance of a " +"delivery of goods. It notes the kind and quantity of goods, their value, and" +" other important information such as weight and transportation charges. Pro-" +"forma invoices are commonly used as preliminary invoices with a quotation, " +"or for customs purposes in importation. They differ from a normal invoice in" +" not being a demand or request for payment." +msgstr "" + +#: ../../sales/invoicing/proforma.rst:13 +#: ../../sales/send_quotations/different_addresses.rst:10 +msgid "Activate the feature" +msgstr "" + +#: ../../sales/invoicing/proforma.rst:15 +msgid "" +"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the" +" *Pro-Forma Invoice* feature." +msgstr "" + +#: ../../sales/invoicing/proforma.rst:24 +msgid "" +"From any quotation or sales order, you know have an option to send a pro-" +"forma invoice." +msgstr "" + +#: ../../sales/invoicing/proforma.rst:30 +msgid "" +"When you click on send, Odoo will send an email with the pro-forma invoice " +"in attachment." +msgstr "" + +#: ../../sales/invoicing/subscriptions.rst:3 +msgid "Sell subscriptions" +msgstr "" + +#: ../../sales/invoicing/subscriptions.rst:5 +msgid "" +"Selling subscription products will give you predictable revenue, making " +"planning ahead much easier." +msgstr "" + +#: ../../sales/invoicing/subscriptions.rst:9 +msgid "Make a subscription from a sales order" +msgstr "" + +#: ../../sales/invoicing/subscriptions.rst:11 +msgid "" +"From the sales app, create a quotation to the desired customer, and select " +"the subscription product your previously created." +msgstr "" + +#: ../../sales/invoicing/subscriptions.rst:14 +msgid "" +"When you confirm the sale the subscription will be created automatically. " +"You will see a direct link from the sales order to the Subscription in the " +"upper right corner." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:3 +msgid "Invoice based on time and materials" +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:5 +msgid "" +"Time and Materials is generally used in projects in which it is not possible" +" to accurately estimate the size of the project, or when it is expected that" +" the project requirements would most likely change." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:9 +msgid "" +"This is opposed to a fixed-price contract in which the owner agrees to pay " +"the contractor a lump sum for the fulfillment of the contract no matter what" +" the contractors pay their employees, sub-contractors, and suppliers." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:14 +msgid "" +"For this documentation I will use the example of a consultant, you will need" +" to invoice their time, their various expenses (transport, lodging, ...) and" +" purchases." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:19 +msgid "Invoice time configuration" +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:21 +msgid "" +"To keep track of progress in the project, you will need the *Project* app. " +"Go to :menuselection:`Apps --> Project` to install it." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:24 +msgid "" +"In *Project* you will use timesheets, to do so go to :menuselection:`Project" +" --> Configuration --> Settings` and activate the *Timesheets* feature." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:32 +msgid "Invoice your time spent" +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:34 +msgid "" +"From a product page set as a service, you will find two options under the " +"invoicing tab, select both *Timesheets on tasks* and *Create a task in a new" +" project*." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:41 +msgid "You could also add the task to an existing project." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:43 +msgid "" +"Once confirming a sales order, you will now see two new buttons, one for the" +" project overview and one for the current task." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:49 +msgid "" +"You will directly be in the task if you click on it, you can also access it " +"from the *Project* app." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:52 +msgid "" +"Under timesheets, you can assign who works on it. You can or they can add " +"how many hours they worked on the project so far." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:58 +msgid "From the sales order, you can then invoice those hours." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:90 +msgid "" +"under the invoicing tab, select *Delivered quantities* and either *At cost* " +"or *Sales price* as well depending if you want to invoice the cost of your " +"expense or a previously agreed on sales price." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:120 +msgid "Invoice purchases" +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:122 +msgid "" +"The last thing you might need to add to the sale order is purchases made for" +" it." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:125 +msgid "" +"You will need the *Purchase Analytics* feature, to activate it, go to " +":menuselection:`Invoicing --> Configuration --> Settings` and select " +"*Purchase Analytics*." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:129 +msgid "" +"While making the purchase order don't forget to add the right analytic " +"account." +msgstr "" + +#: ../../sales/invoicing/time_materials.rst:135 +msgid "" +"Once the PO is confirmed and received, you can create the vendor bill, this " +"will automatically add it to the SO where you can invoice it." +msgstr "" + +#: ../../sales/products_prices.rst:3 +msgid "Products & Prices" +msgstr "" + +#: ../../sales/products_prices/prices.rst:3 +msgid "Manage your pricing" +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:3 +msgid "How to sell in foreign currencies" +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:5 +msgid "Pricelists can also be used to manage prices in foreign currencies." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:7 +msgid "" +"Check *Allow multi currencies* in :menuselection:`Invoicing/Accounting --> " +"Settings`. As admin, you need *Adviser* access rights on " +"Invoicing/Accounting apps." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:10 +msgid "" +"Create one pricelist per currency. A new *Currency* field shows up in " +"pricelist setup form." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:13 +msgid "" +"To activate a new currency, go to :menuselection:`Accounting --> " +"Configuration --> Currencies`, select it in the list and press *Activate* in" +" the top-right corner. Now it will show up in currencies drop-down lists." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:17 +msgid "Prices in foreign currencies can be defined in two fashions." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:20 +msgid "Automatic conversion from public price" +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:22 +msgid "" +"The public price is in your company's main currency (see " +":menuselection:`Accounting --> Settings`) and is set in product detail form." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:28 +msgid "" +"The conversion rates can be found in :menuselection:`Accounting --> " +"Configuration --> Currencies`. They can be updated from Yahoo or the " +"European Central Bank at your convenience: manually, daily, weekly, etc. See" +" :menuselection:`Accounting --> Settings`." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:40 +msgid "Set your own prices" +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:42 +msgid "" +"This is advised if you don't want your pricing to change along with currency" +" rates." +msgstr "" + +#: ../../sales/products_prices/prices/currencies.rst:49 +msgid ":doc:`pricing`" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:3 +msgid "How to adapt your prices to your customers and apply discounts" +msgstr "" + +#: ../../sales/products_prices/prices/pricing.rst:5 +msgid "" +"Odoo has a powerful pricelist feature to support a pricing strategy tailored" +" to your business. A pricelist is a list of prices or price rules that Odoo " +"searches to determine the suggested price. You can set several critarias to " +"use a specific price: periods, min. sold quantity (meet a minimum order " +"quantity and get a price break), etc. 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 "Applicazione delle imposte" + +#: ../../sales/sale_ebay.rst:3 +msgid "eBay" +msgstr "eBay" + +#: ../../sales/send_quotations.rst:3 +msgid "Send Quotations" +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:3 +msgid "Stimulate customers with quotations deadline" +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:5 +msgid "" +"As you send quotations, it is important to set a quotation deadline; Both to" +" entice your customer into action with the fear of missing out on an offer " +"and to protect yourself. You don't want to have to fulfill an order at a " +"price that is no longer cost effective for you." +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:11 +msgid "Set a deadline" +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:13 +msgid "On every quotation or sales order you can add an *Expiration Date*." +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:19 +msgid "Use deadline in templates" +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:21 +msgid "" +"You can also set a default deadline in a *Quotation Template*. Each time " +"that template is used in a quotation, that deadline is applied. You can find" +" more info about quotation templates `here " +"`_." +msgstr "" + +#: ../../sales/send_quotations/deadline.rst:29 +msgid "On your customer side, they will see this." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:3 +msgid "Deliver and invoice to different addresses" +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:5 +msgid "" +"In Odoo you can configure different addresses for delivery and invoicing. " +"This is key, not everyone will have the same delivery location as their " +"invoice location." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:12 +msgid "" +"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the" +" *Customer Addresses* feature." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:19 +msgid "Add different addresses to a quotation or sales order" +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:21 +msgid "" +"If you select a customer with an invoice and delivery address set, Odoo will" +" automatically use those. If there's only one, Odoo will use that one for " +"both but you can, of course, change it instantly and create a new one right " +"from the quotation or sales order." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:30 +msgid "Add invoice & delivery addresses to a customer" +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:32 +msgid "" +"If you want to add them to a customer before a quotation or sales order, " +"they are added to the customer form. Go to any customers form under " +":menuselection:`SALES --> Orders --> Customers`." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:36 +msgid "From there you can add new addresses to the customer." +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:42 +msgid "Various addresses on the quotation / sales orders" +msgstr "" + +#: ../../sales/send_quotations/different_addresses.rst:44 +msgid "" +"These two addresses will then be used on the quotation or sales order you " +"send by email or print." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:3 +msgid "Get paid to confirm an order" +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:5 +msgid "" +"You can use online payments to get orders automatically confirmed. Saving " +"the time of both your customers and yourself." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:9 +msgid "Activate online payment" +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:11 +#: ../../sales/send_quotations/get_signature_to_validate.rst:12 +msgid "" +"Go to :menuselection:`SALES --> Configuration --> Settings` and activate the" +" *Online Signature & Payment* feature." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:17 +msgid "" +"Once in the *Payment Acquirers* menu you can select and configure your " +"acquirers of choice." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:20 +msgid "" +"You can find various documentation about how to be paid with payment " +"acquirers such as `Paypal <../../ecommerce/shopper_experience/paypal>`_, " +"`Authorize.Net (pay by credit card) " +"<../../ecommerce/shopper_experience/authorize>`_, and others under the " +"`eCommerce documentation <../../ecommerce>`_." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:31 +msgid "" +"If you are using `quotation templates <../quote_template>`_, you can also " +"pick a default setting for each template." +msgstr "" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:36 +msgid "Register a payment" +msgstr "Registrare un pagamento" + +#: ../../sales/send_quotations/get_paid_to_validate.rst:38 +msgid "" +"From the quotation email you sent, your customer will be able to pay online." +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:3 +msgid "Get a signature to confirm an order" +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:5 +msgid "" +"You can use online signature to get orders automatically confirmed. Both you" +" and your customer will save time by using this feature compared to a " +"traditional process." +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:10 +msgid "Activate online signature" +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:19 +msgid "" +"If you are using `quotation templates `_, you can also pick a " +"default setting for each template." +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:23 +msgid "Validate an order with a signature" +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:25 +msgid "" +"When you sent a quotation to your client, they can accept it and sign online" +" instantly." +msgstr "" + +#: ../../sales/send_quotations/get_signature_to_validate.rst:30 +msgid "Once signed the quotation will be confirmed and delivery will start." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:3 +msgid "Increase your sales with suggested products" +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:5 +msgid "" +"The use of suggested products is an attempt to offer related and useful " +"products to your client. For instance, a client purchasing a cellphone could" +" be shown accessories like a protective case, a screen cover, and headset." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:11 +msgid "Add suggested products to your quotation templates" +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:13 +msgid "Suggested products can be set on *Quotation Templates*." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:17 +msgid "" +"Once on a template, you can see a *Suggested Products* tab where you can add" +" related products or services." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:23 +msgid "You can also add or modify suggested products on the quotation." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:26 +msgid "Add suggested products to the quotation" +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:28 +msgid "" +"When opening the quotation from the received email, the customer can add the" +" suggested products to the order." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:37 +msgid "" +"The product(s) will be instantly added to their quotation when clicking on " +"any of the little carts." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:43 +msgid "" +"Depending on your confirmation process, they can either digitally sign or " +"pay to confirm the quotation." +msgstr "" + +#: ../../sales/send_quotations/optional_items.rst:46 +msgid "" +"Each move done by the customer to the quotation will be tracked in the sales" +" order, letting the salesperson see it." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:3 +msgid "Use quotation templates" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:5 +msgid "" +"If you often sell the same products or services, you can save a lot of time " +"by creating custom quotation templates. By using a template you can send a " +"complete quotation in no time." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:10 +msgid "Configuration" +msgstr "Configurazione" + +#: ../../sales/send_quotations/quote_template.rst:12 +msgid "" +"For this feature to work, go to :menuselection:`Sales --> Configuration --> " +"Settings` and activate *Quotations Templates*." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:19 +msgid "Create your first template" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:21 +msgid "" +"You will find the templates menu under :menuselection:`Sales --> " +"Configuration`." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:24 +msgid "" +"You can then create or edit an existing one. Once named, you will be able to" +" select the product(s) and their quantity as well as the expiration time for" +" the quotation." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:31 +msgid "" +"On each template, you can also specify discounts if the option is activated " +"in the *Sales* settings. The base price is set in the product configuration " +"and can be alterated by customer pricelists." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:38 +msgid "Edit your template" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:40 +msgid "" +"You can edit the customer interface of the template that they see to accept " +"or pay the quotation. This lets you describe your company, services and " +"products. When you click on *Edit Template* you will be brought to the " +"quotation editor." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:51 +msgid "" +"This lets you edit the description content thanks to drag & drop of building" +" blocks. To describe your products add a content block in the zone dedicated" +" to each product." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:59 +msgid "" +"The description set for the products will be used in all quotations " +"templates containing those products." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:63 +msgid "Use a quotation template" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:65 +msgid "When creating a quotation, you can select a template." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:70 +msgid "Each product in that template will be added to your quotation." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:73 +msgid "" +"You can select a template to be suggested by default in the *Sales* " +"settings." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:77 +msgid "Confirm the quotation" +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:79 +msgid "" +"Templates also ease the confirmation process for customers with a digital " +"signature or online payment. You can select that in the template itself." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:86 +msgid "Every quotation will now have this setting added to it." +msgstr "" + +#: ../../sales/send_quotations/quote_template.rst:88 +msgid "" +"Of course you can still change it and make it specific for each quotation." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:3 +msgid "Add terms & conditions on orders" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:5 +msgid "" +"Specifying Terms and Conditions is essential to ensure a good relationship " +"between customers and sellers. Every seller has to declare all the formal " +"information which include products and company policy; allowing the customer" +" to read all those terms everything before committing to anything." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:11 +msgid "" +"Odoo lets you easily include your default terms and conditions on every " +"quotation, sales order and invoice." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:15 +msgid "Set up your default terms and conditions" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:17 +msgid "" +"Go to :menuselection:`SALES --> Configuration --> Settings` and activate " +"*Default Terms & Conditions*." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:23 +msgid "" +"In that box you can add your default terms & conditions. They will then " +"appear on every quotation, SO and invoice." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:33 +msgid "Set up more detailed terms & conditions" +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:35 +msgid "" +"A good idea is to share more detailed or structured conditions is to publish" +" on the web and to refer to that link in the terms & conditions of Odoo." +msgstr "" + +#: ../../sales/send_quotations/terms_and_conditions.rst:39 +msgid "" +"You can also attach an external document with more detailed and structured " +"conditions to the email you send to the customer. You can even set a default" +" attachment for all quotation emails sent." +msgstr "" diff --git a/locale/it/LC_MESSAGES/website.po b/locale/it/LC_MESSAGES/website.po new file mode 100644 index 000000000..b8acf5893 --- /dev/null +++ b/locale/it/LC_MESSAGES/website.po @@ -0,0 +1,1390 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2015-TODAY, Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +# Translators: +# Paolo Valier, 2019 +# Federico Castellano , 2019 +# Sergio Zanchetta , 2019 +# Martin Trigaux, 2019 +# Simone Bernini , 2019 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 11.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-07-23 12:10+0200\n" +"PO-Revision-Date: 2018-10-19 08:16+0000\n" +"Last-Translator: Simone Bernini , 2019\n" +"Language-Team: Italian (https://www.transifex.com/odoo/teams/41243/it/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: it\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../website.rst:5 +msgid "Website" +msgstr "Sito web" + +#: ../../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 traffic from your Odoo Dashboard" +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:5 +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 +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. Odoo). This project is needed " +"to store your API credentials." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:25 +msgid "Enable the API." +msgstr "" + +#: ../../website/optimize/google_analytics_dashboard.rst:30 +msgid "Create credentials to use in Odoo." +msgstr "Crea le credenziali da usare in Odoo." + +#: ../../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: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:56 +msgid "" +"Finally you are provided with your Client ID. Copy and paste it in Odoo." +msgstr "" + +#: ../../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:67 +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 "Introduzione" + +#: ../../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 "Immagini" + +#: ../../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 "" +"The HTML pages can be compressed, but this is usually handled by your web " +"server (NGINX or Apache)." +msgstr "" + +#: ../../website/optimize/seo.rst:237 +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:241 +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:245 +msgid "``

My Text

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

My Text

``" +msgstr "" + +#: ../../website/optimize/seo.rst:253 +msgid "Responsive Design" +msgstr "" + +#: ../../website/optimize/seo.rst:255 +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:263 +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:270 +msgid "Browser caching" +msgstr "" + +#: ../../website/optimize/seo.rst:272 +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:279 +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:287 +msgid "Scalability" +msgstr "" + +#: ../../website/optimize/seo.rst:289 +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:294 +msgid "" +"`*https://www.odoo.com/slides/slide/197* `__" +msgstr "" + +#: ../../website/optimize/seo.rst:296 +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:303 +msgid "URLs handling" +msgstr "" + +#: ../../website/optimize/seo.rst:306 +msgid "URLs Structure" +msgstr "" + +#: ../../website/optimize/seo.rst:308 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../website/optimize/seo.rst:310 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../website/optimize/seo.rst:312 +msgid "With the following components:" +msgstr "" + +#: ../../website/optimize/seo.rst:314 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../website/optimize/seo.rst:316 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../website/optimize/seo.rst:318 +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:324 +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:329 +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:336 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../website/optimize/seo.rst:338 +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:341 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../website/optimize/seo.rst:343 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../website/optimize/seo.rst:345 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../website/optimize/seo.rst:348 +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:352 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../website/optimize/seo.rst:355 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../website/optimize/seo.rst:357 +msgid "In the above example:" +msgstr "" + +#: ../../website/optimize/seo.rst:359 +msgid "Company News: is the title of the blog" +msgstr "" + +#: ../../website/optimize/seo.rst:361 +msgid "The Odoo Story: is the title of a specific blog post" +msgstr "" + +#: ../../website/optimize/seo.rst:363 +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:367 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../website/optimize/seo.rst:370 +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:375 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../website/optimize/seo.rst:377 +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:380 +msgid "Odoo will automatically update all its links to the new URL" +msgstr "" + +#: ../../website/optimize/seo.rst:382 +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:385 +msgid "As an example, this URL:" +msgstr "" + +#: ../../website/optimize/seo.rst:387 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:389 +msgid "Will automatically redirect to :" +msgstr "" + +#: ../../website/optimize/seo.rst:391 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../website/optimize/seo.rst:393 +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:399 +msgid "HTTPS" +msgstr "" + +#: ../../website/optimize/seo.rst:401 +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:407 +msgid "Links: nofollow strategy" +msgstr "" + +#: ../../website/optimize/seo.rst:409 +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:414 +msgid "Odoo follows the following strategies to manage links:" +msgstr "" + +#: ../../website/optimize/seo.rst:416 +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:420 +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:423 +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:428 +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:433 +msgid "Multi-language support" +msgstr "" + +#: ../../website/optimize/seo.rst:436 +msgid "Multi-language URLs" +msgstr "" + +#: ../../website/optimize/seo.rst:438 +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:441 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (English version = " +"default)" +msgstr "" + +#: ../../website/optimize/seo.rst:443 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../website/optimize/seo.rst:445 +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:450 +msgid "Language annotation" +msgstr "" + +#: ../../website/optimize/seo.rst:452 +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:457 +msgid "" +"" +msgstr "" + +#: ../../website/optimize/seo.rst:460 +msgid "With this approach:" +msgstr "" + +#: ../../website/optimize/seo.rst:462 +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:466 +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:471 +msgid "Language detection" +msgstr "" + +#: ../../website/optimize/seo.rst:473 +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:478 +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:482 +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:489 +msgid "Meta Tags" +msgstr "" + +#: ../../website/optimize/seo.rst:492 +msgid "Titles, Keywords and Description" +msgstr "" + +#: ../../website/optimize/seo.rst:494 +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:500 +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:509 +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:512 +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:521 +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:526 +msgid "Sitemap" +msgstr "" + +#: ../../website/optimize/seo.rst:528 +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:531 +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:537 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../website/optimize/seo.rst:539 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../website/optimize/seo.rst:541 +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:546 +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:553 +msgid "Structured Data Markup" +msgstr "" + +#: ../../website/optimize/seo.rst:555 +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:560 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../website/optimize/seo.rst:563 +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:573 +msgid "robots.txt" +msgstr "" + +#: ../../website/optimize/seo.rst:575 +msgid "" +"Odoo automatically creates a ``/robots.txt`` file for your website. Its " +"content is:" +msgstr "" + +#: ../../website/optimize/seo.rst:578 +msgid "User-agent: \\*" +msgstr "" + +#: ../../website/optimize/seo.rst:580 +msgid "Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../website/optimize/seo.rst:583 +msgid "Content is king" +msgstr "" + +#: ../../website/optimize/seo.rst:585 +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:588 +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:592 +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:596 +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:601 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../website/optimize/seo.rst:604 +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:609 +msgid "Social Features" +msgstr "" + +#: ../../website/optimize/seo.rst:612 +msgid "Twitter Cards" +msgstr "" + +#: ../../website/optimize/seo.rst:614 +msgid "" +"Odoo does not implement twitter cards yet. It will be done for the next " +"version." +msgstr "" + +#: ../../website/optimize/seo.rst:618 +msgid "Social Network" +msgstr "" + +#: ../../website/optimize/seo.rst:620 +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:625 +msgid "Test Your Website" +msgstr "" + +#: ../../website/optimize/seo.rst:627 +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 "Pubblicazione" + +#: ../../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 "Semplice e ovvio" + +#: ../../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 "Evita di usare caratteri speciali" + +#: ../../website/publish/domain_name.rst:19 +msgid "Aim for a .com and/or your country extension" +msgstr "Punta a un dominio .com e/o a un dominio della tua nazionalità" + +#: ../../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:45 +msgid "How to apply my domain name to my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:46 +msgid "" +"First let's authorize the redirection (yourcompany.com -> " +"yourcompany.odoo.com):" +msgstr "" + +#: ../../website/publish/domain_name.rst:48 +msgid "Open your Odoo.com account from your homepage." +msgstr "" + +#: ../../website/publish/domain_name.rst:53 +msgid "Go to the *Manage Databases* page." +msgstr "" + +#: ../../website/publish/domain_name.rst:58 +msgid "" +"Click on *Domains* to the right of the database you would like to redirect." +msgstr "" + +#: ../../website/publish/domain_name.rst:63 +msgid "" +"A database domain prompt will appear. Enter your custom domain (e.g. " +"www.yourcompany.com)." +msgstr "" + +#: ../../website/publish/domain_name.rst:70 +msgid "" +"We can now apply the redirection from your domain name's manager account:" +msgstr "" + +#: ../../website/publish/domain_name.rst:72 +msgid "Log in to your account and search for the DNS Zones management page." +msgstr "" + +#: ../../website/publish/domain_name.rst:74 +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:78 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../website/publish/domain_name.rst:80 +msgid "`GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:81 +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:82 +msgid "" +"`OVH " +"<https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__" +msgstr "" + +#: ../../website/publish/domain_name.rst:85 +msgid "How to enable SSL (HTTPS) for my Odoo instance" +msgstr "" + +#: ../../website/publish/domain_name.rst:87 +msgid "" +"To enable SSL, please use a third-party CDN service provider such as " +"CloudFlare.com." +msgstr "" + +#: ../../website/publish/domain_name.rst:93 +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 "Panoramica" + +#: ../../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 "Processa" + +#: ../../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 ""