From 3ae6a2b39b680b5d532c861581149a47572d3fc5 Mon Sep 17 00:00:00 2001 From: Martin Trigaux Date: Wed, 20 Nov 2019 10:24:42 +0100 Subject: [PATCH] [I18N] *: export 13.0 source terms --- .tx/config | 15 + locale/sources/accounting.pot | 807 +++--- locale/sources/business.pot | 6 +- locale/sources/crm.pot | 109 +- locale/sources/db_management.pot | 46 +- locale/sources/general.pot | 82 +- locale/sources/helpdesk.pot | 66 +- locale/sources/inventory.pot | 3959 ++++++++++----------------- locale/sources/iot.pot | 425 ++- locale/sources/manufacturing.pot | 114 +- locale/sources/point_of_sale.pot | 187 +- locale/sources/purchase.pot | 4 +- locale/sources/quality.pot | 303 ++ locale/sources/sales.pot | 239 +- locale/sources/sms_marketing.pot | 374 +++ locale/sources/social_marketing.pot | 115 + locale/sources/support.pot | 8 +- 17 files changed, 3672 insertions(+), 3187 deletions(-) create mode 100644 locale/sources/quality.pot create mode 100644 locale/sources/sms_marketing.pot create mode 100644 locale/sources/social_marketing.pot diff --git a/.tx/config b/.tx/config index 8342acac9..63dbead32 100644 --- a/.tx/config +++ b/.tx/config @@ -107,6 +107,11 @@ file_filter = locale//LC_MESSAGES/purchase.po source_file = locale/sources/purchase.pot source_lang = en +[odoo-13-doc.quality] +file_filter = locale//LC_MESSAGES/quality.po +source_file = locale/sources/quality.pot +source_lang = en + [odoo-13-doc.recruitment] file_filter = locale//LC_MESSAGES/recruitment.po source_file = locale/sources/recruitment.pot @@ -117,6 +122,16 @@ file_filter = locale//LC_MESSAGES/sales.po source_file = locale/sources/sales.pot source_lang = en +[odoo-13-doc.sms_marketing] +file_filter = locale//LC_MESSAGES/sms_marketing.po +source_file = locale/sources/sms_marketing.pot +source_lang = en + +[odoo-13-doc.social_marketing] +file_filter = locale//LC_MESSAGES/social_marketing.po +source_file = locale/sources/social_marketing.pot +source_lang = en + [odoo-13-doc.website] file_filter = locale//LC_MESSAGES/website.po source_file = locale/sources/website.pot diff --git a/locale/sources/accounting.pot b/locale/sources/accounting.pot index c45970aa4..26f188e0f 100644 --- a/locale/sources/accounting.pot +++ b/locale/sources/accounting.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -79,11 +79,11 @@ msgstr "" #: ../../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/batch_sdd.rst:18 #: ../../accounting/receivables/customer_payments/check.rst:39 #: ../../accounting/receivables/customer_payments/check.rst:103 #: ../../accounting/receivables/customer_payments/credit_cards.rst:40 #: ../../accounting/receivables/customer_payments/credit_cards.rst:113 -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:19 msgid "Configuration" msgstr "" @@ -1007,32 +1007,6 @@ msgstr "" msgid "View *Bank Account* in our Online Demonstration" msgstr "" -#: ../../accounting/bank/setup/create_bank_account.rst:51 -#: ../../accounting/others/adviser/assets.rst:146 -#: ../../accounting/others/analytic/timesheets.rst:78 -#: ../../accounting/payables/misc/employee_expense.rst:169 -#: ../../accounting/payables/pay/sepa.rst:134 -#: ../../accounting/payables/pay/sepa.rst:135 -#: ../../accounting/receivables/customer_invoices/overview.rst:44 -#: ../../accounting/receivables/customer_invoices/overview.rst:59 -#: ../../accounting/receivables/customer_invoices/overview.rst:94 -#: ../../accounting/receivables/customer_invoices/overview.rst:105 -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:31 -msgid "Todo" -msgstr "" - -#: ../../accounting/bank/setup/create_bank_account.rst:51 -msgid "add inherited field tooltip" -msgstr "" - -#: ../../accounting/bank/setup/create_bank_account.rst:53 -msgid "**Display on reports :** Display this bank account on the documents that will be printed or send to the customers" -msgstr "" - -#: ../../accounting/bank/setup/create_bank_account.rst:56 -msgid "**Bank Identifier Code** = BIC : SWIFT Address assigned to a bank in order to send automated payments quickly and accurately to the banks concerned" -msgstr "" - #: ../../accounting/bank/setup/create_bank_account.rst:60 msgid "The initial balance of a bank statement will be set to the closing balance of the previous one within the same journal automatically." msgstr "" @@ -1082,7 +1056,7 @@ msgid "Configure currencies" msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:36 -msgid "Once the Odoo is configured to support multiple currencies, you should activate the currencies you plan to work with. To do that, go the menu :menuselection:`Configuration --> Currencies`. All the currencies are created by default, but you should activate the ones you plan to support. (to activate a currency, check his active field)" +msgid "Once the Odoo is configured to support multiple currencies, you should activate the currencies you plan to work with. To do that, go to the menu :menuselection:`Configuration --> Currencies`. All the currencies are created by default, but you should activate the ones you plan to support (to activate a currency, check its \"Active\" field)." msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:42 @@ -1154,7 +1128,7 @@ msgid "If you have several invoices with different currencies for the same custo msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:109 -msgid "In the above report, the account receivable associated to Camptocamp is not managed in a secondary currency, which means that it keeps every transaction in his own currency. If you prefer, you can set the account receivable of this customer with a secondary currency and all his debts will automatically be converted in this currency." +msgid "In the above report, the account receivable associated to Camptocamp is not managed in a secondary currency, which means that it keeps every transaction in its own currency. If you prefer, you can set the account receivable for this customer in a secondary currency and all its debts will automatically be converted to this currency." msgstr "" #: ../../accounting/bank/setup/foreign_currency.rst:115 @@ -1202,21 +1176,35 @@ msgid "Select 'General' for miscellaneous operations journals." msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Use in Point of Sale" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Check this box if this journal define a payment method that can be used in a point of sale." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 msgid "Company" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 +#: ../../accounting/payables/pay/check.rst:0 msgid "Company related to this journal" msgstr "" +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Defines how the bank statements will be registered" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Synchronization Frequency" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Defines when a new bank statement" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "will be created when fetching new transactions" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "from your bank account." +msgstr "" + #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Short Code" msgstr "" @@ -1250,7 +1238,7 @@ msgid "Check this box if you don't want to share the same sequence for invoices msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Credit Notes: Next Number" +msgid "Credit Notes Next Number" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 @@ -1290,23 +1278,51 @@ msgid "The currency used to enter statement" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Defines how the bank statements will be registered" +msgid "Communication Type" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Creation of Bank Statements" +msgid "You can set here the default communication that will appear on customer invoices, once validated, to help the customer to refer to that particular invoice when making the payment." msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Defines when a new bank statement" +msgid "Communication Standard" msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "will be created when fetching new transactions" +msgid "You can choose different models for each type of reference. The default one is the Odoo reference." msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "from your bank account." +msgid "Alias Name" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "It creates draft invoices and bills by sending an email." +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Profit Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Used to register a profit when the ending balance of a cash register differs from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Loss Account" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Used to register a loss when the ending balance of a cash register differs from what the system computes" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "Lock Posted Entries with Hash" +msgstr "" + +#: ../../accounting/bank/setup/manage_cash_register.rst:0 +msgid "If ticked, the accounting entry or invoice receives a hash as soon as it is posted and cannot be modified anymore." msgstr "" #: ../../accounting/bank/setup/manage_cash_register.rst:0 @@ -1343,46 +1359,6 @@ msgstr "" msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. Enable this option from the settings." msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Profit Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Used to register a profit when the ending balance of a cash register differs from what the system computes" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Loss Account" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Used to register a loss when the ending balance of a cash register differs from what the system computes" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Group Invoice Lines" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "If this box is checked, the system will try to group the accounting lines when generating them from invoices." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Post At Bank Reconciliation" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Whether or not the payments made in this journal should be generated in draft state, so that the related journal entries are only posted when performing bank reconciliation." -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Alias Name for Vendor Bills" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "It creates draft vendor bill by sending an email." -msgstr "" - #: ../../accounting/bank/setup/manage_cash_register.rst:0 msgid "Check Printing Payment Method Selected" msgstr "" @@ -1417,14 +1393,6 @@ msgstr "" msgid "Sequence number of the next printed check." msgstr "" -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "Amount Authorized Difference" -msgstr "" - -#: ../../accounting/bank/setup/manage_cash_register.rst:0 -msgid "This field depicts the maximum difference allowed between the ending balance and the theoretical cash when closing a session, for non-POS managers. If this maximum is reached, the user will have an error message at the closing of his session saying that he needs to contact his manager." -msgstr "" - #: ../../accounting/bank/setup/manage_cash_register.rst:25 msgid "Usage" msgstr "" @@ -3470,134 +3438,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 "Asset 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 "Depreciation Dates" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "The way to compute the date of the first depreciation." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "* Based on last day of purchase period: The depreciation dates will be based on the last day of the purchase month or the purchase year (depending on the periodicity of the depreciations)." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "* Based on purchase date: The depreciation dates will be based on the purchase date." -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "First Depreciation Date" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:0 -msgid "Note that this date does not alter the computation of the first journal entry in case of prorata temporis assets. It simply changes its accounting date" -msgstr "" - -#: ../../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 asset date (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 "" @@ -3658,18 +3498,6 @@ msgstr "" msgid "If you sell or dispose an asset, you need to deprecate completly this asset. Click on the button :guilabel:`Sell or Dispose`. This action will post the full costs of this assets but it will not record the sales transaction that should be registered through a customer invoice." msgstr "" -#: ../../accounting/others/adviser/assets.rst:146 -msgid "→ This has to be changed in Odoo: selling an asset should:" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:148 -msgid "remove all \"Red\" lines" -msgstr "" - -#: ../../accounting/others/adviser/assets.rst:149 -msgid "create a new line that deprecate the whole residual value" -msgstr "" - #: ../../accounting/others/adviser/budget.rst:3 msgid "How to manage a financial budget?" msgstr "" @@ -4114,10 +3942,6 @@ msgstr "" msgid "For more information on how to create a sales order based on time and material please see: *How to invoice based on time and material* (Work in Progress)." msgstr "" -#: ../../accounting/others/analytic/timesheets.rst:79 -msgid "Add a link, and the document is under Sales --> Invoicing Methods --> Services --> How to invoices blabla" -msgstr "" - #: ../../accounting/others/analytic/timesheets.rst:82 msgid "We save a Sales Order with the service product **External Consulting**. An analytical account will automatically be generated once the **Sales Order** is confirmed. Our employees will have to point to that account (in this case **SO002-Smith&Co**) in order to be able to invoice their hours (see picture below)." msgstr "" @@ -4771,6 +4595,22 @@ msgstr "" msgid "Account Type is used for information purpose, to generate country-specific legal reports, and set the rules to close a fiscal year and generate opening entries." msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Can Create Asset" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Technical field specifying if the account can generate asset depending on it's type. It is used in the account form view." +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Asset Model" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "If this is selected, an asset will be created automatically when Journal Items on this account are posted." +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Tags" msgstr "" @@ -4795,6 +4635,14 @@ msgstr "" msgid "The 'Internal Type' is used for features available on different types of accounts: liquidity type is for cash or bank accounts, payable/receivable is for vendor/customer accounts." msgstr "" +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "Internal Group" +msgstr "" + +#: ../../accounting/others/configuration/account_type.rst:0 +msgid "The 'Internal Group' is used to filter accounts based on the internal group set on the account type." +msgstr "" + #: ../../accounting/others/configuration/account_type.rst:0 msgid "Allow Reconciliation" msgstr "" @@ -5462,6 +5310,7 @@ msgid "Multi-currency invoices & Vendor Bills" msgstr "" #: ../../accounting/others/multicurrencies/invoices_payments.rst:54 +#: ../../accounting/payables/pay/check.rst:0 msgid "Invoices" msgstr "" @@ -6386,7 +6235,7 @@ msgid "In Odoo" msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:28 -msgid "Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings` and check *TaxCloud - Compute tax rates based on U.S. ZIP codes*." +msgid "Go to :menuselection:`Invoicing / Accounting --> Configuration --> Settings` and check *TaxCloud - Compute tax rates based on U.S. ZIP codes* (note: actually uses complete street address)." msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:30 @@ -6398,7 +6247,7 @@ msgid "Click SAVE to store your credentials." msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:36 -msgid "Click the Refresh Icon next to *Default Category* to import the TIC product categories from TaxCloud (Taxability Information Codes). Some categories may imply specific rates." +msgid "Click the Refresh Icon next to *Default Category* to import the TIC product categories from TaxCloud (Taxability Information Codes). Some categories may imply specific rates or attract product/service type exemptions." msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:38 @@ -6406,7 +6255,7 @@ msgid "Select your default *TIC Code*. This will apply to any new product create msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:40 -msgid "Set a specific TaxCloud Category on the *General Information* tab of the Product, or on the Product Category." +msgid "Set a specific TaxCloud TIC Category on the *General Information* tab of the Product, or on the Product Category." msgstr "" #: ../../accounting/others/taxes/taxcloud.rst:42 @@ -6790,6 +6639,7 @@ msgid "Balance = Debit - Credit" msgstr "" #: ../../accounting/overview/main_concepts/memento.rst:84 +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:83 msgid "Journal Entries" msgstr "" @@ -7698,10 +7548,6 @@ msgstr "" msgid "To invoice the customer, just click on the invoice button on his sale order. (or it will be done automatically at the end of the week/month if you invoice all your orders in batch)" msgstr "" -#: ../../accounting/payables/misc/employee_expense.rst:171 -msgid "tip If you want to learn more; check the documentation page :doc: ../../../sale/invoicing/service/expense `*How to re-invoice expenses to your customers* `__" -msgstr "" - #: ../../accounting/payables/misc/employee_expense.rst:176 msgid "Reimburse the employee" msgstr "" @@ -7907,6 +7753,18 @@ msgstr "" msgid "Technical field used for usability purposes" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field containing the invoice for which the payment has been generated." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "This does not especially correspond to the invoices reconciled with the payment," +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "as it can have been generated first, and reconciled later" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Hide Payment Method" msgstr "" @@ -7915,6 +7773,10 @@ msgstr "" msgid "Technical field used to hide the payment method if the selected journal has only one available which is 'manual'" msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Payment Method" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Check: Pay bill by check and print it from Odoo." msgstr "" @@ -7927,14 +7789,6 @@ msgstr "" msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. To enable sepa credit transfer, module account_sepa must be installed" msgstr "" -#: ../../accounting/payables/pay/check.rst:0 -msgid "Show Partner Bank Account" -msgstr "" - -#: ../../accounting/payables/pay/check.rst:0 -msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be displayed or not in the payments form views" -msgstr "" - #: ../../accounting/payables/pay/check.rst:0 msgid "Code" msgstr "" @@ -7943,6 +7797,30 @@ msgstr "" msgid "Technical field used to adapt the interface to the payment type selected." msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Saved payment token" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Note that tokens from acquirers set to only authorize transactions (instead of capturing the amount) are not available." +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Show Partner Bank Account" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be displayed or not in the payments form views" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Require Partner Bank Account" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be required or not in the payments form views" +msgstr "" + #: ../../accounting/payables/pay/check.rst:0 msgid "Check Number" msgstr "" @@ -7951,6 +7829,14 @@ msgstr "" msgid "The selected journal is configured to print check numbers. If your pre-printed check paper already has numbers or if the current numbering is wrong, you can change it in the journal configuration page." msgstr "" +#: ../../accounting/payables/pay/check.rst:0 +msgid "Journal Item Label" +msgstr "" + +#: ../../accounting/payables/pay/check.rst:0 +msgid "Change label of the counterpart that will hold the payment difference" +msgstr "" + #: ../../accounting/payables/pay/check.rst:80 msgid "Try paying a supplier bill with a check" msgstr "" @@ -8149,7 +8035,6 @@ msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative msgstr "" #: ../../accounting/payables/pay/sepa.rst:10 -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:10 msgid "SEPA is supported by the banks of the 28 EU member states as well as Iceland, Norway, Switzerland, Andorra, Monaco and San Marino." msgstr "" @@ -8247,14 +8132,6 @@ msgstr "" msgid ":doc:`check`" msgstr "" -#: ../../accounting/payables/pay/sepa.rst:134 -msgid "How to define a new bank?" -msgstr "" - -#: ../../accounting/payables/pay/sepa.rst:135 -msgid "How to reconcile bank statements?" -msgstr "" - #: ../../accounting/payables/supplier_bills/bills_or_receipts.rst:3 msgid "When should I use supplier bills or purchase receipts?" msgstr "" @@ -8528,7 +8405,7 @@ msgid "Account Receivables" msgstr "" #: ../../accounting/receivables/customer_invoices.rst:3 -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:53 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:77 msgid "Customer Invoices" msgstr "" @@ -8632,6 +8509,125 @@ msgstr "" msgid "Once your roundings are created, you can apply them on customer invoices. On the customer invoices, there is a new field called **Cash Rounding Method** where you can simply choose one of the rounding methods created previously. If needed, a rounding will be applied to the invoice." msgstr "" +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:3 +msgid "Credit Notes and Refunds" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:4 +msgid "A **credit note**, or **credit memo**, is a document issued to a customer that notifies them that they have been credited a certain amount." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:11 +msgid "There are several reasons that can lead to a credit note, such as:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:9 +msgid "a mistake in the invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:10 +msgid "a return of the goods, or a rejection of the services" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:11 +msgid "the goods delivered are damaged" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:14 +msgid "Issuing a credit note is the only legal way to cancel, refund or modify a validated invoice. Don’t forget to *register the payment* afterward if you need to send money back to your customer." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:20 +msgid "Issue a Credit Note" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:21 +msgid "You can create a credit note from scratch by going to :menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking on *Create*. Filling the Credit Note’s form works the same way as the Invoice’s form." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:26 +msgid "However, most of the time, credit notes are generated directly from the invoices they are related to." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:29 +msgid "To do so, open the *Customer Invoice*, and click on *Add Credit Note*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:37 +msgid "You can choose between three options:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:35 +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:44 +msgid "Partial Refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:36 +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:55 +msgid "Full Refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:37 +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:66 +msgid "Full refund and new draft invoice" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:40 +msgid "Credit Notes’ numbers start with “R” and are followed by the number of the document they are related to (e.g., RINV/2019/0004)." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:45 +msgid "Odoo creates a draft credit note already prefilled with all the necessary information from the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:48 +msgid "This is the option to choose to do a partial refund, or if you want to modify any detail on the credit note." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:52 +msgid "This is the only option available for invoices that are already marked as *Paid*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:56 +msgid "Odoo creates a credit note, automatically validates it, and reconciles the original invoice with it." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:62 +msgid "This is the option to choose to do a full refund or cancel a validated invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:67 +msgid "Odoo creates a credit note, automatically validates it, reconciles the original invoice with it, and open a new draft invoice prefilled with the same details from the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:71 +msgid "This is the option to choose to modify the content of a validated invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:74 +msgid "Record a Vendor Refund" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:75 +msgid "**Vendor Refunds** are recorded the same way you would do with invoices’ credit notes:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:77 +msgid "You can either create a credit note from scratch by going to :menuselection:`Accounting --> Vendors --> Refund`, and by clicking on *Create*, or by opening the validated *Vendor Bill*, and clicking on *Add Credit Note*." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:84 +msgid "Issuing a credit note from an invoice creates a **reverse entry** that zeroes out the journal items generated by the original invoice." +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:87 +msgid "Here is an example of an invoice’s journal entry:" +msgstr "" + +#: ../../accounting/receivables/customer_invoices/credit_notes.rst:92 +msgid "And here is the credit note’s journal entry generated to reverse the original invoice above:" +msgstr "" + #: ../../accounting/receivables/customer_invoices/deferred_revenues.rst:3 msgid "Deferred revenues: how to automate them?" msgstr "" @@ -8924,10 +8920,6 @@ msgstr "" msgid "This process is good for both services and physical products." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:44 -msgid "Read more: *Invoice based on sales orders.*" -msgstr "" - #: ../../accounting/receivables/customer_invoices/overview.rst:47 msgid "Sales Order ‣ Delivery Order ‣ Invoice" msgstr "" @@ -8940,10 +8932,6 @@ msgstr "" msgid "This way, if you deliver a partial order, you only invoice for what you really delivered. If you do back orders (deliver partially and the rest later), the customer will receive two invoices, one for each delivery order." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:59 -msgid "Read more: *Invoice based on delivery orders.*" -msgstr "" - #: ../../accounting/receivables/customer_invoices/overview.rst:62 msgid "eCommerce Order ‣ Invoice" msgstr "" @@ -8988,10 +8976,6 @@ msgstr "" msgid "You can invoice at the end of the contract or trigger intermediate invoices. This approach is used by services companies that invoice mostly based on time and material. For services companies that invoice on fix price, they use a regular sales order." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:94 -msgid "Read more: - *How to invoice based on time and material?* - *How to manage contracts and invoicing plans?*" -msgstr "" - #: ../../accounting/receivables/customer_invoices/overview.rst:99 msgid "Recurring Contracts ‣ Invoices" msgstr "" @@ -9000,10 +8984,6 @@ msgstr "" msgid "For subscriptions, an invoice is triggered periodically, automatically. The frequency of the invoicing and the services/products invoiced are defined on the contract." msgstr "" -#: ../../accounting/receivables/customer_invoices/overview.rst:105 -msgid "Read more: *Subscription based invoicing.*" -msgstr "" - #: ../../accounting/receivables/customer_invoices/overview.rst:111 msgid "Creating an invoice manually" msgstr "" @@ -9068,10 +9048,6 @@ msgstr "" msgid "A payment term may have one line (ex: 21 days) or several lines (10% within 3 days and the balance within 21 days). If you create a payment term with several lines, be sure the latest one is the balance. (avoid doing 50% in 10 days and 50% in 21 days because, with the rounding, it may not do exactly 100%)" msgstr "" -#: ../../accounting/receivables/customer_invoices/payment_terms.rst:31 -msgid "screenshot payment term forms, after QDP have commited the change planned on this object" -msgstr "" - #: ../../accounting/receivables/customer_invoices/payment_terms.rst:35 msgid "Using Payment Terms" msgstr "" @@ -9116,77 +9092,131 @@ msgstr "" msgid ":doc:`cash_discounts`" msgstr "" -#: ../../accounting/receivables/customer_invoices/refund.rst:3 -msgid "How to edit or refund an invoice?" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:4 -msgid "In Odoo, it's not possible to modify an invoice that has been validated and sent to the customer. If a mistake was made on a validated invoice, the legal way to handle that is to refund the invoice, reconcile it with the original invoice to close them and create a new invoice." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:10 -msgid "Modifying a validated invoice" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:12 -msgid "If you need to modify an existing invoice, use the Refund Invoice button on the invoice. In the refund method field, select \"Modify: create a refund, reconcile, and create a new draft invoice\"." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:19 -#: ../../accounting/receivables/customer_invoices/refund.rst:37 -msgid "Odoo will automatically:" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:21 -#: ../../accounting/receivables/customer_invoices/refund.rst:39 -msgid "Create a refund for your invoice" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:22 -#: ../../accounting/receivables/customer_invoices/refund.rst:40 -msgid "Reconcile the refund invoice with the original invoice (marking both as Paid)" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:23 -msgid "Create a new draft invoice you can modify" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:25 -msgid "Then, you can modify the draft invoice and validate it once it's correct." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:28 -msgid "Cancelling an invoice" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:30 -msgid "If you need to cancel an existing invoice, use the Refund Invoice button on the invoice. In the refund method field, select \"Cancel: create a refund and reconcile\"." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:42 -msgid "Nothing else needs to be done. You can send the refund by regular mail or email to your customer, if you already sent the original invoice." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:46 -msgid "Refunding part of an invoice" -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:48 -msgid "If you need to refund an existing invoice partially, use the Refund Invoice button on the invoice. In the refund method field, select \"Create a draft refund\"." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:55 -msgid "Odoo will automatically create a draft refund. You may modify the refund (example: remove the lines you do not want to refund) and validate it. Then, send the refund by regular mail or email to your customer." -msgstr "" - -#: ../../accounting/receivables/customer_invoices/refund.rst:61 -msgid "Refunding an invoice is different from refunding a payment. Usually, a refund invoice is sent before the customer has done a payment. If the customer has already paid, they should be reimbursed by doing a customer payment refund." -msgstr "" - #: ../../accounting/receivables/customer_payments.rst:3 msgid "Customer Payments" msgstr "" +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:3 +msgid "Batch Payments: SEPA Direct Debit (SDD)" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:4 +msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for simplification of bank transfers denominated in EURO. With **SEPA Direct Debit**, your customers can sign a **mandate** that authorizes you to collect future payments from their bank accounts automatically." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:10 +msgid "You can record your customer mandates in Odoo, and generate XML files containing pending payments made with an SDD mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:0 +msgid "SDD is supported by all SEPA countries, which includes the 28 member states of the European Union as well as additional countries." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:0 +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:123 +msgid "`List of all SEPA countries. `_" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:19 +msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` nd activate the **SEPA Direct Debit (SDD)** feature. Enter the **Creditor Identifier** of your company. This number is provided by your bank, or the authority responsible for delivering them." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:28 +msgid "SEPA Direct Debit Mandates" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:30 +msgid "Create a mandate" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:31 +msgid "The SEPA Direct Debit Mandate is the document that your customers sign to authorize you to collect money directly from their bank accounts." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:34 +msgid "To create a new one, go to :menuselection:`Accounting --> Customers --> Direct Debit Mandates`, click on *Create*, and fill out the new mandate’s form." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:41 +msgid "First, export the PDF file by clicking on *Print*. It is then up to your customer to sign this document. Once done, upload the signed file in the **Original Document** field, and click on *Validate* to start running the mandate." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:47 +msgid "First, make sure, that the **IBAN bank accounts details** are correctly recorded on the debtor’s contact form, under the *Accounting* tab, and in your own *Bank Account* settings." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:52 +msgid "Close or revoke a mandate" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:53 +msgid "Direct Debit mandates are closed automatically after their *End Date*. If this field is left blank, then the mandate keeps being *Active* until it is *Closed* or *Revoked*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:60 +msgid "Clicking on **Close** updates the mandate’s end day to the current day. This means that invoices made after the present day won’t be processed automatically with an SDD payment." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:64 +msgid "Clicking on **Revoke** disables the mandate immediately. No SDD payment can be registered anymore, regardless of the invoice’s date. However, payments that have already been registered will still be included to the next SDD XML file." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:70 +msgid "Once a mandate has been *closed* or *revoked*, it cannot be reactivated. If a customer requires to pay with SDD payments again, you will have to create a new mandate from scratch." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:75 +msgid "Get paid with SDD Batch Payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:78 +msgid "All new posted invoice issued to customers with an active mandate will automatically register payment and have their status marked as *Paid*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:82 +msgid "If you have unpaid invoices that could be paid with a new mandate, it is still possible to do it. Go on the invoice, click on *Register Payment* and choose *SEPA Direct Debit* as payment method." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:87 +msgid "Generate SEPA Direct Debit XML files to submit payments" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:88 +msgid "To submit your SDD payments to your bank, you will first generate an **XML file** that can be uploaded directly to your bank interface." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:91 +msgid "The files generated by Odoo follow the SEPA Direct Debit **PAIN.008.001.02** specifications as required by the SEPA customer-to-bank Implementation Guidelines, which ensures compatibility with the banks." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:95 +msgid "To generate your XML file for the pending SDD payments, go to the related *bank journal* on your *Accounting dashboard*, then click on *Direct Debit Payments to Collect*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:102 +msgid "Select all the payments in the list that you want to include in your SDD XML file, then click on *Action* and select *Create Batch Payment*." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:108 +msgid "Odoo then takes you to your *Batch Payment*’s form. Click on *Validate* and then download the SDD XML file." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:114 +msgid "Finally, upload this file to your bank to process the payments." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:117 +msgid "You can retrieve all the generated SDD XML files by going to :menuselection:`Accounting --> Configuration --> Customers --> Batch Payments`." +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:121 +msgid ":doc:`../../bank/setup/create_bank_account`" +msgstr "" + +#: ../../accounting/receivables/customer_payments/batch_sdd.rst:122 +msgid "`Odoo Academy: SEPA Direct Debit Mandates (SDD) `_" +msgstr "" + #: ../../accounting/receivables/customer_payments/check.rst:3 msgid "How to register customer payments by checks?" msgstr "" @@ -9538,87 +9568,6 @@ msgstr "" msgid "If you would like to get a reminder before the actual due date, set a negative number of due days." msgstr "" -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:3 -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:29 -msgid "Get paid with SEPA" -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:5 -msgid "SEPA, the Single Euro Payments Area, is a payment-integration initiative of the European Union for simplification of bank transfers denominated in EURO. SEPA Direct Debit allows you to withdraw money from the bank accounts of your customers with their approval." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:13 -msgid "With Odoo, you can record customer mandates, generate an SDD XML file containing customer payments and upload it in your bank interface. The file follows the SEPA Direct Debit PAIN.008.001.02 specifications. This is a well-defined standard that makes consensus among banks." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:21 -msgid "Go in :menuselection:`Accounting --> Configuration --> Settings` and activate the SEPA Direct Debit (SDD) Feature. Enter the Creditor Identifier of your company. This number is provided by your bank." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:32 -msgid "Direct Debit Mandates" -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:34 -msgid "Before withdrawing money from a customer bank account, your customer has to sign a mandate. Go in :menuselection:`Accounting --> Sales --> Direct Debit Mandates` and create a new mandate." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:41 -msgid "SEPA Direct Debit only works between IBAN Bank Accounts." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:43 -msgid "Once you have entered all the information in the customer mandate, you can print it and ask your customer to sign it. Once it is done, you can upload the mandate signed by your customer on the mandate in Odoo." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:50 -msgid "You can now validate the mandate." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:55 -msgid "Let's create an invoice for that customer." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:57 -msgid "When you will validate this invoice, the payment will be automatically generated and your invoice will be directly marked as paid." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:61 -msgid "If you already had some invoices for that customer that could be paid using that mandate, it's still possible to do it. Go on the invoice, click on register payment and choose the Sepa Direct Debit as payment method." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:67 -msgid "Generate SDD Files" -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:69 -msgid "You can generate the SDD File with all the customer payments to send to your bank directly from the accounting dashboard :" -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:75 -msgid "You select the payments in the list that you want to include in your SDD File, click on action and select \"Generate Direct Debit XML\"." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:81 -msgid "You can now download the XML file generated by Odoo and upload it in your bank interface." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:85 -msgid "You can retrieve all the generated XML by activating the developer mode and going in :menuselection:`Accounting --> Configuration --> Payments --> SDD Payment File`." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:89 -msgid "Close or revoke a mandate" -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:91 -msgid "The Direct Debit mandate will be closed automatically once the end date defined on it is reached. However, you can **close** a mandate earlier than initially planned. To do that, simply go on the mandate and click on the \"Close\" button.The end date of the mandate will be updated to today's date. This means you will not be able to pay invoices with an invoice date superior to this end date. Be careful, once a mandate is closed, it cannot be reopened." -msgstr "" - -#: ../../accounting/receivables/customer_payments/payment_sepa.rst:99 -msgid "You can also **revoke** a mandate. In that case, you won't be able to pay any invoice using that mandate anymore, no matter the invoice date.To do that, simply go on the mandate and click on the \"Revoke\" button." -msgstr "" - #: ../../accounting/receivables/customer_payments/recording.rst:3 msgid "What are the different ways to record a payment?" msgstr "" diff --git a/locale/sources/business.pot b/locale/sources/business.pot index 0004082e0..0f43b7fff 100644 --- a/locale/sources/business.pot +++ b/locale/sources/business.pot @@ -6,9 +6,9 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: Odoo 11.0\n" +"Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2018-10-19 10:03+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,6 +17,6 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../business.rst:3 -msgid "Business Mementoes" +msgid "Business Mementos" msgstr "" diff --git a/locale/sources/crm.pot b/locale/sources/crm.pot index 0ebd9e22c..8f413479f 100644 --- a/locale/sources/crm.pot +++ b/locale/sources/crm.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -29,37 +29,70 @@ msgid "Convert leads into opportunities" msgstr "" #: ../../crm/acquire_leads/convert.rst:5 -msgid "The system can generate leads instead of opportunities, in order to add a qualification step before converting a *Lead* into an *Opportunity* and assigning to the right sales people. You can activate this mode from the CRM Settings. It applies to all your sales channels by default. But you can make it specific for specific channels from their configuration form." +msgid "The system can generate leads instead of opportunities, in order to add a qualification step before converting a *Lead* into an *Opportunity* and assigning to the right sales people." msgstr "" -#: ../../crm/acquire_leads/convert.rst:13 +#: ../../crm/acquire_leads/convert.rst:9 +msgid "You can activate this mode from the CRM Settings. It applies to all your sales channels by default. But you can make it specific for specific channels from their configuration form." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:14 #: ../../crm/acquire_leads/generate_from_website.rst:41 +#: ../../crm/acquire_leads/lead_mining.rst:8 #: ../../crm/optimize/onsip.rst:13 #: ../../crm/track_leads/lead_scoring.rst:12 #: ../../crm/track_leads/prospect_visits.rst:12 msgid "Configuration" msgstr "" -#: ../../crm/acquire_leads/convert.rst:15 +#: ../../crm/acquire_leads/convert.rst:16 msgid "For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings` and activate the *Leads* feature." msgstr "" -#: ../../crm/acquire_leads/convert.rst:21 +#: ../../crm/acquire_leads/convert.rst:22 msgid "You will now have a new submenu *Leads* under *Leads* where they will aggregate." msgstr "" -#: ../../crm/acquire_leads/convert.rst:28 +#: ../../crm/acquire_leads/convert.rst:29 msgid "Convert a lead into an opportunity" msgstr "" -#: ../../crm/acquire_leads/convert.rst:30 +#: ../../crm/acquire_leads/convert.rst:31 msgid "When you click on a *Lead* you will have the option to convert it to an opportunity and decide if it should still be assigned to the same channel/person and if you need to create a new customer." msgstr "" -#: ../../crm/acquire_leads/convert.rst:37 +#: ../../crm/acquire_leads/convert.rst:38 msgid "If you already have an opportunity with that customer Odoo will automatically offer you to merge with that opportunity. In the same manner, Odoo will automatically offer you to link to an existing customer if that customer already exists." msgstr "" +#: ../../crm/acquire_leads/convert.rst:44 +msgid "Merge opportunities" +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:46 +msgid "Odoo will also automatically propose to merge opportunities if they have the same email address. When merging opportunities, Odoo merges the information into the opportunity which was created first, giving priority to the information present on the first opportunity." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:51 +msgid "No information is lost: data from the other opportunity is logged in the chatter and the information fields for easy access." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:57 +msgid "Would you find a duplicate yourself, ...you can also merge opportunities or leads even if the system doesn't propose it." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:60 +msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge." +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:66 +msgid "..note::" +msgstr "" + +#: ../../crm/acquire_leads/convert.rst:67 +msgid "It is also possible to merge more than 2 opportunities or leads." +msgstr "" + #: ../../crm/acquire_leads/generate_from_email.rst:3 msgid "Generate leads/opportunities from emails" msgstr "" @@ -137,6 +170,66 @@ msgstr "" msgid "When using a contact form, you should use a qualification step before assigning the form to the right sales people. To do so, activate *Leads* in CRM settings and refer to :doc:`convert`." msgstr "" +#: ../../crm/acquire_leads/lead_mining.rst:3 +msgid "Lead mining" +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:4 +msgid "In any business, getting quality leads is essential to keep the business growing. Lead mining allows you to generate leads from scratch directly from your database. Target your leads based on a set of criteria such as the country, the size of the company, the industry your leads are coming from to make them relevant to your business." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:10 +msgid "For this feature to work, go to :menuselection:`CRM → Configuration → Settings` and activate the **Lead Mining** feature." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:17 +msgid "Start generating leads" +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:18 +msgid "You will now have a new button **Generate Leads** available in your pipeline. You are also able to create lead mining requests from the **Configuration → Lead Mining Requests** and trough **Leads → Leads** where you have the **Generate Leads** button" +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:25 +msgid "From there, click on the **Generate Leads** button, a window where you will be able to pick your criteria will pop up." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:32 +msgid "When choosing to target Companied and their contacts you can choose the contacts you are getting based on Role or Seniority. When getting contact information make sure to be aware of the latest EU regulation, get more information about General Data Protection Regulation on `Odoo GDPR `__," +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:37 +msgid "You can decide to filter the leads you are getting depending on the size (number of employees) of the companies. You can pick the countries your leads are coming from. It is possible to pick multiple countries. You can pick the industries your leads are coming from. It is possible to pick multiple countries." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:41 +msgid "You can choose the salesperson and the Salesteam the lead will be assigned to. You can also add tags to track your generated leads." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:45 +msgid "The generated leads will have the name of the company." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:48 +msgid "Pricing" +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:49 +msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature `__, To buy credits you can either go to CRM > Configuration > Settings > Buy Credits; or go to Settings > In-App Purchases>View my Services" +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:62 +msgid "The blue box will automatically tell you how many credits are going to be consumed." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:65 +msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." +msgstr "" + +#: ../../crm/acquire_leads/lead_mining.rst:67 +msgid "More information about `In-App Purchases `__, (IAP)." +msgstr "" + #: ../../crm/acquire_leads/send_quotes.rst:3 msgid "Send quotations" msgstr "" diff --git a/locale/sources/db_management.pot b/locale/sources/db_management.pot index fedc818cc..a51479d03 100644 --- a/locale/sources/db_management.pot +++ b/locale/sources/db_management.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -448,83 +448,83 @@ msgid "Make sure you have sufficient **administrative rights** if you want to ch msgstr "" #: ../../db_management/documentation.rst:39 -msgid "In your Odoo instance, click on **Settings**. You will have a section showing you the active users on your database. Click on **Manage access rights.**" +msgid "In your Odoo instance, click on **Settings**. You will have a section showing you the active users on your database. Click on **Manage Users.**" msgstr "" -#: ../../db_management/documentation.rst:44 -#: ../../db_management/documentation.rst:82 +#: ../../db_management/documentation.rst:43 +#: ../../db_management/documentation.rst:80 msgid "|settings|" msgstr "" -#: ../../db_management/documentation.rst:44 +#: ../../db_management/documentation.rst:43 msgid "|browse_users|" msgstr "" -#: ../../db_management/documentation.rst:47 +#: ../../db_management/documentation.rst:46 msgid "You'll then see the list of your users." msgstr "" -#: ../../db_management/documentation.rst:52 +#: ../../db_management/documentation.rst:51 msgid "The pre-selected filter *Internal Users* shows your paying users (different from the *Portal Users* which are free). If you remove this filter, you'll get all your users (the ones you pay for and the portal ones)" msgstr "" -#: ../../db_management/documentation.rst:57 -msgid "In your list of users, click on the user you want to deactivate. As soon as you are on the userform, go with your mouse cursor on the status **Active** (top right). Click on Active and you will notice that the status will change to **Inactive** immediately." +#: ../../db_management/documentation.rst:56 +msgid "In your list of users, click on the user you want to deactivate. As soon as you are on the userform, click on the Action drop down menu, and then click on Archive." msgstr "" -#: ../../db_management/documentation.rst:66 +#: ../../db_management/documentation.rst:64 msgid "The user is now deactivated." msgstr "" -#: ../../db_management/documentation.rst:68 +#: ../../db_management/documentation.rst:66 msgid "**Never** deactivate the main user (*admin*)" msgstr "" -#: ../../db_management/documentation.rst:71 +#: ../../db_management/documentation.rst:69 msgid "Uninstalling Apps" msgstr "" -#: ../../db_management/documentation.rst:73 +#: ../../db_management/documentation.rst:71 msgid "Make sure you first test what you are about to do on a :ref:`duplicate ` of your database before making any changes (*especially* installing/uninstalling apps)." msgstr "" -#: ../../db_management/documentation.rst:77 +#: ../../db_management/documentation.rst:75 msgid "In your Odoo instance click on **Settings**; in this app, you will be able to see how many applications you have installed. Click on **Browse Apps** to access the list of your installed applications." msgstr "" -#: ../../db_management/documentation.rst:82 +#: ../../db_management/documentation.rst:80 msgid "|browse_apps|" msgstr "" -#: ../../db_management/documentation.rst:85 +#: ../../db_management/documentation.rst:83 msgid "In your applications' dashboard, you will see all the icons of your applications. Click on the application you want to uninstall. Then, on the form of the application, click on **Uninstall**." msgstr "" -#: ../../db_management/documentation.rst:92 +#: ../../db_management/documentation.rst:90 msgid "Some applications have dependencies, like Invoicing, eCommerce, etc. Therefore, the system will give you a warning message to advise you of what is about to be removed. If you uninstall your application, all its dependencies will be uninstalled as well (and the data in them will permanently disappear). If you are sure you still want to uninstall it, then click **Confirm**." msgstr "" -#: ../../db_management/documentation.rst:99 +#: ../../db_management/documentation.rst:97 msgid "Last, after having checked the warning message (if any), click **Confirm**." msgstr "" -#: ../../db_management/documentation.rst:104 +#: ../../db_management/documentation.rst:102 msgid "You have finished uninstalling your application." msgstr "" -#: ../../db_management/documentation.rst:107 +#: ../../db_management/documentation.rst:105 msgid "Good to know" msgstr "" -#: ../../db_management/documentation.rst:109 +#: ../../db_management/documentation.rst:107 msgid "**Uninstalling apps, managing users, etc. is up to you**: no one else can know if your business flow is broken better than you. If we were to uninstall applications for you, we would never be able to tell if relevant data had been removed or if one of your business flow was broken because we *do not know how you work* and therefore cannot validate these kinds of operations." msgstr "" -#: ../../db_management/documentation.rst:115 +#: ../../db_management/documentation.rst:113 msgid "**Odoo Apps have dependencies**: this means that you may need to install modules that you do not actively use to access some features of Odoo you might need. For example, the Website Builder app is needed to be able to show your customer their Quotes in a web page. Even though you might not need or use the Website itself, it is needed for the Online Quotes feature to work properly." msgstr "" -#: ../../db_management/documentation.rst:122 +#: ../../db_management/documentation.rst:120 msgid "**Always test app installation/removal on a duplicate** (or on a free trial database): that way you can know what other apps may be required, etc. This will avoid surprises when uninstalling or when receiving your invoices." msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 23da0949f..150d85eb3 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -517,6 +517,78 @@ msgstr "" msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons." msgstr "" +#: ../../general/in_app_purchase.rst:3 +msgid "In-App Purchase" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:3 +msgid "General guide about In-App Purchase (IAP) Services" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:4 +msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows me to send SMS Text Messages or to send Invoices by post directly from my database." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:7 +msgid "Buying Credits" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:8 +msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to *Settings> Odoo IAP > View my Services*." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:13 +msgid "If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit from free credits to test our IAP features." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:16 +msgid "IAP accounts" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:17 +msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones by going to *Settings app > Activate the Developer Mode > Technical Settings > IAP Accoun*." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:23 +msgid "IAP Portal" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:24 +msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from *Settings app > Odoo IAP > View my Services*. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:30 +msgid "Get notified when credits are low" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:31 +msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through *Settings app> Odoo IAP > View my Services*, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:38 +msgid "IAP services available" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:39 +msgid "Different services are available depending on the hosting type of your Database:" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:41 +msgid "*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:43 +msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used." +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:46 +msgid "Offering my own services" +msgstr "" + +#: ../../general/in_app_purchase/in_app_purchase.rst:47 +msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: `In-App Purchase `_" +msgstr "" + #: ../../general/odoo_basics.rst:3 msgid "Basics" msgstr "" @@ -557,14 +629,6 @@ msgstr "" msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_" msgstr "" -#: ../../general/odoo_basics/add_user.rst:47 -msgid "Todo" -msgstr "" - -#: ../../general/odoo_basics/add_user.rst:47 -msgid "Add link to How to add companies" -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 8f2384ed8..fac3c9a3f 100644 --- a/locale/sources/helpdesk.pot +++ b/locale/sources/helpdesk.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,6 +20,70 @@ msgstr "" msgid "Helpdesk" msgstr "" +#: ../../helpdesk/after_sales.rst:3 +msgid "After sales features: refund, coupon, return, repair, onsite interventions" +msgstr "" + +#: ../../helpdesk/after_sales.rst:4 +msgid "As my business grows, having the tools to allow my helpdesk team to record, track and manage issues raised easy and efficiently, is key. Odoo’s Helpdesk app allows me to generate credit notes, return products, grant coupons, do repairs and plan onsite interventions from a ticket’s page." +msgstr "" + +#: ../../helpdesk/after_sales.rst:7 +msgid "Set up the After Sales services" +msgstr "" + +#: ../../helpdesk/after_sales.rst:8 +msgid "Go to *Configuration > Helpdesk Teams* and enable the After Sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*." +msgstr "" + +#: ../../helpdesk/after_sales.rst:14 +msgid "Generate credit notes from tickets" +msgstr "" + +#: ../../helpdesk/after_sales.rst:15 +msgid "I can use a credit note to refund a customer or adjust the amount due. For that, I’ll simply go to my ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* the credit note will be generated, and I can *Post* it while still being in the *Helpdesk* app." +msgstr "" + +#: ../../helpdesk/after_sales.rst:22 +msgid "Allow product returns from tickets" +msgstr "" + +#: ../../helpdesk/after_sales.rst:23 +msgid "The process of a product return from my customer back to my warehouse will be taken into action when, at the ticket page, I choose the option *Return*." +msgstr "" + +#: ../../helpdesk/after_sales.rst:29 +msgid "Grant coupons from tickets" +msgstr "" + +#: ../../helpdesk/after_sales.rst:30 +msgid "First, be sure to have your *Coupon Program* planned at the *Sales or Website* app. At the *Helpdesk* app, I will open my ticket and click on *Coupon*, choose the *Coupon Program > Generate*." +msgstr "" + +#: ../../helpdesk/after_sales.rst:37 +msgid "Repairs from tickets" +msgstr "" + +#: ../../helpdesk/after_sales.rst:38 +msgid "Clicking on *Repair* option, on my ticket page, a new repair order form will be shown. Fill up the rest of the fields as needed and choose the next step." +msgstr "" + +#: ../../helpdesk/after_sales.rst:44 +msgid "Plan onsite interventions from tickets" +msgstr "" + +#: ../../helpdesk/after_sales.rst:45 +msgid "At the ticket page, I can now configure my onsite interventions exactly the same way I would do being on the *Field Service* app, clicking on *Plan Intervention*." +msgstr "" + +#: ../../helpdesk/after_sales.rst:52 +msgid "`Coupons `_" +msgstr "" + +#: ../../helpdesk/after_sales.rst:53 +msgid ":doc:`../manufacturing/repair/repair`" +msgstr "" + #: ../../helpdesk/getting_started.rst:3 msgid "Get started with Odoo Helpdesk" msgstr "" diff --git a/locale/sources/inventory.pot b/locale/sources/inventory.pot index c727b869d..4bee576f3 100644 --- a/locale/sources/inventory.pot +++ b/locale/sources/inventory.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,6 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../inventory.rst:5 -#: ../../inventory/overview/concepts/double-entry.rst:64 msgid "Inventory" msgstr "" @@ -30,218 +29,242 @@ msgid "Daily Operations" msgstr "" #: ../../inventory/barcode/operations/adjustments.rst:3 -msgid "How to do an inventory adjustment with barcodes?" +msgid "Process to an Inventory Adjustment with Barcodes" msgstr "" #: ../../inventory/barcode/operations/adjustments.rst:5 -msgid "From the Barcode application:" +msgid "To process an inventory adjustment by using barcodes, you first need to open the *Barcode* app. Then, from the application, click on *Inventory Adjustments*." msgstr "" -#: ../../inventory/barcode/operations/adjustments.rst:7 -msgid "Click on **Inventory**" -msgstr "" - -#: ../../inventory/barcode/operations/adjustments.rst:12 -msgid "Scan all the products (if you have 5 identical articles, scan it 5 times, or use the keyboard to set the quantity)." +#: ../../inventory/barcode/operations/adjustments.rst:13 +msgid "If you want to fully work with barcodes, you can download the sheet *Commands for Inventory*." msgstr "" #: ../../inventory/barcode/operations/adjustments.rst:16 -msgid "If you manage multiple locations, scan the location before scanning the products. Eg. scan a shelf's barcode ; scan each product on the shelf ; repeat for each shelf in the wharehouse." +msgid "Once you have clicked on *Inventory Adjustments*, Odoo will automatically create one. Note that, if you work with multi-location, you first need to specify in which location the inventory adjustment takes place." msgstr "" -#: ../../inventory/barcode/operations/adjustments.rst:20 -msgid "When you've scanned all the items of the location, validate the inventory manually or by scanning the **Validate** barcode." +#: ../../inventory/barcode/operations/adjustments.rst:24 +msgid "If you don’t work with multi-location, you will be able to scan the different products you want to include in the inventory adjustment." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:3 -msgid "How to process delivery orders?" +#: ../../inventory/barcode/operations/adjustments.rst:31 +msgid "If you have 5 identical articles, scan it 5 times or use the keyboard to set the quantity." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:5 -msgid "There are two approaches to process delivery orders: you can either work on printed documents (and scan lines on the documents), or on a screen (and scan products directly)." +#: ../../inventory/barcode/operations/adjustments.rst:34 +msgid "Besides using the barcode scanner, you can also manually add a product if necessary. To do so, click on *Add Product* and fill the information in manually." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:10 -msgid "Process printed delivery orders:" +#: ../../inventory/barcode/operations/adjustments.rst:44 +msgid "When you have scanned all the items of the location, validate the inventory manually or scan the *Validate* barcode." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:12 -msgid "Print delivery orders of the day by selecting all documents from the **To Do** list and print **Picking Operations** from the top menu." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:3 +msgid "Work with Barcode Nomenclature" msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:15 -msgid "Once you start processing your delivery orders, **scan the barcode** on the top-right corner of the document to load the right record on the screen." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:5 +msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sales that sells products in bulk. The customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:19 -msgid "Then, **scan the barcode** of every product, or scan the barcode of the product on the picking line if the barcode on the product is not easily accessible, visible or is missing." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:13 +msgid "Create a Barcode Nomenclature" msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:23 -#: ../../inventory/barcode/operations/receipts.rst:24 -msgid "Once you scanned all products, scan the **Validate** barcode action to finish the operation." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:15 +msgid "Odoo supports *Barcode Nomenclatures*, which determine the mapping and interpretation of the encoded information." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:30 -msgid "Process delivery orders from a computer or mobile device:" +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:18 +msgid "To configure the *Barcode Nomenclature*, you need to activate the debug mode. To do so, go to *Inventory > Configuration > Barcode Nomenclature*." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:32 -msgid "Load all the delivery orders marked as **To Do**, and open the first one." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:22 +msgid "You can create a barcode nomenclature from there, and then add a line to create your first rule." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:35 -#: ../../inventory/barcode/operations/receipts.rst:33 -msgid "Pick up and scan each listed product." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:28 +msgid "The first step is to specify the *rule name*, for example, *Weight Barcode* with 3 decimals. Then, you have to specify the type for barcode nomenclature, like the *Weighted Product*." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:37 -msgid "When you've picked all the items, click the **Validate** button or scan the **Validate barcode** action to finish the Operation." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:35 +msgid "The *Barcode Pattern* is a regular expression that defines the structure of the barcode. In this example, 21 defines the products on which the rule will be applied. Those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there to identify the product in question. The “N” defines a number and the “D” defines the decimals." msgstr "" -#: ../../inventory/barcode/operations/delivery.rst:40 -msgid "Move to the next delivery order to process by clicking on the top-right right **arrow** or scanning the **Pager-Next** barcode action." +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:43 +msgid "You can define different rules and order their priority thanks to the sequence. The first rule that matches the scanned barcode will then be applied." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:48 +msgid "Configure your Product" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:50 +msgid "The barcode of the product should start by “21”;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:52 +msgid "The 5 “dots” are the other numbers of your product barcode, allowing to identify the product;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:54 +msgid "The barcode should contain 0’s when you did defined D’s or N’s. In our case, we need to set 5 zeros because we condigures “21………{NNDDD}”;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:56 +msgid "In EAN-13, the last number is a check number. Use an EAN13 generator to know which digit it should be in your case." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:61 +msgid "In case you weight 1,5kg of pasta, the balance will print you the following barcode: *2112345015001*. If you scan this barcode in your PoS, or when receiving the products in your barcode app, Odoo will automatically create a new line for the product, for a quantity of 1,5kg." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:67 +msgid "For the point of sale, a price depending on the quantity will also be computed." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:74 +msgid "Rule Types" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:76 +msgid "**Priced Product**: it allows you to identify the product and specify its price, used in PoS;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:78 +msgid "**Discounted Product**: it allows you to create one barcode per applied discount. Then, you can scan your product in the PoS and apply discounts on the product by scanning the discount barcode;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:80 +msgid "**Weighted Product**: it allows you to identify the product and specify its weight, used in both PoS and in Inventory;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:82 +msgid "**Client**: it allows you to identify the customer, for example used with loyalty program;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:84 +msgid "**Cashier**: it allows you to identify the cashier when entering the PoS;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:86 +msgid "**Location**: it allows you to identify the location on a transfer when multi-location is activated;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:88 +msgid "**Package**: it allows you to identify packages on a transfer when packages are activated;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:90 +msgid "**Lot**: it allows you to identify the lot number of a product on a transfer;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:92 +msgid "**Credit Card**: it doesn’t need manual modification, exists for data from the Mercury module;" +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:94 +msgid "**Unit Product**: it allows you to identify a product for both PoS and Transfers." +msgstr "" + +#: ../../inventory/barcode/operations/barcode_nomenclature.rst:97 +msgid "When the barcode pattern contains .*, it means that it can contain any number of characters. Those characters can be any number." msgstr "" #: ../../inventory/barcode/operations/internal.rst:3 -msgid "How to do an internal transfer?" +msgid "Process to Transfers" msgstr "" -#: ../../inventory/barcode/operations/internal.rst:5 -msgid "In Odoo, there are two types of internal transfers:" +#: ../../inventory/barcode/operations/internal.rst:6 +msgid "Simple Transfers" msgstr "" -#: ../../inventory/barcode/operations/internal.rst:7 -msgid "Those initiated automatically by the system (for example, a quality control)" +#: ../../inventory/barcode/operations/internal.rst:8 +msgid "To process a transfer from the *Barcode* app, the first step is to go to *Operations*." msgstr "" -#: ../../inventory/barcode/operations/internal.rst:10 -msgid "Those created by a worker (for example, through the internal transfer area of the dashboard)." +#: ../../inventory/barcode/operations/internal.rst:14 +msgid "Then, you have the choice to either enter an existing transfer, by going to the corresponding operation type and manually selecting the one you want to enter, or by scanning the barcode of the transfer." msgstr "" -#: ../../inventory/barcode/operations/internal.rst:13 -msgid "To make an Internal Transfer:" +#: ../../inventory/barcode/operations/internal.rst:24 +msgid "From there, you will be able to scan the products that are part of the existing transfer and/or add new products to this transfer. Once all the products have been scanned, you can validate the transfer to proceed with the stock moves." msgstr "" -#: ../../inventory/barcode/operations/internal.rst:15 -msgid "From the home of the barcode application, scan the **source location**" +#: ../../inventory/barcode/operations/internal.rst:33 +msgid "If you have different storage locations in your warehouse, you can add additional steps for the different operation types." msgstr "" -#: ../../inventory/barcode/operations/internal.rst:17 -msgid "Pick up and **scan the products**" +#: ../../inventory/barcode/operations/internal.rst:37 +#: ../../inventory/management/lots_serial_numbers/lots.rst:50 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:45 +msgid "Receipts" msgstr "" -#: ../../inventory/barcode/operations/internal.rst:19 -msgid "Scan the **destination location**" +#: ../../inventory/barcode/operations/internal.rst:39 +msgid "When receiving a product in stock, you need to scan its barcode in order to identify it in the system. Once done, you can either make it enter the main location of the transfer, for example WH/Stock, or scan a location barcode to make it enter a sub-location of the main location." msgstr "" -#: ../../inventory/barcode/operations/internal.rst:21 -msgid "**Validate** the transfer to finish it" +#: ../../inventory/barcode/operations/internal.rst:48 +msgid "If you want the product to enter WH/Stock in our example, you can simply scan the next product." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:3 -msgid "How to handle lots and serial numbers with barcodes?" +#: ../../inventory/barcode/operations/internal.rst:52 +#: ../../inventory/management/delivery.rst:3 +msgid "Delivery Orders" msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:5 -msgid "Lots Numbers can be encoded from incoming shipments, internal moves and outgoing deliveries:" +#: ../../inventory/barcode/operations/internal.rst:54 +msgid "When delivering a product, you have to scan the source location if it is different than the one initially set on the transfer. Then, you can start scanning the products that are delivered from this specific location." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:8 -msgid "In the barcode interface, **scan** the products you want create a lot from" +#: ../../inventory/barcode/operations/internal.rst:62 +msgid "Once the different products have been scanned, you have the possibility to scan another location, such as WH/Stock, and another page will be added to your delivery order. You can move from one to the other thanks to the *Previous* and *Next* buttons." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:10 -msgid "If this product should be manage by lots, a window opens to help you scan the lots/serial numbers" +#: ../../inventory/barcode/operations/internal.rst:70 +msgid "Now, you can validate your transfer. To do so, click on *Next* until you reach the last page of the transfer. There, you will be able to validate it." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:13 -msgid "**Scan** a lot barcode, **type** one manually or **leave empty** to generate one automatically" +#: ../../inventory/barcode/operations/internal.rst:78 +msgid "Internal Transfers" msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:16 -msgid "Click or scan **Validate** once you are done" +#: ../../inventory/barcode/operations/internal.rst:80 +msgid "When realizing an internal transfer with multi-location, you first have to scan the source location of the product. Then, you can scan the product in itself, before having to scan the barcode of the destination location." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:18 -msgid "What is the difference between **Lots** and **Serial Numbers**?" +#: ../../inventory/barcode/operations/internal.rst:85 +msgid "If the source and destination of the internal transfers are already correct, you don’t need to scan them." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:20 -msgid "**Lot** numbers are attributed to several identical products, so each time you scan a lot number, Odoo will add one on the product count." +#: ../../inventory/barcode/operations/internal.rst:89 +msgid "Transfers with Tracked Products" msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:24 -msgid "On the opposite, a **serial number** is unique, and represented by only one barcode, sticked on only one item. This means that Odoo won't accept scanning the same serial number more than once per operation." +#: ../../inventory/barcode/operations/internal.rst:91 +msgid "If you work with products tracked by lot/serial numbers, you have two ways of working:" msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:32 -msgid "Here, we configured **Lu - Petit Beukelaer** tracking by lots." +#: ../../inventory/barcode/operations/internal.rst:94 +msgid "If you work with serial/lot numbers taking all products into consideration, you can scan the barcode of the lot/serial number and Odoo will increase the quantity of the product, setting its lot/serial number." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:37 -msgid "Scan a product from this incoming shipment, then scan the lot number of each product (you can also use the keyboard)." +#: ../../inventory/barcode/operations/internal.rst:99 +msgid "If you have the same lot/serial number for different products, you can work by scanning the product barcode first, and then the barcode of the lot/serial number." msgstr "" -#: ../../inventory/barcode/operations/lots_serial_numbers.rst:43 -msgid "Click save/scan **Validate** and you are done." +#: ../../inventory/barcode/operations/transfers_scratch.rst:3 +msgid "Create a Transfer from Scratch" msgstr "" -#: ../../inventory/barcode/operations/receipts.rst:3 -msgid "How to process incoming receipts?" +#: ../../inventory/barcode/operations/transfers_scratch.rst:5 +msgid "To create a transfer from the *Barcode* application, you first need to print the operation type barcodes. To do so, you can download the *Stock barcode sheet* from the home page of the app." msgstr "" -#: ../../inventory/barcode/operations/receipts.rst:5 -msgid "There are two approaches to process incoming receipts: you can either work on printed documents (and scan lines on the documents), or on a screen (and scan products directly)." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:10 -msgid "Process printed incoming receipts:" -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:12 -msgid "Print incoming receipts of the day by selecting all documents from the **To Receive** list and print **Picking Operations** from the top menu." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:16 -msgid "Once you start processing your incoming receipts, scan the barcode on the top-right corner of the document to load the right record on the screen." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:20 -msgid "Then, scan the barcode of every product, or scan the barcode of the product on the picking line if the barcode on the product is not easily accessible, visible or is missing." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:28 -msgid "Process incoming receipts from a computer or mobile device:" -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:30 -msgid "Load all the incoming receipts marked as **To Receive**, and open the first one." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:35 -msgid "When you've picked all the items, click the **Validate** button or scan the **Validate** barcode action to finish the Operation." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:38 -msgid "Move to the next incoming receipt to process by clicking on the top-right right **arrow** or scanning the **Pager-Next** barcode action." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:42 -#: ../../inventory/management/delivery/scheduled_dates.rst:137 -msgid "Example" -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:44 -msgid "Open operation interface." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:49 -msgid "Scan." -msgstr "" - -#: ../../inventory/barcode/operations/receipts.rst:54 -msgid "The picking appears. Scan items and/or fill in informations using the mouse and keyboard." +#: ../../inventory/barcode/operations/transfers_scratch.rst:12 +msgid "Once done, you can scan the one for which you want to create a new document. Then, an empty document will be created and you will be able to scan your products to populate it." msgstr "" #: ../../inventory/barcode/setup.rst:3 @@ -297,212 +320,39 @@ msgid "By default, Odoo has a 50 milliseconds delay between each successive scan msgstr "" #: ../../inventory/barcode/setup/software.rst:3 -msgid "How to activate the barcodes in Odoo?" +msgid "Activate the Barcodes in Odoo" msgstr "" #: ../../inventory/barcode/setup/software.rst:5 -msgid "The barcode scanning features can save you a lot of the time usually lost switching between the keyboard, the mouse and the scanner. Properly attributing barcodes to products, pickings locations, etc. allows you to work more efficiently by controlling the software almost exclusively with the barcode scanner." +msgid "The barcode scanning features can save you a lot of time usually lost switching between the keyboard, the mouse and the scanner. Properly attributing barcodes to products, pickings locations, etc. allows you to work more efficiently by controlling the software almost exclusively with the barcode scanner." msgstr "" #: ../../inventory/barcode/setup/software.rst:12 -msgid "Set products barcodes" -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:17 -msgid "In order to fill a picking or to perform an inventory, you need to make sure that your products are encoded in Odoo along with their barcodes. If this is not already done, you can fill in the products barcodes through a handy interface. Go to :menuselection:`Inventory --> Configuration --> Settings` and click :menuselection:`Operations --> Barcode Scanner`. Click Save, and go back into the previous screen to click Configure Product Barcodes. This interface can also be accessed via the planner." -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:28 -msgid "Product variants: be careful to add barcodes directly on the variant, and not the template product (otherwise you won't be able to differentiate them)." -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:33 -msgid "Set locations barcodes" -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:38 -msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Warehouse Management --> Locations`. There is button in the **Print** menu that you can use to print the locations names and barcodes. There are 4 barcodes per page, arranged in a way that is convenient to print on sticker paper." -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:47 -msgid "Example of location naming: **warehouse short name** - **location short name** - (**Corridor X** - **Shelf Y** - **Height Z**) Example: A032-025-133" -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:54 -msgid "Barcode formats" -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:56 -msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization: you must pay the International Article Numbering Association a fee in exchange for an EAN code sequence (that's why no two products in a store will ever have the same EAN code)." -msgstr "" - -#: ../../inventory/barcode/setup/software.rst:61 -msgid "Still, as Odoo supports any string as a barcode, so you can always define your own barcode format for internal use." -msgstr "" - -#: ../../inventory/management.rst:3 -msgid "Warehouse Management" -msgstr "" - -#: ../../inventory/management/adjustment.rst:3 -msgid "Inventory Adjustment" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:3 -msgid "How to make the initial inventory?" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:5 -msgid "One of the most important feature in an warehouse management software is to keep the inventory right." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:8 -msgid "Once your products have been defined, it is time to make your initial inventory. You will reflect reality by inventorying the right quantities in the right locations." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:13 -#: ../../inventory/management/lots_serial_numbers/lots.rst:55 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:34 -msgid "Product Configuration" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:15 -msgid "In the Inventory module, open the :menuselection:`Inventory Control --> Products`, then click on **Create** to create a new product. Configure the product type so that it is **Stockable** and not a consumable." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:23 -msgid "Start the initial inventory" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:26 -msgid "Update the product quantity for one product" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:28 -msgid "In the product you just created, you can see in the upper tiles that we have 0 product On Hand. Click on the **Update qty on Hand** button." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:31 -msgid "A new window opens. In the **New Quantity on Hand** field, type the quantity of product you currently hold in stock, then click on **Apply**." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:39 -msgid "if you are using multiple locations for your warehouse, you will be able to set the location of your product from this screen." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:42 -msgid "You can now see from the On Hand tab that the quantity has been updated." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:47 -msgid "Now, if you check the **Inventory Adjustments** in the **Inventory Control** menu, you will see that a new line named \"INV: (name of your product)\" has automatically been created and validated by the system." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:55 -msgid "Multiple products at once" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:57 -msgid "Create all the products for which you want to follow the stock (as stockable products). Once the required products in stock have been defined, use an initial inventory operation to put the current quantities into the system by location. Go to :menuselection:`Inventory Control --> Inventory Adjustments` to start your initial inventory." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:63 -msgid "Give it a name (for example Initial Inventory) and select the stock location of your inventory. Note that when you select a parent location (such as Stock, which might be split into sub locations), you can also select the sub (or child) locations." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:71 -msgid "You can choose between making an inventory for all products, for a few or only for one. In this case, we choose the **All products** option." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:79 -msgid "If you need your stock valuation to be done in a different period than the one that will be selected by default according to the inventory end date, enter the corresponding accounting period in the Force Valuation Period field. The accounting module needs to be installed." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:84 -msgid "Click the **Start Inventory** button. Depending on the type of inventory you have chosen (all products or selected ones) you might have to add products manually by clicking on **Add an item**." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:88 -msgid "Add the **Real Quantity** that you have in your stock for each product." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:92 -msgid "additional information will be available according to the options you activated (multi-locations, serial number, consignee stocks)." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:98 -msgid "Click the **Validate Inventory** button to confirm the inventory and post it." -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:102 -msgid "Reporting" -msgstr "" - -#: ../../inventory/management/adjustment/initial_inventory.rst:104 -msgid "To check the current stock, go to :menuselection:`Inventory Control --> Products`, and click on the **list button**:" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:3 -msgid "How to choose between minimum stock rule and make to order?" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:5 -msgid "**Minimum Stock rules** and **Make to Order** have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:10 -#: ../../inventory/settings/products/strategies.rst:10 -msgid "Terminology" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:13 -#: ../../inventory/settings/products/strategies.rst:13 -msgid "Minimum stock rule" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:15 -msgid "**Minimum Stock** rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement with the quantity needed to reach the maximum stock level." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:22 -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:56 -#: ../../inventory/settings/products/strategies.rst:22 -#: ../../inventory/settings/products/strategies.rst:58 -msgid "Make to Order" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:24 -msgid "The **Make to Order** function will trigger a **Purchase Order** of the amount of the **Sales Order** related to the product. The system will **not** check the current stock valuation. This means that a draft purchase order will be generated regardless of the quantity on hand of the product." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:30 #: ../../inventory/management/delivery/delivery_countries.rst:12 #: ../../inventory/management/delivery/inventory_flow.rst:37 #: ../../inventory/management/delivery/label_type.rst:13 -#: ../../inventory/management/delivery/one_step.rst:13 -#: ../../inventory/management/delivery/packaging_type.rst:13 -#: ../../inventory/management/delivery/three_steps.rst:34 -#: ../../inventory/management/delivery/two_steps.rst:29 +#: ../../inventory/management/delivery/packaging_type.rst:9 +#: ../../inventory/management/delivery/two_steps.rst:6 #: ../../inventory/management/incoming/handle_receipts.rst:50 -#: ../../inventory/management/incoming/three_steps.rst:28 -#: ../../inventory/management/incoming/two_steps.rst:21 -#: ../../inventory/management/misc/owned_stock.rst:22 -#: ../../inventory/management/misc/scrap.rst:25 -#: ../../inventory/overview/concepts/double-entry.rst:159 -#: ../../inventory/overview/concepts/double-entry.rst:164 -#: ../../inventory/routes/concepts/cross_dock.rst:21 +#: ../../inventory/management/incoming/two_steps.rst:6 +#: ../../inventory/management/misc/email_delivery.rst:6 +#: ../../inventory/management/misc/owned_stock.rst:18 +#: ../../inventory/management/misc/scrap.rst:19 +#: ../../inventory/management/misc/sms_delivery.rst:6 +#: ../../inventory/management/products/strategies.rst:30 +#: ../../inventory/management/products/uom.rst:16 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:25 +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:6 +#: ../../inventory/management/warehouses/location_creation.rst:6 +#: ../../inventory/management/warehouses/warehouse_creation.rst:6 +#: ../../inventory/routes/concepts/cross_dock.rst:14 #: ../../inventory/routes/concepts/inter_warehouse.rst:10 #: ../../inventory/routes/concepts/procurement_rule.rst:25 #: ../../inventory/routes/concepts/push_rule.rst:29 #: ../../inventory/routes/concepts/use_routes.rst:22 #: ../../inventory/routes/costing/landed_costs.rst:17 -#: ../../inventory/routes/strategies/putaway.rst:23 +#: ../../inventory/routes/strategies/putaway.rst:10 #: ../../inventory/routes/strategies/removal.rst:18 -#: ../../inventory/settings/products/strategies.rst:30 -#: ../../inventory/settings/products/uom.rst:17 -#: ../../inventory/settings/products/variants.rst:114 -#: ../../inventory/settings/warehouses/location_creation.rst:6 -#: ../../inventory/settings/warehouses/warehouse_creation.rst:6 #: ../../inventory/shipping/operation/invoicing.rst:16 #: ../../inventory/shipping/operation/labels.rst:15 #: ../../inventory/shipping/operation/multipack.rst:13 @@ -511,135 +361,52 @@ msgstr "" msgid "Configuration" msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:33 -#: ../../inventory/settings/products/strategies.rst:33 -msgid "Minimum stock rules" +#: ../../inventory/barcode/setup/software.rst:14 +msgid "To use this feature, you first need to activate the *Barcode* functionality via *Inventory > Settings > Barcode Scanner*. Once you have ticked the feature, you can hit save." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:35 -msgid "The Minimum Stock Rules configuration is available through the menu :menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the drop down menu. There, click on **Create** to set minimum and maximum stock values for a given product." +#: ../../inventory/barcode/setup/software.rst:22 +msgid "Set Product Barcodes" msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Active" +#: ../../inventory/barcode/setup/software.rst:24 +msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to *Settings > Configure Products Barcodes*." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "If the active field is set to False, it will allow you to hide the orderpoint without removing it." +#: ../../inventory/barcode/setup/software.rst:31 +msgid "Then, you have the possibility to assign barcodes to your products directly at creation on the product form." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Product Unit of Measure" +#: ../../inventory/barcode/setup/software.rst:41 +msgid "Be careful to add barcodes directly on the product variants and not on the template product. Otherwise, you won’t be able to differentiate them." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Default unit of measure used for all stock operations." +#: ../../inventory/barcode/setup/software.rst:46 +msgid "Set Locations Barcodes" msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Procurement Group" +#: ../../inventory/barcode/setup/software.rst:48 +msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in *Inventory > Configuration > Locations*." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by stock rules will be grouped into one big picking." +#: ../../inventory/barcode/setup/software.rst:59 +msgid "You can easily print the barcode you allocate to the locations via the *Print* menu." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Minimum Quantity" +#: ../../inventory/barcode/setup/software.rst:63 +msgid "Barcode Formats" msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "When the virtual stock goes below the Min Quantity specified for this field, Odoo generates a procurement to bring the forecasted quantity to the Max Quantity." +#: ../../inventory/barcode/setup/software.rst:65 +msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization. You must pay the International Article Numbering Association a fee in exchange for an EAN code sequence." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Maximum Quantity" +#: ../../inventory/barcode/setup/software.rst:69 +msgid "Still, as Odoo supports any string as a barcode, you can always define your own barcode format for internal use." msgstr "" -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "When the virtual stock goes below the Min Quantity, Odoo generates a procurement to bring the forecasted quantity to the Quantity specified as Max Quantity." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Quantity Multiple" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "The procurement quantity will be rounded up to this multiple. If it is 0, the exact quantity will be used." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Lead Time" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0 -msgid "Number of days after the orderpoint is triggered to receive the products or to order to the vendor" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:45 -msgid "Then, click on your product to access the related product form and, on the **Inventory submenu**, do not forget to select a supplier." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:52 -msgid "Don't forget to select the right product type in the product form. A consumable can not be stocked and will thus not be accounted for in the stock valuation." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:58 -msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory module --> Inventory control --> Products` (or any other module where products are available)." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:62 -msgid "On the product form, under **Inventory**, click on **Make To Order**." -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:68 -#: ../../inventory/settings/products/strategies.rst:70 -msgid "Choice between the two options" -msgstr "" - -#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:70 -#: ../../inventory/settings/products/strategies.rst:72 -msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:3 -msgid "TaKing stock from different warehouses" -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:5 -msgid "When you plan to deliver a customer, you don’t know in advance if the products will come from Warehouse A or Warehouse B. You may, in some cases, need to take stock from different warehouses. With *Odoo*, you can configure this by using the concept of virtual warehouses. Let us show you how to set those virtual warehouses." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:12 -msgid "Set up virtual warehouses" -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:14 -msgid "Let’s say you have two warehouses: Warehouse A and Warehouse B. Create a new warehouse, that will be a virtual one. It will allow you to take the stock from A or B. To do so, go to your inventory app settings and enable the multi-warehouses feature. Then, go to the warehouses menu and click on create." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:24 -msgid "The *Storage Location* feature will be automatically enabled. Good news, because you will need it later in the process." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:27 -msgid "Now, you have to make sure that the main stock locations of warehouse A and warehouse B are children locations of the main stock location of warehouse A + B. Go to the locations menu, and edit the main location of your two warehouses. Then, change their parent location to main location of warehouse A+B." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:37 -msgid "Sell a product from the virtual warehouse" -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:39 -msgid "Let’s say you have two products, one stored in warehouse A and one stored in warehouse B. Now, you can create a new quotation for one of each product. Go to other information and choose Warehouse A+B in the shipping information." -msgstr "" - -#: ../../inventory/management/adjustment/virtual_warehouses.rst:47 -msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B." -msgstr "" - -#: ../../inventory/management/delivery.rst:3 -msgid "Delivery Orders" +#: ../../inventory/management.rst:3 +msgid "Warehouse Management" msgstr "" #: ../../inventory/management/delivery/cancel_order.rst:3 @@ -649,24 +416,13 @@ msgstr "" #: ../../inventory/management/delivery/cancel_order.rst:6 #: ../../inventory/management/delivery/delivery_countries.rst:6 #: ../../inventory/management/delivery/label_type.rst:6 -#: ../../inventory/management/delivery/one_step.rst:6 -#: ../../inventory/management/delivery/packaging_type.rst:6 -#: ../../inventory/management/delivery/three_steps.rst:6 -#: ../../inventory/management/delivery/two_steps.rst:6 #: ../../inventory/management/incoming/handle_receipts.rst:6 -#: ../../inventory/management/incoming/three_steps.rst:6 -#: ../../inventory/management/incoming/two_steps.rst:6 -#: ../../inventory/management/lots_serial_numbers/lots.rst:6 -#: ../../inventory/management/misc/scrap.rst:6 #: ../../inventory/overview.rst:3 -#: ../../inventory/overview/process/sale_to_delivery.rst:6 #: ../../inventory/routes/concepts/procurement_rule.rst:6 #: ../../inventory/routes/concepts/push_rule.rst:6 #: ../../inventory/routes/concepts/use_routes.rst:6 #: ../../inventory/routes/costing/landed_costs.rst:6 -#: ../../inventory/routes/strategies/putaway.rst:6 #: ../../inventory/routes/strategies/removal.rst:6 -#: ../../inventory/settings/products/uom.rst:6 #: ../../inventory/shipping/operation/cancel.rst:6 #: ../../inventory/shipping/operation/invoicing.rst:6 #: ../../inventory/shipping/operation/labels.rst:6 @@ -739,98 +495,103 @@ msgid "This process doesn't work in backend. We assume that when you create a Sa msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:3 -msgid "How to send products to customers directly from suppliers (drop-shipping)?" +msgid "Send Products to Customers Directly from Suppliers (Drop-shipping)" msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:6 -msgid "What is drop-shipping?" +msgid "What is Drop-Shipping?" msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:8 -msgid "Drop-Shipping is a system that allows orders taken from your store to be shipped straight from your supplier to your customer. On a usual delivery system, products are sent from your supplier to your warehouse to be put in stock, and then shipped to your customers after ordering. With drop-shipping, no item is stocked. When a customer places an order in your shop, the item is delivered straight from the supplier to the customer. Therefore, the product doesn't need to get through your warehouse." +msgid "Drop-Shipping is a system that allows orders taken from your store to be shipped straight from your supplier to your customer. On a usual delivery system, products are sent from your supplier to your warehouse to be put in stock and then shipped to your customers after ordering." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:18 -msgid "Points to be considered while implementing drop-shipping" +#: ../../inventory/management/delivery/dropshipping.rst:13 +msgid "With drop-shipping, no item is stocked. When a customer places an order in your shop, the item is delivered straight from the supplier to the customer. Therefore, the product doesn't need to get through your warehouse." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:20 -msgid "Use drop-shipping only for the products you can't or don't want to keep in stock. One reason is that you'll always make smaller margins on items that are drop-shipped, so you should keep it only for items that take up a lot of space in your warehouse." +#: ../../inventory/management/delivery/dropshipping.rst:19 +msgid "Points to be Considered while Implementing Drop-Shipping" msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:25 -msgid "Drop-shipping is best for niche products. Chances are that products that are in high demand are being offered by large suppliers at a fraction of the price you'll be able to charge, so using a more costly shipping method won't be financially rewarding. But if your product is unique, then it makes sense!" +#: ../../inventory/management/delivery/dropshipping.rst:24 +msgid "Use drop-shipping only for the products you can't or don't want to keep in stock." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:31 -msgid "To protect your customers from bad experiences, test drop-shipping companies for yourself beforehand and list the best ones." +#: ../../inventory/management/delivery/dropshipping.rst:22 +msgid "One reason is that you'll always make smaller margins on items that are drop-shipped, so you should keep it only for items that take up a lot of space in your warehouse." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:34 -msgid "Make sure time is not against you. Drop-shipping should take a reasonable amount of time and surely not more than it would have taken you to handle it all by yourself. It's also nice to be able to provide your customers with a tracking number." +#: ../../inventory/management/delivery/dropshipping.rst:30 +msgid "Drop-shipping is best for niche products." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:39 -msgid "Items have to be available from your supplier. It's good to know if the product you're selling is available upstream. If you don't have that information, inform your customers that you don't hold the item in stock and that it's subject to availability from a third party." +#: ../../inventory/management/delivery/dropshipping.rst:27 +msgid "Chances are that products that are in high demand are being offered by large suppliers at a fraction of the price you'll be able to charge, so using a more costly shipping method won't be financially rewarding. But if your product is unique, then it makes sense!" msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:46 -msgid "For more information and insights on Drop-shipping, read our blog on `What is drop-shipping and how to use it `__." +#: ../../inventory/management/delivery/dropshipping.rst:33 +msgid "To protect your customers from bad experiences." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:50 -msgid "Configuring drop-shipping" +#: ../../inventory/management/delivery/dropshipping.rst:33 +msgid "Test drop-shipping companies for yourself beforehand and list the best ones." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:37 +msgid "Make sure time is not against you." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:36 +msgid "Drop-shipping should take a reasonable amount of time and surely not more than it would have taken you to handle it all by yourself. It's also nice to be able to provide your customers with a tracking number." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:44 +msgid "Items have to be available from your supplier." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:40 +msgid "It's good to know if the product you're selling is available upstream. If you don't have that information, inform your customers that you don't hold the item in stock and that it's subject to availability from a third party." +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:47 +msgid "For more information and insights about Drop-Shipping, you can read our blog: `*What is drop-shipping and how to use it* `__." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:52 -msgid "Open the menu :menuselection:`Inventory --> Configuration --> Settings`. Go to **Location & Warehouse**, locate the **Dropshipping** option and tick the box **Allow suppliers to deliver directly to your customers**. Then, click on **Apply**." +msgid "Configure Drop-Shipping" +msgstr "" + +#: ../../inventory/management/delivery/dropshipping.rst:54 +msgid "Activate the functionality in the *Purchase* application by going to *Configuration > Settings*." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:60 -msgid "Then go to the menu :menuselection:`Sales --> Configuration --> Settings`. Locate **Order Routing** and tick the box **Choose specific routes on sales order lines (advanced)**. Click on **Apply**." +msgid "Then, go to the *Inventory* app, in *Configuration > Settings* to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:67 -msgid "Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a supplier to the products you want to dropship." -msgstr "" - -#: ../../inventory/management/delivery/dropshipping.rst:74 -msgid "How to send products from the suppliers directly to the customers" +#: ../../inventory/management/delivery/dropshipping.rst:68 +msgid "Now, in the *Sales* app, go to *Products > Products*. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:76 -msgid "Create a **Sales Order** and specify on a sales order line for your products that the route is **Dropshipping**." +msgid "Send Products from the Suppliers Directly to the Customers" msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:82 -msgid "Open the menu :menuselection:`Purchases --> Purchases --> Requests for Quotation`. The draft purchase order is automatically created from the procurement with the drop-shipping route. Once the order is confirmed, you will see that one shipment has been created." +#: ../../inventory/management/delivery/dropshipping.rst:78 +msgid "Create a *Sales Order* and add the product on which you just set the vendor. Add the *Route* field thanks to the widget on the right of the sale order line. Now, you are able to specify that your products’ route is *Drop-Shipping*." msgstr "" -#: ../../inventory/management/delivery/dropshipping.rst:90 -msgid "To confirm the sending from the vendor to the customer, go back to **Inventory** app. On the dashboard, click on **# TO RECEIVE** on the dropship card." +#: ../../inventory/management/delivery/dropshipping.rst:89 +msgid "Once the sale order is confirmed, Odoo automatically generates a *Request for Quotation* for the supplier who will proceed to the drop-shipping. You can find it in the *Purchase* app, with the sale order as *Source Document*." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:97 -msgid "It will open the list of drop-shipping transfers. Validate the transfer once it has been done. The items will be directly delivered from the partner to the customer without transiting to your warehouse." -msgstr "" - -#: ../../inventory/management/delivery/dropshipping.rst:103 -msgid ":doc:`inventory_flow`" +msgid "Once this *Purchase Order* is confirmed, a *Receipt Order* is created and linked to it. The source location is the vendor location and the destination location is the customer location. Then, the product won’t go through your own stock when you validate the dropship document." msgstr "" #: ../../inventory/management/delivery/dropshipping.rst:105 -#: ../../inventory/management/delivery/one_step.rst:63 -#: ../../inventory/management/delivery/three_steps.rst:159 -#: ../../inventory/management/delivery/two_steps.rst:129 -#: ../../inventory/management/incoming/handle_receipts.rst:70 -#: ../../inventory/overview/concepts/double-entry.rst:179 -#: ../../inventory/settings/products/uom.rst:124 -#: ../../inventory/settings/products/variants.rst:222 -msgid "Todo" -msgstr "" - -#: ../../inventory/management/delivery/dropshipping.rst:106 -msgid "Add link to this section when available * How to analyse the performance of my vendors?" +msgid "You can also easily access the dropship document directly from your inventory dashboard." msgstr "" #: ../../inventory/management/delivery/inventory_flow.rst:3 @@ -931,132 +692,98 @@ msgid "The default label type is paper letter, and if you choose the label type msgstr "" #: ../../inventory/management/delivery/one_step.rst:3 -msgid "How to process delivery orders in one step (shipping)?" +#: ../../inventory/management/incoming/one_step.rst:3 +msgid "Process a Receipt in one step (Receipt)" msgstr "" -#: ../../inventory/management/delivery/one_step.rst:8 -msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a one-step operation: once all goods are available, they are able to be shipped in a single delivery order." +#: ../../inventory/management/delivery/one_step.rst:5 +#: ../../inventory/management/incoming/one_step.rst:5 +msgid "There is no configuration needed to receive in one step. The default incoming shipments are configured to be directly received from the vendors to the stock." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:15 -msgid "There is no configuration needed. The default outgoing shipments are configured to be directly delivered from the stock." +#: ../../inventory/management/delivery/one_step.rst:9 +#: ../../inventory/management/incoming/one_step.rst:9 +msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to *Configuration > Warehouses* and edit the warehouse in question." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:18 -msgid "However, if **advance routes** is activated and you set another shipping configuration on your warehouse, you can set it back to the one-step delivery configuration. Go to :menuselection:`Configuration --> Warehouses` and edit the concerned warehouse." +#: ../../inventory/management/delivery/one_step.rst:14 +#: ../../inventory/management/incoming/one_step.rst:14 +msgid "Set the *Incoming Shipments* option to *Receive goods directly (1 step)*." +msgstr "" + +#: ../../inventory/management/delivery/one_step.rst:21 +#: ../../inventory/management/incoming/one_step.rst:21 +msgid "Create a Purchase Order" msgstr "" #: ../../inventory/management/delivery/one_step.rst:23 -msgid "Set the outgoing shippings the option to **Ship directly from stock (Ship Only)**" +#: ../../inventory/management/incoming/one_step.rst:23 +msgid "To create a *Request for Quotation*, go to the *Purchase* application and click on *Create*. Then, add some storable products to receive and confirm the *RfQ*." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:30 -#: ../../inventory/management/delivery/two_steps.rst:68 -msgid "Create a Sales Order" -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:32 -msgid "Create a sales order (From quotation to sales order) with some products to deliver." +#: ../../inventory/management/delivery/one_step.rst:27 +#: ../../inventory/management/incoming/one_step.rst:27 +msgid "Notice that, now, we see 1 receipt associated with the purchase order you just created. If you click on the button, you will see your receipt order." msgstr "" #: ../../inventory/management/delivery/one_step.rst:35 -msgid "Notice that we now see ``1`` delivery associated with this sales order in the **stat button** above the sales order." +#: ../../inventory/management/incoming/one_step.rst:35 +msgid "Process a Receipt" msgstr "" -#: ../../inventory/management/delivery/one_step.rst:41 -msgid "If you click on the **1 Delivery** stat button, you should now see your picking." +#: ../../inventory/management/delivery/one_step.rst:37 +#: ../../inventory/management/incoming/one_step.rst:37 +msgid "You can also fin the receipt directly from the *Inventory* app. When on the dashboard, you can click the *1 TO PROCESS* button under the *Receipts* Kanban card. Then, you will see your receipt." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:45 -#: ../../inventory/management/delivery/three_steps.rst:99 -#: ../../inventory/management/delivery/two_steps.rst:88 -msgid "Process a Delivery" +#: ../../inventory/management/delivery/one_step.rst:44 +#: ../../inventory/management/incoming/one_step.rst:44 +msgid "Now, enter the picking that you want to process. You will be able to click on *Validate* to complete the move directly as products coming from suppliers are considered as being always available." msgstr "" -#: ../../inventory/management/delivery/one_step.rst:47 -#: ../../inventory/management/delivery/three_steps.rst:143 -#: ../../inventory/management/delivery/two_steps.rst:113 -msgid "Go to **Inventory** and click on the **# TO DO** link under the **Delivery Orders** kanban card." -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:53 -#: ../../inventory/management/delivery/three_steps.rst:110 -#: ../../inventory/management/delivery/three_steps.rst:130 -#: ../../inventory/management/delivery/three_steps.rst:149 -#: ../../inventory/management/delivery/two_steps.rst:99 -#: ../../inventory/management/delivery/two_steps.rst:119 -#: ../../inventory/management/incoming/three_steps.rst:99 -msgid "Click on the picking that you want to process." -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:55 -msgid "Click on **Validate** to complete the move from **WH/Output** to the **customer**." -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:58 -msgid "This has completed the **Shipping Step** and the WH/OUT should now show **Done** in the status column at the top of the page, which means the product has been shipped to the customer." -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:64 -msgid "Ajouter un lien vers ces pages quand elles existeront - Process Overview: From sales orders to delivery orders" -msgstr "" - -#: ../../inventory/management/delivery/one_step.rst:67 -#: ../../inventory/management/delivery/three_steps.rst:163 -#: ../../inventory/management/delivery/two_steps.rst:133 -msgid "Process Overview: From purchase orders to receptions" +#: ../../inventory/management/delivery/one_step.rst:51 +#: ../../inventory/management/incoming/one_step.rst:51 +msgid "Once you *Validate* the receipt, the products leave the *Supplier Location* to enter your *WH/Stock Location*. You can easily see that the receipt took place thanks to the status of the document, which is now *Done*." msgstr "" #: ../../inventory/management/delivery/packaging_type.rst:3 -msgid "How can you change the packaging type for your sale order?" +msgid "Deliver Products in Packages" msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:8 -msgid "Odoo gives you the possibility to change the default packaging type and adapt the packaging the way you want it, depending on the weight of the order." +#: ../../inventory/management/delivery/packaging_type.rst:5 +msgid "In Odoo, you have the possibility to deliver your products in different packages, depending on the volume and or weight of your products." msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:15 -msgid "In the **Inventory** module, Go to **Configuration** and then click on **Settings**." +#: ../../inventory/management/delivery/packaging_type.rst:11 +msgid "First, you need to activate the *Delivery Packages* feature in the *Inventory app > Configuration > Settings*." msgstr "" #: ../../inventory/management/delivery/packaging_type.rst:18 -msgid "In :menuselection:`Traceability --> Packages`, flag **Record packages used on packing : pallets, boxes,...**" +msgid "Proceed to a Delivery" msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:24 -msgid "*Sale process*" +#: ../../inventory/management/delivery/packaging_type.rst:20 +msgid "Now, you can create a planned delivery with some products in it. You will have the possibility to create new packages and assign them to the stock move lines." msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:26 -msgid "In the **Sales** module, go to **Sales** and click on **Sale Order**." +#: ../../inventory/management/delivery/packaging_type.rst:27 +msgid "Then, you can define the package type from this window. Once the delivery order is validated, you can retrieve which products have been included in the package." msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:28 -msgid "Create your new Sale Order, and **Confirm the Sale**." +#: ../../inventory/management/delivery/packaging_type.rst:34 +msgid "A button will appear at the delivery stage, allowing you to find all the packages which were part of the delivery order." msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:33 -msgid "Once you've confirmed the Sale, you need to click on **Delivery**, to be redirected to the Delivery order." +#: ../../inventory/management/delivery/packaging_type.rst:44 +msgid "Use the Put in Pack button" msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:36 -msgid "Click on **Edit**, and you can now change the packaging." +#: ../../inventory/management/delivery/packaging_type.rst:46 +msgid "Another way to put products in packs is to use the *Put in Pack* button. It will automatically assign a pack to the number of products which is set as *Done* and duplicate the stock move line if necessary." msgstr "" -#: ../../inventory/management/delivery/packaging_type.rst:41 -msgid "In the **Operations** tab, in the last column, change the **0** and put the number of products that you want to pack together. Then click on **Put in Pack**." -msgstr "" - -#: ../../inventory/management/delivery/packaging_type.rst:48 -msgid "Choose the type of packaging that you want. You can also see that the weight has been adapted to your package, and you can change it manually if you want it to be more precise. Then click on **Save**." -msgstr "" - -#: ../../inventory/management/delivery/packaging_type.rst:52 -msgid "Repeat the operation until all the products are put in pack." -msgstr "" - -#: ../../inventory/management/delivery/packaging_type.rst:54 -msgid "Finally, click on **Validate** to confirm the delivery." +#: ../../inventory/management/delivery/packaging_type.rst:53 +msgid "Then, you will be able to update the different packages created this way, directly via the *Packages* button." msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:3 @@ -1068,6 +795,7 @@ msgid "Scheduled dates are computed in order to be able to plan deliveries, rece msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:13 +#: ../../inventory/management/planning/scheduled_date.rst:18 msgid "Configuring lead times" msgstr "" @@ -1080,6 +808,7 @@ msgid "Configuration of the different lead times are made as follows:" msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:22 +#: ../../inventory/management/planning/scheduled_date.rst:28 msgid "At a product level" msgstr "" @@ -1120,6 +849,7 @@ msgid "Don't forget to tick the manufacturing box in inventory if you want to cr msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:67 +#: ../../inventory/management/planning/scheduled_date.rst:74 msgid "At the company level" msgstr "" @@ -1160,6 +890,7 @@ msgid "Note that you can also configure a default Manufacturing lead time from h msgstr "" #: ../../inventory/management/delivery/scheduled_dates.rst:110 +#: ../../inventory/management/planning/scheduled_date.rst:134 msgid "At route level" msgstr "" @@ -1187,6 +918,11 @@ msgstr "" msgid "Odoo offers the possibility to select a requested date by the client by indicating the date in the other information tab of the sales order. If this date is earlier than the theoreticaly computed date odoo will automatically display a warning." msgstr "" +#: ../../inventory/management/delivery/scheduled_dates.rst:137 +#: ../../inventory/management/planning/scheduled_date.rst:173 +msgid "Example" +msgstr "" + #: ../../inventory/management/delivery/scheduled_dates.rst:139 msgid "As an example, you may sell a car today (January 1st), that is purchased on order, and you promise to deliver your customer within 20 days (January 20). In such a scenario, the scheduler may trigger the following events, based on your configuration:" msgstr "" @@ -1208,235 +944,202 @@ msgid "January 8: trigger a purchase request to your purchase team, since the te msgstr "" #: ../../inventory/management/delivery/three_steps.rst:3 -msgid "How to process delivery orders in three steps (pick + pack + ship)?" +#: ../../inventory/management/incoming/three_steps.rst:3 +msgid "Process a Receipt in three steps (Input + Quality + Stock)" msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:8 -msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default on a **one-step** operation: once all goods are available, they can be shipped in bulk in a single delivery order. However, that process may not reflect the reality and your company may require more steps before shipping." +#: ../../inventory/management/delivery/three_steps.rst:5 +#: ../../inventory/management/incoming/three_steps.rst:5 +msgid "In many companies, it is necessary to assess the received good. The goal is to check that the products correspond to the quality requirements agreed with the suppliers. Therefore, adding a *quality control step* in the goods receipt process can become essential." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:14 -msgid "With the **three steps** process (**Pick + Pack + Ship**), the items are transferred to a packing area, where they will be assembled by area of destination, and then set to outbound trucks for final delivery to the customers." +#: ../../inventory/management/delivery/three_steps.rst:10 +#: ../../inventory/management/incoming/three_steps.rst:10 +msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the level of the warehouse. By default, the reception is a one-step process, but changing the configuration can allow having 3 steps." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:19 -msgid "A few configuration steps are necessary in order to accomplish **Pick + Pack + Ship** in Odoo. These steps create some additional locations, which by default are called **Output** and **Packing Zone**. So, if your warehouse's code is ``WH``, this configuration will create a location called ``WH/Output`` and another one called ``WH/Packing Zone``." +#: ../../inventory/management/delivery/three_steps.rst:15 +#: ../../inventory/management/incoming/three_steps.rst:15 +msgid "The 3-steps flow is as follows: You receive the goods in an input area, then transfer them into a quality area for *quality control*. When the quality check has been processed, you can move the goods from QC to stock. Of course, you may change the quantity and only transfer to stock the quantity that is valid and decide that you will return the quantity that is not good." +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:23 +#: ../../inventory/management/incoming/three_steps.rst:23 +msgid "Multi-Step Routes" msgstr "" #: ../../inventory/management/delivery/three_steps.rst:25 -msgid "Goods will move from **WH/Stock** to **WH/Packing Zone** in the first step. Then move from **WH/Packing Zone** to **WH/Output**. Then finally it will be delivered from **WH/Output** to its **final destination**." +#: ../../inventory/management/incoming/three_steps.rst:25 +msgid "First, you will need to activate the *multi-step routes* option. Indeed, routes provide a mechanism to chain different actions together. Here, we will chain the picking to the shipping." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:30 -#: ../../inventory/management/delivery/two_steps.rst:25 -msgid "Check out :doc:`inventory_flow` to determine if this inventory flow is the correct method for your needs." +#: ../../inventory/management/delivery/three_steps.rst:29 +#: ../../inventory/management/incoming/three_steps.rst:29 +msgid "To activate *multi-step routes*, open the *inventory app*, and go to *Configuration > Settings* and activate the option. By default, activating *multi-step routes* will also activate *Storage Locations*." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:37 -msgid "Install the Inventory module" +#: ../../inventory/management/delivery/three_steps.rst:38 +#: ../../inventory/management/incoming/three_steps.rst:38 +msgid "Warehouse configuration" msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:39 -msgid "From the **App** menu, search and install the **Inventory** module." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:44 -msgid "You will also need to install the **Sales** module to be able to issue sales orders." +#: ../../inventory/management/delivery/three_steps.rst:40 +#: ../../inventory/management/incoming/three_steps.rst:40 +msgid "Now that *Multi-Step Routes* is activated, go to *Configuration > Warehouse* and open the one you will use to deliver in 3 steps. Then, you can select the option *Pack good, send goods in output and then deliver (3 steps)* as *Outgoing Shipments*." msgstr "" #: ../../inventory/management/delivery/three_steps.rst:48 -msgid "Allow managing routes" +#: ../../inventory/management/incoming/three_steps.rst:48 +msgid "Activating this option will lead to the creation of two new locations, *Output* and *Packing Zone*." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:50 -msgid "Odoo configures movement of delivery orders via **routes**. Routes provide a mechanism to link different actions together. In this case, we will link the picking step to the shipping step." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:54 -msgid "To allow management of routes, go to :menuselection:`Configuration --> Settings`" +#: ../../inventory/management/delivery/three_steps.rst:51 +#: ../../inventory/management/incoming/three_steps.rst:51 +msgid "Of course, you can rename them if you want. To do so, go to *Configuration > Locations* and select the one you want to rename. Change its name and hit save." msgstr "" #: ../../inventory/management/delivery/three_steps.rst:56 -msgid "Under :menuselection:`Location & Warehouse --> Routes`, activate the radio button **Advanced routing of products using rules**. Make sure that the option **Manage several locations per warehouse** is activated as well." +#: ../../inventory/management/incoming/three_steps.rst:56 +msgid "Create a Sales Order" msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:64 -msgid "Configure the warehouse for Pick + Pack + Ship" +#: ../../inventory/management/delivery/three_steps.rst:58 +#: ../../inventory/management/incoming/three_steps.rst:58 +msgid "In the *Sales* app, create a quotation with storable products to deliver. Then, confirm it and three pickings will be created and linked to your sale order." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:66 -msgid "Go to :menuselection:`Configuration --> Warehouses` and edit the warehouse that will be used." +#: ../../inventory/management/delivery/three_steps.rst:65 +#: ../../inventory/management/incoming/three_steps.rst:65 +msgid "Now, click on the button. You should see three different pickings:" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:67 +#: ../../inventory/management/incoming/three_steps.rst:67 +msgid "The first one, with a reference PICK, designates the picking process;" msgstr "" #: ../../inventory/management/delivery/three_steps.rst:69 -msgid "For outgoing shippings, set the option to **Make packages into a dedicated location, bring them to the output location for shipping (Pick + Pack + Ship).**" +#: ../../inventory/management/incoming/three_steps.rst:69 +msgid "The second one, with a reference PACK, is for the packing process;" +msgstr "" + +#: ../../inventory/management/delivery/three_steps.rst:71 +#: ../../inventory/management/incoming/three_steps.rst:71 +msgid "The third one, with a reference OUT, designates the shipping process." msgstr "" #: ../../inventory/management/delivery/three_steps.rst:77 -msgid "Create a Sale Order" +#: ../../inventory/management/incoming/three_steps.rst:77 +msgid "Process the picking, packing, and delivery" msgstr "" #: ../../inventory/management/delivery/three_steps.rst:79 -msgid "From the **Sale** module, create a sales order with some products to deliver." +#: ../../inventory/management/incoming/three_steps.rst:79 +msgid "The first operation to be processed is the picking and has a *Ready* status, while the others are *Waiting Another Operation*. The packing will become *Ready* as soon as the picking is marked as *Done*." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:81 -msgid "Notice that we now see ``3`` transfers associated with this sales order in the **stat button** above the sales order." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:87 -msgid "If you click the button, you should now see three different pickings:" +#: ../../inventory/management/delivery/three_steps.rst:83 +#: ../../inventory/management/incoming/three_steps.rst:83 +msgid "You can enter the picking operation from here, or access it through the inventory app." msgstr "" #: ../../inventory/management/delivery/three_steps.rst:89 -msgid "The first with a reference **PICK** to designate the picking process," +#: ../../inventory/management/incoming/three_steps.rst:89 +msgid "Note that, if you have the product in stock, it will be automatically reserved and you can validate the picking document." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:91 -msgid "The second one with the reference **PACK** that is the packing process," +#: ../../inventory/management/delivery/three_steps.rst:95 +#: ../../inventory/management/incoming/three_steps.rst:95 +msgid "Now that the picking has been validated, the packing order is ready to be processed. Since the documents are chained, the products that have been picked are automatically reserved on the packing order so you can directly validate it." msgstr "" -#: ../../inventory/management/delivery/three_steps.rst:93 -msgid "The last with a reference **OUT** to designate the shipping process." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:102 -#: ../../inventory/management/delivery/two_steps.rst:91 -msgid "How to Process the Picking Step?" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:104 -msgid "Ensure that you have enough product in stock and Go to **Inventory** and click on the **Waiting** link under the **Pick** kanban card." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:112 -#: ../../inventory/management/delivery/two_steps.rst:101 -msgid "Click on **Reserve** to reserve the products if they are available." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:114 -msgid "Click on **Validate** to complete the move from **WH/Stock** to **WH/Packing Zone**." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:116 -msgid "This has completed the picking Step and the **WH/PICK** should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Stock** to **WH/Packing Zone** location, which makes the product available for the next step (Packing)." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:122 -msgid "How to Process the Packing Step?" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:124 -msgid "Go to **Inventory** and click on the **# TRANSFERS** link under the **Pack** kanban card." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:132 -msgid "Click on **Validate** to complete the move from **WH/Packing Zone** to **WH/Output**." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:135 -msgid "This has completed the packing step and the **WH/PACK** should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Packing Zone** to **WH/Output location**, which makes the product available for the next step (Shipping)." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:141 -#: ../../inventory/management/delivery/two_steps.rst:111 -msgid "How to Process the Shipping Step?" -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:151 -msgid "Click on **Validate** to complete the move from **WH/Output** to the **customer** (Click **Apply** to assign the quantities based on the quantities listed in the **To Do** column)." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:155 -msgid "This has completed the shipping step and the **WH/OUT** should now show **Done** in the status column at the top of the page. The product has been shipped to the customer." -msgstr "" - -#: ../../inventory/management/delivery/three_steps.rst:160 -msgid "Link to these sections when available - Process Overview: From sales orders to delivery orders" +#: ../../inventory/management/delivery/three_steps.rst:106 +#: ../../inventory/management/incoming/three_steps.rst:106 +msgid "Then, you can validate your packing. In doing so, the delivery order can be processed. Once again, it will be ready to be validated so you can transfer the products to the customer location." msgstr "" #: ../../inventory/management/delivery/two_steps.rst:3 -msgid "How to process delivery orders in two steps (pick + ship)?" +#: ../../inventory/management/incoming/two_steps.rst:3 +msgid "Process a Receipt in two steps (Input + Stock)" msgstr "" #: ../../inventory/management/delivery/two_steps.rst:8 -msgid "When an order goes to the shipping department for final delivery, Odoo is set up by default to utilize a **one-step** operation: once all goods are available, they are able to be shipped in a single delivery order. However, your company's business process may have one or more steps that happen before shipping. In the **two steps** process, the items in a delivery order are **picked** in the warehouse and brought to an **output location** for **shipping**. The goods are then shipped." +#: ../../inventory/management/incoming/two_steps.rst:8 +msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the *Warehouse* level. By default, the reception is a one-step process, but changing the configuration can allow you to have 2 steps." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:16 -msgid "In order to accomplish a **Pick + Ship** delivery in Odoo, there are a few necessary configuration steps. These steps create an additional location, which by default is called **Output**. So, if your warehouse's code is ``WH``, this configuration will create a location called ``WH/Output``. Goods will move from ``WH/Stock`` to ``WH/Output`` in the first step (picking). Then, they move from ``WH/Output`` to ``WH/Customers`` (in the case of sales orders) in the second step (shipping)." +#: ../../inventory/management/delivery/two_steps.rst:13 +#: ../../inventory/management/incoming/two_steps.rst:13 +msgid "The 2 steps flow is like this: you receive the goods in an input area, then transfer them to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:32 -msgid "Allow management of routes" +#: ../../inventory/management/delivery/two_steps.rst:19 +#: ../../inventory/management/incoming/two_steps.rst:19 +msgid "Activate Multi-Step Routes" +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:21 +#: ../../inventory/management/incoming/two_steps.rst:21 +msgid "The first step is to allow using *multi-step routes*. Indeed, routes provide a mechanism to chain different actions together. In this case, we will chain the unload step in the input area to the step entering the products in stock." +msgstr "" + +#: ../../inventory/management/delivery/two_steps.rst:26 +#: ../../inventory/management/incoming/two_steps.rst:26 +msgid "To allow *multi-step routes*, go to *Configuration > Settings* and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*." msgstr "" #: ../../inventory/management/delivery/two_steps.rst:34 -msgid "Odoo configures movement of delivery orders via the **routes**. Routes provide a mechanism to chain different actions together. In this case, we will chain the picking step to the shipping step." +#: ../../inventory/management/incoming/two_steps.rst:34 +msgid "Configure warehouse for receipt in 2 steps" msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:38 -msgid "To allow management of routes, go to :menuselection:`Configuration --> Settings`." +#: ../../inventory/management/delivery/two_steps.rst:36 +#: ../../inventory/management/incoming/two_steps.rst:36 +msgid "Once *multi-step routes* is activated, you can go to *Configuration > Warehouse* and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:40 -msgid "Ensure that the radio button **Advanced routing of products using rules** is checked." +#: ../../inventory/management/delivery/two_steps.rst:45 +#: ../../inventory/management/incoming/two_steps.rst:44 +msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to *Configuration > Locations > Select Input* and update its name." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:46 -msgid "Click on **Apply** at the top of the page to save changes (if you needed to check the radio button above)." +#: ../../inventory/management/delivery/two_steps.rst:54 +#: ../../inventory/management/incoming/two_steps.rst:52 +msgid "Create a purchase order" msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:50 -msgid "If you checked option **Advanced routing of products using rules** you may need to activate **Manage several locations per warehouse** if it wasn't activated beforehand." +#: ../../inventory/management/delivery/two_steps.rst:56 +#: ../../inventory/management/incoming/two_steps.rst:54 +msgid "In the *Purchase* application, you can create a *Request for Quotation* with some storable products to receive from a supplier. Once the *RfQ* is confirmed, the receipt picking will be created and automatically linked to your purchase order." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:55 -msgid "Configure warehouse for Pick + Ship" +#: ../../inventory/management/delivery/two_steps.rst:65 +#: ../../inventory/management/incoming/two_steps.rst:62 +msgid "Now, by clicking on the *1 Receipt* button, you will see the first picking which will allow entering the product in the *input location*. Then, another picking, an internal transfer, has been created in order to move the products to *Stock*." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:57 -msgid "To configure a **Pick + Ship** move, go to :menuselection:`Configuration --> Warehouses` and edit the warehouse that will be used." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:61 -msgid "For outgoing shippings, set the option to **Bring goods to output location before shipping (Pick + Ship)**" -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:70 -msgid "Install the **Sale** if it is not the case, and create a sales order with some products to deliver." +#: ../../inventory/management/delivery/two_steps.rst:71 +msgid "Process the picking and the delivery" msgstr "" #: ../../inventory/management/delivery/two_steps.rst:73 -msgid "Notice that we now see ``2`` transfers associated with this sales order in the **Delivery** stat button above the sales order." +#: ../../inventory/management/incoming/two_steps.rst:70 +msgid "The receipt is the first one to be processed and has a *Ready* status while the internal transfer will only become *Ready* once the receipt has been marked as *Done*." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:79 -msgid "If you click on the **2 Transfers** stat button, you should now see two different pickings, one with a reference **PICK** to designate the picking process and another with a reference **OUT** to designate the shipping process." +#: ../../inventory/management/delivery/two_steps.rst:77 +#: ../../inventory/management/incoming/two_steps.rst:74 +msgid "You can enter the receipt operation from the purchase order, or access it through the inventory dashboard." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:93 -msgid "Ensure that you have enough product in stock, and go to **Inventory** and click on the **Waiting** link under the **Pick** kanban card." +#: ../../inventory/management/delivery/two_steps.rst:84 +#: ../../inventory/management/incoming/two_steps.rst:80 +msgid "By default, a receipt is always considered as ready to be processed. Then, you will be able to directly click on *Validate* to mark it as done." msgstr "" -#: ../../inventory/management/delivery/two_steps.rst:103 -msgid "Click on **Validate** to complete the move from **WH/Stock** to **WH/Output**." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:105 -msgid "This has completed the picking step and the **WH/PICK** move should now show **Done** in the status column at the top of the page. The product has been moved from **WH/Stock** to **WH/Output** location, which makes the product **available for the next step** (Shipping)." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:121 -msgid "Click on **Validate** to complete the move from **WH/Output** to the customer (Click **Apply** to assign the quantities based on the quantities listed in the **To Do** column)" -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:125 -msgid "This has completed the shipping step and the **WH/OUT** move should now show **Done** in the status column at the top of the page. The product has been shipped to the customer." -msgstr "" - -#: ../../inventory/management/delivery/two_steps.rst:130 -msgid "link to these sections when they will be available - Process Overview: From sales orders to delivery orders" +#: ../../inventory/management/delivery/two_steps.rst:92 +#: ../../inventory/management/incoming/two_steps.rst:87 +msgid "Once the receipt has been validated, the internal transfer is ready to be processed. As documents are chained, the products which have been received are automatically reserved on the internal transfer. Once the transfer is validated, those products enter the stock and you will be able to use them to fulfill customer deliveries or manufacture products." msgstr "" #: ../../inventory/management/incoming.rst:3 @@ -1496,205 +1199,11 @@ msgid "This is the default configuration in Odoo." msgstr "" #: ../../inventory/management/incoming/handle_receipts.rst:68 -#: ../../inventory/management/incoming/three_steps.rst:126 -#: ../../inventory/management/incoming/two_steps.rst:97 msgid ":doc:`../delivery/inventory_flow`" msgstr "" -#: ../../inventory/management/incoming/handle_receipts.rst:71 -msgid "Add section when available - How to analyse the performance of my vendors?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:3 -msgid "How to add a quality control step in goods receipt? (3 steps)" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:8 -msgid "In many companies, it is necessary to assess the received good. The goal is to check that the products correspond to the quality requirements agreed with the suppliers. Therefore, adding a quality control step in the goods receipt process can become essential." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:13 -#: ../../inventory/management/incoming/two_steps.rst:8 -msgid "Odoo uses routes to define exactly how you will handle the different receipt steps. The configuration is done at the level of the warehouse. By default, the reception is a one step process, but changing the configuration can allow to have 2 or even 3 steps." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:18 -msgid "The 3 steps flow is as follows: You receive the goods in an input area, then transfer them into quality area for quality control. When the quality check has been processed, you can move the goods from QC to stock. Of course, you may change the quantity and only transfer to stock the quantity that is valid and decide that you will return the quantity that is not good." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:25 -#: ../../inventory/management/incoming/two_steps.rst:18 -msgid "This is the case that will be explained in this document." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:31 -#: ../../inventory/management/incoming/two_steps.rst:24 -msgid "Use advanced routes" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:33 -msgid "To allow management of routes, go to the menu :menuselection:`Inventory --> Configuration --> Settings`." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:39 -#: ../../inventory/management/incoming/two_steps.rst:32 -msgid "Ensure that the routes option **Advance routing of product using rules** is checked, then click on **Apply** to save changes." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:42 -msgid "Make sure that **Manage several locations per warehouse** is also ticked." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:46 -msgid "How to add a quality control step in goods receipt?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:48 -msgid "Go to the menu :menuselection:`Inventory --> Configuration --> Warehouse` and choose the warehouse where you want to change reception methods." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:51 -msgid "By default, warehouses are configured with one step reception (**Receive goods directly into stock**)." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:54 -msgid "To add quality control before transfer goods into stock location, tick **Unload in input location, go through a quality control before being admitted in stock (3 steps)**." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:62 -msgid "How to control a receipt?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:65 -msgid "How to process the receipt step ?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:67 -msgid "In the **Purchase** app, create a **Request for Quotation**. Click on the **Confirm order** button. You can see that there is one **Shipment** related to purchase order in the stat button above the purchase order form view. This is the receipt step." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:75 -msgid "Go to **Inventory** and click on the link **# TO RECEIVE** in the **Receipts** card." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:80 -msgid "Click on the receipt that you want to process. Click on **Validate** to complete the move from the **Vendor** location to **WH/Input**." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:83 -msgid "This has completed the receipt step and the status column at the top of the page for **WH/IN** should now show **Done**. The product has been moved from the **Vendor** to the **WH/Input** location, which makes the product available for the next step (Move to the quality control zone)" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:89 -msgid "How to move your product from the receipt zone to the quality control zone ?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:91 -msgid "Go to the **Inventory** dashboard. You will see that there is one transfer ready (the move to the quality control zone) and one waiting (the move to the stock after the control). Click on the link **# TRANSFERS** in the **Internal Transfers** to process the quality control." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:101 -msgid "Click on **Validate** to complete the move from **WH/Input** to **WH/Quality Control**." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:104 -msgid "This has completed the internal transfer step and the status column at the top of the page for **WH/INT** should now show **Done**. The receipt is now ready to be controlled." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:109 -msgid "How to to process the quality control ?" -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:111 -msgid "Go back to the **Inventory** dashboard. The waiting transfer is now ready. Click on the link **# TRANSFERS** in the **Internal Transfers** card to process the quality control." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:118 -msgid "Click on the last picking to process. Click on **Validate** to complete the move from **WH/Quality Control** to **WH/Stock**." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:121 -msgid "This has completed the quality control step and the status column at the top of the page for **WH/INT** should now show **Done**. The receipt has been controlled and has moved to your stock." -msgstr "" - -#: ../../inventory/management/incoming/three_steps.rst:127 -msgid ":doc:`two_steps`" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:3 -msgid "How to unload your shipment to an input location? (2 steps)" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:13 -msgid "The 2 steps flow is the following : You receive the goods in an input area then transfer them from input area to your stock. As long as the goods are not transferred in your stock, they will not be available for further processing." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:26 -msgid "To allow management of routes, go to the menu :menuselection:`Inventory --> Configuration --> Settings`" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:35 -msgid "Make sure that **\"Manage several locations per warehouse\"** is also ticked." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:39 -msgid "How to configure your warehouse ?" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:41 -msgid "Go to the the menu :menuselection:`Inventory --> Configuration --> Warehouse` and choose the warehouse where you want to change reception methods." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:44 -msgid "By default, warehouses are configured with one step reception (option **Receive goods directly into stock**)." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:47 -msgid "To add the control step, tick **Unload in input location then go to stock (2 steps)**." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:54 -msgid "How to receipt a shipment in 2 steps?" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:57 -msgid "How to process the Receipt step ?" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:59 -msgid "In the purchase module, create a **Request for Quotation**, then click on the **Confirm order** button. You can see that there is one **Shipment** related to purchase order in the **stat button** above the purchase order form view. This is the receipt step." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:67 -msgid "Go to **Inventory** and click on the **# TO RECEIVE** link on the **Receipts** card." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:73 -msgid "Click on the receipt that you want to process, then click on **Validate** to complete the move from the **Vendor** to **WH/Input**." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:76 -msgid "This has completed the Receipt Step and the move refered with **WH/IN**. The product has been moved from the **Vendor** to the **WH/Input** location, which makes the product available for the next step." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:81 -msgid "How to transfer the receipt to your stock ?" -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:83 -msgid "Go back to the **Inventory** dashboard. The waiting transfer is now ready. Click on the **# TRANSFERS** in the **Internal Transfers** to process the quality control." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:90 -msgid "Click on the picking you want to process. Click on **Validate** to complete the move from **WH/Input** to **WH/Stock**." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:93 -msgid "This has completed the internal transfer step and the move refered with **WH/INT**. The receipt has been moved to your stock." -msgstr "" - -#: ../../inventory/management/incoming/two_steps.rst:98 -msgid ":doc:`three_steps`" +#: ../../inventory/management/incoming/two_steps.rst:68 +msgid "Process the receipt and the internal transfer" msgstr "" #: ../../inventory/management/lots_serial_numbers.rst:3 @@ -1706,9 +1215,6 @@ msgid "What's the difference between lots and serial numbers?" msgstr "" #: ../../inventory/management/lots_serial_numbers/differences.rst:6 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:6 -#: ../../inventory/management/misc/owned_stock.rst:6 -#: ../../inventory/settings/products/variants.rst:170 msgid "Introduction" msgstr "" @@ -1749,446 +1255,965 @@ msgid "On the other hand, giving a serial number to every product is a time-cons msgstr "" #: ../../inventory/management/lots_serial_numbers/differences.rst:46 -#: ../../inventory/management/lots_serial_numbers/lots.rst:135 msgid ":doc:`serial_numbers`" msgstr "" #: ../../inventory/management/lots_serial_numbers/differences.rst:47 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:129 msgid ":doc:`lots`" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:3 -msgid "How to manage lots of identical products?" +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:3 +msgid "Manage expiration dates" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:8 -msgid "Lots are useful for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:5 +msgid "In many companies, products have expiration dates and they should be tracked based on those dates. In the food industry, for example, tracking stocks based on expiration dates is mandatory to avoid selling expired products to customers." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:14 -msgid "Odoo has the capacity to manage lots ensuring compliance with the traceability requirements imposed by the majority of industries." +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:10 +msgid "With Odoo, you can track your products based on their expiration dates, even if they are already tracked by lots or serial numbers." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:17 +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:14 #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:15 -msgid "The double-entry management in Odoo enables you to run very advanced traceability." +msgid "Configurations" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:21 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:19 -msgid "Setting up" -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:24 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:22 +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:17 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:18 msgid "Application configuration" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:26 -msgid "You need activate the tracking of lots in the settings. In the **Inventory** application, go to :menuselection:`Configuration --> Settings`, select **Track lots or serial numbers**" +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:19 +msgid "To use expiration dates tracking, open the *Inventory* application and go to *Configuration > Settings* and activate the *Lots & Serial Numbers* and *Expiration Dates* features." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:27 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:28 +#: ../../inventory/shipping/operation/labels.rst:68 +#: ../../inventory/shipping/setup/third_party_shipper.rst:90 +msgid "Product configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:29 +msgid "Now, you have the possibility to define different dates in the *inventory tab* of the product form:" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:32 +msgid "Product Use Time: it’s the number of days before the goods start deteriorating, without being dangerous yet. It will be computed using the lot/serial number;" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:34 +msgid "Product Life Time: refers to the number of days before the goods may become dangerous and must not be consumed. It will be computed on the lot/serial number;" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:36 +msgid "Product Removal Time: shows the number of days before the goods should be removed from the stock. It will be computed on the lot/serial number;" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:38 +msgid "Product Alert Time: refers to the number of days before an alert should be raised on the lot/serial number." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:44 +msgid "Expiration Date on Lots/Serial Numbers" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:46 +msgid "When receiving a product in stock, the dates will automatically be updated on the corresponding lot/serial number. This update will be based on the reception date of the product and the times set on the product form." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:58 +msgid "Expiration Alerts" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:60 +msgid "You can access all your expiration alerts from the *inventory* app. To do so, go to *Master Data > Lots/Serial Numbers*. There, you can use the pre-existing filter that shows all the lots/serial numbers that exceeded their alert date." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:3 +msgid "Manage lots of identical products" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:5 +msgid "Lots are useful for products you receive in great quantity and for which a lot number can help in reporting, quality controls, or any other info. Lots will help identify a number of pieces having, for instance, a production fault. It can be useful for a batch production of clothes or food." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:11 +msgid "Odoo has the capacity to manage lots, ensuring compliance with the traceability requirements imposed by the majority of industries." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:14 +msgid "The double-entry management in Odoo enables you to run very advanced traceability." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:18 +msgid "Setting Up" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:21 +msgid "Application Configuration" +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:23 +msgid "First, you need to activate the tracking of lot numbers. To do so, go to *Inventory > Configuration > Settings* and tick *Lots & Serial Numbers*. Then, click on save." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:31 +msgid "Product Configuration" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:33 -msgid "In order to have an advanced management of the lots, you should also select **Manage several locations per warehouse**." +msgid "Now, you have to configure which products you want to track by serial numbers." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:39 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:31 -#: ../../inventory/shipping/operation/labels.rst:27 -#: ../../inventory/shipping/setup/third_party_shipper.rst:26 -msgid "Then click on **Apply**." +#: ../../inventory/management/lots_serial_numbers/lots.rst:36 +msgid "Go to *Master Data > Products* and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:42 -msgid "Operation types configuration" +#: ../../inventory/management/lots_serial_numbers/lots.rst:47 +msgid "Manage Lots" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:44 -msgid "You also need to set up how you will manage lots for each operations. In the **Inventory** application, go to :menuselection:`Configuration --> Operation Types`." +#: ../../inventory/management/lots_serial_numbers/lots.rst:52 +msgid "In order to receive a product tracked by lots, you have to specify its lot numbers. You have several ways of doing so:" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:48 -msgid "For each type (receipts, internal transfers, deliveries,...), you can set if you can create new lot numbers or only use existing lot numbers." +#: ../../inventory/management/lots_serial_numbers/lots.rst:55 +#: ../../inventory/management/lots_serial_numbers/lots.rst:65 +msgid "Manually assign the different lot numbers" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:57 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:36 -msgid "Finally, you have to configure which products you want to track in lots." +msgid "Copy/paste lot numbers from an Excel file" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:59 -msgid "Go into :menuselection:`Inventory Control --> Products`, and open the product of your choice. Click on **Edit**, and in the **Inventory** tab, select **Tracking by Lots**, then click on **Save**." +msgid "First, you need to open the detailed operations of your picking." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:67 -msgid "Manage lots" -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:70 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:49 -msgid "Transfers" -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:72 -msgid "In order to process a transfer of a product tracked by lot, you have to input the lot number(s)." +msgid "When opening the detailed operations, you can click on *Add a line*. Then, you will be able to fill the lot number in. Once done, you can click on *Add a line* again to register a new lot number." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:75 -msgid "Click on the lot icon :" +msgid "Copy/paste lot number from an Excel file" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:80 -msgid "A window will pop-up. Click on **Add an item** and fill in the lot number and the quantity." -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:86 -msgid "Depending on your operation type configuration, you will be able to fill in new lot numbers, or only use existing ones." -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:90 -msgid "In the scanner interface, you just have to scan the lot numbers." +#: ../../inventory/management/lots_serial_numbers/lots.rst:77 +msgid "Once the spreadsheet containing the lot numbers you received from your supplier and copy the list. Then, you can paste them in the *Lot/Serial Number Name* column for Odoo to automatically create the necessary lines. After that, you will have to manually enter the number of products that are contained in each one of the lots." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:93 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:79 -msgid "Inventory adjustment" +msgid "Operation Types" msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:95 -msgid "Inventory of a product tracked by lot can be done in 2 ways:" -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:97 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:83 -msgid "Classic inventory by products" +msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to *Configuration > Operation Types*." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:99 -msgid "Inventory of a lot" -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:101 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:87 -msgid "When doing a classic inventory, there is a **Serial Number** column. If the product has already been assigned with a number, it is already pre-filled." -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:105 -msgid "Click on **Add an item** if the product has not been inventoried yet. You can easily create lots, just type in a new lot number in the column." +msgid "For each type (receipts, internal transfers, deliveries, …), you can decide if you allow to create new lot numbers or only use existing ones. By default, the creation of new lots is only allowed at product reception, and using existing lot numbers isn’t allowed in this operation. If you have inter-warehouse transfers and track products by lots, it can be useful to allow using existing lot numbers in receipts too." msgstr "" #: ../../inventory/management/lots_serial_numbers/lots.rst:111 -msgid "You can also just do the inventory of a lot. In this case, you will have to fill in the **Lot number**. You can also create a new lot from here. Just type in the number, a window will pop out to link the number to a product." -msgstr "" - -#: ../../inventory/management/lots_serial_numbers/lots.rst:120 msgid "Lots traceability" msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:122 -msgid "You can check the lot traceability from :menuselection:`Inventory --> Inventory Control --> Serial Numbers/Lots`" +#: ../../inventory/management/lots_serial_numbers/lots.rst:113 +msgid "The lot number given to the products allows you to keep track of where they were received, put in stock, to whom they were sold and where they were shipped to." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:128 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:122 -msgid "You can have more details by clicking on the **Traceability** button :" +#: ../../inventory/management/lots_serial_numbers/lots.rst:117 +msgid "To track an item, open the *Inventory* module and, in *Master Data > Lots/Serial Numbers*, click on the lot number corresponding to your search." msgstr "" -#: ../../inventory/management/lots_serial_numbers/lots.rst:134 -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:128 -msgid ":doc:`differences`" +#: ../../inventory/management/lots_serial_numbers/lots.rst:124 +msgid "When you open the *Traceability* information, you see in which documents the lot number has been used." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/lots.rst:130 +msgid "Now, if you want to locate the lot number, you can do so by clicking on the *Location* stat button." msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:3 -msgid "How to work with serial numbers?" +msgid "Work with serial numbers" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:8 -msgid "Serial Number Tracking is used to track products with serial numbers on every transactions. You can track the current location of the product with serial numbers. When the products are moved from one location to another location, the system will automatically identify the current location of the product based on last movement of the product. So you can get the last location where the products are moved." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:5 +msgid "To track products with serial numbers, you can use the serial number tracking. With them, you can track the current location of the product and, when the products are moved from one location to another, the system will automatically identify the current location of the product, based on its last movement." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:24 -msgid "You need activate the tracking of serial numbers in the settings. In the **Inventory** application, go to :menuselection:`Configuration --> Settings`, select **Track lots or serial numbers**." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:11 +msgid "If you want to do it or run very advanced traceability, the Odoo double-entry management is the feature you need." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:38 -msgid "Go into :menuselection:`Inventory Control --> Products`, and open the product of your choice. Click on **Edit**, and in the **Inventory** tab, select **By Unique Serial Number**, then click on **Save**." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:20 +msgid "First, you need to activate the serial numbers tracking. To do so, go to *Configuration > Settings* in the *Inventory* application. Then, enable the feature and hit save." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:46 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:30 +msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to *Master Data > Products* and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:42 msgid "Manage Serial Numbers" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:51 -msgid "In order to process a transfer of a product tracked by serial number, you have to input the number(s). In order to be able to assign serial numbers to products with tracking features enabled you will first need to mark your transfer as to do. Click on the **Mark as TODO** button to display the Lot Split icon." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:47 +msgid "To receive a product that is tracked by serial number, you have to specify its serial number. Of course, you have several ways of doing so:" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:57 -msgid "Click on the serial number icon :" +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:50 +msgid "Manual assignation" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:62 -msgid "A window will pop-up. Click on **Add an item** and fill in the serial numbers." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:52 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:73 +msgid "Multi-assignation" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:68 -msgid "If you move products that already have serial numbers assigned, those will appear in the list. Just click on the **+** icon to confirm that you are moving those serial numbers." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:54 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:89 +msgid "Copy/pasting from an Excel file" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:76 -msgid "In the scanner interface, you just have to scan the serial numbers." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:56 +msgid "Whatever could be your favorite way to assign serial numbers, you firstly need to open the detailed operations of your picking." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:81 -msgid "Inventory of a product tracked by serial numbers can be done in 2 ways:" +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:63 +msgid "Manual assignation of the different serial numbers" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:85 -msgid "Inventory of a serial number" +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:65 +msgid "When opening the detailed operations, you can click on *Add a line*. Then, you will be able to fill in the serial number field. Once done, you can click again on *Add a line* to register a new serial number." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:75 +msgid "By using the multi-assignation of serial numbers, Odoo will automatically create the necessary lines. To do so, you have to enter the first serial number of your set and the number of products you have to assign a serial number to." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:80 +msgid "Once done, click on *Assign Serial Numbers* and Odoo will do the rest." msgstr "" #: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:91 -msgid "Click on **Add an item** if the product has not been inventoried yet. You can easily create serial numbers, just type in a new number in the column." +msgid "To use copy/pasting, open the spreadsheet containing the serial numbers you received and copy the list. Then, past them in the *Lot/Serial Number Name* column of the wizard. Doing so, Odoo will automatically create the lines you need." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:98 -msgid "The quantity should be 1 for each line." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:106 +msgid "Operation types" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:100 -msgid "You can also just do the inventory of a serial number. In this case, you will have to fill in the serial number. You can also create a new one from here. Just type in the number, a window will pop out to link it to a product." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:108 +msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to *Configuration > Operation Types* in the *Inventory* app." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:109 +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:112 +msgid "For each type, you can decide if you allow the creation of new lot numbers or want to use existing ones. By default, the creation of new lots is only allowed at product reception." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:120 +msgid "If you have inter-warehouse transfers and track products by lots, it can be useful to allow using existing lot numbers in receipts too." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:124 msgid "Serial Number traceability" msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:111 -msgid "The serial number given to these items allow you to keep track of where they were received, put in stock, to whom they were sold and where they were shipped to." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:126 +msgid "Using serial numbers allows you to keep track of where the products were received, put in stock, to whom they were sold, and where they were shipped to." msgstr "" -#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:115 -msgid "To track an item, open the **Inventory** module, and in :menuselection:`Inventory Control --> Serial Numbers/lots`, click on the serial number corresponding to your search." +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:130 +msgid "Tracking an item is easy: open the *Inventory* app, and go to *Master Data > Lots/Serial Numbers* and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used." +msgstr "" + +#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:142 +msgid "And, if you want to locate a serial number, you can do so by clicking on the *Location* button available on the serial number form." msgstr "" #: ../../inventory/management/misc.rst:3 msgid "Miscellaneous Operations" msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:2 -msgid "Immediate & Planned Transfers" +#: ../../inventory/management/misc/email_delivery.rst:3 +msgid "Send Automated Emails at Delivery" msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:4 -msgid "In Odoo, you can create two types of transfers: immediate or planned transfers." +#: ../../inventory/management/misc/email_delivery.rst:8 +msgid "First, go to the *Inventory* app, then to *Settings* and activate the *Email Confirmation* feature. If you work in multi-company, this configuration is company-specific." msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:8 -msgid "Immediate Transfers" +#: ../../inventory/management/misc/email_delivery.rst:15 +msgid "When you enable this feature, Odoo automatically creates an email template. Of course, you can modify it if necessary by clicking on the small arrow next to its name." msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:10 -msgid "When you create a transfer manually, it is by default an immediate transfer." +#: ../../inventory/management/misc/email_delivery.rst:23 +msgid "Send email at delivery validation" msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:13 -msgid "In the case of an immediate transfer, you directly encode the products and quantities you are processing, there is no reservation that applies. This is why the column \"Initial Demand\" is not editable. You only fill in the column \"Done\" for the quantities." +#: ../../inventory/management/misc/email_delivery.rst:25 +msgid "On the inventory dashboard, click on *Create* and fill the form for a specific partner. Once you have added some products in it, *Validate* it and do the same for the delivery." msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:18 -msgid "This is for example used when you are transferring goods from a location A to a location B and that this is not planned (you are processing the transfer right now)." +#: ../../inventory/management/misc/email_delivery.rst:32 +msgid "Doing so, an automated email will be sent and will appear in the chatter." msgstr "" -#: ../../inventory/management/misc/immediate_planned_transfers.rst:23 -msgid "Planned Transfers" -msgstr "" - -#: ../../inventory/management/misc/immediate_planned_transfers.rst:25 -msgid "When a transfer is generated automatically (from a sales order or purchase order for example), it is a planned transfer. This means that there is an initial demand and that reservation applies on this initial demand." -msgstr "" - -#: ../../inventory/management/misc/immediate_planned_transfers.rst:30 -msgid "If you want to create a planned transfer manually, you can do it from the inventory dashboard." -msgstr "" - -#: ../../inventory/management/misc/immediate_planned_transfers.rst:36 -msgid "In that case, you will have to enter the initial demand first (how many units are you supposed to proceed), then to mark your transfer as to do. Once this is done, you will be able to reserve the products and to process the transfer." +#: ../../inventory/management/misc/email_delivery.rst:38 +msgid "If you work with a shipping method, and then have a tracking link, it will be included in the standard email template." msgstr "" #: ../../inventory/management/misc/owned_stock.rst:3 -msgid "How to manage stock that you don't own?" +msgid "Manage Stock that you don't own" +msgstr "" + +#: ../../inventory/management/misc/owned_stock.rst:5 +msgid "Sometimes, suppliers can offer you to store and sell products without having to buy those items. This technique is called *consignee stock*." msgstr "" #: ../../inventory/management/misc/owned_stock.rst:8 -msgid "Some suppliers can sometimes offer you to store and sell products without having to buy those items: this technique is called **consignee stock**." +msgid "Consignee stock is a great way for manufacturers and suppliers to launch new products. As resellers may be reluctant to buy a product they are not sure to be able to sell, consignee stock will allow them to offer an item to check its market without having to pay for it in the first place." msgstr "" -#: ../../inventory/management/misc/owned_stock.rst:12 -msgid "Consignee stock is a great way for manufacturers and suppliers to launch new products. As resellers may be reluctant to buying a product that they are not sure to be able to sell, consignee stock will allow them to propose an item to check its market without having to pay for it in the first place." +#: ../../inventory/management/misc/owned_stock.rst:14 +msgid "Of course, Odoo has the ability to manage those consignee stocks through advanced settings." msgstr "" -#: ../../inventory/management/misc/owned_stock.rst:18 -msgid "Odoo has the ability to manage consignee stocks through the advanced settings." +#: ../../inventory/management/misc/owned_stock.rst:20 +msgid "To use this feature, go to *Inventory > Configuration > Settings* in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save." msgstr "" -#: ../../inventory/management/misc/owned_stock.rst:24 -msgid "Open the menu :menuselection:`Inventory --> Configuration --> Settings`, and in the **Product Owners** section, select **Manage consignee stocks (advanced)**, then click on **Apply**." -msgstr "" - -#: ../../inventory/management/misc/owned_stock.rst:32 +#: ../../inventory/management/misc/owned_stock.rst:28 msgid "Reception of Consignee Stock" msgstr "" -#: ../../inventory/management/misc/owned_stock.rst:34 -msgid "In the Inventory's Dashboard, open the **Receipts** and create a new reception. You can see that in the right side of the page, a new **Owner** line has appeared. You can specify the partner which owns the stock or leave it blank if you are the owner." +#: ../../inventory/management/misc/owned_stock.rst:30 +msgid "When in the *Inventory* app, open the receipts and create a new reception. On the right side, you will see that a new line called *Assign Owner* has appeared. There, you can specify the partner which owns the stock." msgstr "" -#: ../../inventory/management/misc/schedulers.rst:3 -msgid "How to configure and run schedulers?" +#: ../../inventory/management/misc/owned_stock.rst:39 +msgid "If you are the owner, you can leave the field blank." msgstr "" -#: ../../inventory/management/misc/schedulers.rst:6 -msgid "What is a scheduler" -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:8 -msgid "The scheduler is the calculation engine which plans and prioritises production and purchasing automatically according to the rules defined on products. By default, the scheduler is set to run once a day (Odoo automatically creates a **Scheduled Action** for this)." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:14 -msgid "Calculating Requirements / Scheduling" -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:16 -msgid "Scheduling only validates procurements that are confirmed but not yet started. These procurement reservations will themselves start production, tasks or purchases depending on the configuration of the requested product." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:21 -msgid "You take into account the priority of operations when starting reservations and procurements. Urgent requests, those with a date in the past, or requests with a date earlier than the others will be started first. In case there are not enough products in stock to satisfy all the requests, you can be sure that the most urgent requests will be produced first." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:29 -msgid "Configure and run the scheduler" -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:32 -msgid "Run the scheduler manually" -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:34 -msgid "This feature is not visible by default. You have to enable **debug mode** to see this. To enable debug mode, go to :menuselection:`Help --> About` and click on **Activate the developer mode**." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:38 -msgid "You can also start the scheduler manually from the menu :menuselection:`Inventory --> Schedulers --> Run Schedulers`. The scheduler uses all the relevant parameters defined for products, suppliers and the company to determine the priorities between the different production orders, deliveries and supplier purchases." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:48 -msgid "Configure and run the scheduler (only for advanced users)" -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:50 -msgid "This feature is not visible by default. You have to enable **debug mode** to see this. To enable debug mode, go to :menuselection:`Help -> About` and click on **Activate the developer mode**." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:54 -msgid "You can set the starting time of the scheduler by modifying the corresponding action in the menu :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`. Modify the Run mrp Scheduler configuration." -msgstr "" - -#: ../../inventory/management/misc/schedulers.rst:63 -msgid ":doc:`../delivery/scheduled_dates`" +#: ../../inventory/management/misc/owned_stock.rst:41 +msgid "Once the receipt is validated, the products enter your stock but still belong to the owner. They don’t impact your inventory valuation." msgstr "" #: ../../inventory/management/misc/scrap.rst:3 -msgid "How to scrap products?" +msgid "Scrap Products" msgstr "" -#: ../../inventory/management/misc/scrap.rst:8 -msgid "Scrap means waste that either has no economic value or only the value of its basic material" +#: ../../inventory/management/misc/scrap.rst:5 +msgid "In your warehouse, you sometimes find products that are damaged or that are unusable due to expiry or for some other reasons. You often notice this during picking or physical inventory. Since those products cannot be sold or stored, you have to scrap them." msgstr "" -#: ../../inventory/management/misc/scrap.rst:11 -msgid "content recoverable through recycling." +#: ../../inventory/management/misc/scrap.rst:10 +msgid "When goods are scrapped, they are not reflected in the system as a part of the inventory. The scrapped material will be physically moved to the scrap area and not taken into account into inventory valuation." msgstr "" -#: ../../inventory/management/misc/scrap.rst:13 -msgid "In your warehouse you sometimes find products that are damaged or that are unusable due to expiry or for some other reason. You often notice this during picking or physical inventory." +#: ../../inventory/management/misc/scrap.rst:15 +msgid "Scrap means waste that either has no economic value or only the value of its basic material content, recoverable through recycling." msgstr "" -#: ../../inventory/management/misc/scrap.rst:17 -msgid "Since you cannot normally sell or store these products, you have to scrap product." +#: ../../inventory/management/misc/scrap.rst:21 +msgid "When you install the *Inventory* app, Odoo automatically creates a scrap location. It’s named *Virtual Location/Scap*." msgstr "" -#: ../../inventory/management/misc/scrap.rst:20 -msgid "When goods are scrapped they are not reflected in the system as a part of the inventory. The scrapped material will be physically moved to scrap area." +#: ../../inventory/management/misc/scrap.rst:24 +msgid "Of course, you can create new scrap areas if needed. To do so, go to *Inventory > Configuration > Settings* and activate the *Storage Locations* feature." msgstr "" -#: ../../inventory/management/misc/scrap.rst:27 -msgid "When you install inventory management, odoo automatically creates one default scrap location, namely **Virtual location/Scrapped**." +#: ../../inventory/management/misc/scrap.rst:31 +msgid "Now, go to *Configuration > Locations* and create your scrap location." msgstr "" -#: ../../inventory/management/misc/scrap.rst:30 -msgid "To create an extra scrap location, Go to :menuselection:`Inventory --> Configuration --> Settings` and check **Manage several locations per warehouse**, then click on **Apply**." +#: ../../inventory/management/misc/scrap.rst:34 +msgid "You have to check *Is a Scrap Location?* on the location form. In fact, scrap locations cannot be used as normal storage locations and then, a virtual location will be created for scrapped products." msgstr "" -#: ../../inventory/management/misc/scrap.rst:38 -msgid "After applying **Manage several location per warehouse**, you can create a new scrap location in :menuselection:`Configuration --> Warehouse Management --> Locations.`" +#: ../../inventory/management/misc/scrap.rst:39 +msgid "Different ways to scrap products" msgstr "" -#: ../../inventory/management/misc/scrap.rst:43 -msgid "To define a scrap location, you have to check **Is a Scrap Location?** on location form view." +#: ../../inventory/management/misc/scrap.rst:41 +msgid "With Odoo, you have several ways to scrap products: from receipts, from a delivery order, and from an internal transfer." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:45 +msgid "Scrap from receipt" msgstr "" #: ../../inventory/management/misc/scrap.rst:47 -msgid "Different ways to scrap product" +msgid "Scrapping products from receipts is easy. Go to *Inventory > Dashboard > Receipts* or click on *1 TO PROCESS* under the receipts location." msgstr "" -#: ../../inventory/management/misc/scrap.rst:49 -msgid "Odoo provides several ways to scrap products." +#: ../../inventory/management/misc/scrap.rst:53 +msgid "Now, open the receipt and validate the picking. Once the products entered your stock, the Scrap button appears on the top left corner of your screen." msgstr "" -#: ../../inventory/management/misc/scrap.rst:52 -msgid "1) Scrap from Receipt (Initial Demand tab)." +#: ../../inventory/management/misc/scrap.rst:57 +msgid "You can scrap products that were part of the receipt from there. If you do so, it will move them from available stock to the virtual scrap location." msgstr "" -#: ../../inventory/management/misc/scrap.rst:54 -msgid "To scrap product from incoming shipment, Go to :menuselection:`Inventory --> Dashboard --> Receipts`." +#: ../../inventory/management/misc/scrap.rst:68 +msgid "Scrap from delivery order" msgstr "" -#: ../../inventory/management/misc/scrap.rst:60 -msgid "Open the incoming shipment, and in the **Initial demand** tab, click on the scrap products button." +#: ../../inventory/management/misc/scrap.rst:70 +msgid "To scrap products from a delivery order, go to *Inventory > Dashboard > Delivery orders* or click on *1 TO PROCESS*." msgstr "" -#: ../../inventory/management/misc/scrap.rst:67 -msgid "2) Scrap from delivery order (Initial Demand tab) ." +#: ../../inventory/management/misc/scrap.rst:76 +msgid "Once done, open the delivery order. You can see the scrap button in the upper left of the document. If you scrap the product from there, it will be moved from your available stock to the virtual scrap location." msgstr "" -#: ../../inventory/management/misc/scrap.rst:69 -msgid "To scrap product from outgoing shipment, Go to :menuselection:`Inventory --> Dashboard --> Delivery Orders`" +#: ../../inventory/management/misc/scrap.rst:80 +msgid "You can find all the scrap orders made from the picking by clicking on the button on the top right corner of the document." msgstr "" -#: ../../inventory/management/misc/scrap.rst:75 -msgid "Open the outgoing shipment, and in the **Initial demand** tab, click on the scrap products button on stock move in initial demand tab." +#: ../../inventory/management/misc/scrap.rst:93 +msgid "Scrap from an internal transfer" msgstr "" -#: ../../inventory/management/misc/scrap.rst:82 -msgid "3) Scrap from internal transfer (Initial Demand tab)." +#: ../../inventory/management/misc/scrap.rst:95 +msgid "To do this, the flow is almost the same. In fact, you just have to go to *Inventory > Dashboard > Internal Transfers*." msgstr "" -#: ../../inventory/management/misc/scrap.rst:84 -msgid "To scrap product from internal transfer, Go to :menuselection:`Inventory --> Dashboard --> Internal Transfers`" -msgstr "" - -#: ../../inventory/management/misc/scrap.rst:90 -msgid "Open the internal transfer, and in the **Initial demand** tab, click on the scrap products button on stock move in initial demand tab." -msgstr "" - -#: ../../inventory/management/misc/scrap.rst:96 -msgid "When you click on scrap button, a popup will open. You can enter the quantity of products, and specify the scrap location, then click on **Scrap**." +#: ../../inventory/management/misc/scrap.rst:101 +msgid "There, open the internal transfer that interests you. Now, click on the scrap button that is on the top left of the document." msgstr "" #: ../../inventory/management/misc/scrap.rst:104 -msgid "To allow change scrap location on wizard, you have to select **Manage several location per warehouse** in the settings at :menuselection:`Inventory --> Configuration --> Settings`" +msgid "When scrapping before validating the internal transfer, the product is, by default, moved from the source location to the virtual scrap location. But, if you scrap after validating the internal transfer, it will be moved from the destination location, as opposed to the source location, to the virtual scrap location." +msgstr "" + +#: ../../inventory/management/misc/scrap.rst:110 +msgid "Of course, you can manually update the source location of the scrap order if necessary." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:3 +msgid "Send Automated SMS at Delivery" +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:8 +msgid "To send automated SMS, you need to activate the *SMS Confirmation* feature. To do so, go to the *Inventory* app *Settings* and enable the feature. In multi-company, this feature is company-specific." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:15 +msgid "Of course, an SMS template already exists by default in Odoo. You can modify it by clicking on the arrow on the right." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:22 +msgid "Send SMS at delivery validation" +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:24 +msgid "To use this feature, try to *Create* a delivery order for a specific partner and add some products to it. Then, *Validate* the delivery." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:30 +msgid "Now, the automated SMS that has been sent appears in the chatter." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:36 +msgid "The partner which is set on the transfer needs to have a phone number specified in its contact form for the SMS to be sent." +msgstr "" + +#: ../../inventory/management/misc/sms_delivery.rst:39 +msgid "If you work with a shipping method, and then have a tracking link, it will be included in the SMS template." +msgstr "" + +#: ../../inventory/management/planning.rst:3 +msgid "Planning" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:3 +msgid "How is the Scheduled Delivery Date Computed?" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:5 +msgid "In most cases, scheduled dates are computed to be able to plan deliveries, receptions, and so on. Depending on your company’s habits, Odoo generates scheduled dates via the scheduler." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:9 +msgid "To make your life easier, the Odoo scheduler computes everything per line, whether it’s a manufacturing order, a delivery order, a sale order, etc." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:14 +msgid "The computed dates are dependent on the different lead times configured in Odoo." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:20 +msgid "Configuring lead times is the first move if you want to compute scheduled dates. Those are the delays promised (in terms of delivery, manufacturing, etc.) to your partners and/or clients." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:25 +msgid "In Odoo, you can configure different lead times." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:30 +msgid "When configuring lead times at the product level, you have three different types to take into account: supplier lead time, customer lead time, and manufacturing lead time." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:35 +msgid "Supplier lead time" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:37 +msgid "The supplier lead time is the time needed for the supplier to deliver your purchased products. To configure it, select a product and click on the inventory tab. There, you will have to add a vendor to your product." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:44 +msgid "Now, just open the vendor form and fill its *Delivery lead time*. In this case, the delivery day will be equal to *Date of the Purchase Order + Delivery Lead Time*." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:52 +msgid "Do not forget that it is possible to add different vendor pricelists and, thus, different delivery lead times, depending on the vendor." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:56 +msgid "Customer Lead Time" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:58 +msgid "It is the time needed to get your product from your store/warehouse to your customer. It can be configured for any product. To add it, select a product and go to the inventory tab. There, simply indicate your *customer lead time*." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:67 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:69 +msgid "On the same page, it is possible to configure what’s called the *Manufacturing Lead Time*. It is the time needed to manufacture the product." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:76 +msgid "At the company level, you can configure security days. Those are useful to cope with eventual dalys and to be sure to meet your engagements. The idea is to subtract backup days from the computed scheduled date in case of delays." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:81 +msgid "Once again, there are three different types of security lead times: for sales, for purchases, and for manufacturing." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:85 +msgid "Security lead time for sales" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:87 +msgid "In sales, security lead time corresponds to backup days to ensure you will be able to deliver your clients in times. They are margins of errors for delivery lead times. Security days are the same logic as the early wristwatch, in order to arrive on time." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:92 +msgid "The idea is to subtract the numbers of security days from the calculation and, thus, to compute a scheduled date earlier than the one you promised to your client. In that way, you are sure to be able to keep your commitment." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:97 +msgid "To set up your security dates, go to *Inventory > Configuration > Settings* and enable the feature." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:104 +msgid "Security lead time for purchase" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:106 +msgid "It follows the same logic as security lead time for sales except that security lead time for purchase is the margin of error for vendor lead times, not for sales." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:110 +msgid "When the system generates purchase orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:114 +msgid "To find purchase lead time, go to *Inventory > Configuration > Settings* and enable the feature." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:121 +msgid "Security lead time for manufacturing" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:123 +msgid "The security lead time for manufacturing allows generating manufacturing orders which are scheduled that many days earlier to cope with unexpected manufacturing days." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:127 +msgid "To configure it, go to *Manufacturing > Configuration > Settings* and enable the *Security Lead Time* option. Then, hit save." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:136 +msgid "Sometimes, the internal transfers that a product might do may also influence the computed date. The delays due to internal transfers can be specified in the *Inventory* app when you create a new rule in a route." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:141 +msgid "To specify them, go to *Inventory > Configuration > Routes* and add a push rule to set a delay. Of course, you need to activate *Multi-step Routes* to use this feature." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:149 +msgid "At the sale order level" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:152 +msgid "Expected date" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:154 +msgid "In the *Sales* application, you have the possibility to activate the option *Delivery Date*. It will allow you to see additional fields on the sale order." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:158 +msgid "By enabling this option, Odoo will indicate the *Expected Date* in the *Other Info* tab of the sales order. This one is automatically computed based on the different lead times." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:165 +msgid "If you set a *Commitment Date* to deliver your customer that is earlier than the *Expected Date*, a warning message will appear on the screen." +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:175 +msgid "To better understand all the above info, here is 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 20th). In such a scenario, the scheduler will trigger the following events, based on your configuration:" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:181 +msgid "January 19: this is the actual scheduled delivery (1 day of Sales Safety Days);" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:183 +msgid "January 18: you receive the product from your supplier (1 day of Purchase days);" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:185 +msgid "January 10: this is the deadline to order at your supplier (9 days of Supplier Delivery Lead Time);" +msgstr "" + +#: ../../inventory/management/planning/scheduled_date.rst:187 +msgid "January 8: trigger a purchase request to your purchase team, since they need, on average, 2 days to find the right supplier and order." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:3 +msgid "Configure and Run Schedulers" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:6 +msgid "What is a scheduler?" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:8 +msgid "The scheduler is the calculation engine that plans and prioritizes production and purchasing. It does it automatically, according to the rules defined on products. By default, the scheduler is set to run once a day." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:14 +msgid "Calculating Requirements / Scheduling" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:16 +msgid "Scheduling only validates procurements that are confirmed but not yet started. These procurement reservations will start production, tasks or purchases themselves, depending on the configuration of the requested product." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:21 +msgid "As a human would do, the scheduler takes the priority of operations into account when starting reservations and procurements. Urgent requests will be started first." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:26 +msgid "In case there are not enough products in stock to satisfy all the requests, you can be sure that the most urgent ones will be produced first." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:31 +msgid "Configure and run the scheduler" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:34 +msgid "Run the scheduler manually" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:36 +msgid "To start the scheduler manually, go to *Inventory > Operations > Run Schedulers*. The scheduler uses all the relevant parameters defined for products, suppliers and the company to prioritize the different production orders, deliveries and supplier purchases." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:45 +msgid "Configure and run the scheduler (for advanced users)" +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:47 +msgid "To use this feature, you have to enable the debug mode. To do so, go to *Settings > Activate the developer mode*." +msgstr "" + +#: ../../inventory/management/planning/schedulers.rst:53 +msgid "Then, go to *Settings > Technical > Automation > Scheduled Actions* and modify the *Run MRP Scheduler Configuration*. There, you can set the starting time of the scheduler." +msgstr "" + +#: ../../inventory/management/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:3 +msgid "How to select the right replenishment strategy" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:5 +msgid "Minimum Stock rules and Make to Order have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:10 +msgid "Terminology" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:13 +msgid "Minimum stock rule" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:15 +msgid "Minimum Stock rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement order with the quantity needed to reach the maximum stock level." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:22 +#: ../../inventory/management/products/strategies.rst:58 +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:71 +msgid "Make to Order" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:24 +msgid "The Make to Order function will trigger a Purchase Order of the amount of the Sales Order related to the product. The system will **not** check the current stock. This means that a draft purchase order will be generated regardless of the quantity on hand of the product." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:33 +msgid "Minimum stock rules" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:35 +msgid "The Minimum Stock Rules configuration is available through your Inventory module. In the Inventory Control menu select \"Reordering Rule\" in the drop down menu. There, click on \"Create\" to set minimum and maximum stock values for a given product." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:44 +msgid "Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity multiple\" fields" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:47 +msgid "Then, click on your product to access the related product form and, on the \"Inventory submenu\", do not forget to select a supplier." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:54 +msgid "Don't forget to select the right product type. A consumable can not be stocked and will thus not be accounted for in the stock valuation." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:60 +msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory --> Inventory control --> Products` (or any other module where products are available)." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:64 +msgid "On the product form, under Inventory, click on \"Make To Order\"." +msgstr "" + +#: ../../inventory/management/products/strategies.rst:70 +msgid "Choice between the two options" +msgstr "" + +#: ../../inventory/management/products/strategies.rst:72 +msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order." +msgstr "" + +#: ../../inventory/management/products/uom.rst:3 +msgid "Use Different Units of Measure" +msgstr "" + +#: ../../inventory/management/products/uom.rst:5 +msgid "In some cases, handling products in different units of measure is necessary. For example, if you buy products in a country where the metric system is of application and sell in a country where the imperial system is used, you will need to convert the units. Another common use case is buying products in bigger packs to your supplier and selling them in units to your customers." +msgstr "" + +#: ../../inventory/management/products/uom.rst:12 +msgid "You can set up Odoo to work with different units of measure for one product." +msgstr "" + +#: ../../inventory/management/products/uom.rst:18 +msgid "In the *Inventory* application, go to *Configuration > Settings*. In the *Products* section, activate *Units of Measure*, then *Save*." +msgstr "" + +#: ../../inventory/management/products/uom.rst:25 +msgid "Create New Units of Measure" +msgstr "" + +#: ../../inventory/management/products/uom.rst:27 +msgid "In the *Inventory* application go to *Configuration > UoM*. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product." +msgstr "" + +#: ../../inventory/management/products/uom.rst:34 +msgid "The category is important for unit conversion, you will be able to convert products from one unit to another only if those units belong to the same category. The box of 6 is 6 times bigger than the reference unit of measure for the category which is “Units” here." +msgstr "" + +#: ../../inventory/management/products/uom.rst:43 +msgid "Specify Units of Measure on your Products" +msgstr "" + +#: ../../inventory/management/products/uom.rst:45 +msgid "In the *Inventory application > Master Data > Products*, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*." +msgstr "" + +#: ../../inventory/management/products/uom.rst:49 +msgid "In the *General Information* tab, you can select the *Unit of Measure* in which the product will be sold, which is also the unit in which internal transfers will take place. You can also select the *Purchase Unit of Measure*, which is the unit in which you purchase the product." +msgstr "" + +#: ../../inventory/management/products/uom.rst:59 +msgid "Transfer from One Unit to Another" +msgstr "" + +#: ../../inventory/management/products/uom.rst:62 +msgid "Buy in the Pruchase UoM" +msgstr "" + +#: ../../inventory/management/products/uom.rst:64 +msgid "In the *Purchase* application, *Create* a new request for quotation in which you include the product with the different *Units of Measure* and *Confirm* it." +msgstr "" + +#: ../../inventory/management/products/uom.rst:71 +msgid "On the automatically generated purchase orders, the UoM used is the Box of 6, meaning the Purchase UoM. You have of course the possibility to manually modify the UoM if necessary. When you enter the *Receipt* which is linked to the purchase order, you can observe that the 10 boxes of 6 units have been converted in 60 units. Indeed, the stock is managed in units." +msgstr "" + +#: ../../inventory/management/products/uom.rst:82 +msgid "Replenishment" +msgstr "" + +#: ../../inventory/management/products/uom.rst:84 +msgid "When doing a replenishment via the *Replenish* button on the product form, you have the possibility to change the unit of measure." +msgstr "" + +#: ../../inventory/management/products/uom.rst:94 +msgid "Sell in bigger UoM" +msgstr "" + +#: ../../inventory/management/products/uom.rst:96 +msgid "You can choose the unit of measure on the sale order document and decide to sell the eggs by the dozen. When doing so, the price is automatically computed from Units UoM to adapt to the selected *UoM*." +msgstr "" + +#: ../../inventory/management/products/uom.rst:103 +msgid "In the delivery order, the *UoM* used in the sale order is converted to the *UoM* used for stock management, in our use case, the Units." +msgstr "" + +#: ../../inventory/management/products/usage.rst:3 +msgid "When Should you Use Packages, Units of Measure or Kits?" +msgstr "" + +#: ../../inventory/management/products/usage.rst:6 +msgid "Units of Measure" +msgstr "" + +#: ../../inventory/management/products/usage.rst:8 +msgid "Units of measure specify the unit used to handle a product. In Odoo, you have the possibility to specify the unit of measure in which you manage your stock and the one which is used when purchasing the product to your supplier." +msgstr "" + +#: ../../inventory/management/products/usage.rst:16 +msgid "The *conversion* between the different units of measure is done automatically. The only condition is that all the units have to be in the *same category* (Unit, Weight, Volume, Length,...)" +msgstr "" + +#: ../../inventory/management/products/usage.rst:20 +msgid "For example, if I have the following reordering rule for the egg and I run the scheduler, the quantity added in the automatically generated purchase order will be in dozens but what will enter the stock will be units." +msgstr "" + +#: ../../inventory/management/products/usage.rst:35 +msgid "Packages" +msgstr "" + +#: ../../inventory/management/products/usage.rst:37 +msgid "The package is the physical container in which you put one or several products from a picking. For example, when you deliver a product, you can decide to separate the quantity into two different packages. It then allows you to have a report with the quantity of products for each package." +msgstr "" + +#: ../../inventory/management/products/usage.rst:50 +msgid "Packaging" +msgstr "" + +#: ../../inventory/management/products/usage.rst:52 +msgid "The packaging is the physical container that protects your product. If you are selling computers, the packaging contains the computer with the notice and the power plug." +msgstr "" + +#: ../../inventory/management/products/usage.rst:56 +msgid "In Odoo, packagings are used for indicative purposes on sale orders. They can be specified on the product form, in the inventory tab." +msgstr "" + +#: ../../inventory/management/products/usage.rst:66 +msgid "Another useful use of the packaging is for product reception. By scanning the barcode of the packaging, Odoo adds the number of units contained in the packing on the picking." +msgstr "" + +#: ../../inventory/management/replenishment_strategies.rst:3 +msgid "Inventory Adjustment" +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:3 +msgid "Choose Between Reordering Rules and Make to Order" +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:5 +msgid "*Reordering rules* and *make to order* do both allow to automatically replenish products when necessary. The difference between those tools is how they are triggered." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:9 +msgid "*Reordering rules* are used to ensure that you always have a minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement with the needed quantity to reach the maximum stock level." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:15 +msgid "The *Make to Order* route will trigger a procurement (purchase order or manufacturing order) with the necessary quantity to fulfill a product request (coming from a sale order or a manufacturing order). The system will check the quantity on hand for the corresponding product and if the available quantity is higher or equal to the necessary quantity, Odoo will use what is in stock to fulfill the request. In case you don’t have enough available stock to fully fulfill the product request, procurement will be generated for the total quantity requested." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:28 +msgid "Reordering Rules" +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:30 +msgid "The *Reordering Rules* configuration is available through the menu *Inventory > Master Data > Reordering Rules*. There, click on *Create* to set minimum and maximum stock values for a given product." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:37 +msgid "When the forecasted stock goes below the *Minimum Quantity* specified in this field, Odoo generates a procurement to bring the forecasted quantity to the *Maximum Quantity*. The *Quantity Multiple* is used to round the procurement quantity up to this multiple. If it is 0, the exact quantity will be used." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:46 +msgid "The *Lead time* is the number of days after the order point is triggered to receive the products or to order them to the vendor." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:49 +msgid "In case you work with multi-warehouses and/or multi-locations, you will be able to specify different reordering rules for the same product in each location." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:54 +msgid "For the reordering rules to be triggered, on the corresponding product, a route should be specified. In case you manufacture your products, make sure to select the route *Manufacture* and create a *Bill of Material* for the product. In case you purchase your products, make sure to select the route *Buy* and add a *Vendor Pricelist*." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:66 +msgid "Don't forget to select the product type *storable* in the product form. A consumable can not be stocked and won’t trigger reordering rules." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:73 +msgid "The *Make To Order* configuration is available on your product form through your *Inventory module > Master Data > Products* (or in any other module where products are available)." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:77 +msgid "On the product form, in the *Inventory tab*, you can set a route. You can choose *Make To Order* and another route, either *Buy* or *Manufacture*." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:81 +msgid "Again, if the *Buy* route is selected, make sure to set a *Vendor pricelist* in the *Purchase tab*. In case you have set a *Manufacture* route, male sure you have a *BoM* for this product." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:3 +msgid "Resupply from another Warehouse" +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:8 +msgid "In order to be able to resupply from another warehouse, you need to activate \\*multi-warehouses\\* and \\*multi-step routes\\*. Storage locations will be automatically activated when activating multi-warehouses." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:16 +msgid "You can then access your warehouses via \\*Inventory > Configuration > Warehouses\\*. Create the necessary warehouses following this `*documentation* `__. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:26 +msgid "By activating this option, a new route will now be available on your products \\*Supply Product from Second warehouse\\*. It can now be selected, along with either a \\*reordering rule\\* or a \\*make to order\\*." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:34 +msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to \\*Inventory > Operations > Run scheduler\\*." +msgstr "" + +#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:42 +msgid "The system automatically creates two pickings, one \\*delivery order\\* from my Second Warehouse which contains the necessary products, and a receipt in my main warehouse WH/Stock for the same products. The source document is the \\*reordering rule\\* which triggered the route \\*Supply Product from Second warehouse\\*." msgstr "" #: ../../inventory/management/reporting.rst:3 @@ -2657,12 +2682,6 @@ msgstr "" #: ../../inventory/management/reporting/valuation_methods_anglo_saxon.rst:282 #: ../../inventory/management/reporting/valuation_methods_continental.rst:263 #: ../../inventory/management/reporting/valuation_methods_continental.rst:281 -#: ../../inventory/overview/concepts/double-entry.rst:30 -#: ../../inventory/overview/concepts/double-entry.rst:45 -#: ../../inventory/overview/concepts/double-entry.rst:52 -#: ../../inventory/overview/concepts/double-entry.rst:57 -#: ../../inventory/overview/concepts/double-entry.rst:64 -#: ../../inventory/overview/concepts/double-entry.rst:72 msgid "Configuration:" msgstr "" @@ -3059,786 +3078,229 @@ msgstr "" msgid "Inventory Variations: to set as Stock Input/Output Account in product's internal category" msgstr "" -#: ../../inventory/overview/concepts.rst:3 -msgid "Main Concepts" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:5 -msgid "Introduction to Inventory Management" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:7 -msgid "A double-entry inventory has no stock input, output (disparition of products) or transformation. Instead, all operations are stock moves between locations (possibly virtual)." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:16 -msgid "Operations" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:18 -msgid "Stock moves represent the transit of goods and materials between locations." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:30 -msgid "Production Order" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:24 -msgid "Consume:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "2 Wheels: Stock → Production" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "1 Bike Frame: Stock → Production" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:26 -msgid "Produce:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:27 -msgid "1 Bicycle: Production → Stock" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Stock: the location the Manufacturing Order is initiated from" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Production: on the product form, field \"Production Location\"" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:36 -msgid "Drop-shipping" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:33 -msgid "1 Bicycle: Supplier → Customer" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:36 -msgid "Configurarion:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Supplier: on the product form" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Customer: on the sale order itself" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:45 -msgid "Client Delivery" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:39 -msgid "Pick" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:40 -msgid "1 Bicycle: Stock → Packing Zone" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:41 -msgid "Pack" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:42 -msgid "1 Bicycle: Packing Zone → Output" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:43 -#: ../../inventory/shipping.rst:3 -msgid "Shipping" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:44 -msgid "1 Bicycle: Output → Customer" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "on the pick+pack+ship route for the warehouse" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:52 -msgid "Inter-Warehouse transfer" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:49 -msgid "Transfer:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "1 Bicycle: Warehouse 1 → Transit" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "1 Bicycle: Transit → Warehouse 2" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Warehouse 2: the location the transfer is initiated from" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Warehouse 1: on the transit route" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:57 -msgid "Broken Product (scrapped)" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:55 -msgid "1 Bicycle: Warehouse → Scrap" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:58 -msgid "Scrap: Scrap Location when creating the scrapping" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:60 -msgid "Missing products in inventory" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:61 -msgid "1 Bicycle: Warehouse → Inventory Loss" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:62 -msgid "Extra products in inventory" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:63 -msgid "1 Bicycle: Inventory Loss → Warehouse" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:65 -msgid "Inventory Loss: \"Inventory Location\" field on the product" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:72 -msgid "Reception" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "1 Bicycle: Supplier → Input" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "1 Bicycle: Input → Stock" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Supplier: purchase order supplier" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:0 -msgid "Input: \"destination\" field on the purchase order" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:75 -msgid "Analysis" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:77 -msgid "Inventory analysis can use products count or products value (= number of products * product cost)." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:80 -msgid "For each inventory location, multiple data points can be analysed:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:148 -msgid "Procurements & Procurement Rules" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:150 -msgid "A procurement is a request for a specific quantity of products to a specific location. They can be created manually or automatically triggered by:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:159 -msgid "New sale orders" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:157 -#: ../../inventory/overview/concepts/double-entry.rst:162 -#: ../../inventory/overview/concepts/double-entry.rst:168 -msgid "Effect" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:157 -msgid "A procurement is created at the customer location for every product ordered by the customer (you have to deliver the customer)" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:160 -msgid "Procurement Location: on the customer, field \"Customer Location\" (property)" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:164 -msgid "Minimum Stock Rules" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:163 -msgid "A procurement is created at the rule's location." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:165 -msgid "Procurement location: on the rule, field \"Location\"" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:168 -msgid "Procurement rules" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:168 -msgid "A new procurement is created on the rule's source location" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:170 -msgid "*Procurement rules* describe how procurements on specific locations should be fulfilled e.g.:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:173 -msgid "where the product should come from (source location)" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:174 -msgid "whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made To Stock)`" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:179 -msgid "needs schema thing from FP" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:182 -msgid "Routes" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:184 -msgid "Procurement rules are grouped in routes. Routes define paths the product must follow. Routes may be applicable or not, depending on the products, sales order lines, warehouse,..." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:188 -msgid "To fulfill a procurement, the system will search for rules belonging to routes that are defined in (by order of priority):" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:202 -#: ../../inventory/settings/warehouses.rst:3 +#: ../../inventory/management/warehouses.rst:3 msgid "Warehouses" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:194 -msgid "Warehouse Route Example: Pick → Pack → Ship" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:3 +msgid "What is the difference between warehouses and locations?" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:196 -msgid "Picking List:" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:5 +msgid "In Odoo, a **Warehouse** is the actual building/place in which your items are stocked. You can setup multiple warehouses and create moves between warehouses." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:197 -msgid "Pick Zone → Pack Zone" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:9 +msgid "A **Location**, is a specific space within your warehouse. It can be considered as a sublocation of your warehouse, as a shelf, a floor, an aisle, etc. Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. You can configure as much locations as you need under one warehouse." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:198 -msgid "Pack List:" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:15 +msgid "There are 3 types of locations:" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:199 -msgid "Pack Zone → Gate A" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:17 +msgid "The **Physical Locations** are internal locations that are part of the warehouses for which you are the owner. They can be the loading and unloading area of your warehouse, a shelf or a department, etc." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:201 -msgid "Delivery Order:" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:21 +msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as Physical Locations with the only difference being that you are not the owner of the warehouse." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:201 -msgid "Gate A → Customer" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:25 +msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when you want to place lost products out of your stock (in the **Inventory loss**), or when you want to take into account products that are on their way to your warehouse (**Procurements**)." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:203 -msgid "Routes that describe how you organize your warehouse should be defined on the warehouse." +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:31 +msgid "In Odoo, locations are structured hierarchically. You can structure your locations as a tree, dependent on a parent-child relationship. This gives you more detailed levels of analysis of your stock operations and the organization of your warehouses." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:212 -msgid "A Product" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:37 +msgid ":doc:`warehouse_creation`" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:205 -msgid "Product Route Example: Quality Control" +#: ../../inventory/management/warehouses/difference_warehouse_location.rst:38 +msgid ":doc:`location_creation`" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:207 -#: ../../inventory/overview/concepts/double-entry.rst:217 -msgid "Reception:" +#: ../../inventory/management/warehouses/location_creation.rst:3 +msgid "Create a New Location" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:208 -#: ../../inventory/overview/concepts/double-entry.rst:218 -msgid "Supplier → Input" +#: ../../inventory/management/warehouses/location_creation.rst:8 +msgid "In order to be able to create different locations, you will need to activate *Multi-Locations* in the settings which can be done from the *Inventory application > Configuration > Settings*." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:209 -msgid "Confirmation:" +#: ../../inventory/management/warehouses/location_creation.rst:15 +msgid "In the *Inventory application*, you can now go to *Configuration > Locations* and hit *Create* in order to create a new location." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:210 -msgid "Input → Quality Control" +#: ../../inventory/management/warehouses/location_creation.rst:21 +msgid "Type the name of the location in the *Location Name* field, and select the *Parent Location* in the list. The parent location can be a physical, partner or virtual location, and you can add as many sub-locations as needed to a location." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:212 -msgid "Storage:" +#: ../../inventory/management/warehouses/location_creation.rst:29 +msgid "In case you want the location to be suggested when creating a Return or when Scrapping a product, you should check *Is a Scrap Location?* and *Is a Return Location?*." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:212 -msgid "Quality Control → Stock" +#: ../../inventory/management/warehouses/location_creation.rst:33 +msgid "If you have the *Barcode* application installed, you can specify the barcode which will correspond to this location." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:221 -msgid "Product Category" +#: ../../inventory/management/warehouses/location_creation.rst:37 +msgid "A warehouse also corresponds to a location. As the locations are hierarchical, Odoo will create the parent location of the warehouse, containing all the sublocations in it." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:215 -msgid "Product Category Route Example: cross-dock" +#: ../../inventory/management/warehouses/warehouse_creation.rst:3 +msgid "Create a New Warehouse" msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:219 -msgid "Cross-Docks:" +#: ../../inventory/management/warehouses/warehouse_creation.rst:8 +msgid "In order to create a new warehouse, you should activate the *Multi-Warehouse* settings. Note that the *Multi-Locations* settings will be automatically activated at the same time." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:220 -msgid "Input → Output" +#: ../../inventory/management/warehouses/warehouse_creation.rst:12 +msgid "In order to do so, go to the *Inventory app > Configuration > Settings*." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:221 -msgid "Delivery:" +#: ../../inventory/management/warehouses/warehouse_creation.rst:18 +msgid "You can then go to *Inventory > Configuration > Warehouses* and hit *Create* to add a new warehouse." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:222 -msgid "Output → Customer" +#: ../../inventory/management/warehouses/warehouse_creation.rst:24 +msgid "You will be able to enter your warehouse name. You should also choose a short name for your warehouse which is 5-characters long and is used on the different warehouse documents." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:227 -msgid "Sale Order Line" +#: ../../inventory/management/warehouses/warehouse_creation.rst:28 +msgid "In the Address field, you can select an existing company or create one on-the-go. Therefore, the address of your warehouse will be the same as the one of the company you selected. You can also leave this field empty and edit it afterward." msgstr "" -#: ../../inventory/overview/concepts/double-entry.rst:224 -msgid "Sale Order Line Example: Drop-shipping" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:227 -msgid "Order:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:227 -msgid "Supplier → Customer" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:230 -msgid "Push Rules" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:232 -msgid "Push rules trigger when products enter a specific location. They automatically move the product to a new location. Whether a push rule can be used depends on applicable routes." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:240 -#: ../../inventory/settings/products/uom.rst:88 -msgid "Quality Control" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:239 -msgid "Product lands in Input" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:240 -msgid "Push 1: Input → Quality Control" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:241 -msgid "Push 2: Quality Control → Stock" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:244 -msgid "Warehouse Transit" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:243 -msgid "Product lands in Transit" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:244 -msgid "Push: Transit → Warehouse 2" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:247 -msgid "Procurement Groups" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:249 -msgid "Routes and rules define inventory moves. For every rule, a document type is provided:" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:252 -msgid "Picking" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:253 -msgid "Packing" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:254 -msgid "Delivery Order" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:255 -msgid "Purchase Order" -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:256 -msgid "..." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:258 -msgid "Moves are grouped within the same document type if their procurement group and locations are the same." -msgstr "" - -#: ../../inventory/overview/concepts/double-entry.rst:261 -msgid "A sale order creates a procurement group so that pickings and delivery orders of the same order are grouped. But you can define specific groups on reordering rules too. (e.g. to group purchases of specific products together)" -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:3 -msgid "Terminologies" -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:5 -msgid "**Warehouse**: A warehouse in Odoo is a location where you store products. It is either a physical or a virtual warehouse. It could be a store or a repository." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:9 -msgid "**Location**: Locations are used to structure storage zones within a warehouse. In addition to internal locations (your warehouse), Odoo has locations for suppliers, customers, inventory loss counter-parts, etc." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:14 -msgid "**Lots**: Lots are a batch of products identified with a unique barcode or serial number. All items of a lot are from the same product. (e.g. a set of 24 bottle) Usually, lots come from manufacturing order batches or procurements." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:19 -msgid "**Serial Number**: A serial number is a unique identifier of a specific product. Technically, serial numbers are similar to having a lot of 1 unique item." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:23 -msgid "**Unit of Measure**: Define how the quantity of products is expressed. Meters, Pounds, Pack of 24, Kilograms,… Unit of measure of the same category (ex: size) can be converted to each others (m, cm, mm) using a fixed ratio." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:28 -msgid "**Consumable**: A product for which you do not want to manage the inventory level (no quantity on hand or forecasted) but that you can receive and deliver. When this product is needed Odoo suppose that you always have enough stock." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:33 -msgid "**Stockable**: A product for which you want to manage the inventory level." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:36 -msgid "**Package:** A package contains several products (identified by their serial number/lots or not). Example: a box containing knives and forks." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:40 -msgid "**Procurement**: A procurement is a request for a specific quantity of products to a specific location. Procurement are automatically triggered by other documents: Sale orders, Minimum Stock Rules, and Procurement rules. You can trigger the procurement manually. When procurements are triggered automatically, you should always pay attention for the exceptions (e.g. a product should be purchased from a vendor, but no supplier is defined)." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:48 -msgid "**Routes**: Routes define paths the product must follow. Routes may be applicable or not, depending on the products, sales order lines, warehouse,… To fulfill a procurement, the system will search for rules belonging to routes that are defined in the related product/sale order." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:54 -msgid "**Push Rules**: Push rules trigger when products enter a specific location. They automatically move the product to a new location. Whether a push rule can be used depends on applicable routes." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:58 -msgid "**Procurement Rules** or **Pull Rules**: Procurement rules describe how procurements on specific locations should be fulfilled e.g.: where the product should come from (source location), whether the procurement is MTO or MTS,..." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:63 -msgid "**Procurement Group**: Routes and rules define inventory moves. For every rule, a document type is provided: Picking, Packing, Delivery Order, Purchase Order,… Moves are grouped within the same document type if their procurement group and locations are the same." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:69 -msgid "**Stock Moves**: Stock moves represent the transit of goods and materials between locations." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:72 -msgid "**Quantity On Hand**: The quantity of a specific product that is currently in a warehouse or location." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:75 -msgid "**Forecasted Quantity**: The quantity of products you can sell for a specific warehouse or location. It is defined as the Quantity on Hand - Future Delivery Orders + Future incoming shipments + Future manufactured units." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:80 -msgid "**Reordering Rules**: It defines the conditions for Odoo to automatically trigger a request for procurement (buying at a supplier or launching a manufacturing order). It is triggered when the forecasted quantity meets the minimum stock rule." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:85 -msgid "**Cross-Dock**: Cross-docking is a practice in the logistics of unloading materials from an incoming semi-trailer truck or railroad car and loading these materials directly into outbound trucks, trailers, or rail cars, with no storage in between. (does not go to the stock, directly from incoming to packing zone)" -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:91 -msgid "**Drop-Shipping**: move products from the vendor/manufacturer directly to the customer (could be retailer or consumer) without going through the usual distribution channels. Products are sent directly from the vendor to the customer, without passing through your own warehouse." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:97 -msgid "**Removal Strategies**: the strategy to use to select which product to pick for a specific operation. Example: FIFO, LIFO, FEFO." -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:100 -msgid "**Putaway Strategies**: the strategy to use to decide in which location a specific product should be set when arriving somewhere. (example: cables goes in rack 3, storage A)" -msgstr "" - -#: ../../inventory/overview/concepts/terminologies.rst:104 -msgid "**Scrap**: A product that is broken or outdated. Scrapping a product removes it from the stock." +#: ../../inventory/management/warehouses/warehouse_creation.rst:36 +msgid "After the creation of your new warehouse, you can go back to the *Dashboard* and you will see the new operation types automatically created by Odoo due to the creation of a new warehouse." msgstr "" #: ../../inventory/overview/process.rst:3 msgid "Process Overview" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:3 -msgid "From procurement to delivery" +#: ../../inventory/overview/process/deliver_from_stock.rst:3 +#: ../../inventory/overview/process/deliver_from_stock.rst:25 +msgid "Deliver Products from Stock" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:8 -msgid "Inventory is the heart of your business. It can be really complicated, but with Odoo, doing a receipt or a delivery has never been easier. We will show you in this document how easy to do a full process, from the receipt to the delivery." +#: ../../inventory/overview/process/deliver_from_stock.rst:6 +msgid "Create Storable/Consumable Products" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:13 -msgid "Odoo inventory is fully integrated with other applications, such as **Purchase**, **Sales** or **Inventory**. But is not limited to those processes, it is also fully integrated with our **e-Commerce**, **Manufacturing** and **Repairs** applications." +#: ../../inventory/overview/process/deliver_from_stock.rst:8 +#: ../../inventory/overview/process/initial_stock.rst:5 +#: ../../inventory/overview/process/receive_in_stock.rst:5 +msgid "The first step to use the inventory application is to create products in your database via the menu *Master Data > Products*. Click the Create button and enter the name of your product." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:19 -msgid "How to process a receipt ?" +#: ../../inventory/overview/process/deliver_from_stock.rst:15 +#: ../../inventory/overview/process/receive_in_stock.rst:12 +msgid "In case you set the product as *storable*, you will track the stock for this product and know how many units are in stock and what is the forecasted number of units. If you want to include a product on receipts/deliveries but don’t need to track its stock, you can set it as *consumable*." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:22 -msgid "Install Purchase application" +#: ../../inventory/overview/process/deliver_from_stock.rst:27 +msgid "Once you have existing products, you can decide to create a delivery to deliver products to your customers. The process in order to do so is described in the following print screens." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:24 -msgid "First, you will need to install the **Purchase Management** application. Go to :menuselection:`Apps` and install it." +#: ../../inventory/overview/process/deliver_from_stock.rst:37 +msgid "On the delivery order, you can specify to whom the products will be delivered along with the different products and their respective quantities. When the delivery is complete you can hit *Validate* and the products will go out of your stock." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:31 -msgid "Make a purchase order" +#: ../../inventory/overview/process/deliver_from_stock.rst:45 +msgid "In case you have a delivery that is planned but shouldn’t be immediately validated, you can create a *planned delivery* with a scheduled date in the future. You can indicate the initial demand for each product, corresponding to what has been ordered by your customer. Once the document is filled in, you can hit “Mark as to do” in order to consider it in your product forecasts." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:33 -msgid "Go to the **Purchases** applications. The first screen is the **Request for Quotation** list. Click on the **Create** button." +#: ../../inventory/overview/process/deliver_from_stock.rst:56 +msgid "Deliver Products from Stock from a Sale Order" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:36 -msgid "Fill in the **Vendor** information and click on **Add an Item** to add some products to your request for quotation." +#: ../../inventory/overview/process/deliver_from_stock.rst:58 +msgid "If you have the *Sales* application installed, delivery can be directly created by *validating a quotation*. You will be able to find the corresponding delivery directly on the *sale order*." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:42 -msgid "Click on **Confirm order** when you are sure about the products, prices and quantity." +#: ../../inventory/overview/process/initial_stock.rst:3 +msgid "Set your Initial Stock" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:46 -msgid "Retrieve the Receipt" +#: ../../inventory/overview/process/initial_stock.rst:12 +msgid "Set the product as *storable*, in order to track the stock for this product and be able to include it in an inventory adjustment." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:48 -msgid "You can retrieve the receipt order in 2 ways:" +#: ../../inventory/overview/process/initial_stock.rst:19 +msgid "Inventory Adjustment for Multiple Products" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:51 -msgid "From the purchase order" +#: ../../inventory/overview/process/initial_stock.rst:21 +msgid "Once you have created all your *storable products*, you can create an *inventory adjustment* to determine their current stock level in Odoo. You therefore need to go to *Operations > Inventory Adjustments* and create a new one." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:53 -msgid "On the top right of your purchase order, you will see a button with the related **Receipt**:" +#: ../../inventory/overview/process/initial_stock.rst:29 +msgid "You have to enter a title for your *inventory adjustment* and you can then decide if you want to proceed to the *inventory adjustment* of all products or only some of them. For a first *inventory adjustment*, I suggest you to keep the *Products* field empty. You can then *Start Inventory*." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:59 -#: ../../inventory/overview/process/sale_to_delivery.rst:136 -msgid "Click on it to see the **Transfer order**." +#: ../../inventory/overview/process/initial_stock.rst:38 +msgid "If you already have some products in stock, Odoo will add the lines with the theoretical quantity currently in stock. You can also add new lines with your other products." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:62 -#: ../../inventory/overview/process/sale_to_delivery.rst:139 -msgid "From the Inventory Dashboard" +#: ../../inventory/overview/process/initial_stock.rst:46 +msgid "If your products are tracked by Serial/Lot numbers, you will have an additional column allowing you to specify those for the different units added to the inventory adjustment." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:64 -msgid "When opening the **Inventory** application, click on **# to receive** to see the list of your deliveries to process." +#: ../../inventory/overview/process/initial_stock.rst:50 +msgid "Odoo will highlight in red the lines for which there is a difference between the theoretical quantity on hand, which is automatically computed by the system, and the counted quantity you manually entered. Once all the necessary products have been entered, you can hit *Validate Inventory* and the quantities on hand of your different products will be updated." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:70 -msgid "In the list, click on the one related to the purchase order:" +#: ../../inventory/overview/process/initial_stock.rst:58 +msgid "Inventory Adjustment for one Product" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:76 -msgid "Process the Receipt" +#: ../../inventory/overview/process/initial_stock.rst:60 +msgid "On each storable product, you have access to the *Update Quantity* button." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:81 -#: ../../inventory/overview/process/sale_to_delivery.rst:162 -msgid "To process the stock transfer. Simply click on **Validate** to complete the transfer. A message will appear asking if you want to process the whole order, accept it by clicking on **Apply**." +#: ../../inventory/overview/process/initial_stock.rst:66 +msgid "When clicking this button, you see the current stock you have for this product. You can edit the existing lines or create new ones to add stock of your product in different locations and/or add new serial/lot numbers." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:86 -msgid "Procurements can be automated. Please read our document :doc:`../../management/adjustment/min_stock_rule_vs_mto` for more information." +#: ../../inventory/overview/process/initial_stock.rst:74 +msgid "Once you come back to your product, you see that the quantity on hand as been updated taking your modification into account." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:91 -msgid "How to process a delivery order ?" +#: ../../inventory/overview/process/initial_stock.rst:81 +msgid "If you work with product variants, the quantity on hand will show you the total quantity in stock for the product template, taking the different variants into account." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:94 -msgid "Install Sales application" +#: ../../inventory/overview/process/initial_stock.rst:85 +msgid "By default, the quantity on hand of the product form will show you the number of products that are part of your warehouse view location, meaning which are part of an internal type sub-location of this warehouse. It means that if you have any product in a location that isn’t under the main warehouse location, they won’t appear in the stock on hand stat button." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:96 -msgid "First, you will need to install the **Sales Management** application. Go to :menuselection:`Apps` and install it." +#: ../../inventory/overview/process/receive_in_stock.rst:3 +#: ../../inventory/overview/process/receive_in_stock.rst:22 +msgid "Receive Products in Stock" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:103 -msgid "Place a sale order" +#: ../../inventory/overview/process/receive_in_stock.rst:24 +msgid "Once you have existing products, you can decide to create a receipt to enter products from your supplier in stock. The process in order to do so is described in the following print screens." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:105 -msgid "Go to the **Sales** applications. Click on the **Quotations** button of your team." +#: ../../inventory/overview/process/receive_in_stock.rst:34 +msgid "On the receipt document, you can select the quantity of the different products you receive and the supplier from who you received them. When the receipt is complete, you can hit *Validate* and the products will enter your stock." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:111 -msgid "You will get the list of all your quotations. Click on the **Create** button." +#: ../../inventory/overview/process/receive_in_stock.rst:42 +msgid "In case you have a receipt that is planned but shouldn’t be immediately validated, you can create a *planned receipt* with a scheduled date in the future. You can indicate the initial demand for each product, corresponding to what has been ordered to your supplier. Once the document is filled in, you can hit “Mark as to do” in order to consider it in your product forecasts." msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:114 -msgid "Fill in the **Customer informations** and click on **Add an Item** to add some products to your quotation." +#: ../../inventory/overview/process/receive_in_stock.rst:56 +msgid "Receive Products in Stock from Purchase Orders" msgstr "" -#: ../../inventory/overview/process/sale_to_delivery.rst:120 -msgid "Click on **Confirm sale** to place the order." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:123 -msgid "Retrieve the Delivery order" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:125 -msgid "You can retrieve the delivery order in 2 ways:" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:128 -msgid "From the sale order" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:130 -msgid "On the top right of your sale order, you will see a button with the related **Delivery**:" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:141 -msgid "When opening the **Inventory** application, click on **# to do** to see the list of your receipts to process." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:147 -msgid "In the list, click on the one related to the sale order:" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:153 -msgid "If the product is not in stock, the sale order will be listed as **Waiting** on your dashboard." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:157 -msgid "Process the delivery" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:167 -msgid "E-Commerce orders are processed the same way." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:170 -msgid "You can easily integrate your delivery orders with different delivery methods. Please read the document :doc:`../../shipping/setup/delivery_method`." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:175 -msgid "Advanced flows" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:177 -msgid "In this document, the flows that are explained are the most simple ones. Odoo also suit for companies having advanced warehouse management." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:180 -msgid "By default, only **receipts** and **deliveries** are configured but you can activate the use of multi-locations and multi-warehouses to do **internal transfers**." -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:184 -msgid "**Routes**: you can automate flows with push and pull rules" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:186 -msgid "**Multi-step** receipts and deliveries can be easily configured for each warehouse" -msgstr "" - -#: ../../inventory/overview/process/sale_to_delivery.rst:189 -msgid "Much more: **Barcode scanning**, **serial numbers**, **lots**, **cross-docking**, **dropshipping**, integration with a **third-party** shipper, **putaway** and **removal** strategies.... All of it is possible with Odoo." -msgstr "" - -#: ../../inventory/overview/start.rst:3 -msgid "Getting Started" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:3 -msgid "How to setup Odoo inventory?" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:5 -msgid "The Odoo Inventory application has an implementation guide that you should follow to configure it. It's a step-by-step manual with links to the different screens you need." -msgstr "" - -#: ../../inventory/overview/start/setup.rst:9 -msgid "Once you have installed the **Inventory** application, click on the top-right progress bar to get access to the implementation guide." -msgstr "" - -#: ../../inventory/overview/start/setup.rst:15 -msgid "The implementation guide helps you through the following steps:" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:17 -msgid "Set up your warehouse" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:19 -msgid "Import your vendors" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:21 -msgid "Import your products" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:23 -msgid "Set up the initial inventory" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:25 -msgid "Configure your sales and purchase flows" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:27 -msgid "Set up replenishment mechanisms" -msgstr "" - -#: ../../inventory/overview/start/setup.rst:29 -msgid "Configure advanced features like package, traceability, routes and inventory valuation." -msgstr "" - -#: ../../inventory/overview/start/setup.rst:37 -msgid "If you want to set up operations with barcode scanner in your warehouse, you should install the **Barcode** application that adds features on top of the inventory application. The barcode application will guide you to configure and use your scanner optimally." +#: ../../inventory/overview/process/receive_in_stock.rst:58 +msgid "If you have the *Purchase* application installed, receipts can be directly created by validating a *request for quotation*. You will be able to find the corresponding receipt directly on the *purchase order*." msgstr "" #: ../../inventory/routes.rst:3 @@ -3850,91 +3312,55 @@ msgid "Concepts" msgstr "" #: ../../inventory/routes/concepts/cross_dock.rst:3 -msgid "How to organize a cross-dock in your warehouse?" +msgid "Organize a cross-dock in a warehouse" msgstr "" #: ../../inventory/routes/concepts/cross_dock.rst:5 -msgid "Cross dock area is temporarily area where we are not storing any product instead just managing place according to delivery for further customer. This will save lot of time for inter warehouse transfer and storing process. We are managing our products with docking area where product directly place from supplier location and transfer this to gate pass for customer delivery." +msgid "Cross-docking is the process of sending products that are received directly to the customers, without making them enter the stock. The trucks are simply unloaded in a *Cross-Dock* area in order to reorganize products and load another truck." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:17 -msgid "For more information on how to organise your warehouse, read `What is cross docking and is it for me? `_" +#: ../../inventory/routes/concepts/cross_dock.rst:11 +msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? `__" msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:24 -msgid "Warehouse and routes" +#: ../../inventory/routes/concepts/cross_dock.rst:15 +msgid "In the *Inventory* app, open *Configuration > Settings* and activate the *Multi-Step Routes*." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:26 -msgid "In the **Inventory** module, open :menuselection:`Configuration --> Settings --> Location & Warehouse`, then in **Routes**, select **Advanced routing of products using rules**, then click on **Apply**." +#: ../../inventory/routes/concepts/cross_dock.rst:21 +msgid "Doing so will also enable the *Storage Locations* feature." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:33 -msgid "Open :menuselection:`Configuration --> Warehouse Management --> Warehouses`, then open the warehouse you want to cross-dock from and click on **Edit**." +#: ../../inventory/routes/concepts/cross_dock.rst:23 +msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to *Inventory > Configuration > Warehouses* and edit your warehouse." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:28 +msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in *Inventory > Configuration > Routes*." +msgstr "" + +#: ../../inventory/routes/concepts/cross_dock.rst:34 +msgid "Configure products with Cross-Dock Route" msgstr "" #: ../../inventory/routes/concepts/cross_dock.rst:36 -msgid "In the **Warehouse Configuration** tab, select:" +msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:38 -msgid "**Incoming Shipments**: Unload in input location then go to stock (2 steps)" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:41 -msgid "**Outgoing Shipments**: Ship directly from stock (Ship only)" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:43 -msgid "then click on **Save**." -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:48 -msgid "This steps has generated a cross-docking route that you can see in :menuselection:`Inventory --> Configurations --> Routes --> Routes`." +#: ../../inventory/routes/concepts/cross_dock.rst:44 +msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier." msgstr "" #: ../../inventory/routes/concepts/cross_dock.rst:52 -msgid "Cross Docking Route" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:54 -msgid "We will use the route **Buy** for first part of the flow and create a route for the remaining part:" +msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*." msgstr "" #: ../../inventory/routes/concepts/cross_dock.rst:60 -msgid "Each of the procurement rule will now be configured. Cross Dock location is created as an internal physical location." +msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*." msgstr "" -#: ../../inventory/routes/concepts/cross_dock.rst:67 -msgid ":menuselection:`Input --> Cross Dock`" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:73 -msgid ":menuselection:`Cross Dock --> Output`" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:79 -msgid ":menuselection:`Output --> Customer`" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:82 -msgid "Product with cross dock" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:84 -msgid "We have created the Vegetable Fennel product and assigned the routes created above as well as the **Buy** route." -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:87 -msgid "We have also specified a supplier and a minimum order rule which is needed for replenishment of a stockable product." -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:95 -msgid ":doc:`use_routes`" -msgstr "" - -#: ../../inventory/routes/concepts/cross_dock.rst:96 -msgid ":doc:`../../management/incoming/two_steps`" +#: ../../inventory/routes/concepts/cross_dock.rst:68 +msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" #: ../../inventory/routes/concepts/inter_warehouse.rst:3 @@ -3954,7 +3380,6 @@ msgid "This option should also be ticked if you wish to manage different locatio msgstr "" #: ../../inventory/routes/concepts/inter_warehouse.rst:26 -#: ../../inventory/settings/warehouses/warehouse_creation.rst:9 msgid "Creating a new warehouse" msgstr "" @@ -4181,6 +3606,42 @@ msgstr "" msgid ":doc:`procurement_rule`" msgstr "" +#: ../../inventory/routes/concepts/stock_warehouses.rst:3 +msgid "Taking stock from different warehouses" +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:5 +msgid "When you plan to deliver a customer, you don’t know in advance if the products will come from Warehouse A or Warehouse B. You may, in some cases, need to take stock from different warehouses. With *Odoo*, you can configure this by using the concept of virtual warehouses. Let us show you how to set those virtual warehouses." +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:8 +msgid "Set up virtual warehouses" +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:10 +msgid "Let’s say you have two warehouses: Warehouse A and Warehouse B. Create a new warehouse, that will be a virtual one. It will allow you to take the stock from A or B. To do so, go to your inventory app settings and enable the multi-warehouses feature. Then, go to the warehouses menu and click on create." +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:16 +msgid "The *Storage Location* feature will be automatically enabled. Good news, because you will need it later in the process." +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:18 +msgid "Now, you have to make sure that the main stock locations of warehouse A and warehouse B are children locations of the main stock location of warehouse A + B. Go to the locations menu, and edit the main location of your two warehouses. Then, change their parent location to main location of warehouse A+B." +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:24 +msgid "Sell a product from the virtual warehouse" +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:26 +msgid "Let’s say you have two products, one stored in warehouse A and one stored in warehouse B. Now, you can create a new quotation for one of each product. Go to other information and choose Warehouse A+B in the shipping information." +msgstr "" + +#: ../../inventory/routes/concepts/stock_warehouses.rst:31 +msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B." +msgstr "" + #: ../../inventory/routes/concepts/use_routes.rst:3 msgid "How to use routes?" msgstr "" @@ -4350,63 +3811,43 @@ msgid "Putaway & Removal Strategies" msgstr "" #: ../../inventory/routes/strategies/putaway.rst:3 -msgid "What is a putaway strategy?" +msgid "What is a Putaway Rule?" msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:8 -msgid "A good warehouse implementation takes care that products automatically move to their appropriate destination location. Putaway is the process of taking products off the receiving shipment and putting them into the most appropriate location." +#: ../../inventory/routes/strategies/putaway.rst:5 +msgid "A good warehouse implementation takes care that products automatically move to their appropriate destination location. To make that process easier, Odoo uses *Putaway rules*. But what is a putaway rule? Putaway is the process of taking products off the receiving shipments and directly putting them into the most appropriate location." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:13 -msgid "If for instance a warehouse contains volatile substances, it is important to make sure that certain products are not stored close to each other because of a potential chemical reaction." +#: ../../inventory/routes/strategies/putaway.rst:7 +msgid "If, for example, a warehouse contains volatile substances, it is important to make sure that certain products are not stored close to each other because of a potential chemical reaction. That’s where putaway rules intervene, to avoid storing products wrongly." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:17 -msgid "A putaway strategy follows the same principle as removal strategies but affects the destination location. Putaway strategies are defined at the location level (unlike removal strategies which are defined at the product level)." +#: ../../inventory/routes/strategies/putaway.rst:12 +msgid "In the *Inventory* app, go to *Configuration > Settings* and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:25 -msgid "Go to :menuselection:`Inventory --> Configuration --> Settings` and check option **Manage several location per warehouse & Advance routing of products using rules**, then click on **Apply**." +#: ../../inventory/routes/strategies/putaway.rst:18 +msgid "Setting up a Putaway Rule" msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:33 -msgid "Setting up a strategy" +#: ../../inventory/routes/strategies/putaway.rst:20 +msgid "In some cases, like for a retail shop storing vegetables and fruits, we have to store products in different locations to maintain product quality." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:35 -msgid "Let's take as an example a retail shop where we store vegetables and fruits." +#: ../../inventory/routes/strategies/putaway.rst:22 +msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegatable* and *WH/Stock/Fruits*." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:38 -msgid "We have to store this type of product in different locations to maintain product quality." +#: ../../inventory/routes/strategies/putaway.rst:24 +msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to *Configuration > Putaway Rules*. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:41 -msgid "Suppose there is one warehouse location **WH/Stock** and there is sub location **WH/Stock/Vegetables** & **WH/Stock/Fruits**." +#: ../../inventory/routes/strategies/putaway.rst:27 +msgid "The putaway rules can be defined either per product or per product category." msgstr "" -#: ../../inventory/routes/strategies/putaway.rst:44 -msgid "You can create a putaway strategy from :menuselection:`Inventory --> Configuration --> Locations`. Open any location where you want to set a putaway strategy, click on **Edit** and locate the option **Put Away Strategy**." -msgstr "" - -#: ../../inventory/routes/strategies/putaway.rst:52 -msgid "Open the roll-down menu and click on **Create and Edit**. This will open a form view of put away strategy on which you have to set a name for the strategy, and set the method and fixed location for each category." -msgstr "" - -#: ../../inventory/routes/strategies/putaway.rst:59 -msgid "When you have entered all the necessary information, click on **Save**." -msgstr "" - -#: ../../inventory/routes/strategies/putaway.rst:61 -msgid "Now, when you purchase products with those categories, they will automatically be transferred to the correct location." -msgstr "" - -#: ../../inventory/routes/strategies/putaway.rst:64 -msgid "To check current inventory, Go to :menuselection:`Inventory --> Inventory Control --> Current Inventory`" -msgstr "" - -#: ../../inventory/routes/strategies/putaway.rst:67 -msgid "There you can see current inventory by location." +#: ../../inventory/routes/strategies/putaway.rst:32 +msgid "Now, if I purchase apples and carrots to my supplier, they will be grouped in the same receipt but redirected to the right location automatically, thanks to putaway rules. This information is available from *Inventory Report*, under the reporting menu." msgstr "" #: ../../inventory/routes/strategies/removal.rst:3 @@ -4627,600 +4068,8 @@ msgstr "" msgid ":doc:`../../management/reporting/valuation_methods_anglo_saxon`" msgstr "" -#: ../../inventory/settings.rst:3 -msgid "Settings" -msgstr "" - -#: ../../inventory/settings/products.rst:3 -msgid "Products" -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:3 -msgid "How to select the right replenishment strategy" -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:5 -msgid "Minimum Stock rules and Make to Order have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:15 -msgid "Minimum Stock rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement order with the quantity needed to reach the maximum stock level." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:24 -msgid "The Make to Order function will trigger a Purchase Order of the amount of the Sales Order related to the product. The system will **not** check the current stock. This means that a draft purchase order will be generated regardless of the quantity on hand of the product." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:35 -msgid "The Minimum Stock Rules configuration is available through your Inventory module. In the Inventory Control menu select \"Reordering Rule\" in the drop down menu. There, click on \"Create\" to set minimum and maximum stock values for a given product." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:44 -msgid "Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity multiple\" fields" -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:47 -msgid "Then, click on your product to access the related product form and, on the \"Inventory submenu\", do not forget to select a supplier." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:54 -msgid "Don't forget to select the right product type. A consumable can not be stocked and will thus not be accounted for in the stock valuation." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:60 -msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory --> Inventory control --> Products` (or any other module where products are available)." -msgstr "" - -#: ../../inventory/settings/products/strategies.rst:64 -msgid "On the product form, under Inventory, click on \"Make To Order\"." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:3 -msgid "How to use different units of measure?" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:8 -msgid "In some cases, handling products in different unit of measures is necessary. For example, if you buy products in a country where the metric system is of application and sell them in a country where the imperial system is used, you will need to convert the units." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:13 -msgid "You can set up Odoo to work with different units of measure for one product." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:19 -msgid "In the **Inventory** application, go to :menuselection:`Configuration --> Settings`. In the **Products** section, select **Some products may be sold/purchased in different units of measure (advanced)**, then click on **Apply**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:27 -msgid "Setting up units on your products" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:29 -msgid "In :menuselection:`Master Data --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on **Edit**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:32 -msgid "In the **Unit of Measure** section, select the unit in which the product will be sold and in which internal transfers will be done." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:35 -msgid "In the **Purchase Unit of Measure** section, select the unit in which you purchase the product. When you're done, click on **Save**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:42 -msgid "Click on the edit button |edit| to create new unit of measures." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:46 -msgid "Transfer from one unit to another" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:48 -msgid "When doing inter-unit transfers, the rounding is automatically done by Odoo." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:51 -msgid "The unit of measure can be changed throughout the whole process. The only condition is that the unit of measure is part of the same category." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:54 -msgid "In this example, we are in the egg business :" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:56 -msgid "We buy eggs by trays (30 eggs)" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:58 -msgid "We check all eggs individually when receiving it (quality control)" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:60 -msgid "We sell eggs by the dozen to the customers" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:66 -msgid "The **Sale price** is expressed in the **Product unit of measure**. The **Cost price** is expressed in the **Purchase Unit of Measure**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:70 -msgid "All internal transfers are expressed in the **Product Unit of Measure**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:74 -msgid "Procurement" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:76 -msgid "When doing your procurement request, you can still change the unit of measure." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:82 -msgid "The unit of measure can also be changed in the purchase order :" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:90 -msgid "The quality control is done by unit." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:92 -msgid "The basic unit of measure of our product is **Unit**. Therefore the quality check is done by unit." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:99 -msgid "The unit of measure can only be changed when the transfer status is **Draft**." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:103 -#: ../../inventory/shipping/setup/delivery_method.rst:74 -msgid "Delivery process" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:105 -msgid "The eggs are sold by the dozen. You can choose the unit of measure on the sale order document. When doing it, the price is automatically computed from the unit to the dozen." -msgstr "" - -#: ../../inventory/settings/products/uom.rst:112 -msgid "In the delivery order, the initial demand is done in the sales order unit of measure :" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:118 -msgid "But the transfer is done in the product unit of measure. Everything is converted automatically :" -msgstr "" - -#: ../../inventory/settings/products/uom.rst:125 -msgid "Create a link when the document is available - When should you use packages, units of measure or kits?" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:3 -msgid "When should you use packages, units of measure or kits?" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:6 -msgid "Unit of measures" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:8 -msgid "Units of measures are an indication about the unit used to handle a product. Products can be expressed in multiple units of measure at once." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:11 -msgid "Activate this option if you are working with several ones in your warehouse." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:14 -msgid "The purchase unit of measure might be different that the one you use in your warehouse." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:17 -msgid "The selling unit of measure is set on the sale order and can be different." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:24 -msgid "The conversion between the different units of measures is done automatically. The only condition is that all the units have to be in the same category (Unit, Weight, Volume, Length,...)" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:29 -msgid "Packages" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:31 -msgid "The package is the physical container in which you put one or several product." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:38 -msgid "Packaging" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:40 -msgid "Packaging is the physical container that protects your product." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:42 -msgid "If you are selling computers, the packaging contains the computer with the notice and the power plug." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:45 -msgid "In Odoo, packagings are just used for indicative purpose." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:51 -msgid "You can define on the **Packages** which **Packaging** it uses. But it is only for indicative purpose." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:55 -msgid "When to use packages, packagings or unit of measures ?" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:57 -msgid "For example, you are sellings eggs. In your warehouse, you manage the eggs individually. Lots of eggs are scrapped and you do it egg by egg. The **unit of measure** is ``Unit(s)``." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:61 -msgid "If you are selling eggs by the dozen, the selling **unit of measure** is the ``Dozen``. You will set it on your sale order." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:64 -msgid "The ``cardboard trays`` that contains the dozen of eggs is the **packaging**." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:66 -msgid "When you are selling several trays, you might wrap all the trays into a ``box`` or in a ``plastic`` wrapping. It is the **package**." -msgstr "" - -#: ../../inventory/settings/products/usage.rst:70 -msgid ":doc:`../../overview/start/setup`" -msgstr "" - -#: ../../inventory/settings/products/usage.rst:71 -msgid ":doc:`uom`" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:3 -msgid "Using product variants" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:5 -msgid "Product variants are used to manage products having different variations, like size, color, etc. It allows managing the product at the template level (for all variations) and at the variant level (specific attributes)." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:10 -msgid "As an example, a company selling t-shirts may have the following product:" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:13 -msgid "B&C T-shirt" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:15 -msgid "Sizes: S, M, L, XL, XXL" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:16 -msgid "Colors: Blue, Red, White, Black" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:18 -msgid "In this example, **B&C T-Shirt** is called the product template and **B&C T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:22 -msgid "The above example has a total of 20 different products (5 sizes x 4 colors). Each one of these products has its own inventory, sales, etc." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:26 -msgid "Impact of variants" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:28 -msgid "**Barcode**: the code and barcode is associated to a variant, not the template. Every variant may have its own barcode / SKU." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:31 -msgid "**Price**: every product variant has its own public price that is computed based on the template price ($20) with an optional extra for every variant (+$3 for color red). However, you can define pricelist rules that apply on the template or the variant." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:36 -msgid "**Inventory**: the inventory is managed by product variant. You don't own t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For information purpose, on the product template form, you get the inventory that is the sum of every variant. (but the actual inventory is computed by variant)" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:42 -msgid "**Picture**: the picture is related to the variant, every variation of a product may have its own primary picture." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:45 -msgid "**Other fields**: most of the other fields belongs to the product template. If you update them, it updates automatically all the variants. (example: Income Account, Taxes)" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:50 -msgid "Should you use variants?" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:53 -msgid "When should you use variants?" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:55 -msgid "Using variants has the following impacts:" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:57 -msgid "**eCommerce**: in your online shop, the customer will only see product templates in the catalog page. Once the visitor click on such a product, he will have options to choose amongst the variants (colors, sizes, …)" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:62 -msgid "**Manufacturing**: Using variants allows to define only one bill of material for a product template and slight variations for some of the variants. Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you create a bill of material for \"T-shirt\" and add some lines that are specific to the dimension S, and other lines specific to the color Red." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:69 -msgid "**Pricing**: The default price of a product is computed using the price of the product template and add the optional extra price on each dimension of the variant. This way, variant prices are easier to maintain since you don't have to set the price for every variant. However, it's possible to create pricelist rules to fix price per variants too." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:77 -msgid "When should you avoid using variants?" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:79 -msgid "Using variants may add a level of complexity on the way you use Odoo. You should consider using variants only if you need it to reduce the complexity of managing lots of products that are similars." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:83 -msgid "As an example, importing your initial product catalog is more complex if you use variants. You can't just import a list of products, you must import product templates and all their related variations." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:87 -msgid "In addition to that, you should also carefully select the dimensions that you manage as separate product templates and those as variants. As an example, a company having these products:" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:91 -msgid "Quality: T-Shirts, Polos, Shirts" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:93 -#: ../../inventory/settings/products/variants.rst:105 -#: ../../inventory/settings/products/variants.rst:110 -msgid "Color: Red, Blue" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:95 -#: ../../inventory/settings/products/variants.rst:106 -#: ../../inventory/settings/products/variants.rst:111 -msgid "Size: S, M, L, XL" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:97 -msgid "In such a use case, you could create 1 template with three dimensions of variants (Layout, T-Shirts, Polos). But, it's recommended to create two different product templates as T-shirts may highly differ from polos or shirts and customer expect to see these as two different products in the e-Commerce:" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:103 -msgid "Product Template: T-shirt" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:108 -msgid "Product Template: Polos" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:117 -msgid "Activate the variant feature" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:119 -msgid "Before you can use product variants, you must first activate the product variants in the settings. To do so, you must go to the Sales app. In the menu :menuselection:`Configuration --> Settings`, locate the **Products Variants** line, and tick the option **Products can have several attributes**, then click on **Apply**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:129 -msgid "Creating products with variants" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:131 -msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, :menuselection:`Sales --> Products`. It is also accessible from the Purchase and inventory modules." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:135 -msgid "Now, click on the product you wish to add variants to." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:137 -msgid "In the product page, a new tab called Variants has appeared. The number in purple written on top is the number of variants this product currently has. To add new variants, click on the tile. In the new window, click on **Create**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:142 -msgid "In **Attributes**, click on the rolldown menu and select the type of variance you wish to add. If the variant does not yet exist, you can create it on the fly by clicking on Create and edit…" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:149 -msgid "In the Attributes window, the **Value** field is the description of the attribute such as Green, Plastic or 32GB. The **Attribute** field is the type of variant such as Color, Material or Memory." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:156 -msgid "You can add a cost for the variant on the fly by adding it in the **Attribute Price Extra** field, or choose to modify it later. Click on **Save**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:160 -msgid "You can also add a different barcode and internal reference to the variant." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:163 -msgid "When you have entered all the specifications of the variant, click on **Save**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:167 -msgid "Managing Product Variants" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:172 -msgid "The examples below are all based on this product template that has two variant attributes :" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:175 -msgid "T-Shirt B&C" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:177 -msgid "Color: Red, Blue, White" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:179 -msgid "Size: S, M, L, XL, XXL" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:182 -msgid "Managing combination possibilities" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:184 -msgid "By default, with the above product template, you get 15 different products (3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, you can deactivate the white product variant." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:188 -msgid "To do this, click on the **Variants** button, select the XXL, White T-shirt. From the product form, uncheck the **Active** box of the T-shirt White, XXL." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:197 -msgid "That deactivating a product is different than having an inventory of 0." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:200 -msgid "Setting a price per variant" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:202 -msgid "You can add a cost over the main price for some of the variants of a product." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:205 -msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, open :menuselection:`Sales --> Products` and click on the product you want to modify. Click on the **Variant Prices** button to access the list of variant values." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:213 -msgid "Click on the variant name you wish to add a value to, to make the 3 fields editable. In the **Attribute Price Extra** field, add the cost of the variant that will be added to the original price." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:220 -msgid "When you have entered all the extra values, click on **Save**." -msgstr "" - -#: ../../inventory/settings/products/variants.rst:226 -msgid "Accounting Memento: Details of Journal Entries" -msgstr "" - -#: ../../inventory/settings/products/variants.rst:227 -msgid "Process Overview: From Billing to Payment Orders" -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3 -msgid "What is the difference between warehouses and locations?" -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:5 -msgid "In Odoo, a **Warehouse** is the actual building/place in which your items are stocked. You can setup multiple warehouses and create moves between warehouses." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:9 -msgid "A **Location**, is a specific space within your warehouse. It can be considered as a sublocation of your warehouse, as a shelf, a floor, an aisle, etc. Therefore, a location is part of one warehouse only and it is not possible to link one location to multiple warehouses. You can configure as much locations as you need under one warehouse." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:15 -msgid "There are 3 types of locations:" -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:17 -msgid "The **Physical Locations** are internal locations that are part of the warehouses for which you are the owner. They can be the loading and unloading area of your warehouse, a shelf or a department, etc." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:21 -msgid "The **Partner Locations** are spaces within a customer and/or vendor's warehouse. They work the same way as Physical Locations with the only difference being that you are not the owner of the warehouse." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:25 -msgid "The **Virtual Locations** are places that do not exist, but in which products can be placed when they are not physically in an inventory yet (or anymore). They come in handy when you want to place lost products out of your stock (in the **Inventory loss**), or when you want to take into account products that are on their way to your warehouse (**Procurements**)." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:31 -msgid "In Odoo, locations are structured hierarchically. You can structure your locations as a tree, dependent on a parent-child relationship. This gives you more detailed levels of analysis of your stock operations and the organization of your warehouses." -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:37 -#: ../../inventory/settings/warehouses/location_creation.rst:44 -msgid ":doc:`warehouse_creation`" -msgstr "" - -#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:38 -#: ../../inventory/settings/warehouses/warehouse_creation.rst:48 -msgid ":doc:`location_creation`" -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:3 -msgid "How to create a new location?" -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:9 -msgid "Creating a new location" -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:11 -msgid "In order to be able to create new locations, you must allow the system to manage multiple locations. In the **Inventory** module, open the menu :menuselection:`Configuration --> Settings`. In the **Location & Warehouse** section, tick the **Manage several locations per warehouse** box, then click on **Apply**." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:20 -msgid "In the **Inventory** module, open :menuselection:`Configuration --> Warehouse Management --> Locations` In the Locations window, click on **Create**." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:24 -msgid "Type the name of the location in the **Location Name** field, and select the **Parent Location** in the list. The parent location can be a physical, partner or virtual location, and you can add as many sub-locations as needed to a location." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:29 -msgid "You can also fill in the **Additional Information** fields and add a note to describe your location." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:35 -msgid "When you are finished, click on **Save**." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:38 -msgid "A warehouse also corresponds to a location. As the locations are hierarchical, Odoo will create the parent location of the warehouse, containing all the sublocations in it." -msgstr "" - -#: ../../inventory/settings/warehouses/location_creation.rst:43 -#: ../../inventory/settings/warehouses/warehouse_creation.rst:47 -msgid ":doc:`difference_warehouse_location`" -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:3 -msgid "How to create a new warehouse?" -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:11 -msgid "In order to be able to create a new warehouse, you must allow the system to manage multiple locations. In the **Inventory** module, open the menu :menuselection:`Settings --> Configuration`. In the **Location & Warehouse** section, tick the **Manage several locations per warehouse** box, then click on **apply**." -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:20 -msgid "Open the menu :menuselection:`Configuration --> Warehouse Management --> Warehouses`" -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:22 -msgid "In the warehouses screen, click on **Create**. A new screen appears, with 3 fields :" -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:25 -msgid "In **Warehouse Name**, insert the full name of the warehouse." -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:27 -msgid "In the **Short Name** field, insert a 5-characters code for your warehouse. Keep in mind that this code is the one that will appear in the lists, so make sure you choose a name that is easy to understand and easy to enter." -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:32 -msgid "In the **Address** field, you can select an existing company or create one on-the-go. Therefore, the address of your warehouse will be the same as the one of the company you selected. You can also leave this field empty and edit it afterwards." -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:40 -msgid "Click on **Save** to finish configuring your new warehouse." -msgstr "" - -#: ../../inventory/settings/warehouses/warehouse_creation.rst:43 -msgid "When you create a warehouse, the system will create the necessary picking types and main child locations for this main location in the background." +#: ../../inventory/shipping.rst:3 +msgid "Shipping" msgstr "" #: ../../inventory/shipping/operation.rst:3 @@ -5386,6 +4235,11 @@ msgstr "" msgid "In the **Inventory** module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" msgstr "" +#: ../../inventory/shipping/operation/labels.rst:27 +#: ../../inventory/shipping/setup/third_party_shipper.rst:26 +msgid "Then click on **Apply**." +msgstr "" + #: ../../inventory/shipping/operation/labels.rst:30 #: ../../inventory/shipping/setup/delivery_method.rst:34 #: ../../inventory/shipping/setup/third_party_shipper.rst:33 @@ -5439,11 +4293,6 @@ msgstr "" msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." msgstr "" -#: ../../inventory/shipping/operation/labels.rst:68 -#: ../../inventory/shipping/setup/third_party_shipper.rst:90 -msgid "Product configuration" -msgstr "" - #: ../../inventory/shipping/operation/labels.rst:70 #: ../../inventory/shipping/setup/third_party_shipper.rst:92 msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." @@ -5606,6 +4455,10 @@ msgstr "" msgid "You can integrate Odoo with external shippers in order to compute the real price and packagings, and handle the printing the shipping labels. See :doc:`third_party_shipper`" msgstr "" +#: ../../inventory/shipping/setup/delivery_method.rst:74 +msgid "Delivery process" +msgstr "" + #: ../../inventory/shipping/setup/delivery_method.rst:82 msgid "You can now choose the **Delivery Method** on your sale order. If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product." msgstr "" diff --git a/locale/sources/iot.pot b/locale/sources/iot.pot index 1588d6a2d..cf1b66a5a 100644 --- a/locale/sources/iot.pot +++ b/locale/sources/iot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,315 +20,582 @@ msgstr "" msgid "Internet of Things (IoT)" msgstr "" -#: ../../iot/connect.rst:3 +#: ../../iot/config.rst:3 +msgid "Configuration" +msgstr "" + +#: ../../iot/config/connect.rst:3 msgid "Connect an IoT Box to your database" msgstr "" -#: ../../iot/connect.rst:5 +#: ../../iot/config/connect.rst:5 msgid "Install the Internet of Things (IoT) App on your Odoo Database." msgstr "" -#: ../../iot/connect.rst:10 +#: ../../iot/config/connect.rst:10 msgid "Go in the IoT App and click on Connect on the IoT Boxes page." msgstr "" -#: ../../iot/connect.rst:15 +#: ../../iot/config/connect.rst:15 msgid "Follow the steps to connect your IoT Box." msgstr "" -#: ../../iot/connect.rst:21 +#: ../../iot/config/connect.rst:21 msgid "Ethernet Connection" msgstr "" -#: ../../iot/connect.rst:23 +#: ../../iot/config/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 +#: ../../iot/config/connect.rst:26 msgid "Power on the IoT Box." msgstr "" -#: ../../iot/connect.rst:28 +#: ../../iot/config/connect.rst:28 msgid "Then click on the Scan button." msgstr "" -#: ../../iot/connect.rst:34 +#: ../../iot/config/connect.rst:34 msgid "WiFi Connection" msgstr "" -#: ../../iot/connect.rst:36 +#: ../../iot/config/connect.rst:36 msgid "Power on the IoT Box" msgstr "" -#: ../../iot/connect.rst:38 +#: ../../iot/config/connect.rst:38 msgid "Copy the token" msgstr "" -#: ../../iot/connect.rst:43 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/connect.rst:70 msgid "You should now see the IoT Box." msgstr "" -#: ../../iot/connect.rst:76 +#: ../../iot/config/connect.rst:76 msgid "IoT Box Schema" msgstr "" -#: ../../iot/flash_sdcard.rst:3 +#: ../../iot/config/flash_sdcard.rst:3 msgid "Flashing your SD Card" msgstr "" -#: ../../iot/flash_sdcard.rst:5 +#: ../../iot/config/flash_sdcard.rst:5 msgid "In some case, you may need to reflash your IoT Box’s SD Card to benefit from our latest updates." msgstr "" -#: ../../iot/flash_sdcard.rst:9 +#: ../../iot/config/flash_sdcard.rst:9 msgid "Updating your SD Card with Etcher" msgstr "" -#: ../../iot/flash_sdcard.rst:11 +#: ../../iot/config/flash_sdcard.rst:11 msgid "Go to Balena’s website and download `Etcher `__, It’s a free and open-source utility used for burning image files. Install and launch it." msgstr "" -#: ../../iot/flash_sdcard.rst:15 +#: ../../iot/config/flash_sdcard.rst:15 msgid "Now, download the latest image `here `__, and extract it from the zip file. Then, open *Etcher* and select the image. Select the drive to flash (where your SD Card is) and click on *Flash*!." msgstr "" -#: ../../iot/flash_sdcard.rst:19 +#: ../../iot/config/flash_sdcard.rst:19 msgid "Now, your image will be automatically updated. You just have to wait 5 minutes for it to finish." msgstr "" -#: ../../iot/iot_notfound.rst:3 +#: ../../iot/config/iot_notfound.rst:3 msgid "IoT Box not found" msgstr "" -#: ../../iot/iot_notfound.rst:5 +#: ../../iot/config/iot_notfound.rst:5 msgid "When using your IoT Box, a common issue you might encounter is that your box is not found on your database. Fortunately, there are a few easy steps you can follow to find your IoT box." msgstr "" -#: ../../iot/iot_notfound.rst:10 +#: ../../iot/config/iot_notfound.rst:10 msgid "HTTPS Issues" msgstr "" -#: ../../iot/iot_notfound.rst:12 +#: ../../iot/config/iot_notfound.rst:12 msgid "Your IoT Box is not found? You probably have https issues!" msgstr "" -#: ../../iot/iot_notfound.rst:14 +#: ../../iot/config/iot_notfound.rst:14 msgid "To check it, go to your database and verify if your database address starts with an https (like https://www.odoo.com). If this is the case, then you may have problems with your IoT Box image. It should be version 18.12 or later." msgstr "" -#: ../../iot/iot_notfound.rst:19 +#: ../../iot/config/iot_notfound.rst:19 msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here `__)." msgstr "" -#: ../../iot/iot_notfound.rst:23 +#: ../../iot/config/iot_notfound.rst:23 msgid "You can find the documentation about SD card flashing here (`here `__)." msgstr "" -#: ../../iot/pos.rst:3 +#: ../../iot/config/pos.rst:3 msgid "Use the IoT Box for the PoS" msgstr "" -#: ../../iot/pos.rst:9 +#: ../../iot/config/pos.rst:9 msgid "Prerequisites" msgstr "" -#: ../../iot/pos.rst:11 +#: ../../iot/config/pos.rst:11 msgid "Before starting, make sure you have the following:" msgstr "" -#: ../../iot/pos.rst:13 +#: ../../iot/config/pos.rst:13 msgid "An IoT Box" msgstr "" -#: ../../iot/pos.rst:15 +#: ../../iot/config/pos.rst:15 msgid "A 2A Power adapter with pi 3 b+ 2.5 A" msgstr "" -#: ../../iot/pos.rst:17 +#: ../../iot/config/pos.rst:17 msgid "A computer or tablet with an up-to-date web browser" msgstr "" -#: ../../iot/pos.rst:19 +#: ../../iot/config/pos.rst:19 msgid "A running SaaS or Odoo instance with the Point of Sale and IoT apps installed" msgstr "" -#: ../../iot/pos.rst:22 +#: ../../iot/config/pos.rst:22 msgid "A local network setup with DHCP (this is the default setting)" msgstr "" -#: ../../iot/pos.rst:24 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:28 msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner" msgstr "" -#: ../../iot/pos.rst:30 +#: ../../iot/config/pos.rst:30 msgid "An Epson compatible cash drawer" msgstr "" -#: ../../iot/pos.rst:32 +#: ../../iot/config/pos.rst:32 msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)" msgstr "" -#: ../../iot/pos.rst:35 +#: ../../iot/config/pos.rst:35 msgid "Set Up" msgstr "" -#: ../../iot/pos.rst:37 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:44 msgid "Then, you have to connect the peripheral devices to your IoT Box." msgstr "" -#: ../../iot/pos.rst:46 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:50 msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on." msgstr "" -#: ../../iot/pos.rst:53 +#: ../../iot/config/pos.rst:53 msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable." msgstr "" -#: ../../iot/pos.rst:56 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:62 msgid "**Scale**: Connect your scale and power it on." msgstr "" -#: ../../iot/pos.rst:64 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:77 msgid "Set up is done, you can launch a new PoS Session." msgstr "" -#: ../../iot/pos.rst:80 +#: ../../iot/config/pos.rst:80 msgid "Troubleshoot" msgstr "" -#: ../../iot/pos.rst:83 +#: ../../iot/config/pos.rst:83 msgid "The PoS cannot connect to the IoT Box" msgstr "" -#: ../../iot/pos.rst:85 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:106 msgid "Make sure that the POS is not loaded over HTTPS." msgstr "" -#: ../../iot/pos.rst:108 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:113 msgid "The Barcode Scanner is not working" msgstr "" -#: ../../iot/pos.rst:115 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:134 msgid "The Barcode Scanner is not working reliably" msgstr "" -#: ../../iot/pos.rst:136 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:140 msgid "Printing the receipt takes too much time" msgstr "" -#: ../../iot/pos.rst:142 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:148 msgid "Some characters are not correctly printed on the receipt" msgstr "" -#: ../../iot/pos.rst:150 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:155 msgid "The printer is offline" msgstr "" -#: ../../iot/pos.rst:157 +#: ../../iot/config/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 +#: ../../iot/config/pos.rst:162 msgid "The cashdrawer does not open" msgstr "" -#: ../../iot/pos.rst:164 +#: ../../iot/config/pos.rst:164 msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration." msgstr "" +#: ../../iot/devices.rst:3 +msgid "Devices" +msgstr "" + +#: ../../iot/devices/camera.rst:3 +msgid "Connect a Camera" +msgstr "" + +#: ../../iot/devices/camera.rst:5 +msgid "When using your *IoT Box* in Odoo, you could need to use a camera. As it can be done in a few steps, this device is really easy to configure. Then, you can use it in your manufacturing process and link it to a control point. Doing so will allow you to take pictures when you reach the chosen quality control point." +msgstr "" + +#: ../../iot/devices/camera.rst:12 +#: ../../iot/devices/footswitch.rst:13 +#: ../../iot/devices/printer.rst:11 +msgid "Connection" +msgstr "" + +#: ../../iot/devices/camera.rst:14 +msgid "To connect the camera to the *IoT Box*, simply combine the two by cable." +msgstr "" + +#: ../../iot/devices/camera.rst:18 +msgid "In some cases, a serial to USB adapter could be needed." +msgstr "" + +#: ../../iot/devices/camera.rst:20 +msgid "If your camera is a `*supported one* `__, there is no need to set up anything as it will be detected as soon as it is connected." +msgstr "" + +#: ../../iot/devices/camera.rst:27 +msgid "In some cases, you could need to restart the box and download your camera’s drivers from the box. To do so, go to your *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers." +msgstr "" + +#: ../../iot/devices/camera.rst:35 +msgid "Link a Camera to a Quality Control Point" +msgstr "" + +#: ../../iot/devices/camera.rst:38 +#: ../../iot/devices/measurement_tool.rst:42 +msgid "With the Manufacturing app" +msgstr "" + +#: ../../iot/devices/camera.rst:40 +msgid "In your *Quality app*, you can setup the device on a *Quality Control Point*. Go to the *Control Points* menu, under *Quality Control* and open the control point you want to link with the camera." +msgstr "" + +#: ../../iot/devices/camera.rst:44 +msgid "Now, you can edit the control point and select the device from the dropdown list. Now, hit save." +msgstr "" + +#: ../../iot/devices/camera.rst:50 +msgid "Then, your camera can be used with the picked *Control Point*. During the manufacturing process, reaching the *Quality Control Point* you chose before will allow you to take a picture." +msgstr "" + +#: ../../iot/devices/footswitch.rst:3 +msgid "Connect a Footswitch" +msgstr "" + +#: ../../iot/devices/footswitch.rst:5 +msgid "When working, it is always better to have your two hands available. Using Odoo’s *IoT Box* and a footswitch will allow it." +msgstr "" + +#: ../../iot/devices/footswitch.rst:8 +msgid "In fact, you will be able to go from one screen to another by using your foot and the footswitch. Really convenient, it can be configured in a few steps." +msgstr "" + +#: ../../iot/devices/footswitch.rst:15 +msgid "Connecting the footswitch to the *IoT Box* is easy, you just have to combine the two by cable." +msgstr "" + +#: ../../iot/devices/footswitch.rst:19 +msgid "In some cases, a serial to USB adapter may be needed." +msgstr "" + +#: ../../iot/devices/footswitch.rst:21 +msgid "If your footswitch is a `supported one `__, there is no need to set up anything since it will be automatically detected when connected." +msgstr "" + +#: ../../iot/devices/footswitch.rst:28 +msgid "If it is not a supported one, you may need to restart the box and download your footswitch’s drivers from the box. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers." +msgstr "" + +#: ../../iot/devices/footswitch.rst:37 +msgid "Link a Footswitch to a Workcenter" +msgstr "" + +#: ../../iot/devices/footswitch.rst:39 +msgid "To link the footswitch to an action, it needs to be configured on a workcenter. Go to the workcenter you want to use the footswitch in and add the device in the *IoT Triggers* tab. Then, you can link it to an action and also add a key to trigger it." +msgstr "" + +#: ../../iot/devices/footswitch.rst:47 +msgid "Note that the one that is first in the list will be chosen. So, the order matters! In the picture above, using the footswitch will, for example, automatically skip the current part of the process you work on." +msgstr "" + +#: ../../iot/devices/footswitch.rst:52 +msgid "When you are on the work order screen, a status button indicates if you are correctly connected to the footswitch." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:3 +msgid "Connect a Measurement Tool" +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:5 +msgid "With Odoo’s *IoT Box*, it is possible to connect measurement tools to your database. Find the list of supported devices here: `Supported devices `__,." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:10 +msgid "Connect in USB" +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:12 +msgid "To add a device connected by USB, just plug the USB cable in the *IoT Box*, restart the Box and the device should appear in your Odoo database." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:19 +msgid "If the device is not found, make sure the drivers have well been loaded on your IoT Box. For this, connect to the *IoT Box Homepage* and click on load drivers." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:27 +msgid "Connect in Bluetooth" +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:29 +msgid "Activate the Bluetooth on your device (see your device manual for further explanation) and the IoT Box will automatically try to connect to the device." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:33 +msgid "Here is an example of what it should look like:" +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:39 +msgid "Link a measurement tool to a quality control point" +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:44 +msgid "In your *Quality app*, you can setup a device on your *Quality Control Points*. To do so, go to the *Control Points* menu, under *Quality Control* and open the control point to which you want to assign a measurement tool." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:49 +msgid "Now, you can edit the control point and choose the device from the dropdown list. Then, hit save." +msgstr "" + +#: ../../iot/devices/measurement_tool.rst:55 +msgid "Now, your measurement tool is linked to the chosen *Control Point*. The value, which needs to be changed manually, will be automatically updated while the tool is being used." +msgstr "" + +#: ../../iot/devices/printer.rst:3 +msgid "Connect a Printer" +msgstr "" + +#: ../../iot/devices/printer.rst:5 +msgid "When using your *IoT Box* in Odoo, you could need to use a printer. Doing so is easy and convenient as it can be done in a few steps. Then, you can use it to print receipts, orders or even reports in different Odoo apps." +msgstr "" + +#: ../../iot/devices/printer.rst:13 +msgid "To connect the printer to the *IoT Box*, you just have to combine the two by cable." +msgstr "" + +#: ../../iot/devices/printer.rst:17 +msgid "Sometimes, a serial to USB adapter may be needed." +msgstr "" + +#: ../../iot/devices/printer.rst:19 +msgid "If your printer is a `supported one `__, there is no need to set up anything because it will be automatically detected as soon as it is connected." +msgstr "" + +#: ../../iot/devices/printer.rst:24 +msgid "The printer can take up to two minutes to appear in your devices list." +msgstr "" + +#: ../../iot/devices/printer.rst:29 +msgid "In some cases, you may need to restart the box and download your printer’s drivers from the box. To do so, go to the *IoT Box Home Page* and click on *drivers list*. Then, click on load drivers." +msgstr "" + +#: ../../iot/devices/printer.rst:37 +msgid "Link the Printer" +msgstr "" + +#: ../../iot/devices/printer.rst:40 +msgid "To Work Orders" +msgstr "" + +#: ../../iot/devices/printer.rst:42 +msgid "You can link *Work Orders* to printers via a *Quality Control Point* to print labels for manufactured products." +msgstr "" + +#: ../../iot/devices/printer.rst:45 +msgid "To do so, you need to create a *Quality Control Point* from the *Quality* app. Then, you can select the correct manufacturing operation and the work order operation. In type, choose *Print Label* and hit save." +msgstr "" + +#: ../../iot/devices/printer.rst:53 +msgid "Now, each time you reach the quality control point for the chosen product, a *Print Label* button will appear." +msgstr "" + +#: ../../iot/devices/printer.rst:60 +msgid "To Reports" +msgstr "" + +#: ../../iot/devices/printer.rst:62 +msgid "You can also link a type of report to a certain printer. In the *IoT* app, go to the *Devices* menu and select the printer you want to set up." +msgstr "" + +#: ../../iot/devices/printer.rst:69 +msgid "Now, go to the *Printer Reports* tab." +msgstr "" + +#: ../../iot/devices/printer.rst:74 +msgid "Hit edit and then, click on *Add a line*. In the window that shows up, check all the types of reports that should be linked to this printer. Click on select and save." +msgstr "" + +#: ../../iot/devices/printer.rst:81 +msgid "Now, each time you click on *Print* in the control panel, instead of downloading a PDF, it will send it to the selected printer and automatically print it." +msgstr "" + +#: ../../iot/devices/printer.rst:86 +msgid "Print Receipts from the PoS" +msgstr "" + +#: ../../iot/devices/printer.rst:88 +msgid "You can link a printer to your *Point of Sale* app so you can print receipts directly from your *PoS*." +msgstr "" + +#: ../../iot/devices/printer.rst:91 +msgid "Doing so is really easy. Go to your *Point of Sale* app and open your *PoS* settings, under *Configuration*. There, click on *Edit* and check the *IoT Box* feature. Then, enable the *Receipt Printer*." +msgstr "" + +#: ../../iot/devices/printer.rst:98 +msgid "Now, on your *PoS* view, you will be able to print different kinds of tickets: **receipts**, **sale details** and **bills**." +msgstr "" + +#: ../../iot/devices/printer.rst:101 +msgid "For the receipt, it will be printed once the order is validated. The process is automated when you enable the feature in your *PoS*." +msgstr "" + +#: ../../iot/devices/printer.rst:104 +msgid "Sales details can be printed by clicking on the printer icon on the navbar at the top of the *PoS*. It will print the details of the sales of the current day." +msgstr "" + +#: ../../iot/devices/printer.rst:111 +msgid "As for the bill, it is only available in restaurant mode. In your restaurant settings, activate bills and a *Bill* button will appear in the left panel. Click on it and it will print the bill." +msgstr "" + +#: ../../iot/devices/printer.rst:119 +msgid "Print Orders in the kitchen" +msgstr "" + +#: ../../iot/devices/printer.rst:121 +msgid "In restaurant mode, you can send order tickets to the kitchen." +msgstr "" + +#: ../../iot/devices/printer.rst:123 +msgid "To do so, go to the *PoS* app and open your *PoS* settings. Then, tick *Order Printer*." +msgstr "" + +#: ../../iot/devices/printer.rst:129 +msgid "Now, go to the *Printers* menu. Hit create and select the *IoT Box* with all the categories of product that should be printed in the *Printer Product Categories* field." +msgstr "" + +#: ../../iot/devices/printer.rst:136 +msgid "In the *PoS*, when you add or remove a product from one of the selected categories, the button *Order* will be green. If you click on it, a ticket will be printed." +msgstr "" + diff --git a/locale/sources/manufacturing.pot b/locale/sources/manufacturing.pot index 639e4b05d..051dbe132 100644 --- a/locale/sources/manufacturing.pot +++ b/locale/sources/manufacturing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -509,118 +509,106 @@ msgid "Go to the *Manufacturing app > Configuration > Settings* and tick the box msgstr "" #: ../../manufacturing/management/subcontracting.rst:17 -msgid "You can now define subcontractors contacts. When you purchase or receive products from a contact of type subcontractor, the correct stock moves are created to represent the subcontracting of the production." +msgid "You can now define subcontracted *Bill of Materials*. Therefore, you need to go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. In this *BoM*, list the components which will be used by the subcontractor to manufacture the subcontracted finished product. Specify that the *BoM* type is *Subcontracting*." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:25 -msgid "You can set the subcontractor as a vendor in case you plan to buy him the subcontracted products via purchase orders." -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:28 -msgid "The next step is to create a *Bill of Material* of type *subcontracted*. In this *BoM*, list the components you need to supply to the subcontractor." -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:35 +#: ../../manufacturing/management/subcontracting.rst:22 msgid "You can also define subcontractors on the BoM." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:37 +#: ../../manufacturing/management/subcontracting.rst:24 msgid "If no subcontractor is set, the BoM can be used by any subcontractor" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:39 +#: ../../manufacturing/management/subcontracting.rst:26 msgid "If some are set, the BoM can only be used for those subcontractors" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:45 +#: ../../manufacturing/management/subcontracting.rst:32 msgid "Receive or buy a subcontracted product" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:47 +#: ../../manufacturing/management/subcontracting.rst:34 msgid "You have two options to trigger the subcontracting of a product:" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:50 -msgid "**Option A**: You can buy the subcontracted product from your" +#: ../../manufacturing/management/subcontracting.rst:36 +msgid "**Option A**: You can buy the subcontracted product from your subcontractor" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:50 -msgid "subcontractor" -msgstr "" - -#: ../../manufacturing/management/subcontracting.rst:52 +#: ../../manufacturing/management/subcontracting.rst:38 msgid "**Option B**: You can directly receive the subcontracted product" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:54 +#: ../../manufacturing/management/subcontracting.rst:40 msgid "Let’s start with option A (option B is just a simpler version of it)." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:56 +#: ../../manufacturing/management/subcontracting.rst:42 msgid "Create a new purchase order. The vendor must be a subcontractor. The unit price should be the cost you are paying to the subcontractor for the subcontracting (thus, it’s not necessarily the total cost of the subcontracted product)." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:64 +#: ../../manufacturing/management/subcontracting.rst:50 msgid "The validation of the purchase order automatically creates the receipt. Whenever you receive the product, you can validate the receipt. The following stock moves are created:" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:68 +#: ../../manufacturing/management/subcontracting.rst:54 msgid "For the components" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:70 +#: ../../manufacturing/management/subcontracting.rst:56 msgid "From Subcontracting To Production" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:72 +#: ../../manufacturing/management/subcontracting.rst:58 msgid "For the subcontracted product" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:74 +#: ../../manufacturing/management/subcontracting.rst:60 msgid "From Production to Subcontracting" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:76 +#: ../../manufacturing/management/subcontracting.rst:62 msgid "From Subcontracting to Stock" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:78 +#: ../../manufacturing/management/subcontracting.rst:64 msgid "The *Subcontracting Location* represents the place where the products are at your subcontractor’s warehouse. It is configured as an internal location, the components that are sent to the subcontractor are still valued in your stock." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:83 +#: ../../manufacturing/management/subcontracting.rst:69 msgid "For option B, you can simply create the receipt manually with a partner of type subcontractor defined on it." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:87 +#: ../../manufacturing/management/subcontracting.rst:73 msgid "Resupply the subcontractor with the components" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:89 +#: ../../manufacturing/management/subcontracting.rst:75 msgid "There are 3 ways to manage the resupply of your subcontractor with the components:" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:94 +#: ../../manufacturing/management/subcontracting.rst:80 msgid "**Manually**: You create a delivery order in which you set the" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:93 +#: ../../manufacturing/management/subcontracting.rst:79 msgid "subcontractor as a partner and you choose the components to deliver." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:103 +#: ../../manufacturing/management/subcontracting.rst:89 msgid "**With reordering rules**: You can define a *reordering rule*" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:100 +#: ../../manufacturing/management/subcontracting.rst:86 msgid "on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created." msgstr "" -#: ../../manufacturing/management/subcontracting.rst:111 +#: ../../manufacturing/management/subcontracting.rst:97 msgid "**On order**: You can also deliver the components to your" msgstr "" -#: ../../manufacturing/management/subcontracting.rst:109 +#: ../../manufacturing/management/subcontracting.rst:95 msgid "subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components." msgstr "" @@ -720,63 +708,47 @@ msgstr "" msgid "The cells, which are part of the *To replenish* line, can take different colors depending on the situation:" msgstr "" +#: ../../manufacturing/management/use_mps.rst:88 +msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." +msgstr "" + #: ../../manufacturing/management/use_mps.rst:90 -msgid "**Green**: quantity of products which should be replenished to" +msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." msgstr "" -#: ../../manufacturing/management/use_mps.rst:89 -msgid "reach the expected safety stock considering the demand forecast and the indirect demand forecast." +#: ../../manufacturing/management/use_mps.rst:92 +msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." msgstr "" -#: ../../manufacturing/management/use_mps.rst:93 -msgid "**Grey**: replenishment order has already been generated, and its" -msgstr "" - -#: ../../manufacturing/management/use_mps.rst:93 -msgid "quantity still matches current data." +#: ../../manufacturing/management/use_mps.rst:94 +msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." msgstr "" #: ../../manufacturing/management/use_mps.rst:96 -msgid "**Red**: replenishment order has already been generated, and its" -msgstr "" - -#: ../../manufacturing/management/use_mps.rst:96 -msgid "quantity was too high considering current data." -msgstr "" - -#: ../../manufacturing/management/use_mps.rst:99 -msgid "**Orange**: replenishment order has already been generated, and" -msgstr "" - -#: ../../manufacturing/management/use_mps.rst:99 -msgid "its quantity was too low considering current data." -msgstr "" - -#: ../../manufacturing/management/use_mps.rst:101 msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." msgstr "" -#: ../../manufacturing/management/use_mps.rst:105 +#: ../../manufacturing/management/use_mps.rst:100 msgid "What if I have underestimated the demand?" msgstr "" -#: ../../manufacturing/management/use_mps.rst:107 +#: ../../manufacturing/management/use_mps.rst:102 msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment." msgstr "" -#: ../../manufacturing/management/use_mps.rst:112 +#: ../../manufacturing/management/use_mps.rst:107 msgid "What if I have overestimated the demand?" msgstr "" -#: ../../manufacturing/management/use_mps.rst:114 +#: ../../manufacturing/management/use_mps.rst:109 msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually." msgstr "" -#: ../../manufacturing/management/use_mps.rst:119 +#: ../../manufacturing/management/use_mps.rst:114 msgid "What if I wrongly added a product to the MPS?" msgstr "" -#: ../../manufacturing/management/use_mps.rst:121 +#: ../../manufacturing/management/use_mps.rst:116 msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." msgstr "" diff --git a/locale/sources/point_of_sale.pot b/locale/sources/point_of_sale.pot index 4013174a1..2c352a9c8 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 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -38,6 +38,9 @@ msgstr "" #: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9 #: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:10 #: ../../point_of_sale/overview/start.rst:22 +#: ../../point_of_sale/payment/ingenico.rst:12 +#: ../../point_of_sale/payment/six.rst:12 +#: ../../point_of_sale/payment/vantiv.rst:13 #: ../../point_of_sale/restaurant/setup.rst:9 #: ../../point_of_sale/restaurant/split.rst:10 msgid "Configuration" @@ -667,7 +670,187 @@ 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`" +msgid "To connect the PoS to hardware with an Odoo IoT Box, please see the section :doc:`../../../iot/config/connect` and :doc:`../../../iot/config/pos`" +msgstr "" + +#: ../../point_of_sale/payment.rst:3 +msgid "Payment Terminals" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:3 +msgid "Connect an Ingenico Payment Terminal to your PoS" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:5 +msgid "Connecting a payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:8 +msgid "Please note that Ingenico is currently only available for customers in the Benelux." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:15 +#: ../../point_of_sale/payment/six.rst:15 +msgid "Connect a Payment Terminal" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:17 +msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation `__." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:22 +msgid "Once the IoT Box is up and running, you’ll need to link your payment terminal to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:31 +msgid "Configure the Lane/5000 for Ingenico BENELUX" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:33 +msgid "Click on the F button of the terminal, then go in the *PoS Menu* > settings menu and enter the settings password." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:36 +msgid "Now, click on connexion change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:45 +msgid "Configure the payment method" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:47 +msgid "First, go in the general settings of the POS app, and activate the Ingenico setting." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:53 +msgid "Go back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:62 +msgid "Pay with a payment terminal" +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:64 +msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:73 +msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:76 +msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connexion between the terminal and Odoo has issues." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:82 +msgid "This option will only be available if you received an error message telling you the connexion failed." +msgstr "" + +#: ../../point_of_sale/payment/ingenico.rst:85 +#: ../../point_of_sale/payment/six.rst:103 +msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:3 +msgid "Connect SIX/Worldline to your PoS" +msgstr "" + +#: ../../point_of_sale/payment/six.rst:5 +msgid "Connecting a SIX/Worldline payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:9 +msgid "Please note SIX/Worldine is currently only available for UE customers." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:17 +msgid "Connecting a SIX/Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation `__." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:22 +msgid "Once the *IoT Box* is up and running, you’ll need to link it to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:30 +msgid "Then go to your *IoT Box homepage* (accessible from the IoT Box form view in Odoo) and enter the ID of your Six payment terminal." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:36 +msgid "You should now see that the terminal is connected to your IoT Box (it takes +/- 1 min)." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:43 +msgid "The terminal should only be connected to the network with the Ethernet. Do not connect it to the IoT Box with a USB Cable." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:47 +#: ../../point_of_sale/payment/vantiv.rst:16 +msgid "Configure the Payment Method" +msgstr "" + +#: ../../point_of_sale/payment/six.rst:49 +msgid "First, go in the general settings of the POS app, and activate the SIX setting." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:55 +msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for SIX, select the payment terminal option SIX, and select your payment terminal device." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:64 +#: ../../point_of_sale/payment/vantiv.rst:40 +msgid "Pay with a Payment Terminal" +msgstr "" + +#: ../../point_of_sale/payment/six.rst:66 +msgid "In your PoS interface, at the moment of the payment, select a payment method using a payment terminal. Verify that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. If you want to cancel the payment request, click on cancel." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:74 +msgid "When the payment is done, the status will change to *Payment Successful*. You can always reverse the last transaction by clicking on *Reverse*." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:81 +msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connexion between the terminal and Odoo encounters issues." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:87 +msgid "Close your Session" +msgstr "" + +#: ../../point_of_sale/payment/six.rst:89 +msgid "At the end of the day, before closing your session, you need to send the balance of the payments to SIX. To do that, click on this button." +msgstr "" + +#: ../../point_of_sale/payment/six.rst:95 +msgid "Once the balance has been sent, the SIX shift is closed, meaning you cannot do additional operations with the SIX payment terminal (except if you reopen a shift by clicking on the user name and selecting a cashier)." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:3 +msgid "Connect a Vantiv Payment Terminal to your PoS" +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:5 +msgid "Connecting a Vantiv payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:9 +msgid "Please note MercuryPay only operates with US and Canadian banks, making this procedure only suitable for North American businesses." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:18 +msgid "First, go in the general settings of the POS app, and activate the Vantiv setting." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:24 +msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:32 +msgid "To create new Vantiv credentials, fill in your merchant ID and password, then save. Make sure the credentials you just created are selected, then save the payment method." +msgstr "" + +#: ../../point_of_sale/payment/vantiv.rst:42 +msgid "In your PoS interface, at the moment of the payment, select your Vantiv payment method and… that’s all." msgstr "" #: ../../point_of_sale/restaurant.rst:3 diff --git a/locale/sources/purchase.pot b/locale/sources/purchase.pot index 6ef2ef9bf..f2f5de878 100644 --- a/locale/sources/purchase.pot +++ b/locale/sources/purchase.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1172,7 +1172,7 @@ msgid "The replenishments will take place when the scheduler in the *Inventory* msgstr "" #: ../../purchase/replenishment/flows/setup_stock_rule.rst:33 -msgid "See also: :doc:`../../../inventory/management/misc/schedulers`" +msgid "See also: :doc:`../../../inventory/management/planning/schedulers`" msgstr "" #: ../../purchase/replenishment/flows/setup_stock_rule.rst:35 diff --git a/locale/sources/quality.pot b/locale/sources/quality.pot new file mode 100644 index 000000000..b218d37e8 --- /dev/null +++ b/locale/sources/quality.pot @@ -0,0 +1,303 @@ +# 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 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-11-20 10:20+0100\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" + +#: ../../quality.rst:5 +msgid "Quality" +msgstr "" + +#: ../../quality/alert.rst:3 +msgid "Alert" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:3 +msgid "Generate a Quality Alert from a Manufacturing Order" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:5 +msgid "Speaking of manufacturing orders, you have two different situations to consider in Odoo. Those two will result in two different processes:" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:8 +msgid "You work with a simple manufacturing flow;" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:10 +msgid "You work with a complex manufacturing flow that includes routings." +msgstr "" + +#: ../../quality/alert/alert_mo.rst:13 +msgid "Simple manufacturing flow" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:15 +msgid "If you work with simple manufacturing orders, the *Quality Alerts* will be launched from the manufacturing order itself. When manufacturing a product for which you need to process quality controls, a button *Quality Alert* will appear on the top of your manufacturing order." +msgstr "" + +#: ../../quality/alert/alert_mo.rst:23 +msgid "By clicking on the button, you can specify the quality problem that arose during the process." +msgstr "" + +#: ../../quality/alert/alert_mo.rst:29 +msgid "If one of the quality checks failed, the button will be highlighted on the document. If not, the button won’t be highlighted." +msgstr "" + +#: ../../quality/alert/alert_mo.rst:36 +#: ../../quality/checks/quality_mo.rst:50 +msgid "Manufacturing Flow with Routings" +msgstr "" + +#: ../../quality/alert/alert_mo.rst:38 +msgid "If you work with routings defined on your manufacturing orders, the quality alerts will be launched directly from the work orders on which the quality checks took place." +msgstr "" + +#: ../../quality/alert/alert_mo.rst:48 +msgid "Then, a button *Quality Alert* will be available from the work order view. When you click on the button, you can specify the quality problem that appeared during the process." +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:3 +msgid "Generate a Quality Alert from a Transfer" +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:6 +msgid "Use the Quality Alert" +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:8 +msgid "Every time you perform some *Quality Checks* on a transfer, a *Quality Alert* button appears. You can always use it. The button is automatically highlighted once you have a failed quality check for the transfer." +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:16 +msgid "If you click on that *Quality Alert* button, you can specify what was the problem with the product." +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:22 +msgid "The *Quality Alert* that is created from the transfer can be found via the button appearing on the top right corner of the transfer." +msgstr "" + +#: ../../quality/alert/alert_transfer.rst:28 +msgid "You can also access all your *Quality Alerts* via the menu, accessible under *Control*." +msgstr "" + +#: ../../quality/checks.rst:3 +msgid "Checks" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:3 +msgid "Perform Quality Checks on Manufacturing Orders" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:5 +msgid "There are two different situations to consider and that will differ in Odoo processes:" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:8 +msgid "You work with simple manufacturing flows;" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:10 +msgid "You work with complex manufacturing flows that are represented by the use of routings in Odoo." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:13 +msgid "Simple Manufacturing Flow" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:16 +#: ../../quality/checks/quality_mo.rst:53 +#: ../../quality/checks/quality_transfers.rst:6 +msgid "Create the Quality Control Point" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:18 +msgid "To create a quality control point, open the quality app and go to *Control > Control Points*. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:27 +#: ../../quality/checks/quality_mo.rst:69 +#: ../../quality/checks/quality_transfers.rst:17 +msgid "Process the Quality Check" +msgstr "" + +#: ../../quality/checks/quality_mo.rst:29 +msgid "Once your *Quality Control Point* has been created, you can create a manufacturing order for your product. Now, and before marking the manufacturing as done, you can register the *Quality Checks*." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:39 +msgid "Once you have performed your quality checks, you can find them via the *Quality Checks* button available on the manufacturing order form." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:46 +msgid "If you want to access all your quality checks, you can do this by opening the quality checks menu, under quality control." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:55 +msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to *Control > Control Points*. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:64 +msgid "Choosing the work order operation is necessary if you want the quality checks to be performed in the work orders. After that, you can choose the type of quality check." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:71 +msgid "Once your *Quality Control Point* has been configured, create a manufacturing order for your product. You have to plan it if you want to generate the necessary work orders." +msgstr "" + +#: ../../quality/checks/quality_mo.rst:78 +msgid "Now, process the work order and your quality check will appear. In this example, the quality check requests to enter the serial number of the Table Top component." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:3 +msgid "Perform Quality Checks on Transfers" +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:8 +msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to *Quality Control > Control Points > Create*. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:19 +msgid "Let’s say that we will receive a laptop. First, create a planned receipt for the product. Then, on the receipt, you will see a *Quality Checks* button that appears to proceed to the quality check you configured before." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:27 +msgid "By clicking on it, the instruction set on the quality control point will be displayed and will require the check value." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:33 +msgid "Once the quality check is done, you can find it linked to the corresponding transfer and access it by clicking on the button." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:39 +msgid "But, if the quality check failed, the stat button will appear in red (instead of green) and Odoo will suggest you to create a *Quality Alert* by highlighting the corresponding button." +msgstr "" + +#: ../../quality/checks/quality_transfers.rst:46 +msgid "The quality checks can also be found in the *Quality* application by opening the *Quality Checks* menu, under *Quality Control*." +msgstr "" + +#: ../../quality/control.rst:3 +msgid "Control" +msgstr "" + +#: ../../quality/control/control_points.rst:3 +msgid "Define Quality Control Points" +msgstr "" + +#: ../../quality/control/control_points.rst:6 +msgid "Quality Control Points" +msgstr "" + +#: ../../quality/control/control_points.rst:8 +msgid "If it is the first *Quality Control Point* that you create, know that you need to open the *Quality* app. Then, go to *Quality Control > Control Points*. Once there, you have to define the product on which the quality control will take place, as well as the operation at which it should take place." +msgstr "" + +#: ../../quality/control/control_points.rst:14 +msgid "The *Quality Control Points* can take place during transfers or during the manufacturing process of the products. If you work with routings on your *Bill of Materials*, you have to precise at which step of the manufacturing process the quality control point should be applied." +msgstr "" + +#: ../../quality/control/control_points.rst:19 +msgid "The control type defines at which frequency the quality checks should take place:" +msgstr "" + +#: ../../quality/control/control_points.rst:22 +msgid "All Operations: all the operations will generate quality checks to perform;" +msgstr "" + +#: ../../quality/control/control_points.rst:24 +msgid "Randomly: the quality checks will only be performed on x% of the operation. You must define the percentage yourself, on the control point;" +msgstr "" + +#: ../../quality/control/control_points.rst:26 +msgid "Periodically: the quality checks will be performed periodically. The periodicity is based on the period you define (once a day, once a week)." +msgstr "" + +#: ../../quality/control/control_points.rst:32 +msgid "Quality Control Point Types" +msgstr "" + +#: ../../quality/control/control_points.rst:34 +msgid "Now that the rest is configured, you need to define the type of quality check." +msgstr "" + +#: ../../quality/control/control_points.rst:38 +msgid "Some of the types are only available with the manufacturing application." +msgstr "" + +#: ../../quality/control/control_points.rst:41 +msgid "Text" +msgstr "" + +#: ../../quality/control/control_points.rst:43 +msgid "This control point type allows you to give instructions to your workers during the transfer, or the manufacturing process." +msgstr "" + +#: ../../quality/control/control_points.rst:56 +msgid "Take a Picture" +msgstr "" + +#: ../../quality/control/control_points.rst:58 +msgid "This control point type asks you to take a picture of the product in a transfer, or when manufacturing it." +msgstr "" + +#: ../../quality/control/control_points.rst:71 +msgid "Pass-Fail" +msgstr "" + +#: ../../quality/control/control_points.rst:73 +msgid "This type of control point requires that you specify if the products pass or fail a specific text. It can be applied for both transfers or manufacturing orders." +msgstr "" + +#: ../../quality/control/control_points.rst:80 +msgid "For this kind of control point type, you have the possibility to define a failure message that will give instructions to follow in case of quality check failure." +msgstr "" + +#: ../../quality/control/control_points.rst:94 +msgid "Take a Measure" +msgstr "" + +#: ../../quality/control/control_points.rst:96 +msgid "This control point type requires you to enter the product’s measurements during a transfer, or during the manufacturing process." +msgstr "" + +#: ../../quality/control/control_points.rst:102 +msgid "For this kind of control point type, you also have the possibility to define a failure message that will give instructions to the worker." +msgstr "" + +#: ../../quality/control/control_points.rst:115 +msgid "Register Consumed Materials" +msgstr "" + +#: ../../quality/control/control_points.rst:117 +msgid "This control point type requires you register the component serial/lot numbers during the manufacturing process. It is only available if you work with routings." +msgstr "" + +#: ../../quality/control/control_points.rst:128 +msgid "Register By-Products" +msgstr "" + +#: ../../quality/control/control_points.rst:130 +msgid "With this control point type, you must register the serial/lot number of the by-products that are manufactured. It is also only available with routings." +msgstr "" + +#: ../../quality/control/control_points.rst:141 +msgid "Print Label" +msgstr "" + +#: ../../quality/control/control_points.rst:143 +msgid "This control point type allows you to print labels to add to the product during the manufacturing process." +msgstr "" + diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index c70484c02..b2ae7ae74 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -749,6 +749,239 @@ msgstr "" msgid "You can do it using either the name of the related record or its ID. The ID is expected when two records have the same name. In such a case add \" / ID\" at the end of the column title (e.g. for product attributes: Product Attributes / Attribute / ID)." msgstr "" +#: ../../sales/products_prices/products/variants.rst:3 +msgid "Using product variants" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:5 +msgid "Product variants are used to manage products having different variations, like size, color, etc. It allows managing the product at the template level (for all variations) and at the variant level (specific attributes)." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:10 +msgid "As an example, a company selling t-shirts may have the following product:" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:13 +msgid "B&C T-shirt" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:15 +msgid "Sizes: S, M, L, XL, XXL" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:16 +msgid "Colors: Blue, Red, White, Black" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:18 +msgid "In this example, **B&C T-Shirt** is called the product template and **B&C T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:22 +msgid "The above example has a total of 20 different products (5 sizes x 4 colors). Each one of these products has its own inventory, sales, etc." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:26 +msgid "Impact of variants" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:28 +msgid "**Barcode**: the code and barcode is associated to a variant, not the template. Every variant may have its own barcode / SKU." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:31 +msgid "**Price**: every product variant has its own public price that is computed based on the template price ($20) with an optional extra for every variant (+$3 for color red). However, you can define pricelist rules that apply on the template or the variant." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:36 +msgid "**Inventory**: the inventory is managed by product variant. You don't own t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For information purpose, on the product template form, you get the inventory that is the sum of every variant. (but the actual inventory is computed by variant)" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:42 +msgid "**Picture**: the picture is related to the variant, every variation of a product may have its own primary picture." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:45 +msgid "**Other fields**: most of the other fields belongs to the product template. If you update them, it updates automatically all the variants. (example: Income Account, Taxes)" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:50 +msgid "Should you use variants?" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:53 +msgid "When should you use variants?" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:55 +msgid "Using variants has the following impacts:" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:57 +msgid "**eCommerce**: in your online shop, the customer will only see product templates in the catalog page. Once the visitor click on such a product, he will have options to choose amongst the variants (colors, sizes, …)" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:62 +msgid "**Manufacturing**: Using variants allows to define only one bill of material for a product template and slight variations for some of the variants. Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you create a bill of material for \"T-shirt\" and add some lines that are specific to the dimension S, and other lines specific to the color Red." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:69 +msgid "**Pricing**: The default price of a product is computed using the price of the product template and add the optional extra price on each dimension of the variant. This way, variant prices are easier to maintain since you don't have to set the price for every variant. However, it's possible to create pricelist rules to fix price per variants too." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:77 +msgid "When should you avoid using variants?" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:79 +msgid "Using variants may add a level of complexity on the way you use Odoo. You should consider using variants only if you need it to reduce the complexity of managing lots of products that are similars." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:83 +msgid "As an example, importing your initial product catalog is more complex if you use variants. You can't just import a list of products, you must import product templates and all their related variations." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:87 +msgid "In addition to that, you should also carefully select the dimensions that you manage as separate product templates and those as variants. As an example, a company having these products:" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:91 +msgid "Quality: T-Shirts, Polos, Shirts" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:93 +#: ../../sales/products_prices/products/variants.rst:105 +#: ../../sales/products_prices/products/variants.rst:110 +msgid "Color: Red, Blue" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:95 +#: ../../sales/products_prices/products/variants.rst:106 +#: ../../sales/products_prices/products/variants.rst:111 +msgid "Size: S, M, L, XL" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:97 +msgid "In such a use case, you could create 1 template with three dimensions of variants (Layout, T-Shirts, Polos). But, it's recommended to create two different product templates as T-shirts may highly differ from polos or shirts and customer expect to see these as two different products in the e-Commerce:" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:103 +msgid "Product Template: T-shirt" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:108 +msgid "Product Template: Polos" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:114 +#: ../../sales/send_quotations/quote_template.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:117 +msgid "Activate the variant feature" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:119 +msgid "Before you can use product variants, you must first activate the product variants in the settings. To do so, you must go to the Sales app. In the menu :menuselection:`Configuration --> Settings`, locate the **Products Variants** line, and tick the option **Products can have several attributes**, then click on **Apply**." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:129 +msgid "Creating products with variants" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:131 +msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, :menuselection:`Sales --> Products`. It is also accessible from the Purchase and inventory modules." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:135 +msgid "Now, click on the product you wish to add variants to." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:137 +msgid "In the product page, a new tab called Variants has appeared. The number in purple written on top is the number of variants this product currently has. To add new variants, click on the tile. In the new window, click on **Create**." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:142 +msgid "In **Attributes**, click on the rolldown menu and select the type of variance you wish to add. If the variant does not yet exist, you can create it on the fly by clicking on Create and edit…" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:149 +msgid "In the Attributes window, the **Value** field is the description of the attribute such as Green, Plastic or 32GB. The **Attribute** field is the type of variant such as Color, Material or Memory." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:156 +msgid "You can add a cost for the variant on the fly by adding it in the **Attribute Price Extra** field, or choose to modify it later. Click on **Save**." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:160 +msgid "You can also add a different barcode and internal reference to the variant." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:163 +msgid "When you have entered all the specifications of the variant, click on **Save**." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:167 +msgid "Managing Product Variants" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:170 +msgid "Introduction" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:172 +msgid "The examples below are all based on this product template that has two variant attributes :" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:175 +msgid "T-Shirt B&C" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:177 +msgid "Color: Red, Blue, White" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:179 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:182 +msgid "Managing combination possibilities" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:184 +msgid "By default, with the above product template, you get 15 different products (3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, you can deactivate the white product variant." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:188 +msgid "To do this, click on the **Variants** button, select the XXL, White T-shirt. From the product form, uncheck the **Active** box of the T-shirt White, XXL." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:197 +msgid "That deactivating a product is different than having an inventory of 0." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:200 +msgid "Setting a price per variant" +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:202 +msgid "You can add a cost over the main price for some of the variants of a product." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:205 +msgid "Once you have activated the variant option, you can add variants to your products. To do so, go to the Sales module, open :menuselection:`Sales --> Products` and click on the product you want to modify. Click on the **Variant Prices** button to access the list of variant values." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:213 +msgid "Click on the variant name you wish to add a value to, to make the 3 fields editable. In the **Attribute Price Extra** field, add the cost of the variant that will be added to the original price." +msgstr "" + +#: ../../sales/products_prices/products/variants.rst:220 +msgid "When you have entered all the extra values, click on **Save**." +msgstr "" + #: ../../sales/products_prices/taxes.rst:3 msgid "Set taxes" msgstr "" @@ -1118,10 +1351,6 @@ 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 "" diff --git a/locale/sources/sms_marketing.pot b/locale/sources/sms_marketing.pot new file mode 100644 index 000000000..abea003ad --- /dev/null +++ b/locale/sources/sms_marketing.pot @@ -0,0 +1,374 @@ +# 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 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-11-20 10:20+0100\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" + +#: ../../sms_marketing.rst:5 +msgid "SMS Marketing" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:3 +msgid "Build, send and get reports from a SMS mailing" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:5 +msgid "Why to use SMS? Using SMS Marketing as part of my communication strategies can empower me to expand my markets, considering that in some countries emails are not very used or used at all. It also helps to boost my conversion rate, as this strategy has a high open-rate percentage among people who use smartphones - people usually don’t keep unread SMSs!" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:8 +msgid "With Odoo’s SMS Marketing app you can plan, organize, schedule and keep track of your mailings with its easy to use interface." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:12 +msgid "Install the app" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:14 +msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:17 +msgid "Build an SMS mailing" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19 +msgid "Go to *SMS Marketing > Create*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24 +msgid "First, I’ll be able to specify a *subject* name that will help me to remember what the mailing is about. Under *recipients*, I’ll choose to whom I’d like the SMS to be sent. If I choose *Contact*, all my Odoo contacts (vendor, customers, etc.) will receive my SMS. From there, I can refine my recipient list with the *add filter* option. In the example below, I choose to send it to my contacts living in Belgium." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:31 +msgid "The *Mailing list* option, on the other hand, allows me to choose mailing lists I’ve created with specific contacts or people who have subscribed to my Newsletters, or both! I’m allowed to select more than one *Mailing list*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:36 +msgid "Under the *SMS Content* tab, links can be included and Odoo will automatically generate *link trackers*. Thank to those, I’ll be able to get data about those links." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:38 +msgid "On *Settings* I have the option *include opt-out link* available. If activated, the contact will be able to unsubscribe from the mailing list he’s not interested in anymore." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:43 +msgid "in the *Link Tracker* menu under *Configuration*, I can see the history of my sent links, access them and look at statistics." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:48 +msgid "Double-check that you have the phone number of your contacts saved!" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:52 +msgid "Sending my mailing" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:56 +msgid "Once I have my mailing created, I must choose when I would like it to be delivered:" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:58 +msgid "**Put in queue**: the mailing will be triggered with the next automatic run. Interesting option if I don’t mind when the triggering will happen." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:59 +msgid "**Send now**: sends the message immediately. Advised to use this option if there are not that many recipients." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:60 +msgid "**Schedule**: allows me to choose a day and time. Best option for mailings that I would like to send during a specific event, to promote an offer while it is active or to simply plan my content strategy in advance." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:61 +msgid "**Test**: allows me to send an SMS to one or multiple numbers for test purposes. Check, for example, if the link provided lands on the right page while making sure they are responsive. If sending it to multiple numbers, I must remember to use a comma between them." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:65 +msgid "Visualize reports" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:66 +msgid "On the *Reporting* menu, with just a few clicks, I am capable of applying filters, measures and adopt different layouts to do an analysis of the performance of my SMS mailings." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:71 +msgid "I can also check the price to send an SMS on your country when clicking on the *information* icon when creating a new SMS." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:76 +msgid "**Buy Credits!** In order to take advantage of the app and its features, make sure you’ve purchased credits. For more information on that access: :doc:`../sms_marketing/fqapricing`" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:3 +msgid "Contact lists and Blacklist" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:6 +msgid "Contact lists" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:7 +msgid "Creating my own list of contacts, or importing it, is useful when I want to create specific groups of people, such as the subscribers of my newsletter. It is also the best way to get started if I am coming from another system and already have built an audience. It makes the SMS distribution a lot easier." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9 +msgid "Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my *Mailing list*, and activate the option *Public* if I would like to make the mailing list accessible to my recipients in the unsubscription page to allow them to update their subscription preferences." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:12 +msgid "Once inside the list, I can again *Create* or *Import* contacts for that specific list." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:18 +msgid "History with the Log Notes" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:19 +msgid "A record of the mailings sent is kept in the chatter of the recipient (whether it is a contact or an opportunity, for example)." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:24 +msgid "This is important as I and my team can easily keep track and see a history of interactions with my contacts or prospects, granting me the ability to better understand them. Example: my sales representative can easily find out which SMS mailing promotions a customer has received or not." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:29 +msgid "Blacklist" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30 +msgid "If I’m coming from another software and have a list of clients who have already asked to be blacklisted from my news, I can import those entries in my database. For that, I’ll go to *Configuration > Phone Blacklist > Import*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:3 +msgid "Integrations and Templates" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:4 +msgid "Using SMS to reach people can be a strategy not just used for advertisement purposes but also as a reminder of events or issued invoices to your costumers, for example. As you know, one of the biggest benefits of using Odoo is the capability of the apps to be integrated. With the SMS Marketing app isn’t different!" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:9 +msgid "Organize Email Marketing and SMS campaigns" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10 +msgid "First, make sure to have the necessary feature activated. Go to the *Email Marketing app > Configuration > Settings> activate the option Mailing Campaigns*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:15 +msgid "Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* page, allowing me to have an overview of my SMS mailings and my email marketing ones." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:20 +msgid "This feature is especially useful if I have aggregated campaigns, as I have a global reporting view. In addition to that, I can create stages in my kanban view to better organize the work being done." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:26 +msgid "Sending SMSs through the Contacts app" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27 +msgid "Sending SMSs through the contact’s form is available by default in Odoo. It makes my work easier if I need to send an SMS to a specific contact, for example. For that, I’ll go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:33 +msgid "If I’d like to send a message in a batch here, I could go to *List View > select all the contacts > Action > Send SMS*." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:39 +msgid "Set up SMS Templates" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:40 +msgid "To set up *SMS Templates*, I’ll go to the *Settings* app and activate the *developer mode*. Now, back to *Settings* app, I’ll go to *Technical > Phone/SMS section > SMS Templates* and create the content I need." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:48 +msgid "Use *Dynamic Placeholders* to adapt automatically the content of the SMS to the context." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:52 +msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:" +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54 +msgid "*CRM*: send SMSs to your leads and opportunities." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55 +msgid "*Subscription*: alert customers about their subscription." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56 +msgid "*Accounting*: send payment reminders." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57 +msgid "*Marketing Automation*: automate your SMS marketing campaigns." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58 +msgid "*Inventory*: send an automatic confirmation when a delivery order is done." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59 +msgid "*Sign*: receive a validation code to verify your identity before signing a document online." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:60 +msgid "*SEPA debit payment provider*: send a verification code to your customers." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61 +msgid "*Studio*: send an SMS according to your needs by using automated actions." +msgstr "" + +#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63 +msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to `Pricing and FQA `__." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:3 +msgid "SMS Pricing and FAQ" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:6 +msgid "Pricing" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:7 +msgid "SMS Text Messaging is an In-App Purchase (IAP) service which requires prepaid credits to work. The price of an SMS depends on the destination and the length of the message. With 1 credit, I can send up to 92 SMSs." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:9 +msgid "**For more information, please consult our FAQ page**: `Odoo SMS - FAQ `_" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:11 +msgid "To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or go to *Settings > View my Services* (under *Odoo IAP*)." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:18 +msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:21 +msgid "FAQ" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:22 +msgid "**Is there an expiration time for my credits?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:24 +msgid "No, your credits won’t expire." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:26 +msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:28 +msgid "Only if that phone number supports SMS (e.g. SIP phones)." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:30 +msgid "**Do I receive an invoice to buy my credits?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:32 +msgid "Yes." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:34 +msgid "**Can the recipient answer to me?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:36 +msgid "No, it is not possible to reply to the SMS." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:38 +msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:40 +msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:42 +msgid "**Do I have a history of the sent SMSs?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:44 +msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of SMS sent is available under Settings> Activate the developer mode > Technical > SMS." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:46 +msgid "**Can I send as many SMSs I want at once?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:48 +msgid "Yes, if you have enough credits." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:50 +msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:52 +msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:54 +msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:56 +msgid "The SMS will not be delivered to that kind of number, so you won’t be charged." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:58 +msgid "**Can I identify the numbers that do not exist when I send several SMSs?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:60 +msgid "Only the ones that have an invalid format." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:62 +msgid "**How does the GDPR regulation affect this service?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:64 +msgid "Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy `__" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:66 +msgid "**How many types of SMS exist and how many characters make 1 SMS?**" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:68 +msgid "There are 2 types of SMS message:" +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:70 +msgid "*Standard* (GSM-7): contains only characters from the GSM-7 set, which can be seen in the following picture." +msgstr "" + +#: ../../sms_marketing/fqapricing.rst:75 +msgid "*Unicode*: contains at least one character that is not in the previous table. For Standard SMS the size limit is 160 characters, and for Unicode is 70. Above these limits, the content is divided into a multi-part message. The system will inform you in real-time about the number of SMS your message represents." +msgstr "" + diff --git a/locale/sources/social_marketing.pot b/locale/sources/social_marketing.pot new file mode 100644 index 000000000..7d5340249 --- /dev/null +++ b/locale/sources/social_marketing.pot @@ -0,0 +1,115 @@ +# 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 13.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2019-11-20 10:20+0100\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" + +#: ../../social_marketing.rst:5 +#: ../../social_marketing/social_marketing/social_marketing.rst:2 +msgid "Social Marketing" +msgstr "" + +#: ../../social_marketing/social_marketing.rst:3 +msgid "Advanced Topics" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:4 +msgid "One of the biggest challenges of a company is to engage efficiently with their community. Odoo Social helps you to meet your audience with the help of several supports: social media, push notifications, or live chat request." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:10 +msgid "Add your social media and create your feed" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:12 +msgid "You first need to add your social media accounts. To do that, add a Stream and choose your social media account. You’ll need to grant permissions to Odoo Social Marketing application." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:19 +msgid "Once it’s done, you’ll be redirected to your Feed and a column will be automatically added with the publications of your freshly added account. You can then add new streams to your Feed and customize your Kanban view as you like." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:28 +msgid "Adding social media accounts to your Feed will also add some KPIs on it:" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:30 +msgid "Audience: Number of followers of your channel" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:32 +msgid "Engagement: Number of times people have engaged with your posts" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:35 +msgid "Stories: Number of times people who have engaged with your channel" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:35 +msgid "have created stories on their friend’s or follower’s feed (Shares, Retweet,..)" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:37 +msgid "You can access more information by clicking on the “Insights” link: this will lead you to statistics of the selected social medium." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:41 +msgid "Publish content" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:43 +msgid "To publish content on your social media accounts or send a push notification to your subscribed users, either go to your Feed and click on New Post, or use the “Posts” menu and create it from there. Select all the accounts where you want to post your content, write your post and get an instant preview of how it will look when published." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:49 +msgid "If you select the push notifications, you’ll get some additional fields on the form that will allow you to complete the push notifications configuration and choose your segment between all your subscribed users. You can also send push notifications via the Visitors menu, as explained in the previous paragraph." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:56 +msgid "Enable push notifications on your website" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:58 +msgid "The push notifications system uses a Firebase account, configured by default. This feature allows you to send push notifications to your website’s visitors after they subscribed to it. To enable push notifications on your website, go to the Website application Settings, and configure the notifications permission request." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:67 +msgid "Once it’s done, a popup will appear to your website’s visitors, asking them to allow push notifications. As soon as they subscribe to it, you can start sending them push notifications through the Visitors menu. You can either send it individually or target a bigger segment by selecting multiple visitors in the list view (e.g. all the visitors that visited your Homepage)." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:75 +msgid "Interact with your online visitors" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:77 +msgid "You can monitor your online visits via the Visitors menu. You’ll see every visitors that landed on one of your tracked pages (you can configure your tracked pages in the Website application), online or offline. Your online visitors will be authenticated if they’re linked to a lead or an existing partner. You will be able to contact them with an email, a message sms, a push notification (if they have subscribed to it), or even send them a live chat request that they will receive on their next move on one of your tracked pages (if you installed the Live Chat application)." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:91 +msgid "Configure your own Facebook and Twitter developer accounts" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:93 +msgid "By default, the Social application is already configured with a Facebook and Twitter developer accounts but you can use your own if necessary. Activate the developer mode, go to Configuration > Settings and enter your own API keys." +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:102 +msgid "Configure your own Firebase API" +msgstr "" + +#: ../../social_marketing/social_marketing/social_marketing.rst:104 +msgid "By default, a Firebase project is running on your database so there’s no need to configure it. If you have multiple websites, every website will be linked to a different Firebase project. If you need to configure your own Firebase project, please go to :menuselection:`Website --> Configuration --> Settings` Web Push Notifications section." +msgstr "" + diff --git a/locale/sources/support.pot b/locale/sources/support.pot index 8d532d9a3..1b3b27c48 100644 --- a/locale/sources/support.pot +++ b/locale/sources/support.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 13.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-10-03 11:39+0200\n" +"POT-Creation-Date: 2019-11-20 10:20+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -510,10 +510,14 @@ msgid "Any intervention on your own servers/deployments of Odoo" msgstr "" #: ../../support/what_can_i_expect.rst:49 +msgid "Any intervention on your own third party account (Ingenico, Authorize, UPS, etc)" +msgstr "" + +#: ../../support/what_can_i_expect.rst:50 msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)" msgstr "" -#: ../../support/what_can_i_expect.rst:53 +#: ../../support/what_can_i_expect.rst:54 msgid "You can get this type of support with a `Success Pack `__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo." msgstr ""