diff --git a/.tx/config b/.tx/config index 11d36d778..404fc576a 100644 --- a/.tx/config +++ b/.tx/config @@ -2,117 +2,122 @@ host = https://www.transifex.com type = PO -[odoo-11-doc.accounting] +[odoo-12-doc.accounting] file_filter = locale//LC_MESSAGES/accounting.po source_file = locale/sources/accounting.pot source_lang = en -[odoo-11-doc.applications] +[odoo-12-doc.applications] file_filter = locale//LC_MESSAGES/applications.po source_file = locale/sources/applications.pot source_lang = en -[odoo-11-doc.crm] +[odoo-12-doc.crm] file_filter = locale//LC_MESSAGES/crm.po source_file = locale/sources/crm.pot source_lang = en -[odoo-11-doc.db_management] +[odoo-12-doc.db_management] file_filter = locale//LC_MESSAGES/db_management.po source_file = locale/sources/db_management.pot source_lang = en -[odoo-11-doc.discuss] +[odoo-12-doc.discuss] file_filter = locale//LC_MESSAGES/discuss.po source_file = locale/sources/discuss.pot source_lang = en -[odoo-11-doc.ecommerce] +[odoo-12-doc.ecommerce] file_filter = locale//LC_MESSAGES/ecommerce.po source_file = locale/sources/ecommerce.pot source_lang = en -[odoo-11-doc.expenses] +[odoo-12-doc.expenses] file_filter = locale//LC_MESSAGES/expenses.po source_file = locale/sources/expenses.pot source_lang = en -[odoo-11-doc.general] +[odoo-12-doc.general] file_filter = locale//LC_MESSAGES/general.po source_file = locale/sources/general.pot source_lang = en -[odoo-11-doc.getting_started] +[odoo-12-doc.getting_started] file_filter = locale//LC_MESSAGES/getting_started.po source_file = locale/sources/getting_started.pot source_lang = en -[odoo-11-doc.helpdesk] +[odoo-12-doc.helpdesk] file_filter = locale//LC_MESSAGES/helpdesk.po source_file = locale/sources/helpdesk.pot source_lang = en -[odoo-11-doc.index] +[odoo-12-doc.index] file_filter = locale//LC_MESSAGES/index.po source_file = locale/sources/index.pot source_lang = en -[odoo-11-doc.inventory] +[odoo-12-doc.inventory] file_filter = locale//LC_MESSAGES/inventory.po source_file = locale/sources/inventory.pot source_lang = en -[odoo-11-doc.iot] +[odoo-12-doc.iot] file_filter = locale//LC_MESSAGES/iot.po source_file = locale/sources/iot.pot source_lang = en -[odoo-11-doc.livechat] +[odoo-12-doc.livechat] file_filter = locale//LC_MESSAGES/livechat.po source_file = locale/sources/livechat.pot source_lang = en -[odoo-11-doc.manufacturing] +[odoo-12-doc.mobile] +file_filter = locale//LC_MESSAGES/mobile.po +source_file = locale/sources/mobile.pot +source_lang = en + +[odoo-12-doc.manufacturing] file_filter = locale//LC_MESSAGES/manufacturing.po source_file = locale/sources/manufacturing.pot source_lang = en -[odoo-11-doc.point_of_sale] +[odoo-12-doc.point_of_sale] file_filter = locale//LC_MESSAGES/point_of_sale.po source_file = locale/sources/point_of_sale.pot source_lang = en -[odoo-11-doc.portal] +[odoo-12-doc.portal] file_filter = locale//LC_MESSAGES/portal.po source_file = locale/sources/portal.pot source_lang = en -[odoo-11-doc.practical] +[odoo-12-doc.practical] file_filter = locale//LC_MESSAGES/practical.po source_file = locale/sources/practical.pot source_lang = en -[odoo-11-doc.project] +[odoo-12-doc.project] file_filter = locale//LC_MESSAGES/project.po source_file = locale/sources/project.pot source_lang = en -[odoo-11-doc.purchase] +[odoo-12-doc.purchase] file_filter = locale//LC_MESSAGES/purchase.po source_file = locale/sources/purchase.pot source_lang = en -[odoo-11-doc.recruitment] +[odoo-12-doc.recruitment] file_filter = locale//LC_MESSAGES/recruitment.po source_file = locale/sources/recruitment.pot source_lang = en -[odoo-11-doc.sales] +[odoo-12-doc.sales] file_filter = locale//LC_MESSAGES/sales.po source_file = locale/sources/sales.pot source_lang = en -[odoo-11-doc.website] +[odoo-12-doc.website] file_filter = locale//LC_MESSAGES/website.po source_file = locale/sources/website.pot source_lang = en diff --git a/locale/sources/accounting.pot b/locale/sources/accounting.pot index edd15a0d8..62fdcf2cd 100644 --- a/locale/sources/accounting.pot +++ b/locale/sources/accounting.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-07-27 11:08+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../accounting.rst:5 -#: ../../accounting/localizations/mexico.rst:281 +#: ../../accounting/localizations/mexico.rst:283 msgid "Accounting" msgstr "" @@ -56,6 +56,7 @@ msgstr "" #: ../../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 @@ -73,12 +74,10 @@ msgstr "" #: ../../accounting/payables/pay/sepa.rst:26 #: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:30 #: ../../accounting/payables/supplier_bills/manage.rst:31 -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:15 #: ../../accounting/receivables/customer_invoices/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/automated_followups.rst:31 #: ../../accounting/receivables/customer_payments/check.rst:39 #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 @@ -466,7 +465,7 @@ msgid "Once you filled in your credentials, your bank feeds will be synchronized msgstr "" #: ../../accounting/bank/feeds/synchronize.rst:73 -#: ../../accounting/localizations/mexico.rst:531 +#: ../../accounting/localizations/mexico.rst:533 msgid "FAQ" msgstr "" @@ -977,6 +976,16 @@ msgstr "" 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 +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Type" +msgstr "" + +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "Bank account type: Normal or IBAN. Inferred from the bank account number." +msgstr "" + #: ../../accounting/bank/setup/create_bank_account.rst:0 msgid "ABA/Routing" msgstr "" @@ -985,6 +994,14 @@ msgstr "" msgid "American Bankers Association Routing Number" msgstr "" +#: ../../accounting/bank/setup/create_bank_account.rst:0 +msgid "Account Holder Name" +msgstr "" + +#: ../../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 "" @@ -1141,11 +1158,6 @@ msgstr "" msgid "Set active to false to hide the Journal without removing it." msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -#: ../../accounting/others/configuration/account_type.rst:0 -msgid "Type" -msgstr "" - #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Select 'Sale' for customer invoices journals." msgstr "" @@ -1422,6 +1434,226 @@ msgstr "" msgid "Localizations" msgstr "" +#: ../../accounting/localizations/colombia.rst:3 +msgid "Colombia" +msgstr "" + +#: ../../accounting/localizations/colombia.rst:6 +#: ../../accounting/localizations/mexico.rst:14 +#: ../../accounting/others/taxes/B2B_B2C.rst:63 +msgid "Introduction" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" @@ -1718,11 +1950,6 @@ msgstr "" 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:14 -#: ../../accounting/others/taxes/B2B_B2C.rst:63 -msgid "Introduction" -msgstr "" - #: ../../accounting/localizations/mexico.rst:16 msgid "The mexican localization is a group of 3 modules:" msgstr "" @@ -1767,549 +1994,545 @@ msgstr "" 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:66 +#: ../../accounting/localizations/mexico.rst:68 msgid "3. Set you legal information in the company" msgstr "" -#: ../../accounting/localizations/mexico.rst:68 +#: ../../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:75 +#: ../../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 **ACO560518KW7**." msgstr "" -#: ../../accounting/localizations/mexico.rst:83 +#: ../../accounting/localizations/mexico.rst:85 msgid "4. Set the proper \"Fiscal Position\" on the partner that represent the company" msgstr "" -#: ../../accounting/localizations/mexico.rst:85 +#: ../../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:92 +#: ../../accounting/localizations/mexico.rst:94 msgid "5. Enabling CFDI Version 3.3" msgstr "" -#: ../../accounting/localizations/mexico.rst:95 +#: ../../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:100 +#: ../../accounting/localizations/mexico.rst:102 msgid "Enable debug mode:" msgstr "" -#: ../../accounting/localizations/mexico.rst:105 +#: ../../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:111 +#: ../../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:120 +#: ../../accounting/localizations/mexico.rst:122 msgid "Important considerations when yo enable the CFDI 3.3" msgstr "" -#: ../../accounting/localizations/mexico.rst:122 -#: ../../accounting/localizations/mexico.rst:611 +#: ../../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:130 +#: ../../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:137 +#: ../../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:144 +#: ../../accounting/localizations/mexico.rst:146 msgid "6. Configure the PAC in order to sign properly the invoices" msgstr "" -#: ../../accounting/localizations/mexico.rst:146 +#: ../../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:152 +#: ../../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:156 +#: ../../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:166 +#: ../../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:173 +#: ../../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:176 +#: ../../accounting/localizations/mexico.rst:178 msgid "`Certificate`_" msgstr "" -#: ../../accounting/localizations/mexico.rst:177 +#: ../../accounting/localizations/mexico.rst:179 msgid "`Certificate Key`_" msgstr "" -#: ../../accounting/localizations/mexico.rst:178 +#: ../../accounting/localizations/mexico.rst:180 msgid "**Password :** 12345678a" msgstr "" -#: ../../accounting/localizations/mexico.rst:181 +#: ../../accounting/localizations/mexico.rst:183 msgid "7. Configure the tag in sales taxes" msgstr "" -#: ../../accounting/localizations/mexico.rst:183 +#: ../../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:190 +#: ../../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:194 -msgid "Usage and testing" -msgstr "" - -#: ../../accounting/localizations/mexico.rst:197 +#: ../../accounting/localizations/mexico.rst:199 msgid "Invoicing" msgstr "" -#: ../../accounting/localizations/mexico.rst:199 +#: ../../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:202 +#: ../../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:209 +#: ../../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:216 +#: ../../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:223 +#: ../../accounting/localizations/mexico.rst:225 msgid "Cancelling invoices" msgstr "" -#: ../../accounting/localizations/mexico.rst:225 +#: ../../accounting/localizations/mexico.rst:227 msgid "The cancellation process is completely linked to the normal cancellation in Odoo." msgstr "" -#: ../../accounting/localizations/mexico.rst:227 +#: ../../accounting/localizations/mexico.rst:229 msgid "If the invoice is not paid." msgstr "" -#: ../../accounting/localizations/mexico.rst:229 +#: ../../accounting/localizations/mexico.rst:231 msgid "Go to to the customer invoice journal where the invoice belong to" msgstr "" -#: ../../accounting/localizations/mexico.rst:237 +#: ../../accounting/localizations/mexico.rst:239 msgid "Check the \"Allow cancelling entries\" field" msgstr "" -#: ../../accounting/localizations/mexico.rst:242 +#: ../../accounting/localizations/mexico.rst:244 msgid "Go back to your invoice and click on the button \"Cancel Invoice\"" msgstr "" -#: ../../accounting/localizations/mexico.rst:247 +#: ../../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:250 +#: ../../accounting/localizations/mexico.rst:252 msgid "**Legal considerations**" msgstr "" -#: ../../accounting/localizations/mexico.rst:252 +#: ../../accounting/localizations/mexico.rst:254 msgid "A cancelled invoice will automatically cancelled on the SAT." msgstr "" -#: ../../accounting/localizations/mexico.rst:253 +#: ../../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:256 +#: ../../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:261 +#: ../../accounting/localizations/mexico.rst:263 msgid "Payments (Just available for CFDI 3.3)" msgstr "" -#: ../../accounting/localizations/mexico.rst:263 +#: ../../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:266 +#: ../../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:269 +#: ../../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:271 +#: ../../accounting/localizations/mexico.rst:273 msgid "You must print the payment in order to retrieve the PDF properly." msgstr "" -#: ../../accounting/localizations/mexico.rst:272 +#: ../../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:277 +#: ../../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:282 +#: ../../accounting/localizations/mexico.rst:284 msgid "The accounting for Mexico in odoo is composed by 3 reports:" msgstr "" -#: ../../accounting/localizations/mexico.rst:284 +#: ../../accounting/localizations/mexico.rst:286 msgid "Chart of Account (Called and shown as COA)." msgstr "" -#: ../../accounting/localizations/mexico.rst:285 +#: ../../accounting/localizations/mexico.rst:287 msgid "Electronic Trial Balance." msgstr "" -#: ../../accounting/localizations/mexico.rst:286 +#: ../../accounting/localizations/mexico.rst:288 msgid "DIOT report." msgstr "" -#: ../../accounting/localizations/mexico.rst:288 +#: ../../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:291 +#: ../../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:297 +#: ../../accounting/localizations/mexico.rst:299 msgid "Electronic Accounting (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:300 +#: ../../accounting/localizations/mexico.rst:302 msgid "Electronic Chart of account CoA" msgstr "" -#: ../../accounting/localizations/mexico.rst:302 +#: ../../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:309 +#: ../../accounting/localizations/mexico.rst:311 msgid "**How to add new accounts?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:311 +#: ../../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:314 +#: ../../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:324 +#: ../../accounting/localizations/mexico.rst:326 msgid "**What is the meaning of the tag?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:326 +#: ../../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:330 +#: ../../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:336 +#: ../../accounting/localizations/mexico.rst:338 msgid "Electronic Trial Balance" msgstr "" -#: ../../accounting/localizations/mexico.rst:338 +#: ../../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:347 +#: ../../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:351 +#: ../../accounting/localizations/mexico.rst:353 msgid "DIOT Report (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:353 +#: ../../accounting/localizations/mexico.rst:355 msgid "**What is the DIOT and the importance of presenting it SAT**" msgstr "" -#: ../../accounting/localizations/mexico.rst:355 +#: ../../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:358 +#: ../../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:363 +#: ../../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:367 +#: ../../accounting/localizations/mexico.rst:369 msgid "**When to file the DIOT and in what format?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:369 +#: ../../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:373 +#: ../../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:378 +#: ../../accounting/localizations/mexico.rst:380 msgid "**Where the DIOT is presented?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:380 +#: ../../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:384 +#: ../../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:387 +#: ../../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:393 +#: ../../accounting/localizations/mexico.rst:395 msgid "**One more fact to know: the Batch load?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:395 +#: ../../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:399 +#: ../../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:406 +#: ../../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:411 +#: ../../accounting/localizations/mexico.rst:413 msgid "You can find the `official information here`_." msgstr "" -#: ../../accounting/localizations/mexico.rst:413 +#: ../../accounting/localizations/mexico.rst:415 msgid "**How Generate this report in odoo?**" msgstr "" -#: ../../accounting/localizations/mexico.rst:415 +#: ../../accounting/localizations/mexico.rst:417 msgid "Go to :menuselection:`Accounting --> Reports --> Mexico --> Transactions with third partied (DIOT)`." msgstr "" -#: ../../accounting/localizations/mexico.rst:420 +#: ../../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:426 +#: ../../accounting/localizations/mexico.rst:428 msgid "Click on \"Export (TXT)." msgstr "" -#: ../../accounting/localizations/mexico.rst:431 +#: ../../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:435 +#: ../../accounting/localizations/mexico.rst:437 msgid "Important considerations on your Supplier and Invice data for the DIOT" msgstr "" -#: ../../accounting/localizations/mexico.rst:437 +#: ../../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:445 +#: ../../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:448 +#: ../../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:451 +#: ../../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:454 +#: ../../accounting/localizations/mexico.rst:456 msgid "Remember this report only shows the Supplier Invoices that were actually paid." msgstr "" -#: ../../accounting/localizations/mexico.rst:456 +#: ../../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:467 +#: ../../accounting/localizations/mexico.rst:469 msgid "Extra Recommended features" msgstr "" -#: ../../accounting/localizations/mexico.rst:470 +#: ../../accounting/localizations/mexico.rst:472 msgid "Contact Module (Free)" msgstr "" -#: ../../accounting/localizations/mexico.rst:472 +#: ../../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:477 +#: ../../accounting/localizations/mexico.rst:479 msgid "Multi currency (Requires Accounting App)" msgstr "" -#: ../../accounting/localizations/mexico.rst:479 +#: ../../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:486 +#: ../../accounting/localizations/mexico.rst:488 msgid "Go to settings and enable the multi currency feature." msgstr "" -#: ../../accounting/localizations/mexico.rst:492 +#: ../../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:494 +#: ../../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:499 +#: ../../accounting/localizations/mexico.rst:501 msgid "Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`" msgstr "" -#: ../../accounting/localizations/mexico.rst:500 +#: ../../accounting/localizations/mexico.rst:502 msgid "Look for the Action called \"Download XSD files to CFDI\"" msgstr "" -#: ../../accounting/localizations/mexico.rst:501 +#: ../../accounting/localizations/mexico.rst:503 msgid "Click on button \"Create Contextual Action\"" msgstr "" -#: ../../accounting/localizations/mexico.rst:502 +#: ../../accounting/localizations/mexico.rst:504 msgid "Go to the company form :menuselection:`Settings --> Users&Companies --> Companies`" msgstr "" -#: ../../accounting/localizations/mexico.rst:503 +#: ../../accounting/localizations/mexico.rst:505 msgid "Open any company you have." msgstr "" -#: ../../accounting/localizations/mexico.rst:504 -#: ../../accounting/localizations/mexico.rst:527 +#: ../../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:509 +#: ../../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:514 +#: ../../accounting/localizations/mexico.rst:516 msgid "If you see an error like this:" msgstr "" -#: ../../accounting/localizations/mexico.rst:516 +#: ../../accounting/localizations/mexico.rst:518 msgid "The cfdi generated is not valid" msgstr "" -#: ../../accounting/localizations/mexico.rst:518 +#: ../../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:522 +#: ../../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:526 +#: ../../accounting/localizations/mexico.rst:528 msgid "Go to the company in which the error occurs." msgstr "" -#: ../../accounting/localizations/mexico.rst:533 +#: ../../accounting/localizations/mexico.rst:535 msgid "**Error message** (Only applicable on CFDI 3.3):" msgstr "" -#: ../../accounting/localizations/mexico.rst:535 +#: ../../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:537 +#: ../../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:540 +#: ../../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:543 -#: ../../accounting/localizations/mexico.rst:568 -#: ../../accounting/localizations/mexico.rst:578 -#: ../../accounting/localizations/mexico.rst:591 -#: ../../accounting/localizations/mexico.rst:602 +#: ../../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:545 +#: ../../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:547 +#: ../../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:550 +#: ../../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:557 +#: ../../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:565 +#: ../../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:570 +#: ../../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:573 +#: ../../accounting/localizations/mexico.rst:575 msgid "**Solution:** The payment method is required on your invoice." msgstr "" -#: ../../accounting/localizations/mexico.rst:580 +#: ../../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:585 -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 `3. Set you legal information in the company`." +#: ../../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:593 +#: ../../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:596 +#: ../../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:604 +#: ../../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:608 +#: ../../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 "" @@ -2772,110 +2995,6 @@ msgstr "" msgid "Explanation of the fields:" msgstr "" -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Status" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "When an asset is created, the status is 'Draft'." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "If the asset is confirmed, the status goes in 'Running' and the depreciation lines can be posted in the accounting." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "You can manually close an asset when the depreciation is over. If the last line of depreciation is posted, the asset automatically goes in that status." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Category" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Category of asset" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Date" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Date of asset" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Gross Value" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Gross value of asset" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Salvage Value" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "It is the amount you plan to have that you cannot depreciate." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Computation Method" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Choose the method to use to compute the amount of depreciation lines." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "* Linear: Calculated on basis of: Gross Value / Number of Depreciations" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "* Degressive: Calculated on basis of: Residual Value * Degressive Factor" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Time Method Based On" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Choose the method to use to compute the dates and number of 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 "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Indicates that the first depreciation entry for this asset have to be done from the purchase date instead of the first January / Start date of fiscal year" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Number of Depreciations" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "The number of depreciations needed to depreciate your asset" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Number of Months in a Period" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "The amount of time between two depreciations, in months" -msgstr "" - #: ../../accounting/others/adviser/assets.rst:88 msgid "Try creating an *Asset* in our online demonstration" msgstr "" @@ -3044,19 +3163,15 @@ msgstr "" msgid ":doc:`../../receivables/customer_invoices/overview`" msgstr "" -#: ../../accounting/others/adviser/budget.rst:128 -msgid ":doc:`../../../purchase/overview/process/from_po_to_invoice`" -msgstr "" - -#: ../../accounting/others/adviser/budget.rst:130 +#: ../../accounting/others/adviser/budget.rst:129 msgid "Go back in the budget list and find the Smith Project." msgstr "" -#: ../../accounting/others/adviser/budget.rst:132 +#: ../../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:141 +#: ../../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 "" @@ -3160,6 +3275,26 @@ msgstr "" 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 "" @@ -3249,42 +3384,42 @@ msgid "Purchase Product" msgstr "" #: ../../accounting/others/analytic/purchases_expenses.rst:104 -msgid "We also need to buy a software for our customers. In the purchase app create a purchase order for the software product. (please refer to the following document: :doc:`../../../purchase/overview/process/from_po_to_invoice`). Within the line we can link the product's cost with the analytical account. Specify the order line and select the correct analytical account. Confirm the sale." +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:114 +#: ../../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:118 +#: ../../accounting/others/analytic/purchases_expenses.rst:117 msgid "Subcontracting" msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:120 +#: ../../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:128 +#: ../../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:131 +#: ../../accounting/others/analytic/purchases_expenses.rst:130 msgid "Track costs in accounting" msgstr "" -#: ../../accounting/others/analytic/purchases_expenses.rst:133 +#: ../../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:136 +#: ../../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:139 +#: ../../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:147 +#: ../../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 "" @@ -4037,6 +4172,34 @@ msgstr "" 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 "" @@ -4477,6 +4640,7 @@ 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 "" @@ -6467,7 +6631,6 @@ msgid "15" msgstr "" #: ../../accounting/overview/process_overview/customer_invoice.rst:117 -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:89 msgid "Payment" msgstr "" @@ -7425,7 +7588,6 @@ msgstr "" #: ../../accounting/payables/pay/sepa.rst:132 #: ../../accounting/receivables/customer_payments/credit_cards.rst:168 -#: ../../accounting/receivables/customer_payments/followup.rst:168 #: ../../accounting/receivables/customer_payments/recording.rst:129 msgid ":doc:`check`" msgstr "" @@ -7708,125 +7870,51 @@ msgid "Customer Invoices" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_discounts.rst:3 -msgid "How to setup cash discounts?" +msgid "Offer cash discounts" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_discounts.rst:5 -msgid "Cash discounts are an incentive (usually a small percentage) that you offer to customers in return for paying a bill owed before the scheduled due date. If used properly, cash discounts improve the Days Sales Outstanding aspect of a business's cash conversion cycle." +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:10 -msgid "For example, a typical cash discount would be: you offer a 2% discount on an invoice due in 30 days if the customer were to pay within the first 5 days of receiving the invoice." +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:12 +msgid "Set up a cash discount" msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:18 -msgid "Payment terms" +#: ../../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:20 -msgid "In order to manage cash discounts, we will use the payment terms concept of Odoo (From the Accounting module, go to :menuselection:`Configuration --> Management --> Payment terms --> Create`)." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:24 -msgid "Let's start with the above example: a 2% discount on an invoice due in 30 days if the customer were to pay within the first 5 days." +#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:25 +msgid "Start offering the cash discount" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_discounts.rst:27 -msgid "A typical payment term of 30 days would have only one installment: balance in 30 days. But, in order to configure the cash discount, you can configure the payment term with two installments:" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:31 -msgid "98% within 5 days" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:32 -msgid "balance within 30 days" +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 "To make it clear that it's not a payment term but a cash discount, don't forget to set a clear description that will appear on the invoice: Invoice is due within 30 days, but you can benefit from a 2% cash discount if you pay within 5 days." +msgid "Grant the cash discount" msgstr "" -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:43 -msgid "Bank reconciliation model" +#: ../../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:45 -msgid "In order to speed up the bank reconciliation process, we can create a model of entry for all cash discounts. To do that, from the Accounting application dashboard, click on the \"More\" link on the bank and choose the option \"Reconciliation Models\"." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:53 -msgid "Create a new model for cash discounts as follow:" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:55 -msgid "**Button Label**: Cash Discount" +#: ../../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 "**Account**: Cash Discount (according to your country)" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:57 -msgid "**Amount Type**: Percentage" +msgid "Register the full payment" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_discounts.rst:58 -msgid "**Amount**: 100%" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 -msgid "**Taxes**: depending on your country, you may put a tax on the cash" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:60 -msgid "discount if taxes have to be deduced" +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 "Even if it's a 2% cash discount, set a 100% amount on the reconciliation model as it means 100% of the remaining balance (the 2%). You can use the same reconciliation model for all your cash discount. No need to create a model per payment term." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:73 -msgid "Creating an invoice with a cash discount" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:75 -msgid "When you create a customer invoice, set the right payment term \"30 days, 2% cash discount\" right after having selected the customer." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:81 -msgid "Once the invoice is validated, Odoo will automatically split the account receivable part of the journal entry with two installments having a different due date: 98% within 5 days, 2% within 30 days." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:92 -msgid "Paying the invoice with a cash discount" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:94 -msgid "If the customer pays with a cash discount, when processing the bank statement, you will match the payment (98%) with the related line in the journal entry." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:101 -msgid "As you can see in the above screenshot, when selecting the customer, you also see the 2% remaining of 3$. If you want to accept the cash discount (if the customer paid within the 5 days), you can click on this line with 2%, click on \"Open Balance\", and select your \"Cash Discount\" reconciliation model. That way, the invoice is marked as fully paid." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:109 -msgid "from now on, matching the remaining 2% has to be done manually. In the future, we plan to automate the reconciliation of the 2% if the 98% are paid on time." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:113 -msgid "Paying the invoice in full" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:115 -msgid "If the customer pays the invoice fully, without benefiting from the cash discount, you will reconcile the payment (in full) with the two lines from the invoice (98% and 2%). Just click on the two lines to match them with the payment." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/cash_discounts.rst:125 -#: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:116 -#: ../../accounting/receivables/customer_invoices/installment_plans.rst:86 -msgid ":doc:`overview`" +msgid ":doc:`../../receivables/customer_invoices/payment_terms`" msgstr "" #: ../../accounting/receivables/customer_invoices/cash_rounding.rst:2 @@ -8020,6 +8108,11 @@ msgstr "" 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 "" @@ -8411,240 +8504,6 @@ msgstr "" msgid "Customer Payments" msgstr "" -#: ../../accounting/receivables/customer_payments/automated_followups.rst:3 -msgid "How to automate customer follow-ups with plans?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:5 -msgid "With the Odoo Accounting application, you get a dynamic aged receivable report, customer statements and you can easily send them to customers." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:8 -msgid "If you want to go further in the automation of the credit collection process, you can use follow-up plans. They will help you automate all the steps to get paid, by triggering them at the right time: send customer statements by emails, send regular letter (through the Docsaway integration), create a task to manually call the customer, etc..." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:14 -msgid "Here is an example of a plan:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:17 -msgid "When?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:17 -msgid "What?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:17 -msgid "Who?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:19 -msgid "3 days before due date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:19 -msgid "Email" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:19 -#: ../../accounting/receivables/customer_payments/automated_followups.rst:21 -msgid "automated" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:21 -msgid "1 day after due date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:21 -msgid "Email + Regular Letter" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:23 -msgid "15 days after due date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:23 -msgid "Call the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:23 -#: ../../accounting/receivables/customer_payments/automated_followups.rst:25 -msgid "John Mac Gregor" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:25 -msgid "35 days after due date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:25 -msgid "Email + Letter + Call" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:27 -msgid "60 days after due date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:27 -msgid "Formal notice" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:27 -msgid "Bailiff" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:34 -msgid "Install Reminder Module" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:36 -msgid "You must start by activating the feature, using the menu :menuselection:`Configuration --> Settings` of the Accounting application. From the settings screen, activate the feature **Enable payment follow-up management**." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:44 -msgid "Define Payment Follow-ups Levels" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:46 -msgid "To automate customer follow ups, you must configure your follow–up levels using the menu :menuselection:`Accounting --> Configuration --> Payment Follow-ups`. You should define one and only one follow-up plan per company." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:50 -msgid "The levels of follow-up are relative to the due date; when no payment term is specified, the invoice date will be considered as the due date." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:53 -msgid "For each level, you should define the number of days and create a note which will automatically be added into the reminder letter." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:59 -msgid "Odoo defines several actions for every reminder:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:61 -msgid "**Manual Action:** assign a responsible that will have to call the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:62 -msgid "**Send an Email:** send an email to customer using the provided text" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:63 -msgid "**Send a Letter:** send a letter by regular mail, using the provided note" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:69 -msgid "As you need to provide a number of days relative to the due date, you can use a negative number. As an example, if an invoice is issued the January 1st but the due date is January 20, if you set a reminder 3 days before the due date, the customer may receive an email in January 17." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:76 -msgid "Doing your weekly follow-ups" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:78 -msgid "Once everything is setup, Odoo will prepare follow-up letters and emails automatically for you. All you have to do is to the menu :menuselection:`Sales --> Customers Statement` in the accounting application." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:85 -msgid "Odoo will automatically propose you actions based on the follow-up plan you defined, invoices to pay and payment received." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:88 -msgid "You can use this menu every day, once a week or once a month. You do not risk to send two times the same reminder to your customer. Odoo only proposes you the action you have to do. If you do it every day, you will have a few calls to do per day. If you do it once a month, you will have much more work once you do it." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:94 -msgid "It's up to you to organize the way you want to work. But it's a good practice to reconcile your bank statements before launching the follow-ups. That way, all paid invoices will be reconciled and you will not send a follow-up letter to a customer that already paid his invoice." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:99 -msgid "From a customer follow-up proposition, you can:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:101 -msgid "Get the customer information to contact him" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:103 -msgid "Drill down to the customer information form by clicking on its name" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:105 -msgid "Change the text (or the email or letter) and adapt to the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:107 -msgid "Change the colored dot to mark the customer as being a good, normal or bad debtor" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:110 -msgid "Log a note is you called the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:112 -msgid "Exclude some invoices from the statement table (litigation)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:114 -msgid "Send an email with the statement" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:116 -msgid "Print a letter, or send a regular mail (if you installed the Docsaway integration)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:119 -msgid "Plan the next reminder (but it's better to keep in automatic mode so that Odoo will stick to the follow-up plan of the company)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:122 -msgid "Drill down to an invoice" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:124 -msgid "Change the expected payment date of an invoice (thus, impacting the next time Odoo will propose you to send a reminder)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:128 -msgid "You can force a customer statement, even if Odoo do not proposes you to do it, because it's not the right date yet. To do this, you should go to the Aged Receivable report (in the report menu of the Accounting application). From this report, you can click on a customer to get to his customer statement." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:135 -msgid "How to exclude an invoice from auto follow up?" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:137 -msgid "To see all **overdue invoices** or **on need of action**," -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:139 -msgid "Go to :menuselection:`Accounting --> Sales --> Customers Statement`" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:145 -msgid "Exclude a specific invoice for a specific date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:147 -msgid "Odoo can exclude an invoice from follow-ups actions for specific date by clicking on **Log a Note**, then choose one of the ready options (*one week*, *two weeks*, *one month*, *two months*), So Odoo will calculate the required date according to the current date." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:155 -msgid "Another way to achieve it is the following: click on the required invoice, then choose **Change expected payment date/note**, then enter a new payment date and note." -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:162 -msgid "Exclude a specific invoice forever" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:164 -msgid "Odoo can exclude an invoice for a specific customer by clicking on the checkbox **Excluded**" -msgstr "" - -#: ../../accounting/receivables/customer_payments/automated_followups.rst:168 -msgid "If you click on **History**, you can see all follow ups actions." -msgstr "" - #: ../../accounting/receivables/customer_payments/check.rst:3 msgid "How to register customer payments by checks?" msgstr "" @@ -8927,7 +8786,6 @@ msgid "If you use this approach to manage received credit cards, you can use the msgstr "" #: ../../accounting/receivables/customer_payments/credit_cards.rst:166 -#: ../../accounting/receivables/customer_payments/followup.rst:167 msgid ":doc:`recording`" msgstr "" @@ -8942,163 +8800,59 @@ msgid ":doc:`followup`" msgstr "" #: ../../accounting/receivables/customer_payments/followup.rst:3 -msgid "How to get paid and organize customer follow-ups?" +msgid "Follow-up on invoices and get paid faster" msgstr "" #: ../../accounting/receivables/customer_payments/followup.rst:5 -msgid "Getting paid and organizing customer reminders is always a difficult task, however it is critical for the health of the company to stay diligent about outstanding receivables. Fortunately, Odoo provides the right tools to track receivables, automate customer statements, and measure your performance." +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:12 -msgid "Customer follow-ups: A step by step guide" +#: ../../accounting/receivables/customer_payments/followup.rst:10 +msgid "Manage your follow-ups" msgstr "" -#: ../../accounting/receivables/customer_payments/followup.rst:15 -msgid "Cleaning up outstanding payments" +#: ../../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 "If you have any unreconciled transactions in your bank account, you will need to process them first before you begin analyzing your customers statements. This ensures that you have recorded all of the latest customer payments before sending out reminders to any customers with outstanding balances." +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:27 -msgid "Checking the Aged Receivables report" +#: ../../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:29 -msgid "After you have reconciled all of your bank accounts, you can then generate an accurate Aged Receivables Report from the Reports menu. This report will display all of the customers and their outstanding balances on open invoices." +#: ../../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:37 -msgid "The report displays this information in time increments to better paint a picture of the outstanding balances your customers hold and for how long they have held these outstanding balances. You can then appropriately focus your efforts on the appropriate customers." +#: ../../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 "You can then select any of the customers on this list and Odoo will open up their invoice details in the form of the Customer Follow-Up letter, also known as the **Customer Statement**." +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:49 -msgid "From the customer statement, you can:" +#: ../../accounting/receivables/customer_payments/followup.rst:52 +msgid "Plan a follow-up process" msgstr "" -#: ../../accounting/receivables/customer_payments/followup.rst:51 -msgid "Change and customize the message that is sent to the customer" +#: ../../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:53 -msgid "Send a reminder email to the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:55 -msgid "Send a printed reminder letter to the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:57 -msgid "Send automated printed reminders by utilizing our Docsaway integration" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:60 -msgid "Zoom in on the different open invoices or payments" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:62 -msgid "Remove an invoice or payment from the report (in case of conflict)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:64 -msgid "Log any call notes made to the customer" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:66 -msgid "Schedule your next follow up task to stay on top of customer payments (e.g. call back in 15 days if not payments are made)" +#: ../../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 "You can set reminders for when you would like to next contact the particular customer. Selecting **Manual** will open up the follow up scheduling tool, while selecting **Auto** will automatically recommend that you contact the customer 15 days from then if the customer has not yet paid for the invoice. Installing the **Follow-Up Plans** module will allow you to define automated actions and intervals to send reminders." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:79 -msgid "If you have already sent out a reminder to a customer a few days ago, a warning message will appear at the top of the screen, reminding you that you should not send another reminder so soon since one was already sent recently. Every time you log a note, Odoo will automatically set the next reminder date, unless you choose to manually set it by selecting the next reminder button at the top right of the screen." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:88 -msgid "You can also specify the expected payment date on an invoice line directly, therefore defining the next reminder in case the invoice has not been paid." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:92 -msgid "Sending customer statements" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:94 -msgid "Send your customers reminders in batches in the menu :menuselection:`Sales --> Customer Statements`." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:97 -msgid "Here Odoo will open all the statements awaiting to be processed, which is determined by the last reminder they received. You can choose to process them one by one, send multiple letters or emails in batches, or set a next action date for the next time they'll be contacted." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:104 -msgid "If an invoice has not yet been paid, Odoo will remind you to contact at particular customer based after their next action date." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:107 -msgid "You can access the customer statement report daily and Odoo will only display the customers you need to contact on any given day. This is based on:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:111 -msgid "Customers you have not yet received a payment from" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:113 -msgid "Customers that have not been reminded over the last X days (\"X\" being defined as the overdue date of the invoice after the first reminder, then the next action date set at every reminder)" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:118 -msgid "Setting up your dunning process" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:120 -msgid "The **Payment Follow-up Management** module allows you to define reminder plans. After installing it from the **Apps** menu, go to the **Follow-up Levels** menu in the accounting configuration to set up your dunning process." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:125 -msgid "Some Examples are:" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:127 -msgid "**Email**: 3 days before overdue date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:129 -msgid "**Email+Letter**: at the overdue date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:131 -msgid "**Email+Call**: 15 days after the overdue date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:133 -msgid "**Email+Letter**: 60 days after the overdue date" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:138 -msgid "Thanks to this module, you can send every email and letters in batches for all your customers at once. The next reminder will automatically be computed based on your configured follow-up plan." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:142 -msgid "The module will also add a red/green dot on each customer, this will allow you to easily mark customer status's with the following options: \"Good Debtor, Normal Debtor, or bad debtors." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:150 -msgid "DSO: Measuring your performance" -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:152 -msgid "The DSO (Days of Outstanding Sales) is a measure of the average number of days that a company takes to collect revenue after a sale has been made. DSO is calculated by dividing the amount of accounts receivable during a given period by the total value of credit sales during the same period, and multiplying the result by the number of days in the period measured." -msgstr "" - -#: ../../accounting/receivables/customer_payments/followup.rst:159 -msgid "You can get the DSO of your company from the Executive Summary report under Reporting (check the KPI average debtors days)." +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 diff --git a/locale/sources/applications.pot b/locale/sources/applications.pot index 42b33aed2..581b986dc 100644 --- a/locale/sources/applications.pot +++ b/locale/sources/applications.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-06-07 09:30+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/business.pot b/locale/sources/business.pot index 50112919c..0004082e0 100644 --- a/locale/sources/business.pot +++ b/locale/sources/business.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-10-10 09:08+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/discuss.pot b/locale/sources/discuss.pot index a33351fda..060e36072 100644 --- a/locale/sources/discuss.pot +++ b/locale/sources/discuss.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-07-27 11:08+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -25,15 +25,19 @@ 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 in `Odoo Online `__ & `Odoo.sh `__." +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 such convenient Odoo hosting solutions. Indeed 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." +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 to do so by integrating your own email solution with Odoo. .. note::" +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 @@ -308,6 +312,22 @@ msgstr "" 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 "" diff --git a/locale/sources/ecommerce.pot b/locale/sources/ecommerce.pot index 9712040a0..840cbcf20 100644 --- a/locale/sources/ecommerce.pot +++ b/locale/sources/ecommerce.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-10-10 09:08+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/expense.pot b/locale/sources/expense.pot index b420dc10a..dfe8ac84d 100644 --- a/locale/sources/expense.pot +++ b/locale/sources/expense.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-10-20 11:50+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,7 +16,6 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../expense.rst:5 #: ../../expense/expense.rst:5 msgid "Expenses" msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 4c9d83a78..d45e9e029 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-10-10 09:08+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -505,10 +505,6 @@ msgstr "" msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_" msgstr "" -#: ../../general/odoo_basics/add_user.rst:46 -msgid ":doc:`../../crm/salesteam/setup/create_team`" -msgstr "" - #: ../../general/odoo_basics/choose_language.rst:3 msgid "Manage Odoo in your own language" msgstr "" diff --git a/locale/sources/helpdesk.pot b/locale/sources/helpdesk.pot index a4f09d674..2258546ad 100644 --- a/locale/sources/helpdesk.pot +++ b/locale/sources/helpdesk.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-03-08 14:28+0100\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/index.pot b/locale/sources/index.pot index f657a1074..713e8e96f 100644 --- a/locale/sources/index.pot +++ b/locale/sources/index.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-06-07 09:30+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/inventory.pot b/locale/sources/inventory.pot index cdfddc6f1..e9c402a16 100644 --- a/locale/sources/inventory.pot +++ b/locale/sources/inventory.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-01-08 17:10+0100\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -4839,10 +4839,6 @@ msgstr "" msgid ":doc:`uom`" msgstr "" -#: ../../inventory/settings/products/usage.rst:72 -msgid ":doc:`packages`" -msgstr "" - #: ../../inventory/settings/products/variants.rst:3 msgid "Using product variants" msgstr "" diff --git a/locale/sources/iot.pot b/locale/sources/iot.pot new file mode 100644 index 000000000..b0940b0e2 --- /dev/null +++ b/locale/sources/iot.pot @@ -0,0 +1,282 @@ +# 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 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: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\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 "" + +#: ../../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/sources/manufacturing.pot b/locale/sources/manufacturing.pot index bcfe96c4e..7e4d8cd9d 100644 --- a/locale/sources/manufacturing.pot +++ b/locale/sources/manufacturing.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-12-22 15:27+0100\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -41,102 +41,102 @@ 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. For more information about which method of management to use, review the **Getting Started** section of the *Manufacturing* chapter of the documentation." +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:22 +#: ../../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:32 +#: ../../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:38 +#: ../../manufacturing/management/bill_configuration.rst:35 msgid "Adding a Routing to a BoM" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:40 +#: ../../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:46 +#: ../../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:50 +#: ../../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:61 +#: ../../manufacturing/management/bill_configuration.rst:58 msgid "Adding Byproducts to a BoM" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:63 +#: ../../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:66 +#: ../../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:72 +#: ../../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:81 +#: ../../manufacturing/management/bill_configuration.rst:78 msgid "Setting up a BoM for a Product With Sub-Assemblies" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:83 +#: ../../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:90 +#: ../../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:97 +#: ../../manufacturing/management/bill_configuration.rst:94 msgid "Configure the Top-Level Product BoM" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:99 +#: ../../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:107 +#: ../../manufacturing/management/bill_configuration.rst:104 #: ../../manufacturing/management/sub_assemblies.rst:29 msgid "Configure the Subassembly Product Data" msgstr "" -#: ../../manufacturing/management/bill_configuration.rst:109 +#: ../../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:117 +#: ../../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:123 +#: ../../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:125 +#: ../../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:132 +#: ../../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:137 +#: ../../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 "" @@ -271,7 +271,83 @@ msgstr "" 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 "" +#: ../../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/sources/mobile.pot b/locale/sources/mobile.pot new file mode 100644 index 000000000..113ffbf99 --- /dev/null +++ b/locale/sources/mobile.pot @@ -0,0 +1,98 @@ +# 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 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: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../mobile/firebase.rst:5 +msgid "Mobile" +msgstr "" + +#: ../../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 "" + +#: ../../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/sources/point_of_sale.pot b/locale/sources/point_of_sale.pot index 925fa3ea8..f11f3cb19 100644 --- a/locale/sources/point_of_sale.pot +++ b/locale/sources/point_of_sale.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-07-26 12:01+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -48,7 +48,7 @@ msgid "To use a barcode scanner, go to :menuselection:`Point of Sale --> Configu msgstr "" #: ../../point_of_sale/advanced/barcode.rst:14 -msgid "Under the PosBox / Hardware category, you will find *Barcode Scanner* select it." +msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* select it." msgstr "" #: ../../point_of_sale/advanced/barcode.rst:21 @@ -406,7 +406,7 @@ msgid "Serial-to-USB adapter per FDM (`example Configuration --> Point of Sale` and ensure Hardware Proxy / POSBox and the serial number of your POSBox is set). The first time you open the Point of Sale and attempt to do a transaction, you will be asked to input the PIN that you received with your VAT signing card." +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 @@ -462,11 +462,11 @@ msgid "Selling products without a valid tax" msgstr "" #: ../../point_of_sale/belgian_fdm/setup.rst:90 -msgid "Multiple Odoo POS configurations per POSBox are not allowed" +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 POSBox (and thus FDM)" +msgid "Using the POS without a connection to the IoT Box (and thus FDM)" msgstr "" #: ../../point_of_sale/belgian_fdm/setup.rst:92 @@ -506,614 +506,6 @@ msgstr "" msgid "Use the save button when you are done. You can then select that customer in any future transactions." msgstr "" -#: ../../point_of_sale/overview/setup.rst:3 -msgid "Point of Sale Hardware Setup" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:6 -msgid "POSBox Setup Guide" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:11 -#: ../../point_of_sale/overview/setup.rst:205 -msgid "Prerequisites" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:13 -msgid "Before you start setting up your POSBox make sure you have everything. You will need :" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:16 -msgid "The POSBox" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:17 -msgid "A 2A Power adapter" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:18 -msgid "A computer or tablet with an up-to-date web browser" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:19 -msgid "A running SaaS or Odoo database with the Point of Sale installed" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:20 -msgid "A local network set up with DHCP (this is the default setting)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:21 -msgid "An Epson USB TM-T20 Printer or another ESC/POS compatible printer (officially supported printers are listed at the `POS Hardware page `_)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:24 -msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:25 -msgid "An Epson compatible cash drawer" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:26 -msgid "An RJ45 Ethernet Cable (optional, Wi-Fi is built in)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:29 -#: ../../point_of_sale/overview/setup.rst:213 -msgid "Step By Step Setup Guide" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:32 -msgid "Current version of the POSBox (since 2015)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:36 -msgid "Connect peripheral devices" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:38 -msgid "Officially supported hardware is listed on `the POS Hardware page `_, but other hardware might work as well." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:42 -msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:45 -msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:48 -msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must behave as a keyboard and must be configured in **US QWERTY**. It also must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:54 -msgid "**Scale**: Connect your scale and power it on." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:56 -msgid "**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. Make sure this will connect the POSBox to the same network as your POS device." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:60 -msgid "**Wi-Fi**: The current version of the POSBox has Wi-Fi built in. Make sure not to plug in an Ethernet cable, because all Wi-Fi functionality will be bypassed when a wired network connection is available." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:66 -msgid "Power the POSBox" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:68 -msgid "Plug the power adapter into the POSBox, a bright red status led should light up." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:72 -msgid "Make sure the POSBox is ready" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:74 -msgid "Once powered, The POSBox needs a while to boot. Once the POSBox is ready, it should print a status receipt with its IP address. Also the status LED, just next to the red power LED, should be permanently lit green." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:80 -#: ../../point_of_sale/overview/setup.rst:292 -msgid "Setup the Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:82 -msgid "To setup the POSBox in the Point of Sale go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale. Scroll down to the ``PoSBox / Hardware Proxy`` section and activate the options for the hardware you want to use through the POSBox. Specifying the IP of the POSBox is recommended (it is printed on the receipt that gets printed after booting up the POSBox). When the IP is not specified the Point of Sale will attempt to find it on the local network." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:91 -msgid "If you are running multiple Point of Sale on the same POSBox, make sure that only one of them has Remote Scanning/Barcode Scanner activated." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:94 -msgid "It might be a good idea to make sure the POSBox IP never changes in your network. Refer to your router documentation on how to achieve this." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:99 -msgid "Launch the Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:101 -msgid "If you didn't specify the POSBox's IP address in the configuration, the POS will need some time to perform a network scan to find the POSBox. This is only done once." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:105 -msgid "The Point of Sale is now connected to the POSBox and your hardware should be ready to use." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:109 -msgid "Wi-Fi configuration" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:111 -msgid "The most recent version of the POSBox has Wi-Fi built in. If you're using an older version you'll need a Linux compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 chipset." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:117 -msgid "Make sure not to plug in an Ethernet cable, as all Wi-Fi related functionality will be disabled when a wired network connection is available." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:121 -msgid "When the POSBox boots with a Wi-Fi adapter it will start its own Wi-Fi Access Point called \"Posbox\" you can connect to. The receipt that gets printed when the POSBox starts will reflect this. In order to make the POSBox connect to an already existing Wi-Fi network, go to the homepage of the POSBox (indicated on the receipt) and go to the Wi-Fi configuration page. On there you can choose a network to connect to. Note that we only support open and WPA(2)-PSK networks. When connecting to a WPA-secured network, fill in the password field. The POSBox will attempt to connect to the specified network and will print a new POSBox status receipt after it has connected." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:132 -msgid "If you plan on permanently setting up the POSBox with Wi-Fi, you can use the \"persistent\" checkbox on the Wi-Fi configuration page when connecting to a network. This will make the network choice persist across reboots. This means that instead of starting up its own \"Posbox\" network it will always attempt to connect to the specified network after it boots." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:139 -msgid "When the POSBox fails to connect to a network it will fall back to starting it's own \"Posbox\" Access Point. If connection is lost with a Wi-Fi network after connecting to it, the POSBox will attempt to re-establish connection automatically." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:145 -msgid "Multi-POS Configuration" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:147 -msgid "The advised way to setup a multi Point of Sale shop is to have one POSBox per Point of Sale. In this case it is mandatory to manually specify the IP address of each POSBox in each Point of Sale. You must also configure your network to make sure the POSBox's IP addresses don't change. Please refer to your router documentation." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:154 -msgid "POSBoxless Guide (advanced)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:158 -msgid "If you are running your Point of Sale on a Debian-based Linux distribution, you do not need the POSBox as you can run its software locally. However the installation process is not foolproof. You'll need at least to know how to install and run Odoo. You may also run into issues specific to your distribution or to your particular setup and hardware configuration." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:165 -msgid "Drivers for the various types of supported hardware are provided as Odoo modules. In fact, the POSBox runs an instance of Odoo that the Point of Sale communicates with. The instance of Odoo running on the POSBox is very different from a 'real' Odoo instance however. It does not handle *any* business data (eg. POS orders), but only serves as a gateway between the Point of Sale and the hardware." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:172 -msgid "The goal of this section will be to set up a local Odoo instance that behaves like the Odoo instance running on the POSBox." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:176 -msgid "Image building process" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:178 -msgid "We generate the official POSBox images using the scripts in https://github.com/odoo/odoo/tree/11.0/addons/point_of_sale/tools/posbox. More specifically, we run `posbox_create_image.sh `_. This builds an image called ``posbox.img``, which we zip and upload to `nightly.odoo.com `_ for users to download." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:186 -msgid "The scripts in this directory might be useful as a reference if you get stuck or want more detail about something." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:190 -msgid "Summary of the image creation process" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:192 -msgid "The image creation process starts by downloading the latest `Raspbian `_ image. It then locally mounts this Raspbian image and copies over some files and scripts that will make the Raspbian image turn itself into a POSBox when it boots. These scripts will update Raspbian, remove non-essential packages and install required packages. In order to boot Raspbian we use qemu, which is capable of providing ARM emulation. After this, the emulated Raspbian OS will shut itself down. We then once again locally mount the image, remove the scripts that were used to initialize the image at boot and we copy over some extra configuration files. The resulting image is then ready to be tested and used." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:207 -msgid "A Debian-based Linux distribution (Debian, Ubuntu, Mint, etc.)" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:208 -msgid "A running Odoo instance you connect to load the Point of Sale" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:209 -msgid "You must uninstall any ESC/POS printer driver as it will conflict with Odoo's built-in driver" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:216 -msgid "Extra dependencies" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:218 -msgid "Because Odoo runs on Python 2, you need to check which version of pip you need to use." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:221 -msgid "``# pip --version``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:223 -#: ../../point_of_sale/overview/setup.rst:229 -msgid "If it returns something like::" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:227 -msgid "You need to try pip2 instead." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:233 -msgid "You can use pip." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:235 -msgid "The driver modules requires the installation of new python modules:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:237 -msgid "``# pip install pyserial``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:239 -msgid "``# pip install pyusb==1.0.0b1``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:241 -msgid "``# pip install qrcode``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:244 -msgid "Access Rights" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:246 -msgid "The drivers need raw access to the printer and barcode scanner devices. Doing so requires a bit system administration. First we are going to create a group that has access to USB devices" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:250 -msgid "``# groupadd usbusers``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:252 -msgid "Then we add the user who will run the OpenERP server to ``usbusers``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:254 -msgid "``# usermod -a -G usbusers USERNAME``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:256 -msgid "Then we need to create a udev rule that will automatically allow members of ``usbusers`` to access raw USB devices. To do so create a file called ``99-usbusers.rules`` in the ``/etc/udev/rules.d/`` directory with the following content::" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:264 -msgid "Then you need to reboot your machine." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:267 -msgid "Start the local Odoo instance" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:269 -msgid "We must launch the Odoo server with the correct settings" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:271 -msgid "``$ ./odoo.py --load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale,hw_scanner,hw_escpos``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:274 -msgid "Test the instance" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:276 -msgid "Plug all your hardware to your machine's USB ports, and go to ``http://localhost:8069/hw_proxy/status`` refresh the page a few times and see if all your devices are indicated as *Connected*. Possible source of errors are: The paths on the distribution differ from the paths expected by the drivers, another process has grabbed exclusive access to the devices, the udev rules do not apply or a superseded by others." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:284 -msgid "Automatically start Odoo" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:286 -msgid "You must now make sure that this Odoo install is automatically started after boot. There are various ways to do so, and how to do it depends on your particular setup. Using the init system provided by your distribution is probably the easiest way to accomplish this." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:294 -msgid "The IP address field in the POS configuration must be either ``127.0.0.1`` or ``localhost`` if you're running the created Odoo server on the machine that you'll use as the Point of Sale device. You can also leave it empty." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:300 -msgid "POSBox Technical Documentation" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:303 -msgid "Technical Overview" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:306 -msgid "The POSBox Hardware" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:308 -msgid "The POSBox's Hardware is based on a `Raspberry Pi 2 `_, a popular single-board computer. The Raspberry Pi 2 is powered with a 2A micro-usb power adapter. 2A is needed to give enough power to the barcode scanners. The Software is installed on a 8Gb Class 10 or Higher SD Card. All this hardware is easily available worldwide from independent vendors." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:317 -msgid "Compatible Peripherals" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:319 -msgid "Officially supported hardware is listed on the `POS Hardware page `_." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:323 -msgid "The POSBox Software" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:325 -msgid "The POSBox runs a heavily modified Raspbian Linux installation, a Debian derivative for the Raspberry Pi. It also runs a barebones installation of Odoo which provides the webserver and the drivers. The hardware drivers are implemented as Odoo modules. Those modules are all prefixed with ``hw_*`` and they are the only modules that are running on the POSBox. Odoo is only used for the framework it provides. No business data is processed or stored on the POSBox. The Odoo instance is a shallow git clone of the ``8.0`` branch." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:334 -msgid "The root partition on the POSBox is mounted read-only, ensuring that we don't wear out the SD card by writing to it too much. It also ensures that the filesystem cannot be corrupted by cutting the power to the POSBox. Linux applications expect to be able to write to certain directories though. So we provide a ramdisk for /etc and /var (Raspbian automatically provides one for /tmp). These ramdisks are setup by ``setup_ramdisks.sh``, which we run before all other init scripts by running it in ``/etc/init.d/rcS``. The ramdisks are named /etc_ram and /var_ram respectively. Most data from /etc and /var is copied to these tmpfs ramdisks. In order to restrict the size of the ramdisks, we do not copy over certain things to them (eg. apt related data). We then bind mount them over the original directories. So when an application writes to /etc/foo/bar it's actually writing to /etc_ram/foo/bar. We also bind mount / to /root_bypass_ramdisks to be able to get to the real /etc and /var during development." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:350 -msgid "Logs of the running Odoo server can be found at:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:352 -msgid "``/var/log/odoo/odoo.log``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:354 -msgid "Various POSBox related scripts (eg. wifi-related scripts) running on the POSBox will log to /var/log/syslog and those messages are tagged with ``posbox_*``." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:359 -msgid "Accessing the POSBox" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:362 -msgid "Local Access" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:364 -msgid "If you plug a QWERTY USB keyboard into one of the POSBox's USB ports, and if you connect a computer monitor to the *HDMI* port of the POSBox, you can use it as a small GNU/Linux computer and perform various administration tasks, like viewing some logs." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:369 -msgid "The POSBox will automatically log in as root on the default tty." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:372 -msgid "Remote Access" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:374 -msgid "If you have the POSBox's IP address and an SSH client you can access the POSBox's system remotely. The login credentials are ``pi``/``raspberry``." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:379 -msgid "Updating The POSBox Software" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:381 -msgid "Only upgrade the POSBox if you experience problems or want to use newly implemented features." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:384 -msgid "The best way to update the POSBox software is to download a new version of the image and flash the SD-Card with it. This operation is described in detail in `this tutorial `_, just replace the standard Raspberry Pi image with the latest one found at `the official POSBox image page `_. This method of upgrading will ensure that you're running the latest version of the POSBox software." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:393 -msgid "The second way of upgrading is through the built in upgrade interface that can be reached through the POSBox homepage. The nice thing about upgrading like this is that you don't have to flash a new image. This upgrade method is limited to what it can do however. It can not eg. update installed configuration files (like eg. /etc/hostapd.conf). It can only upgrade:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:400 -msgid "The internal Odoo application" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:401 -msgid "Scripts in the folder ``odoo/addons/point_of_sale/tools/posbox/configuration/``" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:403 -msgid "When in doubt, always use the first method of upgrading." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:406 -msgid "Troubleshoot" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:409 -msgid "The POS cannot connect to the POSBox" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:411 -msgid "The easiest way to make sure the POSBox is properly set-up is to turn it on with the printer plugged in as it will print a receipt indicating any error if encountered or the POSBox's IP address in case of success. If no receipt is printed, check the following steps:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:415 -msgid "Make sure the POSBox is powered on, indicated by a brightly lit red status LED." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:417 -msgid "Make sure the POSBox is ready, this is indicated by a brightly lit green status LED just next to the red power status LED. The POSBox should be ready ~2 minutes after it is started." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:420 -msgid "Make sure the POSBox is connected to the same network as your POS device. Both the device and the POSBox should be visible in the list of connected devices on your network router." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:423 -msgid "Make sure that your LAN is set up with DHCP, and gives IP addresses in the range 192.168.0.X, 192.168.1.X, 10.0.0.X. If you cannot setup your LAN that way, you must manually set up your POSBox's IP address." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:427 -msgid "If you have specified the POSBox's IP address in the configuration, make sure it correspond to the printed on the POSBox's status receipt." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:430 -msgid "Make sure that the POS is not loaded over HTTPS." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:431 -msgid "A bug in Firefox's HTTP implementation prevents the autodiscovery from working reliably. When using Firefox you should manually set up the POSBox's IP address in the POS configuration." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:436 -msgid "The Barcode Scanner is not working" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:438 -msgid "The barcode scanner must be configured in US QWERTY and emit an Enter after each barcode. This is the default configuration of most barcode readers. Refer to the barcode reader documentation for more information." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:442 -msgid "The POSBox needs a 2A power supply to work with some barcode scanners. If you are not using the provided power supply, make sure the one you use has enough power." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:445 -msgid "Some barcode scanners will need more than 2A and will not work, or will work unreliably, even with the provided power supply. In those case you can plug the barcode scanner in a self-powered USB hub." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:448 -msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a usb keyboard instead, and will not be recognized by the POSBox." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:453 -msgid "The Barcode Scanner is not working reliably" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:455 -msgid "Make sure that no more than one device with 'Scan via Proxy'/'Barcode Scanner' enabled are connected to the POSBox at the same time." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:460 -msgid "Printing the receipt takes too much time" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:462 -msgid "A small delay before the first print is expected, as the POSBox will do some preprocessing to speed up the next printings. If you suffer delays afterwards it is most likely due to poor network connection between the POS and the POSBox." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:468 -msgid "Some characters are not correctly printed on the receipt" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:470 -msgid "The POSBox does not support all languages and characters. It currently supports Latin and Cyrillic based scripts, with basic Japanese support." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:475 -msgid "The printer is offline" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:477 -msgid "Make sure the printer is connected, powered, has enough paper and has its lid closed, and is not reporting an error. If the error persists, please contact support." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:482 -msgid "The cashdrawer does not open" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:484 -msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:488 -msgid "Credits" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:489 -msgid "The POSBox project was developed by Frédéric van der Essen with the kind help of Gary Malherbe, Fabien Meghazi, Nicolas Wisniewsky, Dimitri Del Marmol, Joren Van Onder and Antony Lesuisse." -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:493 -msgid "This development would not have been possible without the Indiegogo campaign and those who contributed to it. Special thanks goes to the partners who backed the campaign with founding partner bundles:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:497 -msgid "Camptocamp" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:498 -msgid "BHC" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:499 -msgid "openBig" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:500 -msgid "Eeezee-IT" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:501 -msgid "Solarsis LDA" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:502 -msgid "ACSONE" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:503 -msgid "Vauxoo" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:504 -msgid "Ekomurz" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:505 -msgid "Datalp" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:506 -msgid "Dao Systems" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:507 -msgid "Eggs Solutions" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:508 -msgid "OpusVL" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:510 -msgid "And also the partners who've backed the development with the Founding POSBox Bundle:" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:513 -msgid "Willow IT" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:514 -msgid "E\\. Akhalwaya & Sons" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:515 -msgid "Multibase" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:516 -msgid "Mindesa" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:517 -msgid "bpso.biz" -msgstr "" - -#: ../../point_of_sale/overview/setup.rst:518 -msgid "Shine IT." -msgstr "" - #: ../../point_of_sale/overview/start.rst:3 msgid "Getting started with Odoo Point of Sale" msgstr "" @@ -1230,6 +622,10 @@ msgstr "" 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 "" @@ -1283,7 +679,7 @@ msgid "To activate the *Order printing* feature, go to :menuselection:`Point of msgstr "" #: ../../point_of_sale/restaurant/kitchen_printing.rst:16 -msgid "Under the PosBox / Hardware Proxy category, you will find *Order Printers*." +msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*." msgstr "" #: ../../point_of_sale/restaurant/kitchen_printing.rst:19 @@ -1515,7 +911,7 @@ msgid "In this example, you can see I want to have 275$ in various denomination msgstr "" #: ../../point_of_sale/shop/cash_control.rst:24 -msgid "When clicking on *->Opening/Closing Values* you will be able to create those values." +msgid "When clicking on **Opening/Closing Values** you will be able to create those values." msgstr "" #: ../../point_of_sale/shop/cash_control.rst:31 diff --git a/locale/sources/practical.pot b/locale/sources/practical.pot index cf53b4973..7a1c84f83 100644 --- a/locale/sources/practical.pot +++ b/locale/sources/practical.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-06-07 09:30+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" diff --git a/locale/sources/project.pot b/locale/sources/project.pot index 1abedc830..0d172b9b0 100644 --- a/locale/sources/project.pot +++ b/locale/sources/project.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-07-26 12:01+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -120,10 +120,6 @@ msgstr "" msgid "Then, you will be able to publish your result on your website by clicking on the website button in the upper right corner and confirming it in the front end of the website." msgstr "" -#: ../../project/advanced/feedback.rst:111 -msgid ":doc:`claim_issue`" -msgstr "" - #: ../../project/advanced/so_to_task.rst:3 msgid "How to create tasks from sales orders?" msgstr "" diff --git a/locale/sources/purchase.pot b/locale/sources/purchase.pot index 0a0493d8f..cbfeca72e 100644 --- a/locale/sources/purchase.pot +++ b/locale/sources/purchase.pot @@ -1,14 +1,14 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2015-TODAY, Odoo S.A. -# This file is distributed under the same license as the Odoo Business package. +# This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo Business 10.0\n" +"Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2017-12-22 15:27+0100\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,233 +20,6 @@ msgstr "" msgid "Purchase" msgstr "" -#: ../../purchase/overview.rst:3 -#: ../../purchase/replenishment/flows/dropshipping.rst:6 -#: ../../purchase/replenishment/flows/purchase_triggering.rst:6 -#: ../../purchase/replenishment/flows/warning_triggering.rst:6 -#: ../../purchase/replenishment/multicompany/setup.rst:6 -msgid "Overview" -msgstr "" - -#: ../../purchase/overview/process.rst:3 -msgid "Process Overview" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:3 -msgid "Request for Quotation, Purchase Tender or Purchase Order?" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:5 -msgid "Although they are intimately related, Requests for Quotation, Purchase Tenders and Purchase Orders are not the same." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:8 -msgid "A **Request for Quotation** (RfQ) is used when you plan to purchase some products and you would like to receive a quote for those products. In Odoo, the Request for Quotation is used to send your list of desired products to your supplier. Once your supplier has answered your request, you can choose to go ahead with the offer and purchase or to turn down the offer." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:15 -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:5 -msgid "A **Purchase Tender** (PT), also known as Call for Bids, is used to drive competition between several suppliers in order to get the best offer for a list of products. In comparison to the RfQ, a Purchase Tender is sent to multiple suppliers, stating each are competing with one another, and that the best offer will win. The main interest is that it usually leads to better offers." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:22 -msgid "The **Purchase Order** (PO) is the actual order that you place to the supplier that you chose, either through a RfQ, a Purchase Tender, or simply when you already know which supplier to order from." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:27 -msgid "When to use?" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:29 -msgid "A **RfQ** is interesting when you have never purchased the products with that supplier before and therefore don't know their price. It is also useful if you want to challenge your suppliers once you have a well-established relationship with them. You can also use it to assess the cost of a project and see if it makes it feasible." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:35 -msgid "A **Purchase Tender** is used for public offers that require an open offering from several suppliers. It is also useful when you need to make a one-off order for a product and you would like to get the best offer, no matter which supplier it is. It may be used when your supplier has not been up to your standards and you would like to either push them to deliver a better service, or find a replacement in their competitors." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:43 -msgid "When not to use?" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:45 -msgid "**RfQ**\\ s become unnecessary once you have established your favorite supplier for each item, and will only increase the delay in the delivery of your items. In that case, the process will be simpler by starting straight from a Purchase Order." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:50 -msgid "**Purchase Tenders** are a long and tedious process that will likely take more than several weeks in the best cases. If you need a quick delivery, this is not the way to go. Also, if you have a well-established relationship with one supplier, think twice before you initiate a PT with them as it might tear the relationship and finally lead to less interesting deals." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:58 -#: ../../purchase/replenishment/flows/compute_date.rst:139 -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:39 -msgid "Example" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:60 -msgid "My company builds wooden furniture. For the new series of table we are designing, we need some screws, metal frames and rubber protections." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:63 -msgid "I create a Request for Quotation in Odoo with those products to my usual supplier, and send it by email. He answers back with an offer. However, I am not convinced by the offer, and I want to see if anyone can give a better one." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:68 -msgid "I decide to push competition a bit and set up a Purchase Tender, that Odoo will send to a list of suppliers I specified. Out of the 8 offers I receive, one gets my attention and I decide to go ahead with that one." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:72 -msgid "I confirm the order to the supplier by creating a Purchase Order from the PT, and Odoo automatically asks delivery of the items to the supplier." -msgstr "" - -#: ../../purchase/overview/process/difference.rst:77 -#: ../../purchase/purchases/master/suppliers.rst:16 -#: ../../purchase/purchases/master/uom.rst:22 -#: ../../purchase/purchases/rfq/3_way_matching.rst:18 -#: ../../purchase/purchases/rfq/analyze.rst:24 -#: ../../purchase/purchases/rfq/bills.rst:31 -#: ../../purchase/purchases/rfq/create.rst:16 -#: ../../purchase/purchases/rfq/reception.rst:14 -#: ../../purchase/purchases/tender/partial_purchase.rst:14 -#: ../../purchase/replenishment/flows/dropshipping.rst:13 -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:58 -#: ../../purchase/replenishment/flows/warning_triggering.rst:21 -msgid "Configuration" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:79 -msgid "If you want to know how to create a **Purchase Order**, read the documentation on :doc:`from_po_to_invoice`" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:82 -msgid "If you want to know how to create a **RfQ**, read the documentation on :doc:`../../purchases/rfq/create`" -msgstr "" - -#: ../../purchase/overview/process/difference.rst:85 -msgid "If you want to know how to create a **Purchase Tender**, read the documentation on :doc:`../../purchases/tender/manage_multiple_offers`" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:3 -msgid "From purchase order to invoice and receptions" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:5 -msgid "For most of your everyday purchases, chances are you already know where to purchase and at what price. For these cases, a simple Purchase Order (PO) will allow you to handle the whole process." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:9 -msgid "In Odoo, a purchase order can be created as is, but can also be the result of a Request for Quotation or of a Purchase Tender. Therefore, every purchase made in Odoo has a PO." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:13 -msgid "The PO will generate an invoice, and depending on the contract with your supplier, you will be required to pay the invoice before or after delivery." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:18 -msgid "Install the Purchase Management application" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:20 -msgid "From the **Apps** application, search and install the **Purchase Management** application." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:27 -msgid "Creating a Purchase Order" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:29 -msgid "In the **Purchases** app, open the **Purchase** menu and click on **Purchase Orders**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:32 -msgid "In the **Purchase Orders** window, click on **Create**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:37 -msgid "From the new window, insert the **Vendor** and type in the **Order Date**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:40 -msgid "In the **Products** section, click on **Add an item**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:45 -msgid "Select your product from the list and add a description if necessary." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:47 -msgid "The **Scheduled Date** menu corresponds to the expected delivery date." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:49 -msgid "Type in the quantity which you wish to purchase, then click on **Save** and on **Confirm Order**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:53 -msgid "If you wish to go through the complete flow and create a **Request for Quotation** for this order, refer to the document on :doc:`../../purchases/rfq/create`" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:57 -msgid "As you can see, the status of the PO has switched to ``Purchase Order``." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:63 -msgid "Registering invoice, payments and receiving products" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:65 -msgid "Depending on the contract you have with your supplier, you can either pay for the purchase upon delivery of the goods, or get the goods delivered after payment." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:70 -msgid "Payment upon or after reception" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:72 -msgid "Still from your purchase order, click on **Receive Products**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:74 -msgid "In the next page, check that the number of products received corresponds to the number ordered, then manually enter the delivered quantity and click on **Validate**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:81 -msgid "Go back to the PO. In the PO, a **Shipment** and an **Invoice** button have appeared." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:87 -msgid "Click on the **Invoices** button, then click on **Validate**. The invoice is now registered in the system. Click on **Register Payment**, insert the detail of the payment, and click on **Validate**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:94 -#: ../../purchase/overview/process/from_po_to_invoice.rst:124 -msgid "Your products are now ready for picking and storage, and the invoice is marked as paid." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:98 -msgid "Upfront payment" -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:100 -msgid "From the **Purchase Order** page, open the **Invoices** tab, then click on **Create**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:103 -msgid "In the next page, click on **Validate**. The invoice is now registered in the system. Click on **Register Payment**, insert the detail of the payment, and click on **Validate**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:110 -msgid "Go back to the PO. In the PO, a **Shipment** tab and an **Invoice** tab have appeared." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:116 -msgid "Click on **Receive Products**, then in the new page, click on **Validate**." -msgstr "" - -#: ../../purchase/overview/process/from_po_to_invoice.rst:121 -msgid "A window will appear, asking if you wish to process every item at once. Click on **Apply**." -msgstr "" - #: ../../purchase/purchases.rst:3 msgid "Purchases" msgstr "" @@ -256,315 +29,95 @@ msgid "Master Data" msgstr "" #: ../../purchase/purchases/master/import.rst:3 -msgid "How to import supplier pricelists?" +msgid "Import vendors pricelists" msgstr "" -#: ../../purchase/purchases/master/import.rst:6 -msgid "Introduction" +#: ../../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:8 -msgid "Big companies use to import supplier pricelists day to day. Indeed, prices are always changing and you need to get price up to date to deal with a high number of products." +#: ../../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 "" -#: ../../purchase/purchases/master/import.rst:12 -msgid "To manage supplier prices on product form, read this document (:doc:`suppliers`). Here we will show you how to import customer prices." +#: ../../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:16 -msgid "Required configuration" +#: ../../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:18 -msgid "In purchase settings, you have 2 options:" +#: ../../purchase/purchases/master/import.rst:21 +msgid "Import a pricelist" msgstr "" -#: ../../purchase/purchases/master/import.rst:20 -msgid "Manage vendor price on the product form" +#: ../../purchase/purchases/master/import.rst:23 +msgid "To import go to :menuselection:`Purchase --> Vendor Pricelists`" msgstr "" -#: ../../purchase/purchases/master/import.rst:22 -msgid "Allow using and importing vendor pricelists" +#: ../../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:24 -msgid "Here we are selecting: **Allow using and importing vendor pricelists**" +#: ../../purchase/purchases/master/import.rst:28 +msgid "See below a template of the columns used." msgstr "" -#: ../../purchase/purchases/master/import.rst:30 -msgid "Import vendor pricelists" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:32 -msgid "There are 2 scenarios: import the vendor pricelist for the first time, or update an existing vendor pricelist. In both scenarios, we assume your product list and vendor list is updated and you want to import the price list of vendors for a given product." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:40 -msgid "To import a list from a document, the best pratice is to export first to get an example of data formating and a proper header to reimport." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:50 -msgid "Import the list for the first time" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:53 -msgid "Prepare the document" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:55 -msgid "In :menuselection:`Purchase --> Purchase --> Supplier Pricelists`, export a template of document to get import/export compatible and get the right format to import in mass. Create manually a data and export it (:menuselection:`select --> Action --> Export`)" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:63 -msgid "Here is the list of fields you can import:" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:66 -msgid "**Header of the document to import (csv, xls)**" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:66 -msgid "**Meaning and how to get it**" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:66 -msgid "**Example**" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:68 -msgid "name_id" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:68 -msgid "Vendor ID -> export supplier list to get it" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:68 -msgid "\\_\\_export\\_\\_.res\\_partner\\_12" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:70 -msgid "product_code" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:70 -msgid "Vendor product Code -> free text" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:70 -msgid "569874" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:72 -msgid "price" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:72 -msgid "Vendor Price -> free text" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:72 -msgid "1500" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:74 -msgid "product_tmpl_id.id" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:74 -msgid "Product Template ID -> export you product list to get it" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:74 -msgid "\\_\\_export\\_\\_.product_template_13" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:76 -msgid "currency_id.id" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:76 -msgid "Currency -> to get it export the currency list" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:78 -msgid "date_end" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:78 -msgid "End date of the price validity" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:78 -msgid "2015-10-22" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:80 -msgid "min_qty" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:80 -msgid "Minimal quantity to purchase from this vendor" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:80 -msgid "2" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:82 -msgid "product_id.id" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:82 -msgid "Product Variante name -> export your variant list to get it" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:82 -msgid "\\_\\_export\\_\\_.product\\_13" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:84 -msgid "date_start" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:84 -msgid "Start date of price validity" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:84 -msgid "2015-12-31" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:87 -msgid "You obtain a document which can be imported, fill in your vendor pices" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:92 -msgid "Import this document in Odoo. Click on **Import** in the list view and upload your document. You can validate and check error. Once the system tells you everything is ok, you can import the list." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:102 -msgid "After the import, the **Vendors** section in **Inventory** tab of the product form is filled in." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:106 -msgid "Update the vendor pricelist" -msgstr "" - -#: ../../purchase/purchases/master/import.rst:108 -msgid "When the pricelist of your suppliers change, it is necessary to update existing prices." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:111 -msgid "Follow the procedure of the first scenario in order to export existing data from :menuselection:`Purchases --> Purchase --> Vendor Pricelist`. Select everything, and export from the **Action** menu." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:115 -msgid "Change price, end date, add a line, change a supplier, ... and then reimport in Odoo. Thanks to the ID, the list will be updated. Either the id is recognized and the line is updated or the ID is not known by Odoo and it will create a new pricelist line." -msgstr "" - -#: ../../purchase/purchases/master/import.rst:120 -msgid "After the import, the **Vendors** section in **Inventory** tab of the product form is updated." +#: ../../purchase/purchases/master/import.rst:33 +msgid "`Template download `__" msgstr "" #: ../../purchase/purchases/master/suppliers.rst:3 -msgid "How to set several suppliers on a product?" +msgid "Set multiple vendors on a product" msgstr "" #: ../../purchase/purchases/master/suppliers.rst:5 -msgid "Keeping track of your vendors can be a real burden in day-to-day business life. Prices can change and you might have several suppliers for one product. With Odoo you have the possibility to directly link vendors with the corresponding product and specify prices automatically the first time you purchase them." +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 "We will take the following example: We need to buy ``5 t-shirts``. We found a **Vendor**; called ``Bob&Jerry's`` and we want to issue a request for quotation." +msgid "To use this feature, go to :menuselection:`Purchases --> Products`, then select a product." msgstr "" -#: ../../purchase/purchases/master/suppliers.rst:19 -msgid "Install the purchase module" +#: ../../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:21 -msgid "The first step to set your suppliers on your products is to install the purchase module. Go into your **App** module and install the **Purchase** module." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:29 -msgid "By installing the purchase module, the inventory and invoicing module will be installed as well." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:33 -msgid "Create a Vendor" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:35 -msgid "The second step is to create a vendor. In this case we'll create the vendor ``Bob&Jerry's``. Enter the purchase module, select :menuselection:`Purchase --> Vendors` and create a new vendor." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:39 -msgid "You can choose if the contact is a company or a person, fill in basic information such as address, phone, email,..." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:42 -msgid "If you did not create the contact from the purchase module you will need to go in the **Sales and Purchases** tab as well and indicate that the contact is a **Vendor** (see picture below). If the contact is created from the purchase module this box will be ticked automatically." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:51 -msgid "Create a product" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:53 -msgid "Next we can create the product we want to buy. We don't know the price of the t-shirt yet because we still need to issue our **Request for Quotation**." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:57 -msgid "To create a product enter your purchase module select :menuselection:`Purchase --> Products` and create a new product." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:60 -msgid "We will call our product ``T-shirt`` and specify that the product can be sold and purchased." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:67 -msgid "Add Vendors to the product" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:69 -msgid "The next action is to add vendors to the product. There are two ways to handle this. If you issue a purchase order for the first time Odoo will automatically link the vendor and its price to the product. You can also add vendors manually" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:75 -msgid "By issuing a first Purchase Order to new vendor" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:77 -msgid "When issuing a purchase order for the first time to a vendor, he will automatically be linked to the product by Odoo. For our example let's say that we issue a first purchase order to ``Bob&Jerry's`` for ``5 t-shirts`` at ``12.35 euros / piece``." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:82 -msgid "First create your purchase order with the correct product and supplier (see picture below, or the documentation page :doc:`../rfq/create` for more information)" -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:89 -msgid "When we save and validate the purchase order the vendor will automatically be added to the product's vendors list. To check this enter the purchase module, select :menuselection:`Purchase --> Products` and select our T-shirt product. By opening the **Inventory** tab we notice that our vendor and its price has automatically been added." -msgstr "" - -#: ../../purchase/purchases/master/suppliers.rst:98 +#: ../../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:103 -msgid "By adding manually" +#: ../../purchase/purchases/master/suppliers.rst:24 +msgid "Add price & quantity as well as a validity period" msgstr "" -#: ../../purchase/purchases/master/suppliers.rst:105 -msgid "We can of course also add vendors and vendors information manually. On the same page than previously, simply click on **Edit** and click the **Add an item** button." +#: ../../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:112 -msgid "When adding a new **Vendor** you are also able to add extra information such as the vendor product name or code, the validity of the price and the eventual minimum quantity required. These informations can be added and modified for existing vendors by simply clicking on the vendors line." +#: ../../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 "How to purchase in different unit of measures than sales?" +msgid "Purchase in different unit of measures than sales" msgstr "" #: ../../purchase/purchases/master/uom.rst:5 @@ -680,55 +233,47 @@ msgid "It is now possible to input **square meters** as Unit of measure and a ** msgstr "" #: ../../purchase/purchases/rfq.rst:3 -msgid "Request for Quotations" +msgid "Request for Quotation and Purchase Orders" msgstr "" #: ../../purchase/purchases/rfq/3_way_matching.rst:3 -msgid "How to determine if a vendor bill should be paid (3-way matching)" +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, the bill should maybe not be paid until the products have actually been received." +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 is called the **3-way matching**. It refers to the comparison of the information appearing on the Purchase Order, the Vendor Bill and the Receipt." +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 to avoid paying incorrect or fraudulent vendor bills." +msgid "The 3-way matching helps you avoid paying incorrect or fraudulent vendor bills." msgstr "" #: ../../purchase/purchases/rfq/3_way_matching.rst:20 -msgid "Go in :menuselection:`Purchase --> Configuration --> Settings` and activate the 3-way matching." +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:30 -msgid "Should I pay this vendor bill?" +#: ../../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 "Once this setting has been activated, a new information appears on the vendor bill, defining whether the bill should be paid or not. There are three possible values:" +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:36 -msgid "*Use case 1*: I have received the ordered products." -msgstr "" - -#: ../../purchase/purchases/rfq/3_way_matching.rst:43 -msgid "*Use case 2*: I have not received the ordered products." -msgstr "" - -#: ../../purchase/purchases/rfq/3_way_matching.rst:50 -msgid "*Use case 3*: the quantities do not match across the Purchase Order, Vendor Bill and Receipt." -msgstr "" - -#: ../../purchase/purchases/rfq/3_way_matching.rst:59 -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." +#: ../../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 "How to analyze the performance of my vendors?" +msgid "Analyze the performance of my vendors" msgstr "" #: ../../purchase/purchases/rfq/analyze.rst:5 @@ -756,7 +301,6 @@ msgid "For example, an IT products reseller that issues dozens of purchase order msgstr "" #: ../../purchase/purchases/rfq/analyze.rst:27 -#: ../../purchase/purchases/tender/partial_purchase.rst:17 msgid "Install the Purchase Management module" msgstr "" @@ -769,92 +313,79 @@ msgid "Issue some purchase orders" msgstr "" #: ../../purchase/purchases/rfq/analyze.rst:38 -msgid "Of course, in order to analyze your vendors' performance, you need to issue some **Request For Quotations** (RfQ) and confirm some **Purchase Orders**. If you want to know how to generate a purchase order, please read the documentation :doc:`../../overview/process/from_po_to_invoice`." +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:44 +#: ../../purchase/purchases/rfq/analyze.rst:43 msgid "Analyzing your vendors" msgstr "" -#: ../../purchase/purchases/rfq/analyze.rst:47 +#: ../../purchase/purchases/rfq/analyze.rst:46 msgid "Generate flexible reports" msgstr "" -#: ../../purchase/purchases/rfq/analyze.rst:49 +#: ../../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:60 +#: ../../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:67 +#: ../../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:77 +#: ../../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:81 +#: ../../purchase/purchases/rfq/analyze.rst:80 msgid "Customize reports" msgstr "" -#: ../../purchase/purchases/rfq/analyze.rst:83 +#: ../../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:97 +#: ../../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/analyze.rst:103 -#: ../../purchase/purchases/rfq/create.rst:76 -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:86 -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:81 -#: ../../purchase/purchases/tender/partial_purchase.rst:77 -msgid ":doc:`../../overview/process/from_po_to_invoice`" -msgstr "" - #: ../../purchase/purchases/rfq/approvals.rst:3 -msgid "How to setup two levels of approval for purchase orders?" +msgid "Request managers approval for expensive orders" msgstr "" -#: ../../purchase/purchases/rfq/approvals.rst:6 -msgid "Two level approval setup" -msgstr "" - -#: ../../purchase/purchases/rfq/approvals.rst:8 -msgid "Double validation on purchases forces a validation when the purchased amount exceeds a certain limit." +#: ../../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 "Install **Purchase Management** module and then go to **General Settings** to configure the company data." +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:17 -msgid "Set here the amount limit for second approval and set approval from manager side." +#: ../../purchase/purchases/rfq/approvals.rst:20 +msgid "Create a new Request for Quotation" msgstr "" -#: ../../purchase/purchases/rfq/approvals.rst:21 -#: ../../purchase/replenishment/flows/purchase_triggering.rst:47 -msgid "Process" +#: ../../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:23 -msgid "Logged as a purchase user, create a purchase order for more than the amount set above, and confirm it. The purchase order is set in a state **To Approve**" +#: ../../purchase/purchases/rfq/approvals.rst:31 +msgid "Approve the order" msgstr "" -#: ../../purchase/purchases/rfq/approvals.rst:29 -msgid "The manager gets the order to approve and validates the final order." +#: ../../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:34 +#: ../../purchase/purchases/rfq/approvals.rst:37 msgid "Once approved, the purchase order follows the normal process." msgstr "" #: ../../purchase/purchases/rfq/bills.rst:3 -msgid "How to control supplier bills?" +msgid "Control supplier bills" msgstr "" #: ../../purchase/purchases/rfq/bills.rst:5 @@ -1066,7 +597,7 @@ msgid "When creating a vendor bill and selecting the appropriate purchase order, msgstr "" #: ../../purchase/purchases/rfq/cancel.rst:3 -msgid "How to cancel a purchase order?" +msgid "Cancel a purchase order" msgstr "" #: ../../purchase/purchases/rfq/cancel.rst:5 @@ -1086,192 +617,184 @@ msgid "The first step to create a **Purchase Order** is to create a **Request fo msgstr "" #: ../../purchase/purchases/rfq/cancel.rst:25 -msgid "To learn more about the purchase order process, read the documentation page :doc:`../../overview/process/from_po_to_invoice`" -msgstr "" - -#: ../../purchase/purchases/rfq/cancel.rst:30 msgid "Cancel your Purchase Order" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:33 +#: ../../purchase/purchases/rfq/cancel.rst:28 msgid "Use case 1 : you didn't receive your goods yet" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:35 +#: ../../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:41 +#: ../../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:48 +#: ../../purchase/purchases/rfq/cancel.rst:43 msgid "Use case 2 : partially delivered goods" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:50 +#: ../../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:54 +#: ../../purchase/purchases/rfq/cancel.rst:49 msgid "Register good received and cancel backorder" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:56 +#: ../../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:66 +#: ../../purchase/purchases/rfq/cancel.rst:61 msgid "To learn more, see :doc:`reception`" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:68 +#: ../../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:75 +#: ../../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:83 +#: ../../purchase/purchases/rfq/cancel.rst:78 msgid "Create reverse transfer" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:85 +#: ../../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:93 +#: ../../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:99 +#: ../../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:104 -#: ../../purchase/purchases/rfq/reception.rst:120 +#: ../../purchase/purchases/rfq/cancel.rst:99 +#: ../../purchase/purchases/rfq/reception.rst:116 msgid ":doc:`bills`" msgstr "" -#: ../../purchase/purchases/rfq/cancel.rst:105 +#: ../../purchase/purchases/rfq/cancel.rst:100 msgid ":doc:`reception`" msgstr "" #: ../../purchase/purchases/rfq/create.rst:3 -msgid "How to create a Request for Quotation?" +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:12 -msgid "For more information on best uses, please read the chapter :doc:`../../overview/process/difference`" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:19 +#: ../../purchase/purchases/rfq/create.rst:16 msgid "Creating a Request for Quotation" msgstr "" -#: ../../purchase/purchases/rfq/create.rst:21 +#: ../../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:27 +#: ../../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 "Shipment" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Incoming Shipments" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Vendor Reference" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Reference of the sales order or bid sent by the vendor. It's used to do the matching when you receive the products as this reference is usually written on the delivery order sent by your vendor." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Order Date" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Depicts the date where the Quotation should be validated and converted into a purchase order." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Source Document" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Reference of the document that generated this purchase order request (e.g. a sales order)" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Deliver To" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "This will determine operation type of incoming shipment" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Drop Ship Address" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Put an address if you want to deliver directly from the vendor to the customer. Otherwise, keep empty to deliver to your own company." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Destination Location Type" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Technical field used to display the Drop Ship Address" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "Incoterm" -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:0 -msgid "International Commercial Terms are a series of predefined commercial terms used in international transactions." -msgstr "" - -#: ../../purchase/purchases/rfq/create.rst:35 +#: ../../purchase/purchases/rfq/create.rst:32 msgid "View *Request for Quotation* in our Online Demonstration" msgstr "" -#: ../../purchase/purchases/rfq/create.rst:37 +#: ../../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:51 +#: ../../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:57 +#: ../../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:62 +#: ../../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:68 +#: ../../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 "How to control product received? (entirely & partially)" +msgid "Control product received (entirely & partially)" msgstr "" #: ../../purchase/purchases/rfq/reception.rst:5 @@ -1327,282 +850,196 @@ msgid "From the purchase application, create a purchase order with a few product msgstr "" #: ../../purchase/purchases/rfq/reception.rst:67 -msgid "See the documentation page :doc:`../../overview/process/from_po_to_invoice` for a full overview of the purchase process." -msgstr "" - -#: ../../purchase/purchases/rfq/reception.rst:71 msgid "Receive Products" msgstr "" -#: ../../purchase/purchases/rfq/reception.rst:73 +#: ../../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:81 +#: ../../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:87 +#: ../../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:96 +#: ../../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:103 +#: ../../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:107 +#: ../../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:114 +#: ../../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:121 +#: ../../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 Tenders" +msgid "Purchase Agreements" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:3 -msgid "How to manage Blanket Orders" +#: ../../purchase/purchases/tender/blanket_orders.rst:3 +msgid "Manage Blanket Orders" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:5 -msgid "A **Blanket Order** is a contract between you (the customer) and your supplier. It is used to negotiate a discounted price. The supplier is benefited by the economies of scale inherent in a large order. You are benefited by being allowed to take multiple smaller deliveries over a period of time, at a lower price, without paying for the large order immediately. Each small periodic delivery is called a release or call-off." +#: ../../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/manage_blanket_orders.rst:12 -msgid "As the blanket order is a contract, it will have some prearranged conditions. These usually include:" +#: ../../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/manage_blanket_orders.rst:15 -msgid "Total quantity of each product to be delivered" +#: ../../purchase/purchases/tender/blanket_orders.rst:20 +msgid "Start a Blanket Order" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:17 -msgid "Completion deadline, by which you must take delivery of the total quantity" +#: ../../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/manage_blanket_orders.rst:19 -msgid "Unit price for each product" +#: ../../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/manage_blanket_orders.rst:21 -msgid "Delivery lead time in days for each release" +#: ../../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/manage_blanket_orders.rst:24 -msgid "Activate the Purchase Agreements" +#: ../../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/manage_blanket_orders.rst:26 -msgid "The Blanket Order function is provided by the Purchase Agreements feature. By default, the Purchase Agreements is not activated. To be able to use blanket orders, you must first activate the option." +#: ../../purchase/purchases/tender/blanket_orders.rst:41 +msgid "RFQ from the Blanket Order" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:30 -msgid "In the Purchases module, open the Configuration menu and click on Settings. In the **Orders** section, locate the **Purchase Agreements** and tick the box, then click on **Save**." +#: ../../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/manage_blanket_orders.rst:38 -msgid "Create a Blanket Order" +#: ../../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/manage_blanket_orders.rst:40 -msgid "To create a new blanket order, open :menuselection:`Purchase --> Purchase Agreements`." +#: ../../purchase/purchases/tender/blanket_orders.rst:51 +msgid "Vendors prices on your product" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:45 -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:39 -msgid "In the Purchase Agreements window, click on **Create**. A new Purchase Agreement window opens." +#: ../../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/manage_blanket_orders.rst:48 -msgid "In the **Agreement Type** field, choose Blanket Order." +#: ../../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/manage_blanket_orders.rst:50 -msgid "Choose the **Vendor** with whom you will make the agreement." +#: ../../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/manage_blanket_orders.rst:52 -msgid "Set the **Agreement Deadline** as per the conditions of the agreement." +#: ../../purchase/purchases/tender/call_for_tender.rst:3 +msgid "Manage Call for Tender" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:54 -msgid "Set the **Ordering Date** to the starting date of the contract." +#: ../../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/manage_blanket_orders.rst:56 -msgid "Leave the **Delivery Date** empty because we will have different delivery dates with each release." +#: ../../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/manage_blanket_orders.rst:59 -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:52 -msgid "In the **Products** section, click on **Add an item**. Select products in the Product list, then insert **Quantity**. You can add as many products as you wish." +#: ../../purchase/purchases/tender/call_for_tender.rst:19 +msgid "Create a Call for Tender" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:66 -msgid "Click on **Confirm**." +#: ../../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/manage_blanket_orders.rst:68 -msgid "Now click on the button **New Quotation**. A RfQ is created for this vendor, with the products chosen on the PT. Repeat this operation for each release." +#: ../../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/manage_blanket_orders.rst:71 -msgid "Be careful to change the **Quantity** field on the RFQ. By default, the RFQ quantity will be for the entire remaining quantity. Your individual releases should be for some smaller quantity." +#: ../../purchase/purchases/tender/call_for_tender.rst:34 +msgid "Request new quotations from the Call for Tender" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:78 -msgid "When all of the releases (purchase orders) have been delivered and paid, you can click on **Validate** and **Done**." +#: ../../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/manage_blanket_orders.rst:81 -msgid "View `Purchase Agreements `__ in our Online Demonstration." +#: ../../purchase/purchases/tender/call_for_tender.rst:40 +msgid "Select the best offer" msgstr "" -#: ../../purchase/purchases/tender/manage_blanket_orders.rst:88 -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:83 -msgid ":doc:`../../overview/process/difference`" +#: ../../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/manage_multiple_offers.rst:3 -msgid "How to manage Purchase Tenders" +#: ../../purchase/purchases/tender/call_for_tender.rst:50 +msgid "Close the Call for Tender" msgstr "" -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:12 -msgid "For more information on best uses, please read the chapter `Request for Quotation, Purchase Tender or Purchase Order? `__" -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:17 -msgid "Activate the Purchase Tender function" -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:19 -msgid "By default, the Purchase Tender is not activated. To be able to use PTs, you must first activate the option." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:22 -msgid "In the Purchases module, open the Configuration menu and click on Settings. In the Purchase Order section, locate the **Calls for Tenders** and tick the box Allow using call for tenders... (advanced), then click on **Apply**." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:31 -msgid "Create a Purchase Tender" -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:33 -msgid "To create a new Purchase Tender, open :menuselection:`Purchase --> Purchase Agreements (PA)`." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:42 -msgid "In the **Agreement Type** field, choose Purchase Tender." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:44 -msgid "The **Agreement Deadline** field tells the vendors when to have their offers submitted." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:46 -msgid "The **Ordering Date** field tells the vendors when we will submit a purchase order to the chosen vendor." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:48 -msgid "The **Delivery Date** field tells the vendors when the product will have to be delivered." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:50 -msgid "You do not have to define a **Vendor**." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:59 -msgid "Click on **Confirm Call**." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:61 -msgid "Now click on the button **New Quotation**. A RfQ is created with the products chosen on the PT. Choose a **Vendor** and send the RfQ to the vendor. Repeat this operation for each vendor." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:68 -msgid "Once all the RfQs are sent, you can click on **Validate** on the PT." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:70 -msgid "The vendors will send their offers, you can update the RfQs accordingly. Then, choose the ones you want to accept by clicking on **Confirm Order** on the RfQs and **Cancel** the others." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:74 -msgid "You can now click on **Done** on the PT." -msgstr "" - -#: ../../purchase/purchases/tender/manage_multiple_offers.rst:76 -msgid "View `Purchase Tenders `__ in our Online Demonstration." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:3 -msgid "How to purchase partially at two vendors for the same purchase tenders?" -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:5 -msgid "For some Purchase Tenders (PT), you might sometimes want to be able to select only a part of some of the offers you received. In Odoo, this is made possible through the advanced mode of the **Purchase** module." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:10 -msgid "If you want to know how to handle a simple **Purchase Tender**, read the document on :doc:`manage_multiple_offers`." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:19 -msgid "From the **Apps** menu, install the **Purchase Management** app." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:25 -msgid "Activating the Purchase Tender and Purchase Tender advanced mode" -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:27 -msgid "In order to be able to select elements of an offer, you must activate the advanced mode." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:30 -msgid "To do so, go into the **Purchases** module, open the **Configuration** menu and click on **Settings**." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:33 -msgid "In the **Calls for Tenders** section, tick the option **Allow using call for tenders to get quotes from multiple suppliers(...)**, and in the **Advanced Calls for Tenders** section, tick the option **Advanced call for tender (...)** then click on **Apply**." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:42 -msgid "Selecting elements of a RFQ/Bid" -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:44 -msgid "Go to :menuselection:`Purchase --> Purchase Tenders`. Create a purchase tender containing several products, and follow the usual sequence all the way to the **Bid Selection** status." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:49 -msgid "When you closed the call, click on **Choose Product Lines** to access the list of products and the bids received for all of them." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:55 -msgid "Unroll the list of offers you received for each product, and click on the *v* symbol (**Confirm order**) next to the offers you wish to proceed with. The lines for which you've confirmed the order turn blue. When you're finished, click on **Generate PO** to create a purchase order for each product and supplier." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:64 -msgid "When you come back to you purchase tender, you can see that the status has switched to **PO Created** and that the **Requests for Quotations** now have a status of **Purchase Order** or **Cancelled**." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:72 -msgid "From there, follow the documentation :doc:`../../overview/process/from_po_to_invoice` to proceed with the delivery and invoicing." -msgstr "" - -#: ../../purchase/purchases/tender/partial_purchase.rst:76 -msgid ":doc:`manage_multiple_offers`" +#: ../../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 @@ -1614,143 +1051,116 @@ msgid "Replenishment Flows" msgstr "" #: ../../purchase/replenishment/flows/compute_date.rst:3 -msgid "How are the order date and scheduled dates computed?" +msgid "Schedule your receipts and deliveries" msgstr "" #: ../../purchase/replenishment/flows/compute_date.rst:5 -msgid "Scheduled dates are computed in order to be able to plan deliveries, receptions and so on. Depending on the habits of your company, Odoo automatically generates scheduled dates via the scheduler. The Odoo scheduler computes everything per line, whether it's a manufacturing order, a delivery order, a sale order, etc. The dates that are computed are dependent on the different leads times configured in Odoo." +msgid "To manage your supply chain scheduling, you will need to use Odoo *Lead Times*." msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:13 -msgid "Configuring lead times" +#: ../../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 "Configuring **lead times** is an essential move in order to compute scheduled dates. Lead times are the delays (in term of delivery, manufacturing, ...) promised to your different partners and/or clients. Configuration of the different lead times are made as follows:" +msgid "Vendor Lead Time" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:21 -msgid "On a product level" +#: ../../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:24 -msgid "Supplier lead time:" +#: ../../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:26 -msgid "The supplier lead time is the time needed for the supplier to deliver your purchased product. To configure the Supplier lead time select a product (from the Purchase module, go to :menuselection:`Purchase --> Product`), and go in the **Inventory** tab. You will have to add a **Vendor** to your product in order to select a supplier lead time." +#: ../../purchase/replenishment/flows/compute_date.rst:28 +msgid "Customer Lead Time" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:36 -msgid "It is possible to add more than one vendor per product and thus different delivery lead times depending on the vendor." +#: ../../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:39 -msgid "Once a vendor is selected, click on it to open its form and indicate its delivery lead time." +#: ../../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:46 -msgid "In this case security days have no influence, the scheduled delivery days will be equal to: Date of the purchase order + Delivery Lead Time." +#: ../../purchase/replenishment/flows/compute_date.rst:40 +msgid "Manufacturing lead time" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:50 -msgid "Customer lead time" +#: ../../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 "The customer lead time is the time needed to get your product from your store/warehouse to your customer. It can be configured for any product. Simply select a product (from the **Sales** module, go to :menuselection:`Sales --> Product`), and go into the **Sales** tab to indicate your customer lead time." +msgid "Configure Security Lead Times" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:62 -msgid "On the company level" +#: ../../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:64 -msgid "On company level, it is possible to parameter **security days** in order to cope with eventual delays and to be sure to meet your engagements. The idea is to subtract **backup** days from the computed scheduled date in case of delays." +#: ../../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:70 -msgid "Sales Safety days" +#: ../../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:72 -msgid "Sales Safety days are **back-up** days to ensure you will be able to deliver your clients engagements on time. They are margins of errors for delivery lead times. Security days are the same logic as the early wristwatch, in order to arrive on time. The idea is to subtract the numbers of security days from the calculation and thus to compute a scheduled date earlier than the one you promised to your client. That way you are sure to be able to keep your commitment." +#: ../../purchase/replenishment/flows/compute_date.rst:69 +msgid "Lead & security times in a use case" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:80 -msgid "To set up your security dates, go to the app :menuselection:`Settings --> General settings`, and click on **Configure your company data**." +#: ../../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 "Go the **Configuration** tab to indicate the number of safety days" +msgid "January 18: scheduled receipt date (19th January - 1 day of security lead time for Purchase)" msgstr "" -#: ../../purchase/replenishment/flows/compute_date.rst:93 -msgid "Note that you can in this menu configure a default **Manufacturing** lead time." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:97 -msgid "Purchase days" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:99 -msgid "Purchase days response to the same logic than sales security days." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:101 -msgid "They are margins of error for vendor lead times. When the system generates purchase orders for procuring products, they will be scheduled in order to cope with unexpected vendor delays. Purchase lead time can be found in the same menu as the sales safety days (see screenshot above)." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:108 -msgid "On route level" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:110 -msgid "The internal transfers due to the movement of stocks can also influence the computed date." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:113 -msgid "The delays due to internal transfers can be specified in the **Inventory** module when creating a new push rule for a new route." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:117 -msgid "Read the documentation :doc:`../../../../inventory/routes/concepts/push_rule` to learn more." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:125 -msgid "On document level:" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:128 -msgid "Requested date" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:130 -msgid "Odoo offers the possibility to indicate a requested date by the client straight on the sale order, under the tab **Other information**. If this date is earlier than the theoretically computed date, Odoo will automatically display a warning." -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:141 -msgid "As an example, you may sell a car today (January 1st), that is purchased on order, and you promise to deliver your customer within 20 days (January 20). In such a scenario, the scheduler may trigger the following events, based on your configuration:" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:146 -msgid "January 19: actual scheduled delivery (1 day of Sales Safety days)" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:148 -msgid "January 18: receive the product from your supplier (1 day of Purchase days)" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:151 -msgid "January 10: deadline to order at your supplier (9 days of supplier delivery lead time)" -msgstr "" - -#: ../../purchase/replenishment/flows/compute_date.rst:154 -msgid "January 8: trigger a purchase request to your purchase team, since the team needs on average 2 days to find the right supplier and order." +#: ../../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 "How to setup drop-shipping?" +msgid "Setup drop-shipping" +msgstr "" + +#: ../../purchase/replenishment/flows/dropshipping.rst:6 +#: ../../purchase/replenishment/multicompany/setup.rst:6 +msgid "Overview" msgstr "" #: ../../purchase/replenishment/flows/dropshipping.rst:8 @@ -1782,369 +1192,103 @@ msgid "In order to be able to invoice the delivery, you must set the invoice pol msgstr "" #: ../../purchase/replenishment/flows/purchase_triggering.rst:3 -msgid "How to trigger the purchase of products based on sales?" +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 "When you work in just-in-time, you don't manage stock so you directly order the product you need from your vendor." +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:11 -msgid "The usual flow is:" +#: ../../purchase/replenishment/flows/purchase_triggering.rst:12 +msgid "Configure the product" msgstr "" -#: ../../purchase/replenishment/flows/purchase_triggering.rst:13 -msgid "Create a sale order" +#: ../../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:15 -msgid "Purchase the product" +#: ../../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:17 -msgid "Receive and pay the bill" +#: ../../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:19 -msgid "Deliver your product" +#: ../../purchase/replenishment/flows/purchase_triggering.rst:27 +msgid "Create a sales order using Buy & MTO" msgstr "" -#: ../../purchase/replenishment/flows/purchase_triggering.rst:21 -msgid "Invoice your customer" +#: ../../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:24 -msgid "Product configuration" +#: ../../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:26 -msgid "In the purchases application, open the **Purchase** menu and click on **Products**. Open the product on which you want to do your purchases based on sales." +#: ../../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:30 -msgid "Next to Routes, tick **Buy** and **Make to order** as a procurement method. When you are generating sales order, Odoo will automatically reorder the same quantity through procurement." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:37 -msgid "Don't forget to set a vendor otherwise the rule won't be triggered." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:39 -msgid "You can also configure minimum stock rules that will trigger the purchase orders." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:43 -msgid "To know how to configure a minimum stock rule, please read the document :doc:`setup_stock_rule`." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:50 -msgid "Sale order" +#: ../../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 "To create a sale order, go to the **Sales** application, :menuselection:`Sales --> Sales order` and create a new sale order." +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:58 -msgid "After confirming it, you will see one **Delivery** associated with this sale order on the **button** on the top of it." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:64 -msgid "Click on the **Delivery** button to see the transfer order. The status of the outgoing shipment is **Waiting Another Operation**. It won't be done until the purchase order is confirmed and received." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:69 -msgid "Purchase order" -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:71 -msgid "The purchase order is automatically created. Go to the **Purchase** application :menuselection:`Purchase --> Request for Quotation`. The source document is the sale order that triggered the procurement." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:79 -msgid "If you make some more sales that trigger procurements to the same vendor, it will be added to the existing request for quotation. Once it is confirmed, the next procurements will create a new request for quotation." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:85 -msgid "Receipt and delivery" -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:87 -msgid "Go the the **Inventory** application. Click on **# To Receive** on the **Receipts** tile." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:93 -msgid "Select the receipt from your vendor and **Validate** it." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:98 -msgid "Go back to the **Inventory** dashboard. In the delivery order, click on **# To Do**. The delivery order is now ready to ship." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:104 -msgid "The status of the delivery changed from **Waiting Availability** to **Available**. Validate the transfer to confirm the delivery." -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:111 -msgid ":doc:`setup_stock_rule`" -msgstr "" - -#: ../../purchase/replenishment/flows/purchase_triggering.rst:112 -msgid ":doc:`warning_triggering`" +#: ../../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 "How to setup a minimum stock rule?" +msgid "Don’t run out of stock thanks to Reordering Rules" msgstr "" #: ../../purchase/replenishment/flows/setup_stock_rule.rst:5 -msgid "For some items you hold in stock, it might be useful to have rules making sure you never run out of stocks (for example, products with a high demand, or large items requiring a lot of storage space meaning they're harder to stock)." +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 "Odoo allows you to set up rules so that an automatic replenishment for those items is made, based on minimum stocks available." +msgid "Set a reordering rule" msgstr "" -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:14 -msgid "When should I use Reordering Rules?" +#: ../../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:16 -msgid "Reordering Rules work best for items that have a high demand and high flow. It will relieve you from a lot of work to focus on the rest of your activities knowing that stocks will always be right." +#: ../../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:20 -msgid "It can also be used when you have limited storage space and you need to keep large items in stock. In this case, you can keep as little as 1 item in stock, and have a new one ordered as a stock replenishment as soon as the item in stock is sold." +#: ../../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:26 -msgid "When should I avoid Reordering Rules?" +#: ../../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:28 -msgid "If you are offering a new product and don't know yet how fast it will go, you should handle stocks yourself first, and setup reordering rules only a few months into the sale to have better forecasts of the demand." +#: ../../purchase/replenishment/flows/setup_stock_rule.rst:33 +msgid "See also: :doc:`../../../inventory/management/misc/schedulers`" msgstr "" -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:32 -msgid "If you sell items that have a limited lifetime, such as fashion items, technology items, or products working together with a system that is meant to evolve, you have to be very well informed on when to stop automated replenishments, in order to avoid having to sell these items at a price that will not allow you to break even." +#: ../../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 "My company sells modern furniture. We sell a set of table and chairs that are available in 4 seatings and 6 seatings." +msgid "Troubleshooting" msgstr "" -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:44 -msgid "To keep things simple, we stock tables and chairs separately, but sell them all together to our clients as a kit. In order to make sure we can always deliver a complete set of table and chairs, I setup a Reordering Rule for the chairs to make sure I always have at least 10 chairs in stock, but no more than 20. This way, I can sell up to 5 sets of table at once while keeping my stock low enough not to eat up all my storage space." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:52 -msgid "The last table I sold was a 4 seatings, and there were 12 chairs left in my stock. Because the stock in chairs is now only 8 chairs, Odoo will automatically order 12 new chairs to fill up my stock to the maximum amount." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:61 -msgid "Set up your product" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:63 -msgid "In the Purchases module, open the Purchase menu and click on Products. Open the product to which you would like to add a Reordering Rule (or create a new one)." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:67 -msgid "3 conditions for correct reordering rule :" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:69 -msgid "In :menuselection:`General information --> Product type`, make the product stockable (as soon as this is done, the icon \"Reordering rule will appear)" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:71 -msgid "In :menuselection:`Inventory --> route`, tick the \"Buy\" box (and untick the Make To Order box)" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:73 -msgid "Select a vendor (don't forget to put a minimal quantity greater than 0)" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:76 -msgid "Create a reordering rule" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:78 -msgid "Click on the Reordering Rules tab, click on Create. A new page opens." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:83 -msgid "By default, Reordering Rules in Odoo are named as \"OP/XXXXX\" but you are free to use any nomenclature. You can modify it via the **Name** field." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:86 -msgid "The **Product** field is the product you are creating the rule for." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:88 -msgid "Select the warehouse to which the product should be delivered in the **Warehouse** field." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:91 -msgid "If you have configured multiple warehouses and location, specify the location in which the product will be stored in the **Location** field." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:96 -msgid ":doc:`../../../inventory/settings/warehouses/difference_warehouse_location`" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:102 -msgid "In the **Minimum Quantity** field, insert the quantity to which the system will trigger a new order for replenishment." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:105 -msgid "In the **Maximum Quantity** field, insert the maximum of items that has to be stocked. The replenishing order will be based on that quantity to reorder." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:109 -msgid "The **Quantity Multiple** is the lowest number of items that can be ordered at once. For instance, some items may be only available for purchase in a set of 2." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:113 -msgid "In the Misc section, the **Active** box allows you to activate or deactivate the rule." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:116 -msgid "In the **Lead Time** section, you can enter:" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:118 -msgid "the number of Day(s) to purchase: correspond to the number of days for the supplier to receive the order" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:120 -msgid "the number of Day(s) to get the products" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:122 -msgid "By default, the lead times are in calendar days. You can change that in :menuselection:`Inventory --> Configuration --> Settings --> Minimum Stock Rules`" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:125 -msgid "When you have entered all the info, click on Save." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:127 -msgid "From now on, every time a product with a reordering rule reaches the minimum stock, the system will automatically send a RfQ to your supplier based on your maximum quantity to replenish your stock." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:131 -msgid "The replenishments will take place when the scheduler in the Inventory module runs. By default in Odoo, the schedulers will run every night at 12:00PM." -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:135 -msgid "To know how to configure and run the schedulers manually, read the document on :doc:`../../../inventory/management/misc/schedulers`" -msgstr "" - -#: ../../purchase/replenishment/flows/setup_stock_rule.rst:140 -msgid ":doc:`../../../inventory/management/misc/schedulers`" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:3 -#: ../../purchase/replenishment/flows/warning_triggering.rst:69 -msgid "How to trigger a warning when purchasing at a specific vendor?" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:8 -msgid "The **Warning Messages and Alerts** module allow you to configure alerts on the customers and vendors or products." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:11 -msgid "You can select the following types of warnings and create different warnings for purchases and sales:" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:14 -msgid "Warning: This option displays the warning message during the process, but allows the user to continue." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:17 -msgid "Blocking Message: The message displays a warning message, but the user cannot continue the process further." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:24 -msgid "Module Installation" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:26 -msgid "First, you need to install the **Warning Messages and Alerts** module. Go to **Apps** and look for it (don't forget to remove the **Apps** filter)." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:33 -msgid "Vendor or Customer warnings" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:35 -msgid "Go to :menuselection:`Purchases --> Vendors` or to :menuselection:`Sales --> Customers`." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:37 -msgid "Open the vendor or the customer and click on the **Warnings** tab." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:42 -#: ../../purchase/replenishment/flows/warning_triggering.rst:62 -msgid "The available warnings are:" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:44 -msgid "Warning on the **Sales Order**" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:46 -msgid "Warning on the **Purchase Order**" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:48 -msgid "Warning on the **Picking**" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:50 -msgid "Warning on the **Invoice**" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:53 -msgid "Product Warnings" -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:55 -msgid "Go to :menuselection:`Purchases --> Products` or to :menuselection:`Sales --> Products`." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:57 -msgid "Open the product and click on the **Notes** tab." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:64 -msgid "Warning when selling this product." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:66 -msgid "Warning when Purchasing this product." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:71 -msgid "Go to the Purchases application, click on :menuselection:`Purchase --> Vendors`. Go to the **Warnings** tab." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:74 -msgid "Under **Warning on the Purchase Order**, choose **Warning** and write your warning." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:80 -msgid "Create a **Request for Quotation**. Go to :menuselection:`Purchase --> Request for Quotation` and click on **Create**. Choose the vendor on which a warning was set." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:84 -msgid "When choosing the vendor, the warning will appear." -msgstr "" - -#: ../../purchase/replenishment/flows/warning_triggering.rst:90 -msgid "If you set a blocking message instead of a warning message, you won't be able to choose the vendor." +#: ../../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 @@ -2199,55 +1343,3 @@ msgstr "" msgid "In order to be able to manage the inter-company rules, be sure that your user has the rights to manage the companies." msgstr "" -#: ../../purchase/replenishment/trouble_shooting.rst:3 -msgid "Trouble-Shooting" -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:3 -msgid "How to check that everything is working fine?" -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:6 -msgid "Vendor Bills" -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:8 -msgid "Even if you don't have the rights to the accounting application, you can still control the vendor bills." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:11 -msgid "Go to the **Purchases** application: :menuselection:`Control --> Vendor Bills`." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:17 -msgid "Incoming Products" -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:19 -msgid "Even if you don't have the rights to the inventory application, you can still control the incoming products." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:22 -msgid "Go to the **Purchases** application: :menuselection:`Control --> Incoming Products`." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:28 -msgid "Procurements exceptions" -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:30 -msgid "Here, you need the **Inventory Manager** access rights." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:32 -msgid "Go to the **Inventory** application: :menuselection:`Control --> Procurement Exceptions`." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:37 -msgid "To understand why the procurement is not running, open the exception and check the message in the chatter." -msgstr "" - -#: ../../purchase/replenishment/trouble_shooting/is_everything_ok.rst:43 -msgid "Usually, the problem is located on the procurement rules. Either there are no stock rules, or there are no vendor associated to a product." -msgstr "" - diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 0aad84993..06605851c 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 11.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-07-23 12:10+0200\n" +"POT-Creation-Date: 2018-10-19 10:03+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -160,441 +160,321 @@ msgstr "" msgid "Invoicing Method" msgstr "" -#: ../../sales/invoicing/services.rst:3 -msgid "Services" +#: ../../sales/invoicing/down_payment.rst:3 +msgid "Request a down payment" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:3 -msgid "How to invoice milestones of a project?" +#: ../../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/services/milestones.rst:5 -msgid "There are different kind of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) or a fixed price contract (e.g. a project)." +#: ../../sales/invoicing/down_payment.rst:10 +msgid "First time you request a down payment" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:9 -msgid "In this section, we will have a look at how to invoice milestones of a project." +#: ../../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/services/milestones.rst:12 -msgid "Milestone invoicing can be used for expensive or large scale projects, with each milestone representing a clear sequence of work that will incrementally build up to the completion of the contract. For example, a marketing agency hired for a new product launch could break down a project into the following milestones, each of them considered as one service with a fixed price on the sale order :" +#: ../../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/services/milestones.rst:19 -msgid "Milestone 1 : Marketing strategy audit - 5 000 euros" +#: ../../sales/invoicing/down_payment.rst:22 +msgid "You will then see the invoice for the down payment." msgstr "" -#: ../../sales/invoicing/services/milestones.rst:21 -msgid "Milestone 2 : Brand Identity - 10 000 euros" +#: ../../sales/invoicing/down_payment.rst:27 +msgid "On the subsequent or final invoice, any prepayment made will be automatically deducted." msgstr "" -#: ../../sales/invoicing/services/milestones.rst:23 -msgid "Milestone 3 : Campaign launch & PR - 8 500 euros" +#: ../../sales/invoicing/down_payment.rst:34 +msgid "Modify the income account and customer taxes" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:25 -msgid "In this case, an invoice will be sent to the customer each time a milestone will be successfully reached. That invoicing method is comfortable both for the company which is ensured to get a steady cash flow throughout the project lifetime and for the client who can monitor the project's progress and pay in several times." +#: ../../sales/invoicing/down_payment.rst:36 +msgid "From the products list, search for *Down Payment*." msgstr "" -#: ../../sales/invoicing/services/milestones.rst:32 -msgid "You can also use milestones to invoice percentages of the entire project. For example, for a million euros project, your company might require a 15% upfront payment, 30% at the midpoint and the balance at the contract conclusion. In that case, each payment will be considered as one milestone." +#: ../../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/services/milestones.rst:39 -#: ../../sales/invoicing/services/reinvoice.rst:26 -#: ../../sales/invoicing/services/reinvoice.rst:95 -#: ../../sales/invoicing/services/support.rst:17 -#: ../../sales/send_quotations/quote_template.rst:10 -msgid "Configuration" +#: ../../sales/invoicing/expense.rst:3 +msgid "Re-invoice expenses to customers" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:42 -msgid "Install the Sales application" +#: ../../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/services/milestones.rst:44 -#: ../../sales/invoicing/services/reinvoice.rst:28 -msgid "In order to sell services and to send invoices, you need to install the **Sales** application, from the **Apps** icon." +#: ../../sales/invoicing/expense.rst:12 +#: ../../sales/invoicing/time_materials.rst:64 +msgid "Expenses configuration" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:51 -msgid "Create products" +#: ../../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/services/milestones.rst:53 -msgid "In Odoo, each milestone of your project is considered as a product. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:" +#: ../../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/services/milestones.rst:57 -msgid "**Name**: Strategy audit" +#: ../../sales/invoicing/expense.rst:22 +#: ../../sales/invoicing/time_materials.rst:74 +msgid "Add expenses to your sales order" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:59 -#: ../../sales/invoicing/services/support.rst:50 -msgid "**Product Type**: Service" +#: ../../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/services/milestones.rst:61 -msgid "**Invoicing Policy**: Delivered Quantities, since you will invoice your milestone after it has been delivered" +#: ../../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/services/milestones.rst:64 -msgid "**Track Service**: Manually set quantities on order, as you complete each milestone, you will manually update their quantity from the **Delivered** tab on your sale order" +#: ../../sales/invoicing/expense.rst:33 +#: ../../sales/invoicing/time_materials.rst:85 +msgid "Here, we are creating a *Hotel* product:" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:72 -msgid "Apply the same configuration for the others milestones." +#: ../../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/services/milestones.rst:75 -msgid "Managing your project" +#: ../../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/services/milestones.rst:78 -msgid "Quotations and sale orders" +#: ../../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/services/milestones.rst:80 -msgid "Now that your milestones (or products) are created, you can create a quotation or a sale order with each line corresponding to one milestone. For each line, set the **Ordered Quantity** to ``1`` as each milestone is completed once. Once the quotation is confirmed and transformed into a sale order, you will be able to change the delivered quantities when the corresponding milestone has been achieved." +#: ../../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/services/milestones.rst:91 +#: ../../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/services/milestones.rst:93 -msgid "Let's assume that your first milestone (the strategy audit) has been successfully delivered and you want to invoice it to your customer. On the sale order, click on **Edit** and set the **Delivered Quantity** of the related product to ``1``." +#: ../../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/services/milestones.rst:99 -msgid "As soon as the above modification has been saved, you will notice that the color of the line has changed to blue, meaning that the service can now be invoiced. In the same time, the invoice status of the SO has changed from **Nothing To Invoice** to **To Invoice**" +#: ../../sales/invoicing/milestone.rst:33 +msgid "You can then invoice that first milestone." msgstr "" -#: ../../sales/invoicing/services/milestones.rst:104 -msgid "Click on **Create invoice** and, in the new window that pops up, select **Invoiceable lines** and validate. It will create a new invoice (in draft status) with only the **strategy audit** product as invoiceable." +#: ../../sales/invoicing/proforma.rst:3 +#: ../../sales/invoicing/proforma.rst:22 +msgid "Send a pro-forma invoice" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:112 -msgid "In order to be able to invoice a product, you need to set up the **Accounting** application and to configure an accounting journal and a chart of account. Click on the following link to learn more: :doc:`../../../accounting/overview/getting_started/setup`" +#: ../../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/services/milestones.rst:117 -msgid "Back on your sale order, you will notice that the **Invoiced** column of your order line has been updated accordingly and that the **Invoice Status** is back to **Nothing to Invoice**." +#: ../../sales/invoicing/proforma.rst:13 +#: ../../sales/send_quotations/different_addresses.rst:10 +msgid "Activate the feature" msgstr "" -#: ../../sales/invoicing/services/milestones.rst:121 -msgid "Follow the same workflow to invoice your remaining milestones." +#: ../../sales/invoicing/proforma.rst:15 +msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature." msgstr "" -#: ../../sales/invoicing/services/milestones.rst:124 -msgid ":doc:`reinvoice`" +#: ../../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/services/milestones.rst:125 -#: ../../sales/invoicing/services/reinvoice.rst:185 -msgid ":doc:`support`" +#: ../../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/services/reinvoice.rst:3 -msgid "How to re-invoice expenses to your customers?" +#: ../../sales/invoicing/subscriptions.rst:3 +msgid "Sell subscriptions" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:5 -msgid "It often happens that your employees have to spend their personal money while working on a project for your client. Let's take the example of an employee paying a parking spot for a meeting with your client. As a company, you would like to be able to invoice that expense to your client." +#: ../../sales/invoicing/subscriptions.rst:5 +msgid "Selling subscription products will give you predictable revenue, making planning ahead much easier." msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:11 -msgid "In this documentation we will see two use cases. The first, very basic, consists of invoicing a simple expense to your client like you would do for a product. The second, more advanced, will consist of invoicing expenses entered in your expense system by your employees directly to your customer." +#: ../../sales/invoicing/subscriptions.rst:9 +msgid "Make a subscription from a sales order" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:18 -msgid "Use case 1: Simple expense invoicing" +#: ../../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/services/reinvoice.rst:20 -msgid "Let's take the following example. You are working on a promotion campaign for one of your customers (``Agrolait``) and you have to print a lot of copies. Those copies are an expense for your company and you would like to invoice them." +#: ../../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/services/reinvoice.rst:35 -msgid "Create product to be expensed" +#: ../../sales/invoicing/time_materials.rst:3 +msgid "Invoice based on time and materials" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:37 -msgid "You will need now to create a product called ``Copies``." +#: ../../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/services/reinvoice.rst:39 -#: ../../sales/invoicing/services/reinvoice.rst:112 -msgid "From your **Sales** module, go to :menuselection:`Sales --> Products` and create a product as follows:" +#: ../../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/services/reinvoice.rst:42 -msgid "**Product type**: consumable" +#: ../../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/services/reinvoice.rst:44 -msgid "**Invoicing policy**: on delivered quantities (you will manually set the quantities to invoice on the sale order)" +#: ../../sales/invoicing/time_materials.rst:19 +msgid "Invoice time configuration" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:51 -msgid "Create a sale order" +#: ../../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/services/reinvoice.rst:53 -msgid "Now that your product is correctly set up, you can create a sale order for that product (from the menu :menuselection:`Sales --> Sales Orders`) with the ordered quantities set to 0. Click on **Confirm the Sale** to create the sale order. You will be able then to manually change the delivered quantities on the sale order to reinvoice the copies to your customer." +#: ../../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/services/reinvoice.rst:64 -#: ../../sales/invoicing/services/reinvoice.rst:177 -msgid "Invoice expense to your client" +#: ../../sales/invoicing/time_materials.rst:32 +msgid "Invoice your time spent" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:66 -msgid "At the end of the month, you have printed ``1000`` copies on behalf of your client and you want to re-invoice them. From the related sale order, click on **Delivered Quantities**, manually enter the correct amount of copies and click on **Save**. Your order line will turn blue, meaning that it is ready to be invoiced. Click on **Create invoice**." +#: ../../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/services/reinvoice.rst:73 -msgid "The total amount on your sale order will be of 0 as it is computed on the ordered quantities. It is your invoice which will compute the correct amount due by your customer." +#: ../../sales/invoicing/time_materials.rst:41 +msgid "You could also add the task to an existing project." msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:77 -msgid "The invoice generated is in draft, so you can always control the quantities and change the amount if needed. You will notice that the amount to be invoiced is based here on the delivered quantities." +#: ../../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/services/reinvoice.rst:84 -msgid "Click on validate to issue the payment to your customer." +#: ../../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/services/reinvoice.rst:87 -msgid "Use case 2: Invoice expenses via the expense module" +#: ../../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/services/reinvoice.rst:89 -msgid "To illustrate this case, let's imagine that your company sells some consultancy service to your customer ``Agrolait`` and both parties agreed that the distance covered by your consultant will be re-invoiced at cost." +#: ../../sales/invoicing/time_materials.rst:58 +msgid "From the sales order, you can then invoice those hours." msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:97 -msgid "Here, you will need to install two more modules:" +#: ../../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/services/reinvoice.rst:99 -msgid "Expense Tracker" +#: ../../sales/invoicing/time_materials.rst:120 +msgid "Invoice purchases" msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:101 -msgid "Accounting, where you will need to activate the analytic accounting from the settings" +#: ../../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/services/reinvoice.rst:108 -msgid "Create a product to be expensed" +#: ../../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/services/reinvoice.rst:110 -msgid "You will now need to create a product called ``Kilometers``." +#: ../../sales/invoicing/time_materials.rst:129 +msgid "While making the purchase order don't forget to add the right analytic account." msgstr "" -#: ../../sales/invoicing/services/reinvoice.rst:115 -msgid "Product can be expensed" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:117 -msgid "Product type: Service" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:119 -msgid "Invoicing policy: invoice based on time and material" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:121 -msgid "Expense invoicing policy: At cost" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:123 -msgid "Track service: manually set quantities on order" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:129 -msgid "Create a sales order" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:131 -msgid "Still from the Sales module, go to :menuselection:`Sales --> Sales Orders` and add your product **Consultancy** on the order line." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:135 -msgid "If your product doesn't exist yet, you can configure it on the fly from the SO. Just type the name on the **product** field and click on **Create and edit** to configure it." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:139 -msgid "Depending on your product configuration, an **Analytic Account** may have been generated automatically. If not, you can easily create one in order to link your expenses to the sale order. Do not forget to confirm the sale order." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:148 -msgid "Refer to the documentation :doc:`../../../accounting/others/analytic/usage` to learn more about that concept." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:152 -msgid "Create expense and link it to SO" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:154 -msgid "Let's assume that your consultant covered ``1.000km`` in October as part of his consultancy project. We will create a expense for it and link it to the related sales order thanks to the analytic account." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:158 -msgid "Go to the **Expenses** module and click on **Create**. Record your expense as follows:" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:161 -msgid "**Expense description**: Kilometers October 2015" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:163 -msgid "**Product**: Kilometers" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:165 -msgid "**Quantity**: 1.000" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:167 -msgid "**Analytic account**: SO0019 - Agrolait" -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:172 -msgid "Click on **Submit to manager**. As soon as the expense has been validated and posted to the journal entries, a new line corresponding to the expense will automatically be generated on the sale order." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:179 -msgid "You can now invoice the invoiceable lines to your customer." -msgstr "" - -#: ../../sales/invoicing/services/reinvoice.rst:186 -msgid ":doc:`milestones`" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:3 -msgid "How to invoice a support contract (prepaid hours)?" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:5 -msgid "There are different kinds of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) and a fixed price contract (e.g. a project)." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:9 -msgid "In this section, we will have a look at how to sell and keep track of a pre-paid support contract." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:12 -msgid "As an example, you may sell a pack of ``50 Hours`` of support at ``$25,000``. The price is fixed and charged initially. But you want to keep track of the support service you did for the customer." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:20 -msgid "Install the Sales and Timesheet applications" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:22 -msgid "In order to sell services, you need to install the **Sales** application, from the **Apps** icon. Install also the **Timesheets** application if you want to track support services you worked on every contract." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:33 -msgid "Create Products" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:35 -msgid "By default, products are sold by number of units. In order to sell services ``per hour``, you must allow using multiple unit of measures. From the **Sales** application, go to the menu :menuselection:`Configuration --> Settings`. From this screen, activate the multiple **Unit of Measures** option." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:44 -msgid "In order to sell a support contract, you must create a product for every support contract you sell. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:48 -msgid "**Name**: Technical Support" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:52 -msgid "**Unit of Measure**: Hours" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:54 -msgid "**Invoicing Policy**: Ordered Quantities, since the service is prepaid, we will invoice the service based on what has been ordered, not based on delivered quantities." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:58 -msgid "**Track Service**: Timesheet on contracts. An analytic account will automatically be created for every order containing this service so that you can track hours in the related account." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:66 -msgid "There are different ways to track the service related to a sales order or product sold. With the above configuration, you can only sell one support contract per order. If your customer orders several service contracts on timesheet, you will have to split the quotation into several orders." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:72 -msgid "Note that you can sell in different unit of measure than hours, example: days, pack of 40h, etc. To do that, just create a new unit of measure in the **Unit of Measure** category and set a conversion ratio compared to **Hours** (example: ``1 day = 8 hours``)." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:78 -msgid "Managing support contract" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:81 -msgid "Quotations and Sales Orders" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:83 -msgid "Once the product is created, you can create a quotation or a sales order with the related product. Once the quotation is confirmed and transformed into a sales order, your users will be able to record services related to this support contract using the timesheet application." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:93 -msgid "Timesheets" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:95 -msgid "To track the service you do on a specific contract, you should use the timesheet application. An analytic account related to the sale order has been automatically created (``SO009 - Agrolait`` on the screenshot here above), so you can start tracking services as soon as it has been sold." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:104 -msgid "Control delivered support on the sales order" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:106 -msgid "From the **Sales** application, use the menu :menuselection:`Sales --> Sales Orders` to control the progress of every order. On the sales order line related to the support contract, you should see the **Delivered Quantities** that are updated automatically, based on the number of hours in the timesheet." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:116 -msgid "Upselling and renewal" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:118 -msgid "If the number of hours you performed on the support contract is bigger or equal to the number of hours the customer purchased, you are suggested to sell an extra contract to the customer since they used all their quota of service. Periodically (ideally once every two weeks), you should check the sales order that are in such a case. To do so, go to :menuselection:`Sales --> Invoicing --> Orders to Upsell`." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:127 -msgid "If you use Odoo CRM, a good practice is to create an opportunity for every sale order in upselling invoice status so that you easily track your upselling effort." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:131 -msgid "If you sell an extra support contract, you can either add a new line on the existing sales order (thus, you continue to timesheet on the same order) or create a new order (thus, people will timesheet their hours on the new contract). To unmark the sales order as **Upselling**, you can set the sales order as done and it will disappear from your upselling list." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:138 -msgid "Special Configuration" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:140 -msgid "When creating the product form, you may set a different approach to track the service:" -msgstr "" - -#: ../../sales/invoicing/services/support.rst:143 -msgid "**Create task and track hours**: in this mode, a task is created for every sales order line. Then when you do the timesheet, you don't record hours on a sales order/contract, but you record hours on a task (that represents the contract). The advantage of this solution is that it allows to sell several service contracts within the same sales order." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:150 -msgid "**Manually**: you can use this mode if you don't record timesheets in Odoo. The number of hours you worked on a specific contract can be recorded manually on the sales order line directly, in the delivered quantity field." -msgstr "" - -#: ../../sales/invoicing/services/support.rst:156 -msgid ":doc:`../../../inventory/settings/products/uom`" +#: ../../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 @@ -901,10 +781,6 @@ msgstr "" 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:10 -msgid "Activate the feature" -msgstr "" - #: ../../sales/send_quotations/different_addresses.rst:12 msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Customer Addresses* feature." msgstr "" @@ -1054,6 +930,10 @@ msgstr "" 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 "" + #: ../../sales/send_quotations/quote_template.rst:12 msgid "For this feature to work, go to :menuselection:`Sales --> Configuration --> Settings` and activate *Quotations Templates*." msgstr ""